Your Dynamics NAV system still processes orders, manages stock and closes the books. So why consider replacing something that works?
Because a functioning ERP system can become a business risk long before it stops working. The warning signs often appear in rising support costs, ageing integrations and the growing effort needed to accommodate even modest business changes.
When Should You Move from NAV to Business Central?
A NAV to Business Central migration makes sense when the cost, risk and limitations of maintaining NAV outweigh the investment and disruption involved in moving. The decision should reflect Microsoft’s support timelines, operational requirements, technical dependencies and business readiness. A stable NAV environment may justify continued use, provided the risks are understood, controlled and regularly reviewed.
Your NAV support position may be closer to a decision point than you think
Microsoft’s published lifecycle dates show that mainstream support for Dynamics NAV 2018 ended on 10 January 2023, with extended support scheduled to end on 11 January 2028.
During extended support, eligible security updates remain available, but mainstream product improvements and routine non-security fixes are no longer provided under the standard lifecycle policy.
Older NAV versions may already be beyond extended support.
These dates matter because the exposure extends beyond NAV itself. An ageing installation may depend on older Windows Server or SQL Server versions, specialist developers, third-party extensions and interfaces that become increasingly difficult to maintain.
Consider a distributor whose warehouse integration still works reliably. A planned infrastructure upgrade reveals that the interface depends on software no longer supported by its supplier.
The immediate problem is not failed order processing. It is the cost, uncertainty and operational exposure associated with making a necessary change.
The question is no longer simply whether NAV works. It is how confidently the business can continue operating, adapting and recovering when something changes.
Staying on NAV Has a Cost. So Does Moving.
Remaining on NAV can be reasonable when critical processes are stable, security risks are manageable and the business has dependable support.
Moving to Business Central online offers a different operating model, with Microsoft-managed cloud infrastructure, ongoing platform updates and access to newer Microsoft capabilities.
Yet cloud migration introduces its own costs and responsibilities. Existing customisations may need redevelopment, integrations may require redesign, and employees must adapt to changed processes.
Subscription licensing, data migration, training and potential disruption belong in the investment case alongside any anticipated operational improvements.
This leaves three possible routes:
- Retain NAV temporarily: Where continued operation remains supportable and risks can be managed.
- Upgrade through a supported route: Where preserving existing processes and functionality is commercially justified.
- Move selectively to Business Central online: Where a modernised operating model offers sufficient value to justify the transition.
The strongest decision starts with understanding what the business needs from its ERP system, rather than assuming everything built into NAV must survive.
Before choosing a route, there is a more revealing question: What should the business actually take with it?
What Should You Actually Move from NAV to Business Central?
A successful NAV to Business Central migration starts by questioning what belongs in the new system, rather than assuming everything in the old one deserves a place.
Years of modifications can make NAV highly dependent on processes that no longer reflect how the business operates. Migrating those arrangements unchanged may preserve familiarity, but it can also preserve unnecessary cost and complexity.
Some NAV customisations may have outlived their purpose
Start by examining how finance, purchasing, inventory and order management work today.
Consider a distributor that commissioned custom stock-allocation logic years ago to overcome a NAV limitation. Before rebuilding it, the business should establish whether standard Business Central functionality now meets the requirement.
The same scrutiny applies to approvals, specialist reports and manual workarounds.
Technical dependencies matter here. Older NAV modifications commonly use C/AL code, whereas modern Business Central uses AL extensions. Required functionality may need redevelopment rather than straightforward conversion.
Third-party EDI, warehouse and shipping integrations also need checking for cloud compatibility, replacement options and data dependencies.
The objective is to preserve business capability, not necessarily the code that once delivered it.
Use four decisions to define your migration scope
A practical Business Central migration assessment should classify functionality and data according to their future business purpose.
| Decision | What belongs here | Why it matters |
| Move | Active customers, suppliers, items, required open transactions and opening balances | Protects operational continuity |
| Redesign | Necessary custom workflows, integrations and specialist reporting | Reduces avoidable legacy complexity |
| Archive | Older posted transactions and supporting records that must remain accessible | Preserves audit and reporting access without automatically enlarging the live database |
| Retire | Obsolete modifications, redundant reports and unused records | Reduces maintenance and migration effort |
The correct treatment depends on the chosen migration route. A technical upgrade may preserve substantially more transaction history, whereas a selective reimplementation generally requires explicit decisions about what to import.
Historical data should remain accessible for the applicable legal, financial and reporting requirements, even when excluded from the live system.
Poor data can undermine an otherwise successful migration
Imagine an inventory database containing inconsistent units of measure, duplicate item records and unreconciled stock values.
Moving these records into Business Central does not resolve their weaknesses. It risks carrying inaccurate inventory information into purchasing, fulfilment and financial reporting.
Data cleansing should therefore include record ownership, field mapping, duplicate checks and reconciliation against NAV before migration begins.
People require equal attention. Finance and operations must approve data decisions, while IT assesses integrations, Microsoft Entra ID access and security permissions. Process owners should have time allocated for testing and training.
This is why GO ERP’s process-analysis and Business Central migration approach begins with understanding operational requirements rather than simply transferring records.
Once the business knows what must move, what can change and what can be left behind, it has a far stronger basis for comparing the available migration routes and their true costs.
Retain, Upgrade or Migrate: Let the Evidence Decide
Once the migration scope is understood, the next decision is whether to retain NAV, pursue a technical upgrade or move selectively to Business Central online.
These routes carry different costs, risks and operational consequences. The lowest initial investment is not necessarily the least expensive option over time.
Which NAV migration route makes the strongest business case?
| Route | When it makes sense | Principal trade-off |
| Retain NAV | Processes remain effective, support risks are manageable and immediate change offers limited value | Lower immediate expenditure, but continued maintenance exposure |
| Technical upgrade | Existing functionality remains valuable and a supported upgrade path is practical | Greater continuity, but potentially retains legacy complexity |
| Selective cloud migration | Process improvement and reduced legacy dependency justify broader change | Greater redesign effort, with scope to simplify future operations |
A technical upgrade may require intermediate version steps. It should not be assumed that every NAV environment can move directly to Business Central online.
Use the NAV ROUTE Decision Test before committing investment
A structured assessment can prevent personal preferences or software demonstrations from determining a major ERP investment.
The NAV ROUTE Decision Test evaluates five factors:
- R — Risk and support exposure: How sustainable is the existing environment, including security, infrastructure and specialist support?
- O — Operational fit: How well does each route support the business’s required finance, purchasing and inventory processes?
- U — Upgrade and customisation effort: What must be converted, rebuilt or replaced?
- T — Technical dependencies: Can integrations, reporting, data and deployment requirements be supported?
- E — Economics and execution readiness: Can the business justify the investment and resource the change?
Weight each factor according to business priorities, with the combined weights totalling 100%. Score each route from one to five, where five represents the most favourable outcome. Multiply scores by their weights to produce a comparison.
Treat unacceptable security, compliance or operational-continuity risks as separate decision gates. A high overall score should never override an unresolved critical risk.
Compare five-year costs, not just implementation prices
A credible three-to-five-year comparison should include infrastructure, licences, implementation services, extensions, integrations, support, training and internal resource commitments.
It should also account for disruption and the value of improvements that can be substantiated, such as reduced reconciliation work or fewer manual inventory adjustments.
Consider two hypothetical businesses.
A company running relatively standard NAV 2018 with stable integrations might justify a planned upgrade while preparing for its approaching support deadline.
An older, heavily customised NAV environment may present a stronger case for selective Business Central reimplementation, particularly where maintaining legacy modifications offers little continuing value.
Neither conclusion should be reached without assessing costs, dependencies and operational readiness.
GO ERP’s Business Central advisory approach connects these technical choices with process requirements and commercial priorities.
The outcome should be a documented decision: the preferred route, its expected costs, accepted risks, unresolved questions and clear criteria for proceeding.
Once agreed, that decision must translate into firm migration boundaries and measurable go-live conditions.
A Successful NAV Migration Depends on What You Leave Behind
Choosing the right migration route is only part of the decision. The next challenge is protecting business operations while moving to a different ERP environment.
A technically successful migration means little if orders cannot be fulfilled, inventory valuations are unreliable or finance cannot close the first reporting period.
Define what must work on day one
Before implementation begins, agree precisely what Business Central must support at go-live.
This includes essential processes, active master data, outstanding transactions, opening balances and critical integrations.
Historical records retained outside Business Central need an agreed archive, with appropriate access controls and retrieval procedures. Non-essential reports, customisations and improvements can be scheduled after stabilisation.
Every addition to go-live scope creates another requirement to build, test and support. Controlling that scope helps protect delivery cost, operational continuity and the team’s capacity to manage change.
Go-live readiness must be demonstrated, not assumed
A NAV migration should be rehearsed against real business processes before the production environment is approved.
A practical readiness checklist should confirm:
- Financial accuracy: General ledger opening balances, customer and supplier balances, and inventory valuations reconcile against approved source figures.
- Operational continuity: Order-to-cash, procure-to-pay, stock movements and financial-close processes pass end-to-end user acceptance testing.
- Technical readiness: Critical integrations, access permissions, scheduled tasks and reporting requirements function as agreed.
- Cutover control: A timed migration plan identifies responsibilities, dependencies, decision points and feasible contingency arrangements.
- Business ownership: Users have completed relevant training, acceptance criteria are signed off and support responsibilities are documented.
Unresolved critical defects should trigger an explicit go/no-go decision, not an assumption that they can be resolved afterwards.
Following go-live, monitor transaction processing, reconciliation differences, support incidents and user adoption through the first financial reporting cycle.
The objective is operational confidence, not simply a completed deployment.
Frequently Asked Questions About NAV to Business Central Migration
Can NAV migrate directly to Business Central online?
Not always. The available migration path depends on the NAV version, customisations and Microsoft’s supported migration tools. Some environments require intermediate upgrades or selective data migration.
Must every historical NAV transaction be migrated?
No. Historical records can sometimes remain in a separately accessible archive, provided legal retention, audit, operational and reporting requirements are satisfied.
What happens to existing NAV customisations?
Each modification needs assessment. Some requirements can use standard Business Central functionality; others require AL extensions, compatible third-party applications or redesigned processes.
When should a business begin its NAV migration assessment?
Before support deadlines or infrastructure constraints force an urgent decision. Allow time for process discovery, technical assessment, budgeting, user preparation and testing.
Make the Next ERP Decision with Greater Confidence
The strongest NAV migration is not necessarily the one that transfers the most functionality or data. It is the one that preserves what the business needs, removes unnecessary complexity and protects operations throughout the change.
GO ERP can help through a NAV-to-Business Central Migration Scope and Readiness Assessment, examining process fit, customisations, integrations, data requirements, delivery risks and the available migration routes.
The practical outcome is a clearer basis for deciding what to move, what to leave behind and how to proceed with confidence before committing to a full implementation.
