Dynamics NAV end of support 2026: the final countdown is already here
March 17, 2026
If you are operating on Dynamics NAV 2016 or BC 25, Microsoft support for these versions is nearing its end.
Surprisingly, if you are running NAV 2017 or 2018, you still have some time. But considering the typical migration timeline of about 6 months, starting a pre-migration assessment would be a wise step to avoid last-minute workarounds that NAV 2016 users are now facing.
End of support actually means that your ERP solution is quietly entering an unsupported territory. After support ends, you will end up without security updates, compliance patches, or assistance from Microsoft should you face any issues. For systems that backbone finance, compliance, and operations, such a shift poses real business risks.
It’s not a question of “can-we-find-a-slot-in-our-schedule-for-an-upgrade.” It’s a question of business continuity and risk management.
Acting now by staying informed, realistic, and proactive gives control of timelines and options. Waiting until the last minute doesn’t.
The 2026 Dynamics 365 support timeline
Below are the most relevant Dynamics NAV and Business Central on-prem end-of-support deadlines to consider for decision-making in the near future.
Product, version
NAV 2016
NAV 2017
NAV 2018
BC 14 (fixed policy)
BC 25 (modern)
BC 26 (modern)
Support status
Extended support end: April 14, 2026
Extended support end: January 11, 2027
Extended support end: January 11, 2028
Support ended: October 14, 2025
Support end: April 4, 2026
Support end: October 13, 2026
For businesses still using these versions, understanding the NAV 2016 end of extended support implications is crucial for business risk management.
You can certainly notice Microsoft’s focus shifting towards Business Central cloud versions. The support windows for on-prem versions are obviously tightening. Choosing to stick to a version that is technically currently supported, organizations may soon need to make strategic decisions on the go, when the runway is shrinking and the efforts for cloud migration increase dramatically.
NAV and Business Central on-prem end of support: what it means in practice
While end-of-support is sometimes treated as a purely theoretical event, the unsupported ERP risks are always more than real.
Security updates become unavailable
As you end up on your own, without the vendor taking care of your solution, there are no longer patches for the newly discovered vulnerabilities. Microsoft ERP compliance risks arise since an unsupported solution becomes more exposed to cyberattacks. Complicated audit outcomes and problematic coverage of cyber insurance are among the risks that are, unfortunately, often discovered too late.
No support when issues arise
When things break, Microsoft cannot support outdated solutions with platform-level corrections or hotfixes. Thus, organizations find themselves operating solutions that become more fragile over time and depending on niche expertise or custom workarounds. Once a stable and reliable ERP, your system turns into a solution that works until it suddenly doesn’t.
Audit problems and partner pressure
There is no chance an unsupported NAV or Business Central on-prem remains unnoticed during audits. Such vulnerable systems are certainly flagged. What is more, staying on NAV becomes quite a reputational and competitive concern as partners, vendors, and customers expect supported, protected, and thus reliable platforms.
The unsupported ERP risks don’t emerge overnight. But as they compound unnoticed – or deliberately ignored – under the hood, they eventually make you face the reality. And you are not going to like it.
The hidden risks of choosing the old ways
Ignoring end-of-support deadlines and postponing cloud migration is the most expensive option.
Day by day, legacy ERP technical debt grows. Maintenance is getting costlier and harder for C/AL customizations while experienced NAV software engineers are harder to find. Emergency fixes happen more often and get more expensive each time. What is more, modern Microsoft ecosystem capabilities like Power Platform, deep insights driven by Copilot, and advanced analytics, remain unavailable unless you are in the cloud.
Eventually, you have no choice but to migrate. But now the Dynamics NAV to Business Central migration is forced, time-compressed, and far more expensive. Thorough planning and choosing a BC cloud migration strategy beforehand costs much less than migrating when push comes to shove.
The key point: the gap widens. While some do nothing, their competitors evolve and modernize. For those standing still, it becomes more challenging to integrate with partners and customers. With innovation slowing down, your technical delays may become a strategic failure.
Why migration to Business Central Cloud is a strategic advantage
In view of the above, many businesses are reshaping their vision of a long-term ERP strategy. The Business Central cloud vs. on-prem becomes a strategic discussion.
The continuous support model from Microsoft is a pivotal shift. In fact, it makes Business Central cloud an evergreen solution with automated delivery of updates, security enhancements, and regulatory changes. In a long-term perspective, this alignment with Microsoft’s roadmap is hard to ignore.
Another key benefit: Microsoft ecosystem integration. Business Central cloud easily connects with Microsoft 365 products, Power Platform, Azure services, and a bunch of modern tools for analytics. By design, Copilot and AI-assisted insights are cloud-only. Moving to the cloud naturally lifts legacy-system barriers for those craving for process automation, better visibility, and getting more value from data.
There are also purely pragmatic benefits for operational costs. You no longer need to maintain servers or run infrastructure refresh cycles. Instead, organizations gain clearer financial planning and reduced operational costs with a predictable subscription model for Business Central cloud, scaling their solution when needed and only paying for the resources they really use.
Still, moving to the cloud isn’t a silver bullet for every scenario. For some solutions – heavily customized or highly regulated environments – alternative approaches like hybrid development or Business Central reimplementation may suit better than full migration. But as practice shows, for a majority of mid-market organizations, the BC SaaS benefits justify the possible friction of cloud transition. Especially compared to a snowballing technical debt of unsupported solutions.
Business Central Cloud migration realities: what to consider
A Dynamics NAV to Business Central migration is more than a version upgrade. Neglecting this fact puts a migration project at risk. On the other hand, getting ready for what a cloud migration really takes means setting realistic timelines and expectations.
Code migration
The NAV customizations migration risk is real but manageable with proper planning. Refactoring C/AL customizations into AL extensions is a must. This step is often seen as an obstacle, but in fact, this is an opportunity. Many customizations are kept as substitutions for functionality no longer available in the Business Central cloud. The pre-migration period is a chance to rationally assess what functionality really needs to move to the cloud version and what has better alternatives as standard functionality or BC SaaS extensions. Pre-migration review is a pragmatic opportunity to reduce long-term complexity and project risks.
Data complexity
The complexity of data migration greatly depends on the database size, custom tables, and historical retention requirements of a specific solution. Migration scope and timeline are very much formed by the decision about how much history an organization wants to bring into the new cloud system. Depending on customer requirements and needs, we offer multiple approaches to data migration.
Common challenges to remember
Most often, organizations face:
heavily customized code
custom add-ons that need replacing with cloud-native alternatives
user adoption struggles that implies serious change management
redesigning integrations with modern APIs and authentication
The bottom line: cloud migrations are successful when they are properly structured and managed. Unlike emergency transfers pushed by nearing support deadlines or unpredictable failures.
A clear migration roadmap with Stairway to Cloud
At Global Mediator, we consistently see that organizations with a clear, well-prepared cloud migration strategy achieve more predictable and future-proofed results than those that jump into a new technology abruptly.
Stairway to Cloud, our structured, 8-step cloud migration suite, is designed for a well-defined, risk-managed journey to Business Central cloud.
Heavily customized solutions are often treated as a reason to postpone migration. In practice, such a scenario is one of the most common we work with.
Discovery phase
We run Discovery X-ray, a NAV/BC pre-migration review, scanning our customers’ solution code for customizations to help them filter the vital functionality they need in the cloud vs non-essential features.
Defining migration and maintenance strategy
We design a clear migration plan based on your cloud migration concerns, needs, goals, and budget.
Data migration
We show a flexible way based on 4 approaches to data migration – each depending on a specific cloud migration goal (data first, code first, data only, code only).
Scoping
We conduct workshops to select features for reimplementation in the cloud; pinpoint functional fits and gaps to later maximize the use of Microsoft standard functionality. We use these findings to estimate the migration scope.
Solution development
We reimplement the cloud solution that is easy to maintain over time, rather than recreate the old one. If needed, we can add digitalization advantages at this phase and power up your solution with AI, process automation, and Power Platform.
Testing
As part of the QA phase, we conduct manual and automated testing with a sharp focus on regression testing. This step helps keep the new cloud solution stable and reliable after any changes. With Testing, we ensure it goes live with minimized risks.
Go-live
The new cloud solution is ready for work after deployment and proper testing.
Maintenance and enhancement
For healthy performance, cloud solutions must align with regular Microsoft updates. Organizations may also need to develop new features or optimize what they currently have. That’s where proactive maintenance ensures sustainable future growth.
ℹ️ NOTE: As a rule, the duration of cloud migration projects varies. It directly depends on a range of factors, like the number of customizations and database size.
Related services
Stairway to Cloud in action
Challenge: our customer, running an old NAV 2015 with 800+ customizations, wanted to migrate to the latest BC SaaS before Microsoft support ends.
Solution: with Stairway to Cloud, we reimplemented the solution instead of a lift-and-shift approach, removing layers of technical debt and focusing on essential business functionality.
Core benefits:
EUR 25.000 saved (15% under budget in the long run)
Earlier Go-live
Additional capabilities: AI agents, Telemetry, Azure services, Power Platform, etc
Summary: customizations are not an obstacle to a migration. It’s a chance to modernize.
Where 2026 puts you
The situation is no longer about cloud vs on-prem. We’re talking about a planned, smooth migration vs unmanaged risk.
Organizations that migrated before 2025 benefited from a controlled process, flexible transition, and realistic timeline.
Late-2025 cloud transitions felt time-constrained, but organizations still had some space for planning, prioritizing, and managing risks.
In 2026, many businesses are operating either close to or already beyond critical dates, with fewer options remaining available, timelines compressing, and costs increasing. The longer organizations postpone cloud migration, the more likely the transition becomes a reactive effort of juggling challenges and putting out fires.
The decision-makers must honestly answer the questions: what level of ERP risks is acceptable for them now? Core operations – how exposed are they in the unsupported (or soon-to-be unsupported) solutions?
And no, you don’t need to commit to a cloud migration straight away. But in 2026, ignoring these questions means narrowing your options, losing control over timing, scope, and cost.
Don’t stray into unsupported territory
NAV 2016, BC 25, and BC 26 are running out of support.
Panic will not help you navigate a cloud transition successfully.
But preparation, a structured migration roadmap, and a reliable migration partner will. You will stay in control of the outcomes when you assess your current risk exposure and see your options clearly. It's up to you – to either manage the shift strategically or to react under pressure, with every tick of the clock getting louder.
Not sure how to start? Contact us to talk about your current risks and available paths forward.