Dynamics NAV to Business Central: Upgrade or Reimplement? How to Choose the Right Path
A Dynamics NAV to Business Central migration does not always have to preserve everything exactly as it exists today. Microsoft documents both a full migration path that carries forward data and converted customizations and a reimplementation path that moves essential data into a cleaner Business Central environment. The right choice depends less on system age alone and more on how much of the current environment is still worth carrying forward.
Microsoft's current guidance explains that NAV customers on supported paths move through Business Central on-premises version 14 before completing migration to Business Central online. From there, organizations can continue through full migration, including conversion of C/AL customizations to AL extensions, or use the reimplementation approach when a cleaner start makes more sense.
The real decision is what deserves to survive
Many long-running NAV environments contain three different things mixed together: valuable business logic, outdated customizations, and workarounds created around limitations that may no longer exist. Treating all three as equally important can make a migration larger, riskier, and more expensive than necessary.
A good Business Central migration assessment separates those layers before choosing the technical path. The goal is to preserve business value, not automatically preserve every artifact of the old system.
When a full upgrade path makes sense
A full migration can be a strong fit when the existing NAV environment is well understood, historical data has ongoing operational value, customizations still support important processes, and the company wants continuity with less process redesign.
The advantage is continuity. The company carries more history, more setup, and more of the current system forward. The tradeoff is that technical debt can come along too, especially when old customizations or integrations are preserved without first questioning whether they still belong in the future state.
When reimplementation deserves a harder look
Reimplementation is worth serious consideration when the current NAV environment has accumulated years of unused fields, obsolete reports, brittle customizations, duplicate setup, manual workarounds, inconsistent master data, or processes the company would not choose today.
The benefit of a cleaner path is that the organization can begin with current extensions, cleaner data, modern reporting, and processes designed around how the business works now. The tradeoff is that users may face more process change, and historical detail may need to remain in the legacy environment or an archive.
Use six questions to choose the path
The decision becomes clearer when the team evaluates six areas: customizations, historical data, process health, integrations, change capacity, and future-state goals.
1. How much customization is still genuinely needed?
Inventory every customization, then ask who uses it, how often, what business problem it solves, whether the problem is still real, and whether standard Business Central, an AppSource extension, Power BI, or Power Platform can now solve it differently.
Do not pay to migrate custom code simply because it exists.
2. How much historical detail must remain active?
Companies often say they need all the history. The better question is what users actually need inside the operational ERP. Regulatory retention, audit access, historical analysis, customer service, and everyday transaction processing have different requirements.
Some history may need to remain accessible without being migrated into the live Business Central database.
3. Are the current processes healthy?
A technically successful upgrade can faithfully preserve a bad approval process, unnecessary duplicate entry, weak item setup, or a report nobody trusts. Before deciding to migrate a process, ask whether you would design that process the same way today.
4. How many external systems depend on NAV?
Interfaces often determine migration complexity more than the ERP database itself. Review EDI, ecommerce, warehouse systems, banking, payroll, CRM, Power BI, custom SQL databases, document management, and external applications.
A future Business Central environment may need different integration patterns, which is why migration planning often overlaps with Microsoft Cloud & Business Systems.
5. How much operational change can the business absorb?
A cleaner future state may be attractive technically, but the rollout still has to fit the company. Busy seasons, month-end, inventory counts, production schedules, customer commitments, staffing, training availability, and other major projects all affect the implementation window.
6. What does the future state need to accomplish?
If the goal is simply to reproduce NAV in the cloud, the migration will look different than a project intended to simplify operations, improve reporting, connect Microsoft 365, introduce Power BI, modernize integrations, and prepare the company for AI-supported workflows.
The destination should shape the migration strategy.
Do not migrate reports blindly
Legacy ERP migrations often spend too much time recreating reports simply because the reports exist. Before rebuilding one, ask who uses it, what decision it supports, whether the information is still important, and whether Business Central, Excel, Power BI, or another approach can answer the question better.
Use the project to remove process debt
A migration is one of the few times a company has enough attention focused on its ERP to question long-standing habits. Use that window to ask which spreadsheets should disappear, which approvals can be simplified, which integrations should be retired, which customizations standard Business Central now replaces, and which data should not come with you.
This is also a good time to review broader triniT Partners solutions around reporting, integrations, Microsoft cloud, and practical AI so the target state reflects the business you want to run next.
Start with an assessment before choosing the architecture
The upgrade versus reimplementation decision should come after reviewing NAV version, customizations, data, integrations, reports, permissions, process problems, user needs, and future business goals. Choosing the migration path first and forcing the facts to fit it is backwards.
If your organization is running Dynamics NAV and needs help deciding what should be upgraded, rebuilt, archived, or retired, talk to triniT Partners about a practical migration path to Business Central.
Comments