What is Dynamics NAV and is it still relevant in 2026?

Dynamics NAV is a Microsoft ERP system that has been replaced by Microsoft Dynamics 365 Business Central. Microsoft stopped active development of NAV as a standalone product in 2018, when Business Central became its official successor. If you are still running NAV today, you are using a legacy platform — and understanding what that means for your organisation in 2026 is worth your time. Below, we answer the most common questions about NAV’s current status and what your options are.

When did Microsoft stop developing Dynamics NAV?

Microsoft officially ended new development of Dynamics NAV in 2018, when it launched Dynamics 365 Business Central as the product’s direct successor. From that point forward, Microsoft shifted all investment and innovation to Business Central, leaving NAV in a maintenance-only phase with no new feature development.

Before 2018, NAV had a long history as one of Microsoft’s flagship ERP products for small and mid-sized businesses. Earlier versions were known under names like Navision and Microsoft Business Solutions — NAV. The product had a loyal user base, particularly in Europe, and was known for its flexibility and strong partner ecosystem. That heritage is part of why so many organisations are still running it today, even as the platform ages.

Microsoft did not abandon NAV users overnight. It announced a clear transition path to Business Central and continued to provide limited support for existing NAV versions. But no new functionality has been added to NAV since 2018, which means any organisation still on the platform is running software that is now eight years behind the current product.

What is the difference between Dynamics NAV and Business Central?

Dynamics NAV and Business Central share the same core foundation, but they are fundamentally different in how they are delivered, maintained, and extended. Business Central is a cloud-native SaaS platform, while NAV was a traditional on-premises application. Business Central receives continuous updates from Microsoft, whereas NAV development stopped in 2018.

The differences go beyond the deployment model. Business Central is built on a modern architecture that supports open APIs, native integration with Microsoft 365 and Azure, and a marketplace of extensions through Microsoft AppSource. NAV relied on direct code modifications, which made upgrades difficult and expensive. Many organisations that customised their NAV environment heavily found that those customisations became a long-term liability.

Business Central also introduces a different licensing model. Rather than a one-time perpetual licence, it uses a subscription-based model per user per month. This changes the financial profile of the system and shifts responsibility for infrastructure and updates to Microsoft rather than the customer’s IT team.

In short: Business Central is what NAV would have become if it had been rebuilt for the cloud era. The functional overlap is significant, but the underlying technology and operational model are quite different.

Is Dynamics NAV still supported in 2026?

Support for Dynamics NAV depends on the specific version you are running. Microsoft has ended mainstream support for most NAV versions, and extended support deadlines have been passing steadily over recent years. In 2026, many NAV versions are either in extended support only or have reached end of life entirely, meaning no security patches or bug fixes are provided.

Microsoft published a clear support lifecycle for each NAV version. NAV 2017 and earlier versions have already passed their extended support end dates. NAV 2018 — the final version before Business Central — has extended support running until January 2028. If you are on NAV 2018, you are still receiving security updates, but you are not receiving any new functionality and the clock is ticking.

Running an ERP system beyond its supported lifecycle carries real risk. Security vulnerabilities go unpatched, integrations with other systems become harder to maintain, and finding consultants with deep NAV expertise becomes more difficult and expensive over time. The support window is not a reason to delay action — it is a reason to start planning now.

Should organisations still running NAV migrate to Business Central?

Yes. For the vast majority of organisations still running Dynamics NAV, migrating to Business Central is the right move. The combination of ageing support, no new features, and a clear successor product with a proven migration path makes staying on NAV a diminishing proposition. The question is not whether to migrate, but when and how.

That said, timing matters. Migrating too quickly without proper preparation creates risk. Migrating too slowly means accumulating technical debt and operating on an increasingly unsupported platform. The organisations that navigate this transition well are those that start with a clear picture of where they stand today before committing to a roadmap.

This is where a business transformation assessment adds real value. Before any budget is committed or timelines are set, understanding your current ERP maturity — how your processes, data, and customisations are structured — gives you a solid baseline for planning the migration. Without that baseline, scope and costs are guesswork.

There are cases where organisations might delay migration: if they are mid-way through a major business change, if their NAV version still falls within extended support, or if a merger or acquisition is pending. But delay should be a deliberate choice based on circumstances, not a default position.

How complex is a migration from Dynamics NAV to Business Central?

A migration from Dynamics NAV to Business Central ranges from moderately complex to highly complex, depending on the extent of your NAV customisations, the quality of your data, and the number of integrations you have built over the years. Organisations with heavily modified NAV environments typically face the most significant effort.

Several factors drive complexity in a NAV to Business Central migration:

Custom code and modifications: NAV’s C/AL programming language allowed deep customisation. Business Central uses AL extensions instead. Any custom functionality needs to be re-evaluated, rebuilt as an extension, or replaced with standard Business Central features.
Data quality and structure: Years of accumulated data in NAV often includes inconsistencies, duplicates, and outdated records. Data migration is not just a technical exercise — it requires a thorough As-Is analysis of your current data structures before any migration begins.
Integrations with other systems: NAV integrations built on older APIs or direct database connections will need to be rebuilt using Business Central’s modern API framework.
User adoption and process change: Business Central works differently enough from NAV that end users will need structured support to adapt. Change management is not optional — low adoption after go-live is one of the most common reasons ERP migrations fail to deliver their expected value.

Microsoft does provide a migration tool for moving data from NAV to Business Central, which helps with the technical side of the transition. But the tool handles data movement, not the broader programme of work: redesigning processes, managing stakeholders, testing thoroughly, and executing a controlled cutover. Those elements require experienced hands.

For organisations with complex NAV environments, treating this as a straightforward upgrade is a mistake. It is a full ERP transformation, and it deserves the same level of planning and governance as any major system change. You can explore our full range of services to see how each phase of the migration can be structured and supported.

How Optinus helps with Dynamics NAV to Business Central migration

We work with organisations at every stage of the transition from Dynamics NAV to Business Central — from the initial assessment through to post-go-live support. Here is what that looks like in practice:

Maturity assessment: We start by mapping your current NAV environment, including customisations, data quality, integrations, and process gaps. This gives you a clear baseline before any roadmap or budget is committed.
Data migration management: We use rigorous As-Is/To-Be analysis and structured testing procedures to make sure your data arrives in Business Central accurately and completely, with no surprises at go-live.
Cutover management: We plan and manage the transition from NAV to Business Central in detail, with real-time monitoring during the cutover window and hypercare support immediately after go-live to protect operational continuity.
Change management: We address both the technical and human side of the migration, helping your teams understand and adopt Business Central so the investment actually delivers results.
Active across Microsoft Dynamics 365 and other ERP platforms: Our consultants have hands-on experience from real migrations at leading multinationals, not just theoretical knowledge of the methodology.

If your organisation is still running Dynamics NAV and you want to understand what a migration to Business Central would actually involve, get in touch with our team for a straightforward conversation. Or if you want to understand more about who we are and how we work, learn more about what we do.

home|

blog|