A closer look at the support dates, the new 2031 licensing deadline, and the decision window still open for NAV customers
The Microsoft Dynamics NAV end of life is now anchored on two key dates. NAV 2018, the final release, loses Microsoft security patching on January 11, 2028. Separately, Microsoft announced on July 28, 2026, that Annual Service Plan coverage, additional perpetual licenses, and Solution Provider Agreement renewals for Dynamics NAV all stop on April 30, 2031. Customers still running NAV can use Microsoft's Bridge to Cloud 3 promotion, a 30% discount on Business Central Online available through December 31, 2027, to fund a migration before those windows close.
Most Dynamics NAV customers have known for years which way this was heading. What they haven't had, until recently, was a specific date attached to the part of the story that forces a decision. On July 28, 2026, Microsoft closed that gap. Buried inside a routine migration-guidance post was a new deadline that matters more than the support dates NAV customers have been tracking since the last version shipped: April 30, 2031, the date Microsoft stops renewing service plans, stops selling additional licenses, and stops treating Dynamics NAV as a product with a future.
Where the NAV timeline stands today
Dynamics NAV end of life isn't a single date. It's a stack of them, spread across six years, and it's easy to lose track once you're a few versions deep running a system nobody on staff quite remembers configuring. NAV 2016 used up its extended support in April of this year. NAV 2017 has a few months left, its cutoff landing in January 2027. NAV 2018, the final release Microsoft ever shipped, is the only version with real runway, and even that runway ends January 11, 2028. If your organization is still running an earlier version, you're already operating without a Microsoft safety net for anything that goes wrong.
What the July announcement adds isn't a new support date. It's a licensing one, and it closes off the workarounds that made the support date feel less urgent. Starting April 30, 2031, Annual Service Plan coverage (both Enhancement Plan and Advantage Plan) stops renewing. Microsoft stops selling additional perpetual user licenses for existing NAV deployments, so you can't quietly add users to a system you're planning to outgrow slowly. Subscription licenses issued through a Solution Provider Agreement stop being renewable. Subscription access through a Services Provider License Agreement is "expected to end" altogether, in Microsoft's own phrasing, which leaves more ambiguity than the other three items and is worth watching rather than assuming. Together, though, the direction is clear: Microsoft isn't just letting NAV age out, it's dismantling the paths that let a customer keep buying into it.
What this looks like for a company still running it
Picture an operations manager holding together a NAV 2017 environment with a shop-floor customization nobody's touched since the contractor who wrote it left the company. The system still does its job. Orders go out, invoices get cut, month-end closes, on schedule. That's the part that makes the end-of-life conversation easy to postpone: nothing looks broken from where the operations team is sitting.
Once extended support ends for a given version, Microsoft stops issuing security patches for it. Not slower service, not deprioritized tickets. None. A vulnerability discovered in NAV 2016 today has no Microsoft-side fix coming, regardless of severity. That risk accumulates quietly rather than announcing itself, which is exactly why it gets underweighted until an audit, a cyber-insurance renewal, or a customer security questionnaire forces the question.
Honestly, the licensing cutoff is probably the more consequential of the two dates for most organizations, because it forecloses options rather than just adding risk. A support deadline is something you can technically ignore for a while, unpatched but functioning. A licensing deadline that stops renewals and blocks new perpetual users is a hard wall. It's the difference between a system getting riskier and a system becoming unmanageable, and 2031 is closer than a five-year runway sounds once a migration is factored in.
The window that's open right now
Dynamics 365 Business Central is where Microsoft has pointed NAV customers since 2018, and the case for it isn't just "newer." Continuous update cycles remove the need for the kind of multi-year upgrade projects NAV customers are used to, and built-in Power BI, Teams, and Copilot integration replace a lot of what used to require custom development or a bolted-on reporting tool. None of that changes the fact that a migration is real work: customizations built in C/AL don't carry over, and rebuilding them as extensions is the largest single line item in most NAV to Business Central migrations.
There's also a financial incentive attached to moving now rather than later. Microsoft's Bridge to Cloud 3 promotion gives eligible NAV customers a 30% discount on Business Central Online licenses, locked in for a three-year term, through enrollment by December 31, 2027. Eligibility requires a perpetual NAV license purchased before September 1, 2024 and an active Enhancement Plan, and the discount runs alongside dual-access rights, so a company can operate NAV and Business Central Online in parallel while the migration is still underway rather than facing a single forced cutover weekend.
What to do with this timeline
None of the dates above demand action today. What they demand is that the decision gets made deliberately instead of by default. A realistic NAV migration, from assessment through go-live, tends to run six to twelve months depending on how much customization has accumulated and how clean the underlying data is. Counted backward from January 2028, that leaves less room than it looks like on a calendar, especially for organizations that haven't yet done the harder work of inventorying which customizations still earn their keep and which were built for a version of the business that no longer exists.
Microsoft's own guidance is specific about what that assessment should cover: current version, existing customizations, integrations, data volume, and the reporting your team relies on day to day, not the reports nobody's opened since they were built. That's not a project plan so much as a starting point, and it's the same starting point regardless of which version of NAV you're on or how close its support date is.
For teams that haven't looked closely at where their environment stands against the full 2026 to 2031 timeline, the most useful next step is a structured NAV migration readiness assessment: what's running, what's custom, what's eligible for Bridge to Cloud 3, and what a realistic timeline looks like against dates that are now fixed. That's a smaller commitment than a migration decision, and for most organizations still running NAV, it's the piece of information they're currently missing.
