What does a Dynamics NAV migration project actually involve?

A Dynamics NAV migration project involves moving your business data, processes, and configurations from Microsoft Dynamics NAV to a modern platform, most commonly Microsoft Dynamics 365 Business Central. The project typically spans several months and covers data extraction, cleansing, mapping, testing, and go-live cutover. The sections below break down exactly what to expect at each stage.

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

A Dynamics NAV migration project moves through five core phases: discovery and scoping, data preparation, system configuration, testing, and cutover with go-live. Each phase builds on the previous one, and skipping or rushing any stage significantly increases the risk of delays or data issues after launch.

The discovery and scoping phase is where you map out your current setup, identify what needs to move, and define what the target environment should look like. This includes an As-Is analysis of your existing NAV configuration and a To-Be design for the new system. Getting this right early saves significant rework later.

During data preparation, your team extracts data from NAV, cleanses it, and maps it to the structure of the target system. This is often the most labour-intensive phase because legacy data tends to include duplicates, outdated records, and inconsistencies that need to be resolved before migration can proceed.

System configuration covers the setup of your new environment, including custom fields, workflows, integrations, and user roles. This phase runs partly in parallel with data preparation. Once the system is configured, testing begins, covering unit tests, integration tests, and user acceptance testing to confirm that data has migrated correctly and that business processes work as expected.

The final phase is cutover and go-live, where you switch from NAV to the new system. This requires precise timing, a detailed cutover plan, and real-time monitoring to catch and resolve issues immediately. A well-managed cutover management process is what separates a smooth go-live from a chaotic one.

What data needs to be migrated from Dynamics NAV?

The data that needs to migrate from Dynamics NAV typically includes master data, open transactions, and historical records. Master data covers customers, vendors, items, chart of accounts, and employees. Open transactions include outstanding invoices, purchase orders, and open general ledger entries. Historical data migration depends on your business requirements and regulatory obligations.

Not all historical data needs to move. Many organisations choose to migrate only a defined period of history, such as the past two to three years, and archive the rest in a read-only environment. This reduces migration complexity and keeps the new system lean.

Common data categories in a NAV migration include:

Customer and vendor master records
Item and inventory data
Chart of accounts and financial dimensions
Open sales and purchase orders
Bank accounts and payment terms
Fixed assets and depreciation schedules
Employee records (where HR modules are in scope)

Each data category requires its own mapping logic. The source field in NAV rarely matches the target field exactly, which is why a thorough As-Is/To-Be data analysis is a non-negotiable step. Our data migration management approach uses rigorous testing procedures specifically to prevent data loss and mapping errors before anything goes live.

How long does a Dynamics NAV migration typically take?

A Dynamics NAV migration typically takes between four and twelve months, depending on the size of the organisation, the complexity of the existing setup, and the volume of data being migrated. Smaller companies with a standard NAV configuration can complete the project in four to six months. Large multinationals with custom development, multiple legal entities, or complex integrations often need nine to twelve months or more.

The biggest time variables are:

Data quality: Poor or inconsistent legacy data extends the cleansing and mapping phase significantly
Custom code: NAV implementations with heavy customisation require additional analysis to decide what to rebuild, replace, or retire
Number of integrations: Every connected system adds testing and configuration work
Stakeholder availability: Delayed decisions from key business users are one of the most common causes of project overruns
Testing cycles: Insufficient time allocated for user acceptance testing leads to issues being discovered post-go-live rather than before

A realistic timeline built on a proper scoping exercise, rather than an optimistic estimate, is the most reliable way to set expectations with your board and leadership team from the start.

What are the biggest risks in a NAV migration project?

The biggest risks in a Dynamics NAV migration project are data integrity failures, go-live disruption, low user adoption, and scope creep. Each of these can derail a project that looked well-planned on paper, and most of them are preventable with the right preparation.

Data integrity failures happen when data is migrated without sufficient cleansing or validation. Errors in customer balances, inventory quantities, or financial records can cause immediate operational problems after go-live and take weeks to resolve.

Go-live disruption is the risk that the cutover itself causes downtime or data inconsistencies. This is why cutover planning deserves its own dedicated workstream, not just a few bullet points in a project plan. A detailed cutover runbook with clear rollback criteria is a practical safeguard.

Low user adoption is frequently underestimated. Even a technically successful migration fails to deliver value if the people using the system revert to workarounds or resist the new processes. Change management that addresses behaviour and not just training is what drives lasting adoption.

Scope creep occurs when requirements expand during the project without corresponding adjustments to timeline or budget. Establishing a clear change control process at the start keeps this manageable.

When should an organisation migrate from NAV to Business Central?

An organisation should migrate from Dynamics NAV to Business Central when the current version of NAV is no longer receiving mainstream support, when the business has outgrown the functionality of its existing setup, or when operational inefficiencies are directly linked to system limitations. For most organisations in 2026, the combination of end-of-support timelines and the availability of cloud-native capabilities in Business Central makes migration a practical priority rather than a distant consideration.

Specific triggers that indicate the right time to migrate include:

Your NAV version has reached or is approaching the end of mainstream support
You are spending an increasing budget on custom development to compensate for missing functionality
Integrations with other systems are becoming difficult to maintain
Your organisation is scaling, adding legal entities, or entering new markets
Reporting and analytics capabilities no longer meet leadership requirements
A broader digital transformation initiative is underway and the ERP needs to keep pace

Before committing to a migration roadmap and budget, it is worth establishing a clear baseline of where your organisation actually stands. A maturity assessment gives you that starting point, identifying gaps in processes, data quality, and organisational readiness before any investment is made.

How Optinus helps with your Dynamics NAV migration

We cover the full spectrum of a Dynamics NAV migration, from the initial scoping and data analysis through to cutover, go-live, and post-go-live hypercare. Our consultants have hands-on experience with real ERP migrations at leading multinationals, which means we bring practical knowledge to every phase, not just methodology.

Here is what working with us looks like in practice:

Maturity assessment to establish a clear baseline before budgets or timelines are committed
As-Is/To-Be analysis of your data structures, processes, and system configuration
Data migration management with rigorous testing to prevent data loss and mapping errors
Cutover management with real-time monitoring and hypercare included
Change management that drives genuine user adoption, not just training delivery
Available on-site and remote, across the Netherlands, Belgium, and internationally

We also cover our full range of services under one roof, so there are no handover gaps between workstreams. If you are planning a NAV migration or trying to work out where to start, get in touch with our team or learn more about what we do.

home|

blog|