To start a Dynamics NAV migration, you need to take three steps: assess your current environment and data landscape, define your target state in Microsoft Dynamics 365 Business Central, and build a structured migration plan that covers data, integrations, and change management. These steps give your project a solid foundation before any technical work begins. The sections below cover the full picture, from why organisations move away from NAV to the risks you need to plan for.
Why do organisations migrate away from Dynamics NAV?
Organisations migrate away from Dynamics NAV because Microsoft ended mainstream support for older NAV versions, and the platform no longer receives the updates, cloud capabilities, or integration options that modern businesses need. As NAV becomes harder to maintain and extend, the gap between what it can do and what the business requires keeps growing.
Several practical pressures accelerate the decision. Customisations that were built over years become expensive to maintain and create compatibility problems with third-party tools. Reporting is often slow and manual. Remote access and real-time data visibility, which are standard expectations in 2026, are difficult to deliver on an on-premises NAV setup without significant workaround investment.
The natural destination for most NAV users is Microsoft Dynamics 365 Business Central, which is the cloud-based successor to NAV. It shares the same data model and logic in many areas, which makes migration more manageable than switching to an entirely different platform. That said, “more manageable” does not mean simple. The move still involves a full data migration, process redesign, and user adoption effort.
What is the difference between a NAV upgrade and a full migration?
A NAV upgrade moves your existing system to a newer version of the same platform, preserving most of your customisations and data structures as they are. A full migration replaces the system entirely, typically moving from on-premises NAV to cloud-based Business Central, and involves rebuilding or replacing customisations, cleaning and transforming data, and redesigning processes to fit the new environment.
The distinction matters because the two paths carry very different levels of effort, risk, and cost. An upgrade is faster and cheaper in the short term but may leave you with an ageing architecture that still needs replacing in a few years. A full migration takes more planning and investment upfront but delivers a modern, scalable platform.
For most organisations running NAV 2016 or earlier, a direct upgrade path no longer exists in a meaningful sense. Microsoft’s guidance points toward migration to Business Central as the supported route forward. If you are on NAV 2018 or Dynamics 365 Business Central on-premise, a technical upgrade may still be an option, but the business case for moving to the cloud version is strong in most scenarios.
What are the 3 steps to start a Dynamics NAV migration?
The three steps to start a Dynamics NAV migration are: assess your current state, define your target state, and build your migration plan. These steps happen before any technical configuration or data movement begins, and skipping them is one of the most common reasons NAV migrations run over time and budget.
Step 1: Assess your current environment
Start by mapping what you actually have. This means documenting your existing NAV version, all active customisations and integrations, your data volumes and quality, and the business processes that depend on the system. A structured As-Is analysis gives you a clear picture of what needs to move, what needs to be rebuilt, and what can be left behind.
Data quality deserves particular attention at this stage. Legacy NAV environments often carry years of duplicate records, incomplete master data, and inconsistent coding structures. Identifying these issues early gives you time to clean the data before migration rather than discovering problems during cutover. Our data migration management approach always starts with this kind of rigorous As-Is analysis, specifically to prevent data loss and errors later in the project.
Step 2: Define your target state
Once you understand your current environment, define what Business Central needs to look like when the project is done. This is your To-Be design: which standard Business Central functionality replaces existing customisations, which processes need to be redesigned, and which integrations need to be rebuilt or replaced with native connectors.
This step also includes decisions about deployment model (cloud, on-premise, or hybrid), licensing structure, and which modules to activate at go-live versus in later phases. Getting these decisions made early prevents scope creep and gives your implementation partner a clear brief to work from.
Step 3: Build your migration plan
With a clear As-Is and To-Be picture in place, you can build a realistic migration plan. This plan should cover the full project lifecycle: data migration approach, integration rebuild sequence, test strategy, cutover approach, and change management activities. It should also include a timeline with milestones, resource requirements, and a risk register.
A good migration plan is not just a project schedule. It is a decision-making tool that keeps the team aligned and gives stakeholders confidence that the project is under control. You can explore our full range of services to see how each phase of a migration is typically supported.
How long does a Dynamics NAV migration typically take?
A Dynamics NAV migration to Business Central typically takes between six and eighteen months, depending on the complexity of your current environment, the number of customisations, data volumes, and the number of business units or legal entities involved. Smaller organisations with limited customisations can complete the move in six to nine months. Large multinationals with complex integrations and multiple country rollouts should plan for twelve to eighteen months or longer.
The phases that most often cause delays are data migration and user acceptance testing. Data migration takes longer than expected when data quality issues surface late. Testing takes longer when business users are not available or when scope continues to change during the project. Building realistic buffers into both phases is important.
Cutover planning also affects the overall timeline. A well-planned cutover with clear go/no-go criteria and a tested rollback procedure reduces the risk of last-minute delays. Rushing cutover preparation to hit a deadline is one of the most common causes of failed go-lives.
What are the most common risks in a NAV migration project?
The most common risks in a Dynamics NAV migration are poor data quality, underestimated customisation complexity, insufficient testing time, low user adoption after go-live, and inadequate cutover planning. Each of these risks is manageable when identified early, but they become serious problems when discovered late in the project.
- Poor data quality: Dirty or incomplete master data in NAV creates errors in Business Central. Data cleansing takes time and requires business input, not just technical effort.
- Customisation complexity: Many NAV environments carry years of bespoke development. Not all of it can be replicated in Business Central without significant rework, and some of it should simply be retired.
- Insufficient testing: Compressed testing phases leave defects undetected until after go-live. Integrated test management, covering both technical and business readiness, is important for a stable launch.
- Low user adoption: Business Central works differently from NAV in several areas. Without structured change management and hands-on training, users revert to workarounds or resist the new system entirely.
- Cutover failures: A poorly planned cutover can disrupt operations for days. This phase requires meticulous preparation, real-time monitoring, and a clear hypercare plan for the period immediately after go-live.
Risk management in a migration project is not about eliminating uncertainty. It is about knowing where the exposure is and having a plan for each scenario before the project reaches that point.
How we help with your Dynamics NAV migration
We work with organisations at every stage of a Dynamics NAV migration, from the initial assessment through to post-go-live support. Our consultants have hands-on experience from real ERP migrations at leading multinationals, which means we bring practical knowledge to every phase, not just frameworks.
- Maturity assessment: We start by giving you a clear baseline of where your organisation stands before any budget or roadmap is committed.
- Data migration management: We use rigorous As-Is/To-Be analysis and testing procedures to protect data integrity throughout the migration.
- Cutover management: We plan and monitor your cutover end-to-end, including hypercare and aftercare, so operational continuity is never at risk.
- Change management: We address both the technical and human side of the transition, driving genuine adoption across your organisation.
- On-site and remote delivery: We work across the Netherlands, Belgium, and internationally, both on-site and remotely, to fit your project structure.
Ready to take the first step? Get in touch with our team to discuss your NAV migration, or learn more about what we do and how we support the full transformation journey.
