Anyone who knows me knows that I can get quite excited about new technologies. Not simply because they are new, but because they solve a problem we have been dealing with in customer projects for many years. One of those challenges is data migration. Over the past few years, I have had the opportunity to support numerous upgrade and migration projects from Microsoft Dynamics NAV to Microsoft Dynamics 365 Business Central. Whether it was NAV 2009, NAV 2013, NAV 2016 or NAV 2017, the real challenge was rarely the technical upgrade itself. Almost invariably, the biggest challenge was the data.
At BC TechDays 2026 in Antwerp, Microsoft presented a new framework, the BC14 Reimplementation Tool, designed to address precisely this issue. After returning, we presented the tool internally at OTE and discussed it in detail. The more I have explored it, the more convinced I have become that this approach could play an important role in complex upgrade and migration projects in the future.
Data Migration Today Means Much More Than Copying Data
Many companies are currently facing the decision of whether to modernise their existing Microsoft Dynamics NAV solution by moving to Business Central. The first thought is often the technical migration. In my experience, however, that is now frequently the comparatively straightforward part of the project. The real complexity lies in the data. An ERP system grows alongside a company over many years. Processes change, new requirements emerge and custom extensions are introduced wherever the standard system is no longer sufficient. At some point, the ERP system no longer simply represents customers, suppliers or products. It also contains the accumulated knowledge and experience of the business. That is precisely why data migration today is much more than a traditional import.
The Real Challenge Is Particularly Evident in Food Wholesale
At OTE, we have been supporting companies in the food wholesale industry for many years. From my perspective, it is one of the most demanding sectors when it comes to ERP systems and data migration. Of course, there is the usual master data. At the same time, however, topics such as batch management, best-before dates, deposit systems, different pricing units and complex EDI processes play a central role. On top of that, there are custom extensions that have often evolved over many years and have become an indispensable part of day-to-day operations. If a company has worked with the same NAV version for ten or fifteen years, a considerable amount of its business knowledge is embedded in precisely these data structures. That is why, in my view, the goal of a migration should never be simply to copy everything one-to-one into Business Central. The far more interesting question is how this knowledge can be transferred into a modern system landscape – and how the migration can also be used as an opportunity to simplify and improve processes.
Link to: Food Wholesale ERP Solutions
A Framework That Rethinks Migration
This is exactly where Microsoft’s new Reimplementation Tool comes in. Its approach differs significantly from traditional import methods. Data is initially transferred into what are known as buffer tables. There, it can be analysed, validated, transformed or enriched before subsequently being written to the actual Business Central tables. This creates an additional layer in which data can be specifically adapted during the migration. At first, that may not sound particularly remarkable.
The longer I have looked at the concept, however, the clearer its potential has become. Instead of simply transferring data, it can already be adapted to new processes and data structures during the migration. Custom fields can be taken into account, information can be added and existing data models can be modernised. This is precisely the kind of flexibility that has often been missing in complex projects.
The Name Is Actually a Little Misleading
One thing immediately stood out to me when the tool was presented. The name BC14 Reimplementation Tool initially suggests that the framework is intended exclusively for Business Central 14. In reality, however, the name reflects the origins of the project more than its actual capabilities. The framework works with SQL data sources. This means that, in principle, it is not limited to Business Central 14. SQL databases from older Microsoft Dynamics NAV versions such as NAV 2009, NAV 2013, NAV 2015, NAV 2016 or NAV 2017 can also be used as data sources with the appropriate mapping. Even other SQL-based applications are conceivable in principle, provided their data structures are known. This is exactly what makes the tool so interesting to me. Many companies are still running older NAV versions and are now considering the move to Business Central. These are precisely the companies that could benefit from a flexible framework that not only transfers existing data, but also allows it to be transformed and modernised at the same time.
Why Repeatability Is So Convincing
There is another aspect that particularly impressed me. Anyone who has worked on larger upgrade projects knows that data migrations are rarely carried out just once. There are usually several test migrations. After each run, data is cleaned up, rules are adjusted and minor errors are corrected. With traditional approaches, many of these adjustments have to be repeated during the next test. The Reimplementation Tool takes a different approach. The transformation logic itself becomes part of the migration. This means test migrations can be repeated as often as necessary without having to make the same adjustments manually each time. This saves time, improves quality and makes the entire process much easier to trace. I see this as a significant advantage, particularly for larger projects involving multiple companies or international rollouts.
Greenfield Doesn’t Mean Starting from Zero
Microsoft positions the framework primarily for greenfield projects. I find this idea particularly interesting. After all, a greenfield project does not mean that a company is starting from zero. Quite the opposite: there are often years of experience, established processes and an enormous amount of valuable data. The real challenge is to transfer that knowledge into a modern ERP system without bringing unnecessary legacy baggage along with it. From my perspective, the Reimplementation Tool offers a very interesting approach to precisely this challenge. It provides the opportunity to select and transform data deliberately while using the migration as an opportunity to critically review existing processes. As a result, migration becomes more than a technical project. It also becomes an opportunity to prepare the ERP system for the years ahead.
Why We Are Already Exploring This Topic in Depth at OTE
New technologies only reveal their real value once they prove themselves in practice. That is why we at OTE try to explore new Microsoft developments at an early stage. Not because we want to use every new tool immediately, but because we want to understand what opportunities they could create for our customers. For me, the Reimplementation Tool falls into exactly this category. The framework is, of course, still at an early stage and will undoubtedly continue to evolve in future versions. Nevertheless, Microsoft is already demonstrating a very interesting approach to making complex data migrations considerably more structured and flexible in the future. Companies that are still using older NAV versions and are planning the move to Microsoft Dynamics 365 Business Central should, in my view, keep a close eye on this development.
My Personal Impression
Not every technical innovation is immediately exciting at first glance. Some tools only reveal their true value when you consider how they could be applied to real customer projects. For me, the Reimplementation Tool belongs in exactly this category. It will not completely replace traditional data migrations, nor will it automatically simplify every upgrade. But for companies with NAV systems that have evolved over many years, custom extensions and complex business processes – such as those we regularly support in food wholesale – I see enormous potential. Successful migrations today are no longer about copying as much data as possible. They are about intelligently transferring existing knowledge into a modern Business Central environment while taking the opportunity to improve processes for the long term. I am therefore very interested to see how this framework develops and to gain our first practical experience with it in our projects. From my perspective, there is far more potential here than the name BC14 Reimplementation Tool might initially suggest.
