Moving off Dynamics NAV: Upgrade or Reimplement in Business Central?
This guide is for companies running Dynamics NAV 2009 to 2018, or an early Business Central on-premises version, often with heavy C/AL customization. Microsoft ends support for NAV 2018 on 11 January 2028, so the decision is whether to upgrade with your data and customizations or reimplement Business Central online with a fresh start, and what to do with each customization along the way.
Key points
- NAV 2017 support ends on 11 January 2027 and NAV 2018 on 11 January 2028; every earlier NAV version, and Business Central 14 on-premises, is already out of support.
- Every NAV version must pass through Business Central 14 on-premises before it can reach Business Central online.
- A full upgrade keeps all history but requires every C/AL customization to be converted to an AL extension.
- A reimplementation moves master data, open documents and balances, and leaves old customizations behind.
- Triage customizations first: convert, replace with a standard feature or app, or drop.
When does Dynamics NAV support end?
NAV 2017 leaves extended support on 11 January 2027 and NAV 2018, the last NAV release, on 11 January 2028. NAV 2009 through 2016 and Business Central 14 on-premises are already unsupported. After the date NAV keeps running, but Microsoft ships no more security updates. Older versions also need more upgrade hops, so your start date depends on your version as well as the deadline. Our timeline lists every date and the risks of staying.
Upcoming Guide: Dynamics NAV end-of-support dates for every version
Should you upgrade NAV or reimplement Business Central?
A full upgrade wins when customizations still match how you work and you need complete history in the live system. A reimplementation wins when customizations are many, outdated or now covered by standard features and apps, and when data needs a clean start. Both end in Business Central online at the same subscription price. Our comparison sets out both paths in one table, including where the upgrade is the better call.
Upcoming Guide: NAV upgrade vs reimplementation comparison
What happens to your C/AL customizations?
Business Central online runs only AL extensions, so every C/AL change must be converted, replaced or dropped before migration. Microsoft's Txt2Al tool converts code from a Business Central 14 database, but its output still needs refactoring into table extensions, page extensions and event subscribers. Our guide walks through the inventory, triage, conversion, testing and code freeze, with a mapping of each C/AL object type. Many items never need converting, because a standard feature or an AppSource app already does the job.
Upcoming Guide: how to convert NAV customizations to AL extensions
What does the wider Business Central project look like?
Moving off NAV is still a Business Central project, with discovery, design, data migration, testing, training and go-live. A typical SME implementation takes about 3 to 6 months, and heavy customization can extend that. The NAV-specific work, such as upgrade hops, code conversion and history archiving, sits inside those phases rather than beside them. Our implementation roadmap lists the deliverables, roles and go/no-go criteria for each phase, so you can plan the NAV move inside a realistic schedule.
Upcoming Guide: Business Central implementation roadmap
Every Moving off Dynamics NAV article, by buying stage
1. Understand
Why AX customers are moving to Dynamics 365 now that AX support has ended.
2. Compare
3. Plan
Plan your move from Dynamics NAV to Business Central
Hull Technologies is a Microsoft Dynamics partner in Naperville, Illinois, with more than 7 years of helping SMEs upgrade, migrate to and extend Business Central.
Frequently asked questions
Can we move from Dynamics NAV straight to Business Central online?
Not in one step. Microsoft's supported path takes NAV 2015 to 2018 to Business Central 14 on-premises, then to version 25 or later, then online. NAV 2013 and older go through NAV 2018 first. A reimplementation can avoid most hops by loading only master data, open documents and balances into a new Business Central environment, while older history stays in an archive.
Do we lose our customizations when we move to Business Central?
Only the ones you choose not to keep. Customizations you still need are rebuilt as AL extensions, which survive Business Central's automatic updates. Many can be replaced by standard features or AppSource apps instead, such as Hull's ScanPro WMS for handheld warehouse scanning or TillPro RMS for in-store point of sale. Unused customizations are simply dropped.
How long does a NAV to Business Central project take?
A typical SME Business Central implementation takes about 3 to 6 months. The number of customizations, the NAV version you start from and how much history you move decide where you land, and heavily customized systems can take longer.
What does Business Central online cost after we move?
Microsoft lists Essentials at $80 and Premium at $110 per user per month in the US, billed yearly, with Team Members at $8 for staff who mainly view data or approve. Premium adds manufacturing and service management. Prices vary by country.
Is staying on Business Central on-premises an option?
Yes, but it is not a way to stop upgrading. Each on-premises version from version 15 onward is serviced for about 18 months, so you must upgrade regularly to stay supported, and you keep running the servers, backups and SQL Server yourself. Customizations still have to be converted to AL, because version 14 was the last release to run C/AL.
Related areas
Business Central
For growing SMEs choosing Business Central as their ERP and planning the implementation.
Moving off Dynamics GP
For finance and IT leads running Dynamics GP on-premises who need a plan before support ends.
Dynamics 365 support and development
For IT leaders who keep Business Central or Finance and Supply Chain running and need it extended.