The short version. Microsoft has set an end-of-sale date for Dynamics NAV, but the right time to migrate is not the same for every company. A Modernization Decision Framework weighs four factors: risk exposure, upcoming business change, incentive timing, and team readiness. For most NAV customers, those factors point to a move in the next 12 to 24 months rather than a wait.
The deadline is set. The timing is still your decision.
Microsoft has named April 30, 2031 as the end of sale for . After that date, customers cannot renew Service Plans, renew subscription licenses, or buy additional perpetual licenses. That is a real deadline, and it has pushed NAV modernization onto a lot of leadership agendas this year.
A deadline five years out is not a reason to panic, and it is not a reason to wait either. The useful question is not when NAV ends. It is when the right time to move is for your business, given what you already know about where you are headed. That is a decision, and decisions are easier with a framework.
Why "it still works" is the wrong test
The most common reason companies stay on aging ERP is that the system still runs. That is also the least useful test, because it measures the wrong thing.
A system can run fine day to day and still expose you in ways that stay hidden until they are expensive. End of sale is not the same as end of support. Once a version is past support it stops receiving security patches and regulatory updates, and most Dynamics NAV versions are already there. The cost of staying does not show up in daily operations. It shows up in an audit, a security review, or a due diligence request during a sale or a raise. "It still works" answers a question no auditor is asking.
The Modernization Decision Framework: four lenses
The Modernization Decision Framework, or MDF, replaces "it still works" with a clearer read on timing. It weighs the decision across four lenses. They do not all need to point the same way. The more that do, the sooner you should move.
- Risk exposure. How far past mainstream support is your version, and what compliance, security, or audit obligations do you carry? A regulated company on an unsupported version is carrying risk every quarter it waits.
- Business change on the horizon. Are you planning an acquisition, a sale, a new entity, or a growth push that leans on your ERP? Migrate before a major change, not during it. Moving the system and the business at the same time is where projects go sideways.
- Incentive and cost timing. Microsoft is funding early NAV migrations. Bridge to Cloud 3 gives qualifying customers a 30 percent discount on a three-year term. That funding rewards early movers, and the cost of the project rises as the deadline compresses the timeline and the pool of available help.
- Team readiness. Do you have internal bandwidth and appetite now? The pool of NAV specialists shrinks every year as they move to Business Central work. Readiness rarely improves by waiting.
Putting it together
Score each lens as low, medium, or high pressure to move. The pattern tells you where you stand.
| If most lenses read... | The signal is... |
| High | Move now. Start planning this year. |
| Mixed | Plan the move within 12 to 18 months, while incentives and NAV talent are still available. |
| Low | Monitor and set a review date. Do not confuse low pressure today with no deadline. |
For most mid-market , at least two lenses read high right now, usually risk exposure and incentive timing. That is why the honest answer for the majority is the next 12 to 24 months, not 2030.
The one mistake that makes a expensive
One pattern turns a manageable project into an expensive one: waiting until the deadline sets your timeline. A migration you plan across two years is a controlled project with testing, training, and a real go-live date. A migration forced into the last year before end of sale is a fire drill, and fire drills cost more in fees, overtime, and disruption. The deadline does not move. Your control over it does, and it shrinks every year you wait.
Where to go deeper
is the successor to Dynamics NAV, built on the same product lineage, which is why the move is a migration rather than a rebuild from zero. For the detail on what end of sale actually changes and how a Dynamics NAV migration actually works, including data, customizations, and the incentive specifics, that full breakdown is here:
Frequently asked questions
Is Dynamics NAV going away immediately?
No. Microsoft has set April 30, 2031 as end of sale, which is when you can no longer renew or buy licenses. Your system keeps running after that. The more immediate issue is end of support, since most NAV versions already do not receive security or regulatory updates.
How do I know if I should migrate now or wait?
Weigh four factors: how exposed you are on security and compliance, whether a major business change is coming, whether current migration incentives apply to you, and whether your team has bandwidth now. The more of these that point to pressure, the sooner you should move.
Does waiting save money?
Usually the opposite. Microsoft's migration incentives favor early movers, and a rushed migration near the deadline costs more in fees and disruption than a planned one. Waiting tends to raise both the price and the risk.
What is the Modernization Decision Framework?
It is a decision tool that weighs an ERP modernization move across four lenses: risk exposure, upcoming business change, incentive timing, and team readiness. It replaces "the system still works" with a clearer read on whether and when to migrate.
About the author
Stephanie McColly is Chief Marketing Officer at Crestwood Associates, a Microsoft Business Central and Acumatica partner that has completed more than 5,000 ERP implementations over 27 years. She writes about translating operational strategy into practical systems decisions. Learn more at