Dynamics NAV end of support: what it means and what to do next
Many companies still run their business on Microsoft Dynamics NAV, and it still works. But its runway is ending. Planning now means you choose the timing of your move, rather than having it chosen for you.
Where NAV support stands
NAV 2018 was the final release of Dynamics NAV. Its extended support from Microsoft ends in January 2028, and earlier NAV versions have already reached the end of support or are close to it. No new NAV versions will be released. Microsoft's successor is Dynamics 365 Business Central.
Check your version. In NAV, open Help → About to see your version and build. If you're on anything older than NAV 2018, you're likely already outside Microsoft support.
What "end of support" actually means
Your system won't switch off. But over time, the risks build:
- No security updates for the application, a growing concern for auditors and cyber-insurance questionnaires.
- Compatibility drift. Newer Windows, SQL Server and Office versions aren't tested against old NAV releases.
- A shrinking talent pool. Fewer people know C/AL and older NAV versions every year, and many original NAV partners have retired or been acquired.
- A harder upgrade later. Every year adds more data, more customizations to carry, and more pressure on the timeline.
Your options
1. Upgrade to Business Central (cloud)
The path most companies take, and where Microsoft is investing. You get automatic updates, no servers to maintain, and native integration with Microsoft 365, Power BI and Copilot. Customizations are rebuilt as extensions so future updates stay simple.
2. Upgrade to Business Central on-premises
An option if you have specific hosting, connectivity or regulatory reasons to stay on your own infrastructure. You still move to a supported product, but you keep responsibility for servers and update projects.
3. Stay on NAV for now
Reasonable short-term if the system is stable, but it should be a deliberate decision with a date attached, not a default. Use the time to plan, clean up data and retire customizations you no longer need.
What a NAV-to-Business Central upgrade involves
- Readiness assessment. Inventory your customizations, add-ons, integrations, reports, data volume and companies.
- Strategy. Decide what standard Business Central now replaces, what to rebuild as extensions, and how much history to bring.
- Build and test. Convert code to AL, run test migrations, and reconcile balances and history.
- Cutover. A rehearsed go-live with a short downtime window, followed by support through your first month-end closes.
The biggest variable is customization. A lightly modified NAV system can move quickly; one with decades of C/AL changes and third-party add-ons needs careful review. Often many customizations can be retired because Business Central now does the job as standard.
Start with what you know
You don't need to commit to a project to make progress. A readiness assessment gives you a clear inventory, a recommended path and a realistic estimate, so you can budget and choose your timing with confidence.