Let’s work together
Want to discuss potential opportunities? Pick the most suitable way to contact us.
Book a call+370 5 2 780 400
info@ba.lt
A growing number of companies are seeking to modernise their business data analytics, driven by the increasing need to collect and analyse information more accurately and make data-driven decisions.
One of the common triggers for such modernisation is the replacement of outdated ERP (Enterprise Resource Planning) systems such as Dynamics AX or Dynamics NAV with newer Dynamics 365 platforms (Business Central, Finance and Operations, Supply Chain Management, etc.), following Microsoft’s discontinuation of support for older versions. This raises a key question: how should Business Intelligence (BI) systems be adapted and upgraded accordingly?
This blog post explores a real-life use case of a successfully executed BI modernisation project carried out alongside an ERP transition. It highlights common challenges, key steps, and practical solutions for building a flexible, efficient, and value-generating analytics solution.
When companies upgrade their core ERP systems, their BI solutions must be adapted to the new IT environment. The following outlines a practical project scenario with major tasks needed to successfully transition to a new ERP-supported BI environment:
Key BI modernisation tasks during ERP transition:
In larger corporate groups, old and new ERP systems may run in parallel. The BI architecture must therefore support:
ERP replacement projects typically commence first, but this does not mean BI implementation must wait until ERP deployment concludes. Two key principles apply:
The curve reflects that the contribution of the company implementing the BI modernisation is significantly greater at the beginning of the project. However, over time, the internal team of the Client becomes increasingly involved, gaining knowledge and hands-on experience. Gradually, the implementer steps back from the role of main provider, transferring responsibility to the Client’s representatives.
A clear and phased approach ensures a smooth transition from the current BI setup to the new system. A practical project may follow these steps:
We familiarise ourselves with the systems, perform data and infrastructure analysis, and prepare a detailed project plan.
We install and configure the platform according to the Medallion architecture concept.
We conduct an analysis of the data from the old ERP system.
We analyse the consolidation/integration of data from both the old and new ERP systems.
We carry out the MVP phase, during which low-priority (LOW) reports are migrated to the new BI system.
We train the Client’s internal team and provide practical knowledge. This helps to accelerate the further implementation of the solution.
We migrate high-priority (HIGH) reports and data from the old ERP system.
We integrate the new ERP data for the HIGH-priority reports with the existing ERP system.
We migrate medium-priority (MEDIUM) reports and data from the old ERP system.
We integrate the new ERP data for the MEDIUM-priority reports with the existing ERP system.
Migration, connection, and consolidation of remaining reports and data. Based on priority levels (HIGH, MEDIUM), legacy and new ERP data are connected and consolidated, and remaining reports are migrated.
The table presents the activity plan and timeline for the ERP implementation project for the years 2025–2026.
In order to transition to the Medallion architecture, it is important to emphasise that this model enables a structured and gradual improvement of data quality, as well as the expansion of the solution by integrating new data sources. The Medallion architecture helps ensure both flexibility and data quality – the key requirements for successful business analytics modernisation.
Each layer – bronze, silver, and gold – has its own specific role, which allows for a better understanding of how data is processed, analysed, and presented to the end user. Thanks to this structure, we can refer to specific models tailored to the various needs of the company – from initial data collection and processing to top-quality business analytics solutions.
The bronze layer stores all data from external sources. The table structure mirrors the structure of the source systems, along with metadata columns (such as upload date, process ID, etc.).
Main advantages of this layer:
In the silver layer, data from the bronze layer is joined, cleaned, and transformed into a unified, structured view of key business entities.
Advantages:
In the gold layer, data is transformed into read-optimised, denormalised structures (e.g., star schema models). This layer is used for specific business analytics projects: customer segmentation, product analysis, recommendations, KPI reports.
Advantages:
The Medallion model allows for a gradual increase in data quality and the expansion of the solution by integrating new sources. Using tools such as Delta Live Tables or structured stream processing tools, it is possible to create continuously updating data streams.
The modernisation of business analytics is an integral part of an ERP replacement project. By choosing the right strategy, flexible architecture, and a competent partner, it is possible to achieve significant results: save costs, accelerate implementation, and increase the value of analytics.
Would you like to know what this solution could look like in your business? Get in touch with our data analytics experts and receive a free consultation!
Want to discuss potential opportunities? Pick the most suitable way to contact us.
Book a call+370 5 2 780 400
info@ba.lt
With the EAA deadline nearing, legal expert Vaiva Masidlauskiene shares key tips, challenges and why accessibility is a smart business move.
Learn how to implement secure authentication in Progress OpenEdge using password hashing,JWT tokens, and environment variables. Step-by-step guide with ABL code examples and best practices.
Explore how Windsurf AI can support Progress OpenEdge ABL development. See real examples, benefits, and limitations of using Windsurf for error handling, code generation, and productivity gains.