Microsoft Dynamics NAV reached its mainstream end of support on January 10, 2023, with extended support ending on January 11, 2028, depending on the version you are running. After those dates, Microsoft no longer provides security updates, bug fixes, or technical assistance for the affected versions. If your organisation is still running Dynamics NAV, now is the time to understand what that means and what your options are.
What happens to Dynamics NAV after end of support?
After a Dynamics NAV version reaches its end of support date, Microsoft stops releasing security patches, cumulative updates, and technical fixes for that version. Your system will continue to run, but it will no longer receive protection against newly discovered vulnerabilities, and you will not be able to raise support tickets with Microsoft for issues related to that version.
In practical terms, this creates real business risk. Without security updates, your ERP environment becomes increasingly exposed to threats. Compliance requirements in many industries also mandate that core business systems run on supported software, which means an unsupported NAV installation could put you in breach of internal or regulatory standards. Beyond security, you will gradually find that third-party integrations, add-ons, and partner-built extensions stop being updated for NAV, narrowing your options over time.
Running an unsupported system is not an immediate crisis, but it is a growing liability. Most organisations treat the end of support deadline as the signal to begin planning a migration rather than waiting for something to break.
Which Dynamics NAV versions are still supported?
As of 2026, most Dynamics NAV versions have already passed their mainstream support end dates, and some are approaching the end of extended support. The key dates by version are as follows:
- Dynamics NAV 2015: Mainstream support ended April 14, 2020. Extended support ended April 14, 2025.
- Dynamics NAV 2016: Mainstream support ended April 13, 2021. Extended support ends April 14, 2026.
- Dynamics NAV 2017: Mainstream support ended January 11, 2022. Extended support ends January 11, 2027.
- Dynamics NAV 2018: Mainstream support ended January 10, 2023. Extended support ends January 11, 2028.
If you are running NAV 2016, extended support ends this year. If you are on NAV 2017 or NAV 2018, you are still within the extended support window, but the clock is running. Extended support covers security updates only, not new features or general technical support, so the practical limitations are already significant even before the final deadline arrives.
Understanding exactly where you stand in the Dynamics NAV lifecycle is the starting point for any migration planning. Before committing to a roadmap or budget, it helps to assess your current system maturity, process dependencies, and data quality, so you know what you are actually migrating from. Our ERP transformation services start with exactly that kind of structured baseline assessment.
What is the difference between Dynamics NAV and Business Central?
Dynamics 365 Business Central is the direct successor to Dynamics NAV. Microsoft repositioned and rebuilt NAV as a cloud-native ERP platform and rebranded it as Business Central in 2018. The two products share DNA, but they are not the same system.
The most important differences are:
- Deployment model: NAV was primarily an on-premises system. Business Central is designed for the cloud, running on Microsoft Azure, though an on-premises option also exists.
- Update cadence: Business Central receives two major updates per year, automatically in the cloud version. NAV updates required manual installation and were far less frequent.
- Licensing: NAV used a perpetual licensing model. Business Central uses a subscription model, which changes how costs are structured and forecast.
- Integration: Business Central integrates natively with Microsoft 365, Power BI, Teams, and the broader Dynamics 365 ecosystem. NAV integrations typically required more custom development.
- Customisation approach: NAV customisations were often done directly in the application code, making upgrades difficult. Business Central uses extensions, which are easier to manage and upgrade-safe.
For organisations already familiar with NAV, Business Central will feel recognisable in terms of business logic and terminology. But the technical architecture, deployment model, and customisation approach are meaningfully different, which is why a migration is not simply an upgrade.
Should you migrate from Dynamics NAV to Business Central?
For most organisations still running Dynamics NAV, migrating to Business Central is the right path. It is the only Microsoft-supported successor to NAV, and staying on an unsupported version is not a viable long-term strategy. The question is less whether to migrate and more when and how.
Factors that point toward migrating sooner rather than later include:
- Your NAV version has already passed its extended support deadline
- You are experiencing limitations with integrations or reporting that Business Central would resolve
- Your business processes have evolved significantly since NAV was implemented and need to be re-examined
- You want to take advantage of cloud scalability, automatic updates, and reduced infrastructure costs
Factors that affect the complexity of the migration include the number and depth of customisations in your current NAV environment, the quality and volume of your master and transactional data, and the number of integrations with other systems. Organisations with heavily customised NAV environments often benefit from treating the migration as an opportunity to simplify and standardise, rather than replicating everything they had before.
A structured maturity assessment before you begin gives you a clear picture of your current state and helps you make an informed decision about scope, timeline, and approach. It is a practical first step that avoids committing budget before you know what you are dealing with.
How long does a Dynamics NAV to Business Central migration take?
A NAV to Business Central migration typically takes between three and twelve months, depending on the complexity of your environment. Smaller organisations with a relatively standard NAV setup and limited customisations can complete the migration in three to six months. Larger organisations with complex customisations, multiple legal entities, or significant data volumes should plan for six to twelve months or more.
The main factors that influence the timeline are:
- Customisation depth: Every NAV customisation needs to be assessed, rebuilt as a Business Central extension, or deliberately removed. This is often the most time-consuming part of the project.
- Data migration complexity: Historical data needs to be cleansed, mapped, and validated before it can be loaded into Business Central. Poor data quality in NAV will slow this phase significantly.
- Integration scope: If NAV is connected to other systems, those integrations need to be rebuilt or replaced for Business Central.
- Testing requirements: Thorough testing, including user acceptance testing, is non-negotiable before go-live. Skipping or compressing this phase creates serious risk.
- Change management: Getting your people ready to work in a new system takes time. Training, communication, and adoption support need to be built into the project plan, not added at the end.
Cutover, the moment when you switch off NAV and go live on Business Central, is one of the highest-risk points in the entire process. A well-planned cutover with real-time monitoring and a clear rollback plan protects your operational continuity. Hypercare in the weeks immediately after go-live is equally important to catch and resolve issues before they affect the business.
How Optinus helps with your NAV to Business Central migration
At Optinus, we support organisations through the full NAV to Business Central migration journey, from the first assessment to post-go-live hypercare. We cover every phase that carries risk, so you do not need to manage multiple vendors or deal with gaps between specialisms.
- Maturity assessment: We start by mapping your current NAV environment, customisations, data quality, and process dependencies, so you have a clear baseline before any budget is committed.
- Project and programme management: Our consultants have hands-on experience from real ERP migrations at leading multinationals. We manage scope, timelines, and stakeholder expectations across every workstream.
- Data migration management: We use rigorous As-Is/To-Be analysis and structured testing procedures to ensure your data arrives in Business Central accurately and completely, with no surprises at go-live.
- Cutover management: We plan and monitor the cutover in real time, with hypercare and aftercare included, so your operations continue without disruption.
- Change management: We address both the technical and human side of the migration, helping your teams adopt Business Central confidently rather than reverting to old habits.
We work with organisations across the Netherlands, Belgium, and internationally, both on-site and remotely. Explore our Microsoft Dynamics transformation services to see how we approach each phase of the migration.
Ready to take the next step? Get in touch with us to discuss your NAV environment and what a migration to Business Central would look like for your organisation.
