Overview
This post explains how to upgrade Dynamics NAV to Business Central, starting with where each NAV version stands on support. It then walks through the current upgrade path, the upgrade versus reimplementation decision, and a four-phase project plan.
Key Takeaways
- NAV 2016 left extended support in April 2026. Support for NAV 2017 ends in January 2027, and NAV 2018 in January 2028.
- No NAV version can move straight to Business Central online. You upgrade to Business Central on-premises first, via version 14.
- Since version 26, Microsoft no longer supports a direct jump from version 14 to the latest release. The route now runs through version 25.
- C/AL customisations must become AL extensions, or data in those customised tables will not carry forward.
- A reimplementation leaves legacy code behind, and Microsoft’s Business Central 14 Reimplementation tool (in preview) moves essential data to the cloud.
- Starting with a discovery phase gives you a firm scope and timeline before you commit budget.
Why You Should Upgrade Dynamics NAV to Business Central Now
If you still run NAV, the calendar matters more than it did a year ago. NAV 2016 reached the end of extended support in April 2026. Microsoft no longer issues security updates for it. Next, NAV 2017 follows in January 2027, with NAV 2018 in January 2028.
| NAV Version | Mainstream Support Ended | Extended Support Ends |
| NAV 2013 and 2013 R2 | January 2018 | January 2023 (ended) |
| NAV 2015 | January 2020 | January 2025 (ended) |
| NAV 2016 | April 2021 | April 2026 (ended) |
| NAV 2017 | January 2022 | January 2027 |
| NAV 2018 | January 2023 | January 2028 |
| Business Central Spring 2019 (v14) on-premises | October 2025 | October 2025 (ended) |
Extended support only covers security fixes. Mainstream support, which covers bug fixes and feature changes, has already ended for every NAV version. Our post on what NAV end of support actually means covers the security, compliance and insurance risks in more detail.
One date catches people out. Business Central version 14, the standard intermediate version for NAV upgrades, left support in October 2025. You can still pass through it during an upgrade, but you should not plan to stay on it.
Which Upgrade Path Applies to Your NAV Version
Your starting version decides the route. Microsoft changed its supported upgrade paths in 2025. Older guides, including the first version of this post, no longer reflect them.
Based on current Microsoft Learn guidance, the paths are:
- NAV 2015, 2016, 2017 or 2018: upgrade to Business Central version 14, then to version 25, then to the current release. This route requires you to convert your C/AL code to AL.
- NAV 2013 and 2013 R2: upgrade to NAV 2018 first, then follow the route above.
- Older NAV 2009 SP1 and R2 systems: move through NAV 2013 or 2015 to NAV 2018, then follow the same route.
- Business Central versions 14 to 24: upgrade to version 25, then to the current release.
Since version 26, Microsoft no longer supports a direct jump from version 14 to the latest release. That extra hop through version 25 adds a step to your plan, so build it into your timeline and testing.
Moving to the cloud adds one more stage. No NAV version migrates directly to Business Central online. Instead, you reach Business Central on-premises first, then run Microsoft’s cloud migration tool to move your data across.
Upgrade or Reimplement: Choosing Your Route
You have two broad options. A technical upgrade carries your data, history and customisations into Business Central. By contrast, a reimplementation starts clean and brings across only the data you need.
A technical upgrade suits you when:
- Your processes still work well and you want minimal change for users.
- You need full transaction history inside Business Central.
- Your customisations are few and still relevant.
A reimplementation suits you when:
- Nobody fully understands the custom code built up in NAV over the years.
- Your processes have changed since NAV was first set up.
- You want standard Business Central features instead of rebuilt workarounds.
Microsoft now offers a Business Central 14 Reimplementation tool, currently in preview. It moves master data, open orders, opening balances, setup data and a defined subset of posted history to Business Central online. Legacy C/AL customisations and their data stay behind.
Scope drives cost either way. Panorama Consulting’s 2026 ERP Report found that more than a quarter of organisations exceeded their ERP project budgets. Extra technology needs, which projects often uncover late, were the main reason. A proper discovery phase reduces that risk, because you find the gaps before you commit budget.
Our post on why your NAV migration needs a specialist explains how experience with legacy NAV code changes the outcome.
What Happens to Your Customisations and Data
Customisations are usually the biggest variable in a NAV upgrade. Business Central does not run C/AL code, so you either rebuild each modification as an AL extension or retire it.
Microsoft is clear on the data side. Data from tables with code customisations cannot carry forward unless an extension handles them in both systems. For each customisation, decide whether to rebuild it, replace it with a standard feature, or drop it.
Data volume matters too. Business Central online includes 80 GB of database storage plus a per-user allowance. Microsoft also recommends keeping each migration run under 30 GB. Archiving or cleaning old NAV data before you migrate keeps the project within those limits. Our guide to NAV to Business Central data migration covers the clean-up steps.
Integrations need their own check. Older NAV connections often rely on SOAP web services, which Microsoft removes for standard pages in version 29. Read our post on Business Central SOAP web services before you rebuild any integration.
A Four-Phase Plan for Your NAV Upgrade
Tecvia runs every NAV migration through four phases. Each one ends with a clear decision point, so you never commit to the next stage blind.
Phase 1: Inspect
Start with discovery. Review your NAV setup, customisations, integrations and data volumes. Then decide between on-premises and cloud, and between upgrade and reimplementation. Take a full database backup before any technical work begins.
Phase 2: Design
Next, set up your Business Central environment and plan each version step. Convert the customisations you are keeping into AL extensions. After that, run an end-to-end test of the solution and the migrated data.
Phase 3: Empower
Training starts here. Your team works through Business Central in role-based workshops, using your own data where possible. Users then test their daily processes, which catches gaps before go-live.
Phase 4: Activate
Go-live follows once testing passes. Your team moves onto Business Central, with hypercare support in the first weeks. Ongoing support then keeps the system healthy as Microsoft releases updates.
What You Gain After the Move
Business Central gives NAV users more than a supported version. You get:
- Two major updates a year, in April and October, plus monthly minor updates.
- Copilot features inside everyday tasks, such as suggesting sales lines and matching bank transactions.
- Direct links with Outlook, Excel, Teams and Power BI.
- Access from a browser or mobile app, with no local client to install.
- A choice of cloud or on-premises deployment.
Our post on three Business Central features you cannot get with NAV and our Business Central features page go into more detail. For example, manufacturers can see how the system handles production on our Manufacturing & Engineering page.
What This Means for Your Business
If you run NAV 2017, security updates stop in January 2027. That leaves little room for a project with several version steps, so start discovery now. On NAV 2018, you have more time, but the upgrade path is just as long.
Every NAV upgrade now passes through at least two intermediate Business Central versions, plus a cloud migration if you want to go online. Planning early keeps the choice between upgrade and reimplementation in your hands, rather than letting a deadline decide for you.
Plan Your NAV Upgrade With Tecvia
Tecvia upgrades UK businesses from Dynamics NAV to Business Central, from discovery through to go-live support. Get in touch with Tecvia to talk through your NAV version, or book a free Systems and Process Review to scope your options.
You can also see how our Migrate from NAV service works, or read about our implementation approach for phased, tested rollouts.
FAQs
No. Microsoft requires you to upgrade NAV to Business Central on-premises first. From NAV 2015 to 2018, that means version 14, then version 25 or later, before you run the cloud migration tool.
It depends on your version, customisations and data volume. A lightly customised NAV 2018 system moves faster than a heavily modified NAV 2009 system. Starting with a discovery phase gives you a firm timeline before you commit.
Business Central does not run C/AL code, so you either rebuild each customisation as an AL extension or retire it. Many older modifications now have a standard Business Central equivalent. Data in customised tables will not carry forward unless an extension handles it.
NAV 2018 receives security updates only, until January 2028. Mainstream support, covering bug fixes and new features, ended in January 2023. After January 2028, Microsoft stops all updates for NAV 2018.
Upgrade if your processes still work and you need full history in the new system. Reimplement if years of custom code no longer match how you work. Many businesses that reimplement keep an archived copy of NAV for historical lookups.
Yes, but the route is longer. NAV 2013 needs a move to NAV 2018 first, and NAV 2009 must pass through NAV 2013 or 2015 before that. For these versions, a reimplementation is often the simpler option.
