All facts below come from Microsoft’s own Business Central documentation (public GitHub repository of the published docs), Microsoft’s lifecycle pages and the Microsoft Dynamics 365 blog. The support dates of every NAV version we track are in the table at the end.
Key dates from Microsoft
- Microsoft states (July 2026) that the final Dynamics NAV version was released in 2017, with extended support ending in January 2028. Microsoft’s lifecycle page for NAV 2018 gives the exact day: January 11, 2028.
- On April 30, 2031 Microsoft ends Annual Service Plan coverage (Enhancement and Advantage Plans) for NAV, stops selling additional perpetual users for existing NAV deployments, and stops renewing NAV subscription licences (SPA); subscription use through SPLA is expected to end.
- Microsoft’s suggested destination in the same announcement is Dynamics 365 Business Central.
Which NAV versions can go straight to Business Central?
Microsoft’s upgrade guide for Business Central on-premises version 14 (Spring 2019) describes three groups:
| You are on | Path Microsoft documents |
|---|---|
| NAV 2015, NAV 2016, NAV 2017, NAV 2018, or Business Central October 2018 (v13) | Upgrade directly to Business Central v14 (convert the database, upgrade application code and data). |
| NAV 2013 or NAV 2013 R2 | Upgrade to NAV 2018 first, then to Business Central. |
| NAV 2009 SP1 or NAV 2009 R2 | Go through NAV 2013 or NAV 2015, then on to Business Central. NAV 5.0 and 4.0 must go through NAV 2013. |
Version 14 is not the end of the road. Microsoft states that if you come from version 13 or earlier, v14 is a required step to reach the latest version, but that mainstream support for v14 ended in October 2023 and new customers can’t use v14 in production — only as an upgrade step.
What changes after version 14
- C/AL is replaced by AL. Microsoft describes Business Central 2019 release wave 2 (version 15) as the release where C/AL is completely replaced by AL and the classic development environment (C/SIDE) is no longer included. The base application is delivered as an extension. Customisations therefore have to be moved to extensions, or (as a minimum, per Microsoft) the whole application converted to a customised base application in AL.
- Lifecycle policy changes. Versions 13 and 14 follow the Fixed Lifecycle Policy. From the 2019 release wave 2 onwards, on-premises versions follow the Modern Lifecycle Policy, under which Microsoft supports the software only if you keep it current with updates.
Option 1: Business Central on-premises
Keeps your hosting model and infrastructure. Expect a multi-step technical project (NAV → v14 → current version), plus the AL/extension rework above. Under the Modern Lifecycle Policy you also take on regular updates going forward, so budget for an ongoing update routine rather than a one-off upgrade.
Option 2: Business Central online
Microsoft’s guide says moving from NAV to Business Central online is “fully supported” but is in most cases a migration rather than an upgrade: the core scenario is importing existing data into an empty company in an online tenant. Microsoft manages updates online, and technical upgrades as known from on-premises are not supported there. Customisations must be extensions that are allowed in the online service.
Option 3: Another ERP
If the NAV customisations are extensive, the effort of rebuilding them as extensions can approach the effort of re-implementing on another system. That is the point to compare alternatives on cost and fit rather than defaulting to the upgrade path.
Downsides and risks to plan for
- Multi-hop upgrades (for example NAV 2013 → NAV 2018 → BC v14 → current) multiply testing effort.
- Third-party add-ons must have Business Central/AL versions; check with each vendor before committing to a timeline.
- Staying on NAV after support ends means no further security or regulatory updates from Microsoft.