If you are planning to upgrade Dynamics NAV, the decision today is not just about moving to a newer version. It is about support deadlines, customizations, infrastructure, and whether an upgrade or reimplementation makes more sense for your business. With Dynamics NAV 2018 extended support ending on January 11, 2028, many companies are now under real pressure to plan their next move.
The path to Business Central is still very achievable, but it is not always simple. Microsoft’s guidance shows that upgrade paths vary by version, and in some cases Business Central 14 is still part of the journey rather than the final destination. Microsoft also notes that moving from Dynamics NAV to Business Central online requires customizations to be handled by extensions.
In this guide, we will explain what it really takes to upgrade Dynamics NAV to Business Central today, including upgrade paths, customizations, cloud considerations, common risks, and the high-level steps involved.
If you enjoy this article and would like to talk to Sabre Limited’s president Rob Jolliffe to chat about Business Central, you can book a one-on-one 30-minute call with him at https://calendly.com/robert-jolliffe/30min
Is Dynamics NAV Still Supported?
Yes, but only some versions. As of April 16, 2026, Dynamics NAV 2015 is already out of support, and Dynamics NAV 2016 reached the end of extended support on April 14, 2026. That leaves Dynamics NAV 2017 supported until January 11, 2027 and Dynamics NAV 2018 supported until January 11, 2028.
Here is a simple view of the support window:
- Dynamics NAV 2015: support ended January 14, 2025
- Dynamics NAV 2016: support ended April 14, 2026
- Dynamics NAV 2017: extended support ends January 11, 2027
- Dynamics NAV 2018: extended support ends January 11, 2028
If you are still on NAV 2017 or NAV 2018, that does not mean you should wait. It means your upgrade window is shrinking.
Once support ends, the risks usually go up fast, especially around security, compatibility, and the cost of maintaining older customizations and infrastructure. For many businesses, that is the real reason to start planning a move to Business Central now rather than later.
Why Upgrade Dynamics NAV to Business Central?
For most companies, the biggest reason to upgrade Dynamics NAV is simple: NAV is a legacy product, while Business Central is where Microsoft is continuing to invest. Business Central receives two major update waves each year, monthly minor updates, and ongoing critical fixes. Microsoft also places Business Central on-premises under its Modern Lifecycle Policy, which is a very different long-term position than staying on older NAV versions.
Another major reason is flexibility. If you stay on NAV, your options narrow over time. If you move to Business Central, you can stay on-premises, continue upgrading forward, or plan a future move to Business Central online. Microsoft’s migration guidance is clear that NAV customers can move forward, but the path starts by upgrading to Business Central on-premises first.
Upgrading also helps you modernize how your system is customized. In the NAV world, many companies relied heavily on C/AL changes inside the core application. In Business Central, Microsoft’s direction is app and extension-based customization, especially for businesses that want the option to move online. That makes your environment easier to maintain and better aligned with the product going forward.
There is also a functionality argument. Business Central continues to expand with new capabilities, including Copilot features and regular product improvements that NAV customers simply will not receive by staying where they are. Even if AI is not your priority today, being on Business Central puts you on the platform Microsoft is actively improving.
In short, companies usually upgrade Dynamics NAV for four reasons: support risk, modernization, future cloud flexibility, and access to ongoing innovation. That does not automatically mean every company should do a straight upgrade, but it does mean that staying on NAV gets harder to justify every year.
Upgrade vs Reimplementation: Which Is Better?
There is no universal answer. A direct upgrade is usually the better fit when you are on NAV 2015, 2016, 2017, or 2018, your processes still make sense, and your environment is not overloaded with old custom code. Microsoft still supports upgrade paths from those versions into current Business Central, which is why an upgrade can be the fastest path when the system is relatively clean.
A reimplementation is usually the better fit when your NAV system has years of heavy C/AL customization, outdated processes, poor data quality, or a lot of technical debt. Microsoft’s guidance for moving from NAV to Business Central online requires customizations to be handled by extensions, and it specifically notes that data from tables with code customizations cannot simply be carried forward. In practice, that is one of the biggest reasons some NAV environments are better rebuilt than upgraded.
Here is the practical way to think about it:
A direct upgrade makes more sense when:
- You are on a newer NAV version such as 2017 or 2018.
- Your customizations are limited, well understood, or already being converted to extensions.
- You want to preserve more historical data inside Business Central.
- Your main goal is to move forward with less disruption.
A reimplementation makes more sense when:
- Your NAV system has become heavily customized over time.
- You want to redesign processes instead of carrying old habits into Business Central.
- You plan to move to the cloud and want a cleaner, extension-first foundation.
- You would rather migrate core data and archive history than drag legacy complexity forward.
For many NAV customers, reimplementation is often the better long-term choice, especially if the system is old and highly customized. But if you are on a later NAV version and the environment is relatively clean, a direct upgrade can still be the faster and more cost-effective route. That is why the best starting point is not “How do we upgrade?” but “What are we actually trying to preserve?”
Supported Upgrade Paths for NAV 2015, 2016, 2017, and 2018
If you are on Dynamics NAV 2015, 2016, 2017, or 2018, Microsoft’s current upgrade guidance still provides a supported path forward. The key thing to understand is that Business Central 14 is no longer the finish line. It is typically an intermediate upgrade step on the way to newer Business Central versions.
For companies upgrading toward Business Central 2026 release wave 1 (version 28), Microsoft’s current documented path for NAV 2015, NAV 2016, NAV 2017, NAV 2018, and Business Central October 2018 (version 13) is:
- Step 1: Upgrade to Business Central Spring 2019 (version 14)
- Step 2: Upgrade to Business Central 2024 release wave 2 (version 25)
- Step 3: Upgrade to Business Central 2025 release wave 1 (version 26)
Microsoft notes that this path requires you to convert your application from C/AL to AL.
That is a very important shift from the older way this topic was often explained. In the past, many articles treated BC14 as the target version. Today, Microsoft positions version 14 as a bridge version for older NAV environments. In Microsoft’s own upgrade documentation, version 14 is specifically described as a required step for older source versions, while newer releases continue the journey from there.
In practical terms, that means your upgrade path usually depends on your starting point:
- NAV 2015 to Business Central: supported, but staged through newer versions
- NAV 2016 to Business Central: supported, but staged through newer versions
- NAV 2017 to Business Central: supported, but staged through newer versions
- NAV 2018 to Business Central: supported, but staged through newer versions
If your long-term goal is Business Central online, the path is still possible, but it is usually staged. Most NAV customers first need to upgrade to Business Central on-premises, convert customizations to extensions, and then continue to a deployable version before moving to the cloud.
The key takeaway is simple: if you want to upgrade Dynamics NAV, the path is still open, but it is rarely one jump. It is usually a staged project, and the more customized your NAV system is, the more important planning becomes.
Can You Move from NAV to Business Central Online?
Yes, but usually not in one direct step.
For most NAV customers, the move to Business Central online starts with an upgrade to Business Central on-premises first. From there, the next step is to convert non-standard functionality to apps and extensions, then move forward to a version that is ready for cloud deployment.
That is where many NAV projects become more complex. If your environment still depends on older C/AL customizations, those changes usually need to be reworked before a cloud move makes sense. In some cases, customized data structures also make the transition harder and require additional planning.
So the practical answer is this: yes, you can move from NAV to Business Central online, but it usually takes more than a simple technical upgrade. If the cloud is your long-term goal, that should shape your upgrade strategy from the beginning.
What Happens to C/AL Customizations and Extensions?
This is one of the most important parts of any Dynamics NAV upgrade. If your NAV environment includes C/AL customizations, those changes do not simply move forward into modern Business Central the way many companies expect.
In most cases, custom functionality needs to be reviewed, rebuilt, or converted into the AL extension model. That matters because the more your system depends on older code changes inside the application, the more complex the upgrade usually becomes.
For lightly customized environments, this part of the project may be manageable. For heavily customized environments, it can become one of the biggest drivers of cost, timeline, and risk. In some cases, it is also one of the main reasons a company may decide that reimplementation makes more sense than a direct upgrade.
The practical takeaway is simple: the cleaner your NAV environment is, the easier the upgrade path tends to be. The more heavily customized it is, the more planning is required to decide what should be rebuilt, replaced, or retired as part of the move to Business Central.
Common Challenges During a Dynamics NAV Upgrade
Upgrading Dynamics NAV is rarely just a technical version change. In most cases, the real difficulty comes from the structure of the environment you are trying to move forward.
1. The upgrade path is not always direct
Depending on your current NAV version, you may need to move through one or more intermediate Business Central versions before reaching your final target. That makes planning much more important than many companies expect at the start.
2. C/AL customizations add complexity
Older custom code often needs to be reviewed and reworked before it can fit into a modern Business Central environment. The more your system depends on C/AL, the more difficult the upgrade tends to become.
3. Customized data does not always move cleanly
If your NAV system includes customized tables, fields, or processes, data migration can become more complicated. What looks straightforward on the surface can turn into a deeper cleanup effort once the project begins.
4. Version compatibility matters
Even if a general upgrade path is supported, the exact version and build you choose still matter. A weak upgrade plan can create avoidable issues later in the project.
5. Testing is easy to underestimate
A successful upgrade is not just about getting the system to run. You also need to validate data, test key workflows, confirm integrations, and make sure users are ready for the new environment.
In short, the hardest part of a Dynamics NAV upgrade is usually not the upgrade itself. It is choosing the right path, dealing with customizations, and making sure the system is ready before users ever go live.
How Long Does a Dynamics NAV Upgrade Take?
There is no single timeline for a Dynamics NAV upgrade. The length of the project depends on your NAV version, the amount of customization in the system, and whether you are doing a direct upgrade or a broader reimplementation.
For a lightly customized NAV environment, the process may take a few months. That is often the case when the system is relatively close to standard, the upgrade path is clear, and the goal is to preserve most of the current setup.
For a heavily customized environment, the timeline is usually longer. Older C/AL code, custom tables, third-party add-ons, and more complex data structures all increase the amount of review, rebuild work, testing, and validation required.
Projects can also take longer when they involve more than just the technical upgrade itself. If the business wants to clean up data, redesign processes, reduce old customizations, or prepare for a future move to the cloud, the scope naturally expands.
In practical terms, the biggest factors that affect timeline are your starting NAV version, the amount of customization in the system, the number of integrations and reports involved, and how much user testing and training is required before go-live.
How Much Does It Cost to Upgrade Dynamics NAV?
There is no standard price for a Dynamics NAV upgrade. The cost depends far more on the condition of your current environment than on the word upgrade itself.
For some companies, the project is fairly straightforward. If the NAV system is relatively clean, lightly customized, and well understood, the cost is usually lower because there is less technical risk and less rebuild work involved.
For other companies, the cost rises quickly when the system includes years of C/AL customizations, third-party add-ons, complex reports, custom integrations, or data that needs cleanup before the upgrade can move forward. In those cases, the project often requires more analysis, more development work, more testing, and more user support.
Licensing is also part of the cost picture, but it is only one part. The larger project cost usually comes from planning, technical work, customization strategy, testing, training, and post-go-live support.
The biggest cost drivers are usually your NAV version, how much custom code needs to be addressed, whether you are upgrading or reimplementing, how many integrations and reports need attention, and how much testing and user preparation the project requires.
The practical takeaway is this: a lightly customized NAV environment may be relatively cost-effective to upgrade, while a heavily customized one can become a much larger project. That is why the best starting point is usually an assessment of your current system and long-term goals before trying to estimate the total cost.
High-Level Technical Steps to Upgrade Dynamics NAV
The exact process to upgrade Dynamics NAV depends on your version, your customizations, and your long-term goals. For many companies, the project is not a single jump to the latest version. It is a staged upgrade that requires planning before any technical work begins.
1. Assess your current NAV environment
Start by reviewing your NAV version, customizations, integrations, reports, and overall system complexity. This helps determine whether you are looking at a relatively straightforward upgrade, a more complex project, or a situation where reimplementation may be the better option.
2. Map the right upgrade path
Once the environment is understood, the next step is to identify the supported path forward. For many older NAV versions, that path includes one or more intermediate Business Central versions rather than a single move to the latest release.
3. Prepare the environment and create backups
Before any upgrade work begins, make sure the environment is prepared properly and the data is protected. That usually includes backups, compatibility checks, and confirming that the target version makes sense for your source version and upgrade goals.
4. Upgrade the application and database
At a high level, this stage involves upgrading the application and updating the database structure so the system can move forward into Business Central. This is where the technical transition begins to take shape.
5. Address customizations
If your NAV system includes C/AL customizations, those changes usually need to be reviewed and reworked as part of the upgrade. For many companies, this is one of the most important and time-consuming parts of the project.
6. Upgrade and validate the data
Once the system is in place, the next step is to run the data upgrade and make sure the information carried forward is accurate and usable. This is also where issues tied to customized tables, fields, or processes often become more visible.
7. Continue through any required intermediate versions
For some environments, reaching the first Business Central version is not the end of the journey. Additional upgrade steps may still be needed to reach a more current target version.
8. Test, validate, train, and cut over
Before go-live, the upgraded system needs to be tested carefully. That includes validating workflows, confirming integrations, checking data accuracy, and preparing users for the move to Business Central.
The main takeaway is that upgrading Dynamics NAV is usually not just a database exercise. It is a structured project that involves planning, customization strategy, testing, and business readiness along with the technical work.
Why Work with a Business Central Partner?
Technically, it is possible to upgrade Dynamics NAV without a partner. But for most businesses, that is not the best route.
A NAV upgrade is rarely just a software install. It usually involves version planning, database work, customizations, extension strategy, testing, training, and decisions about whether you should even upgrade directly in the first place. If your system includes older C/AL code, custom tables, third-party add-ons, or plans to move to the cloud later, the project gets much more complicated very quickly.
That is where a Business Central partner adds value. A good partner should help you answer the bigger questions before the technical work starts:
- Should you do a direct upgrade or a reimplementation?
- What is the right upgrade path for your NAV version?
- Which customizations should be rebuilt, replaced, or retired?
- What data should be migrated, cleaned up, or archived?
- How should users be prepared for the move to Business Central?
The technical work matters, but the planning matters just as much. A weak upgrade plan can leave you with broken processes, unnecessary customization costs, and a system that still is not positioned well for future upgrades. A strong partner helps reduce that risk and gives you a clearer path forward.
For many companies, the real value of working with a partner is not just getting the upgrade done. It is making sure the business ends up on the right version, with the right structure, and with a system that is easier to maintain going forward.
Need Help Planning Your Dynamics NAV Upgrade?
If you are trying to upgrade Dynamics NAV to Business Central and want to understand the right path for your environment, Sabre can help.
We work with companies to evaluate their current NAV version, customizations, upgrade risks, and long-term goals so they can make a more informed decision about whether to upgrade or reimplement.
If you would like to talk through your environment, request a quote, or discuss your next steps, you can book a call with our team.
Frequently Asked Questions (FAQ)
Can you still upgrade Dynamics NAV to Business Central?
Yes. Microsoft still supports upgrade paths from Dynamics NAV 2015, 2016, 2017, and 2018 to Business Central, although the path is often staged rather than a single jump to the latest version.
Is Dynamics NAV still supported?
Only some versions are still supported. For example, Dynamics NAV 2018 remains in extended support until January 11, 2028. Older versions have less runway or are already out of support, which is one reason many companies are planning their move now.
Can customized NAV data always be carried forward?
Not always. Microsoft says that data from tables with code customizations cannot be carried forward from Dynamics NAV when moving to Business Central online. That is one of the biggest reasons heavily customized environments require more planning.
Should I upgrade or reimplement?
That depends on the condition of your NAV environment. A direct upgrade is often the better fit when the system is relatively clean and your processes still make sense. A reimplementation is often the better fit when the system is heavily customized, outdated, or carrying a lot of technical debt. Microsoft’s migration rules around extensions and customized data are a big reason that some environments are better rebuilt than upgraded.
Can I stay on-premises after upgrading to Business Central?
Yes. Microsoft supports Business Central on-premises, so upgrading from NAV does not force you into the cloud right away. Many companies upgrade on-premises first, then decide later whether they want to move online.
Conclusion
Upgrading Dynamics NAV to Business Central is rarely a simple version change. For most businesses, it is a project that involves upgrade paths, customizations, data, testing, and bigger decisions about whether an upgrade or reimplementation makes more sense.
At Sabre, we help companies work through those decisions and complete Dynamics NAV to Business Central upgrade projects with a clear plan. That includes evaluating the right path forward, identifying customization risks, and helping clients move to a version of Business Central that is easier to support and build on over time.
If you are trying to understand what your Dynamics NAV upgrade might involve, or what it could cost, we would be happy to talk through your environment and provide a quote. Contact us to get started.
You can also read our article on ERP upgrades vs reimplementation to help determine which approach is the better fit for your business.
