NAV to Business Central Migration: Upgrade Path by NAV Version

Updated October 21, 2026 · Originally published September 15, 2026

A Dynamics NAV to Business Central migration can move companies from almost any NAV version to the current release of Microsoft Dynamics 365 Business Central, but the path depends heavily on the NAV version currently in use. Older NAV environments may require several intermediate upgrades, with each stage involving code conversion, data validation, and testing. Understanding the starting point, existing customizations, and available migration options is essential for developing a realistic timeline and budget.

Key Highlights

• The Dynamics NAV to Business Central migration path depends on the version of NAV currently in use.
• Older NAV versions may require multiple intermediate upgrades before reaching Business Central.
• Customizations, undocumented workarounds, and accumulated technical debt can increase migration complexity and cost.
• Microsoft does not support skipping required upgrade stages.
• An upgrade assessment can help determine whether a technical upgrade or reimplementation is the better approach.

Can You Move Directly From Dynamics NAV to Business Central?

Usually, no. Microsoft's documented upgrade paths treat a Dynamics NAV to Business Central migration as a series of steps rather than one direct jump from an older NAV version to the latest Business Central release.

The starting NAV version makes a significant difference:

• NAV 2018 and Business Central On-premises from October 2018 can move directly to Business Central version 14 and then continue to current releases
• NAV 2013 must first be upgraded to NAV 2018 and then to version 14
• NAV 2015 can move directly to NAV 2018

Companies still running NAV 2009 generally face a longer route. These environments typically need to pass through a mid-2010s NAV release before reaching version 14. Each stage requires its own technical work:

• Converting code from C/AL to AL
• Rebuilding customizations as extensions
• Migrating data
• Testing the resulting system

In other words, the older the NAV environment, the more likely the migration will involve multiple intermediate stages.

Why Does a Dynamics NAV to Business Central Migration Cost More for Older Versions?

The number of upgrade steps is only part of the reason. Technical debt and accumulated customizations are often what make older Dynamics NAV to Business Central migrations more complicated and expensive. Panorama Consulting's cross-industry ERP survey found 30% of ERP projects exceeded budget and 22.3% finished late, with scope expansion and unscoped technical issues among the leading causes.

What happens to NAV workarounds and customizations during the upgrade?

Over time, businesses tend to develop workarounds to address limitations or specific requirements in their ERP system. Some of those workarounds may no longer be necessary because Business Central now includes functionality that addresses the same business need.

Customizations also need to be evaluated individually. A feature that was custom-developed in an older NAV environment may now be available through standard Business Central functionality or an extension. Recreating every customization without first asking whether it is still necessary can add work and cost to the migration without providing a corresponding business benefit. Microsoft's upgrade documentation confirms that a direct upgrade to the current Business Central release is not always possible and that older source versions — Dynamics NAV 2015 (version 8) through NAV 2018 (version 11) — must first be upgraded to an intermediate version.

This is why companies that have waited the longest often need to take a closer look at their existing processes before deciding exactly what should move to Business Central.

What Happens to NAV Customizations During a Business Central Migration?

NAV customizations require particular attention because the development approach has changed. As part of the upgrade process, code may need to be converted from C/AL to AL, while existing customizations are rebuilt as extensions.

That work takes place alongside data migration and testing. As a result, each intermediate upgrade can become a project of its own rather than simply another technical step in one larger migration. In NAV, customisations mixed code from Microsoft, the implementation partner, ISVs and the customer's own developers, all of which could affect upgrades; Business Central's extension model reduces the need for base code customisation.

For companies with years of custom development, the migration also creates an opportunity to determine which modifications are still important to the business. If Business Central already provides equivalent functionality, there may be little reason to recreate an older customization. Microsoft requires C/AL customizations to be converted to AL extensions when moving an on-premises Dynamics NAV solution to Business Central online, unless the Business Central 14 reimplementation path is chosen.

Is There a Way to Shorten the Migration Path?

There are no Microsoft-recommended pathways for skipping required upgrade stages. However, having a clear migration plan and working with a knowledgeable partner can help companies avoid unnecessary complications and mistakes. Microsoft's cloud migration tool cannot be run directly against a Dynamics NAV database: the database must first be upgraded to a supported Business Central on-premises version (version 14 or later) before switching to Business Central online.

Companies considering a Dynamics NAV to Business Central migration may have several options depending on their NAV version and environment. Evaluating those options early can help prevent the project from becoming more complicated than necessary.

What is Microsoft's Bridge to the Cloud program?

Microsoft has also introduced the Bridge to the Cloud program, which is designed to help smooth the migration process and lower overall costs. It does not eliminate critical upgrade steps, but it can change the economics and reduce the chances of errors during the transition.

What Is the First Step in a Dynamics NAV to Business Central Migration?

The best first step is to determine exactly where the existing NAV environment stands before selecting a target migration date.

What does a NAV upgrade assessment cover?

An upgrade assessment can map the current NAV version, customizations, ISV solutions, and the realistic path from the existing environment to Business Central. For some companies, that may result in a relatively straightforward technical upgrade. For others, particularly organizations running older NAV releases with years of custom code, a reimplementation may make more sense than moving through every intermediate stage.

The assessment turns a general goal such as “we should move to the cloud eventually” into something more concrete: an estimated path, timeline, and level of effort. Regulatory and tax updates are not guaranteed on out-of-support NAV versions, which creates a live compliance risk for payroll and VAT reporting.

When does support end for each Dynamics NAV version?

That is important because no two Dynamics NAV to Business Central migrations are necessarily alike. Even companies running the same NAV version can face very different projects based on their customizations, processes, and ISV solutions. Dynamics NAV 2017 remains in extended support until 11 January 2027 and NAV 2018 until 11 January 2028, while NAV 2016 left extended support on 14 April 2026, NAV 2015 on 14 January 2025 and NAV 2013 on 10 January 2023.

Should You Upgrade NAV or Implement Business Central?

Microsoft documents two distinct routes:

• Full migration — moves all data and customisations and requires converting C/AL to AL extensions
• Reimplementation — moves only essential business data such as master data, balances, a subset of posted historical entries and setup

The decision depends on the condition of the existing system and the effort required to preserve it. An assessment can help determine whether moving the current environment forward is practical or whether starting with a cleaner Business Central implementation would make more sense.

The objective should not simply be to complete every technical upgrade step. It should be to establish the most practical path from the system the company has today to the Business Central environment it needs going forward.

Take the Next Step in Your Dynamics NAV to Business Central Migration

A Dynamics NAV to Business Central migration does not have to begin with choosing a target date. It should begin with understanding the current environment and determining what the most practical path forward looks like.

For some organizations, that means planning a technical upgrade. For others, it may mean evaluating reimplementation or taking advantage of programs designed to support the transition to the cloud. Either way, understanding the path before committing to the project can help replace assumptions with a migration plan based on the actual condition of the NAV environment.

Ready to have a conversation about the next steps? Contact our experts at Western Computer. We will be happy to walk you through the different NAV to Business Central migration options we offer.

By Western Computer, westerncomputer.com