How do I switch my ERP to Business Central without carrying over the old mistakes?

There is no single switch path. It depends on the source system: Dynamics NAV, AX, Infor, Sage, SAP or AS/400 each demand their own strategy. What stays common is the sequence: first clarify data foundation and processes, then migrate, then automate. Whoever reverses this sequence builds on sand.

The data side of the move in detail: Data migration to Business Central

Why is the first question not how, but from where?

Before anyone plans a project, an honest assessment belongs at the beginning: which system are you coming from, how deeply is it customised, how clean is the data grown over years? The path follows from this answer, not from a standard procedure.

• From Dynamics NAV: often an upgrade path, but with heavily customised C/AL code not a purely technical upgrade, rather a deliberate rebuild to AL.
• From Dynamics AX: not a one-to-one switch, but a product change with a deliberate decision about what comes along.
• From Infor or Sage: data migration is the real work, not the installation.
• From SAP: BC can be the more viable home in the mid-market, when S/4 would be oversized.
• From AS/400 (IBM i): cleanly replace instead of integrate, especially with undocumented legacy data.

Source: Microsoft Learn: Deployment of Dynamics 365 Business Central

Why will the new system not save your data?

The same principle holds across all of these routes: Business Central does not clean up grown errors, it makes them visible. That is why the foundation, meaning cleansed master data and clarified processes, always comes before the date.

Whoever migrates first and tidies up afterwards cements the old problems in an interface that displays them without mercy. The effect is paradoxical and regularly observed in projects: the new system is considered worse although it calculates correctly, because it processes wrong input correctly and makes it visible.

Four figures per data object are enough as a pre-check: duplicate rate, share of complete mandatory fields, share of inactive master records and the age of the last maintenance. After that you know whether the base holds, evidenced rather than assumed. This measurement takes a few days and in our experience regularly changes the project plan.

Why does senior-led make the difference?

With real complexity, experience decides which legacy process is brought back into the standard and which is kept through an extension. That trade-off cannot be delegated to a checklist, because it has to weigh the business value against the maintenance cost across many years.

The difference shows not in the concept but in the number of special paths that actually make it into the system in the end. Whoever accepts every requirement produces a system that will be a legacy system again in three years, only with a newer interface. The number of special paths in the finished system is therefore the most honest measure of the quality of the steering.

Control stays on your side, with Business Central as home. Before you settle on a route: arrange a first conversation in which we assess your source system and show the honest path for the switch.