How long does a Dynamics NAV migration project take?

A Dynamics NAV migration project typically takes between 3 and 12 months, depending on the size and complexity of your organisation. Smaller companies with straightforward processes and clean data can complete a migration in as little as three months, while mid-to-large enterprises with multiple legal entities, customisations, and integrations should plan for six months or more. The single biggest variable is not the technology itself, but the state of your data and how well your business processes are documented before the project begins.

Below, we break down what drives the timeline, what the main phases look like, and what you can do to avoid the most common delays.

What factors determine the length of a NAV migration?

The length of a Dynamics NAV migration project is determined by four core factors: organisational complexity, data quality, the degree of customisation in your current NAV environment, and the availability of key stakeholders throughout the project. Each of these can add weeks or months to your timeline if not addressed early.

Organisational complexity covers the number of legal entities, countries, currencies, and business units involved. A single-entity company with one warehouse and a clean chart of accounts is fundamentally different from a multinational running five subsidiaries across different regulatory environments. The more entities you have, the more data streams, approval workflows, and localisation requirements need to be handled.

Data quality is often underestimated. If your master data, customers, vendors, items, open transactions, contains duplicates, inconsistencies, or gaps, you will spend significant time cleansing it before any migration can begin. A thorough As-Is analysis of your current data structures at the start of the project prevents costly surprises later.

Customisations in NAV are another major driver. Many organisations have accumulated years of bespoke modifications. Each one needs to be assessed: can it be replaced by standard functionality in the target system, or does it need to be rebuilt? The more customisations, the longer the design and build phases take.

Finally, stakeholder availability matters more than most project plans acknowledge. Business process owners who are unavailable for workshops, sign-offs, or testing cycles are one of the most common causes of delay on ERP transformation projects.

What are the main phases of a Dynamics NAV migration project?

A Dynamics NAV migration project moves through five main phases: preparation and scoping, design, build and configuration, testing, and cutover and go-live. Most projects also include a hypercare period after go-live to stabilise the new environment.

Preparation and scoping

This phase establishes the baseline. You document your current processes (As-Is), define what the new system needs to do (To-Be), and agree on scope, budget, and governance. For organisations that have not done this before, starting with a maturity assessment gives you a clear picture of where you stand before committing to a roadmap or budget. Skipping this step is a frequent cause of scope creep later.

Design and build

The design phase translates your To-Be processes into system configuration. The build phase applies that configuration, develops integrations, and handles any required customisations. These two phases together are usually the longest part of the project and run in parallel with early data migration activities.

Testing and cutover

Testing covers unit testing, integration testing, and user acceptance testing (UAT). A structured test management approach, with clear entry and exit criteria, prevents defects from reaching go-live. Cutover is the final switch from your legacy NAV environment to the new system. This phase requires meticulous planning: every task, dependency, and rollback option needs to be mapped before you begin.

How long does a NAV migration typically take from start to go-live?

A NAV migration typically takes 3 to 6 months for smaller organisations and 6 to 12 months for mid-to-large enterprises. Projects involving a migration to Microsoft Dynamics 365 Business Central with significant customisation, multiple integrations, or multi-country rollout can extend beyond 12 months.

As a rough guide:

Small business (1 entity, limited customisation): 3 to 5 months
Mid-size company (1 to 3 entities, some customisation): 5 to 8 months
Enterprise (multiple entities, complex integrations): 8 to 14 months

These ranges assume that key resources are available, that data cleansing starts early, and that scope is controlled. Add two to four months if your organisation is starting without a clear process baseline or if stakeholder alignment is still in progress.

What causes Dynamics NAV migration projects to run over schedule?

The most common causes of delay in a Dynamics NAV migration project are poor data quality discovered late, scope changes mid-project, insufficient testing time, and low user adoption that forces rework after go-live. Most delays are predictable and avoidable with the right preparation.

Scope creep is particularly damaging. When business units add requirements after the design phase is closed, the project absorbs the extra work without a corresponding extension of the timeline or budget. Tight change control governance from the start prevents this.

Cutover failures are another high-risk area. A go-live that is not supported by a detailed cutover plan, covering data loads, system checks, parallel run decisions, and a tested rollback procedure, can result in operational disruption that is difficult to recover from quickly. This is the phase where the pressure is highest and the margin for error is smallest.

Change management is often treated as a soft add-on, but low user adoption after go-live regularly forces organisations back into remediation mode. If users do not understand the new system or resist the change, the business case for the migration erodes quickly. Addressing the human side of the transition from the start, not just the technical side, is what separates projects that deliver lasting value from those that simply go live.

Should you migrate to Business Central or stay on NAV?

For most organisations still running Dynamics NAV, migrating to Microsoft Dynamics 365 Business Central is the right long-term decision. Microsoft has ended mainstream support for most NAV versions, which means no new feature development and, eventually, no security updates. Staying on NAV is a viable short-term position but an increasingly costly one over time.

Business Central offers cloud deployment, regular automatic updates, a modern user interface, and a significantly expanded ecosystem of integrations and apps. For organisations that rely on NAV for finance, supply chain, or warehouse management, Business Central covers the same functional ground while adding capabilities that NAV cannot match.

The main reasons organisations delay the move are concern about disruption, the cost of migrating customisations, and uncertainty about what the project actually involves. A structured starting point, such as a scoping exercise or maturity assessment, removes much of that uncertainty before any budget is committed. You can find an overview of what that process looks like on our ERP transformation services page.

If your NAV environment is heavily customised, a brownfield approach (carrying forward existing configuration) may reduce the migration effort. If the system has become difficult to maintain and your processes have evolved significantly, a greenfield implementation on Business Central often delivers a cleaner result, even if the upfront effort is higher.

How Optinus helps with your NAV migration

At Optinus, we guide organisations through the full NAV migration journey, from the first scoping conversation to post-go-live hypercare. Our consultants have hands-on experience with real ERP migrations at leading multinationals, not just methodology frameworks, which means we recognise the risks before they become problems.

Here is what we bring to a Dynamics NAV or NAV to Business Central migration:

Maturity assessment to establish a clear baseline before any budget or roadmap is committed
As-Is/To-Be analysis of your current processes and data structures to define scope accurately
Data migration management with rigorous testing procedures to prevent data loss or errors during the transition
Test management covering unit, integration, and UAT with clear quality gates before go-live
Cutover management with meticulous planning, real-time monitoring, and a tested rollback procedure
Change management that addresses both the technical and human side of the transition, driving real adoption across your organisation
Hypercare and aftercare to stabilise operations and resolve issues quickly after go-live

We work on-site and remotely, across the Netherlands, Belgium, and internationally, and we cover the full spectrum of ERP migration and transformation services under one roof. That means no handover gaps between specialisms and one accountable partner throughout the entire project.

If you are planning a Dynamics NAV migration or considering a move to Business Central, we are happy to talk through your situation. Get in touch with us to discuss your project and find out what a realistic timeline looks like for your organisation.

home|

blog|