+1 480 485 7373
Microsoft Teams
What does Dynamics NAV end of support really change on your server?
Microsoft's Fixed Lifecycle Policy covers NAV releases. Each release first gets mainstream support, when Microsoft ships fixes and minor improvements. Then comes extended support, when only security updates arrive. After extended support ends, nothing arrives at all. The dates differ for every release, so look up your exact version on the Microsoft Lifecycle site. Match it to the release name shown in the Help, About screen of your system.
NAV 2018 was the final release sold under the NAV name, and its successor is Business Central. Every release from NAV 2016 back has passed the end of extended support. NAV 2017 reaches that point in January 2027 and NAV 2018 in January 2028, so even the newest NAV systems now have a fixed horizon.
Your system does not stop working on the day support ends. Invoices still post and reports still run. The exposure is quieter than that. There are no security patches for the application, and friction grows with newer Windows Server and SQL Server versions. Regulatory changes, such as revised 1099 reporting, need someone to patch them by hand. Meanwhile, the pool of developers who still write C/AL keeps shrinking. Each year you stay, the eventual move carries a little more risk and a little more rework.
Which Dynamics NAV support dates apply to recent releases?
Four Dynamics NAV upgrade paths after end of support
Why custom C/AL code decides the Dynamics NAV upgrade path
Partners customized NAV by editing Microsoft's own objects in the C/SIDE development environment. Business Central version 14 was the last release that allowed that. From version 15 onward, every change is an AL extension written in Visual Studio Code. It sits beside the base application instead of inside it. That shift lets Business Central upgrade twice a year. It is also why no NAV modification comes across untouched.
In practice, a modification list from an older NAV system falls into three piles. Some changes were workarounds for features Business Central now has as standard. Examples include better bank reconciliation, item attributes and document attachments, and those simply retire. Some match an AppSource app that another vendor maintains. The rest are genuinely specific to how you work and become per-tenant extensions. The size of that third pile drives the effort far more than the size of the database. It also decides between a fresh start and an upgrade with history. So when you weigh Dynamics NAV end of support and upgrade paths, start with this list.
Planning the move in six decisions
- 1
Confirm the version and build
Record the exact NAV release and cumulative update from the About screen. Then check its status on the Microsoft Lifecycle site, so the conversation starts from facts.
- 2
List every modification and interface
Pull the object list, compare it with a standard database, and add every integration, scheduled job and external report. Mark each as retire, replace with an app, or rebuild.
- 3
Choose how much history to carry
Most companies move open items, balances and summarized prior-year figures. They keep the old database readable for audits. Decide this with your auditor, not by habit.
- 4
Pick the route and the edition
Online or on-premises, fresh start or upgrade, Essentials or Premium. Manufacturing and service management need Premium; check Microsoft's licensing guide for the current split.
- 5
Rehearse in a sandbox
Run the data load at least twice into a sandbox. Reconcile trial balance, receivables, payables and inventory to NAV, and let key users test on the loaded data.
- 6
Cut over at a period end
Switch after a month or quarter close so opening balances start clean. Keep NAV in read-only mode for lookups rather than switching it off on day one.
Signals that waiting has become the riskier choice
- ✓Your NAV server runs on a Windows Server or SQL Server version that is itself out of support
- ✓Only one person, inside or outside the company, understands the custom code
- ✓A new ecommerce platform, bank or payroll provider cannot connect to your version
- ✓Your auditor or cyber insurer has asked about unpatched business systems
- ✓Remote staff reach NAV through a VPN or remote desktop setup that keeps breaking
- ✓Reporting lives in spreadsheets because nobody trusts changing the old reports
Which Microsoft sources back this guide?
Microsoft Lifecycle, Dynamics NAV 2018: learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2018. Checked October 9, 2026.
Microsoft Lifecycle, Dynamics NAV 2017: learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2017. Checked October 9, 2026.
Microsoft Lifecycle, Dynamics NAV 2016: learn.microsoft.com/en-us/lifecycle/products/dynamics-nav-2016. Checked October 9, 2026.
Microsoft updates its documentation often, so confirm the current wording on the page itself before you act on it.
Dynamics NAV end of support and upgrade paths: finance team questions
Is Dynamics NAV still supported by Microsoft?
It depends on the release, so rely only on the Microsoft Lifecycle site for the dates. Each NAV version has its own mainstream and extended end dates, and older releases are past both. Look up the release on your About screen, not a date in a sales email.
Can we move straight from an old NAV version to Business Central online?
Sometimes, but older versions usually need at least one technical upgrade step before cloud migration can run. Microsoft lists the source versions its tools accept, and that list changes. A fresh start avoids the question, because only master data, open items and balances move. We confirm your path during scoping.
Will our NAV customizations work in Business Central?
Not as they are, because Business Central no longer allows changes inside Microsoft's code. You retire each change that standard features now cover, replace some with AppSource apps, and rewrite the rest as AL extensions. Do this review before anyone quotes a rebuild.
What happens to our years of NAV history?
You choose, and most firms keep detailed history in the old system. Open items, balances and some prior-year figures move into Business Central. The NAV database stays readable, or you export it to a reporting store, for audits. Some routes can move full history, but it adds effort and old data problems.
Should we stay on-premises or move to the cloud?
For most small and mid-sized companies, online is the simpler long-term choice because Microsoft runs the servers, backups and updates. On-premises still suits a specific hosting or regulatory need. However, it has its own lifecycle, so it only moves the upgrade question. We compare both against your needs first.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.