Is Dynamics NAV still supported in 2026?

Most versions of Dynamics NAV are no longer supported by Microsoft in 2026. Mainstream support ended for all NAV versions up to NAV 2018 years ago, and extended support for the older releases has also expired. If you are still running Dynamics NAV, you are almost certainly operating on an unsupported or minimally supported system, which has real consequences for security, compliance, and your ability to get help when something goes wrong. This article answers the most common questions organisations ask when they realise where they stand.

What happens to Dynamics NAV after Microsoft ends mainstream support?

When Microsoft ends mainstream support for a Dynamics NAV version, you lose access to new features, non-security hotfixes, and free support incidents. Once extended support also ends, even security updates stop. This means your system continues to run, but Microsoft will no longer patch vulnerabilities, fix bugs, or provide assisted support, leaving your organisation exposed to increasing risk over time.

In practice, this creates several problems. Security vulnerabilities go unpatched, which can put your data and operations at risk. Compliance requirements become harder to meet, particularly in regulated industries. Your IT team loses access to official Microsoft support channels, so resolving technical issues falls entirely on internal resources or third-party partners. And as NAV ages further, finding consultants with the right expertise becomes more difficult and more expensive.

Running an unsupported ERP is not an immediate crisis on day one, but the risk compounds over time. The longer an organisation stays on an unsupported version, the more technical debt accumulates and the more complex a future migration becomes.

Which versions of Dynamics NAV are still supported in 2026?

In 2026, Dynamics NAV 2018 is the only NAV version still within Microsoft’s extended support window, and that extended support ends on January 14, 2028. All earlier versions, NAV 2017, NAV 2016, NAV 2015, and older, have passed both mainstream and extended support end dates and are no longer supported by Microsoft.

Here is a quick overview of the support status for the most commonly used NAV versions:

Dynamics NAV 2013 / 2013 R2: Extended support ended January 2023 – fully unsupported
Dynamics NAV 2015: Extended support ended January 2025 – fully unsupported
Dynamics NAV 2016: Extended support ended April 2026 – recently expired
Dynamics NAV 2017: Extended support ended January 2027 – in final phase
Dynamics NAV 2018: Extended support ends January 2028 – currently the only supported version

If you are running NAV 2016 or earlier, your system is already outside Microsoft’s support lifecycle. Even NAV 2017 is approaching its end date, giving organisations on that version limited time to plan a structured transition.

What’s the difference between Dynamics NAV and Business Central?

Dynamics Business Central is the direct successor to Dynamics NAV. Microsoft rebranded and rebuilt NAV as Business Central in 2018, transitioning it to a cloud-first, SaaS-based platform. The core business logic and many familiar processes carry over, but Business Central is architecturally different, designed for continuous updates, cloud deployment, and modern integrations.

The key differences between the two platforms come down to deployment model, update cadence, and extensibility:

Deployment: NAV is an on-premises system. Business Central is available as a cloud (SaaS) solution via Microsoft Azure, or as an on-premises or hybrid deployment for organisations that need it.
Updates: NAV required manual upgrades every few years. Business Central receives automatic updates twice a year from Microsoft, keeping the system current without major migration projects.
Extensibility: NAV relied heavily on C/AL code customisations, which are difficult to maintain and migrate. Business Central uses the AL language and extension-based architecture, making customisations cleaner and upgrade-safe.
Integration: Business Central connects natively with Microsoft 365, Power BI, Power Platform, and Azure services, integrations that NAV could not support in the same way.

For most organisations, Business Central is not just a new name for NAV. It is a genuinely different platform that requires proper planning, data migration, and process redesign to implement well. Understanding your ERP transformation services options before committing to a migration approach is a useful starting point.

Should you migrate from Dynamics NAV to Business Central in 2026?

For most organisations still running Dynamics NAV, migrating to Business Central in 2026 is the right decision, particularly for those on NAV 2016 or earlier, where support has already ended. Staying on an unsupported system means accepting growing security risk, no vendor support, and increasing difficulty integrating with modern tools and partners.

The case for migrating now is stronger than it was two or three years ago. Microsoft has matured Business Central significantly, and the migration tooling has improved. Organisations that delay further face a more complex migration later, as the gap between NAV and Business Central widens with each update cycle.

That said, the decision should not be made without first understanding where your organisation stands. Before committing to a roadmap or budget, it is worth conducting a structured assessment of your current processes, data quality, and customisations. We typically start with a maturity assessment for exactly this reason: it gives organisations a clear baseline before any investment is committed, and it surfaces the complexity that is easy to underestimate when planning a NAV to Business Central migration.

If you are on NAV 2017 or NAV 2018, you have a narrow window to plan properly rather than react under pressure. Using that time to assess, design, and prepare is far less disruptive than rushing a migration when support finally expires. You can explore our approach to ERP transformation to understand what a structured migration journey looks like.

How long does a Dynamics NAV to Business Central migration take?

A Dynamics NAV to Business Central migration typically takes between six and eighteen months, depending on the complexity of your current environment, the volume of customisations, data quality, and the number of integrations involved. Smaller organisations with a relatively standard NAV setup can complete the migration at the lower end of that range. Large multinationals with heavily customised NAV systems, complex data structures, and multiple integrations should plan for twelve to eighteen months or more.

The main phases that drive the timeline are:

Assessment and design: Mapping current processes, identifying customisations, analysing data quality, and defining the target state in Business Central. Skipping or rushing this phase is the most common cause of project overruns.
Data migration: Cleansing, transforming, and migrating master data, transactional history, and open items. Data migration is consistently one of the highest-risk phases and requires rigorous As-Is/To-Be analysis and testing to prevent errors from carrying into the new system.
Configuration and development: Building the Business Central environment, recreating or replacing NAV customisations using the AL extension model, and configuring integrations.
Testing: Unit testing, integration testing, and user acceptance testing to validate that the new system meets business requirements before go-live.
Cutover and go-live: The final switch from NAV to Business Central. This phase requires meticulous planning and real-time monitoring to protect operational continuity. A poorly managed cutover can disrupt day-to-day operations even when everything else has gone well.
Hypercare: The period immediately after go-live where issues are resolved quickly and users get the support they need to work effectively in the new system.

Organisations that treat the migration as purely a technical project, and underinvest in change management and user adoption, often find that the system goes live on time but adoption lags, undermining the business case. The human side of the transition matters as much as the technical execution.

How Optinus helps with your Dynamics NAV migration

We help organisations move from Dynamics NAV to Business Central in a structured, low-risk way, covering every phase from initial assessment through to post-go-live support. Our consultants have hands-on experience from real ERP migrations at leading multinationals, not just theoretical frameworks, which means we understand where projects go wrong and how to prevent it.

Maturity assessment: We start by mapping where your organisation actually stands, processes, data, customisations, and readiness, before any roadmap or budget is committed.
Data migration management: We use rigorous As-Is/To-Be analysis and testing procedures to ensure data arrives in Business Central accurately, with no loss and no surprises at go-live.
Cutover management: We plan and monitor the cutover end-to-end, including hypercare and aftercare, so your operations stay uninterrupted through the transition.
Change management: We address both the technical and human side of the migration, driving genuine user adoption rather than just delivering training and walking away.
Available on-site and remote: We work with organisations across the Netherlands, Belgium, and internationally, on-site where it matters, remote where it makes sense.

If you are ready to understand your options and plan a migration that actually works, take a look at our Microsoft Dynamics transformation services or get in touch with us to discuss your specific situation.

home|

blog|