Microsoft Dynamics NAV End of Life: What Organisations Should Do Before 2028

For many organisations, Microsoft Dynamics NAV has been a dependable Enterprise Resource Planning (ERP) platform for finance, inventory, and operational management. It has supported thousands of businesses for decades and continues to run core operations across distribution, manufacturing, and services organisations today.

However, Microsoft’s product strategy has shifted decisively toward cloud platforms. With mainstream support for NAV 2018 having ended on 10 January 2023 and extended support ending on 11 January 2028, organisations still operating Dynamics NAV now face an important strategic question. Not whether the system still works.

But whether it remains a defensible platform for the next stage of the business.

Understanding what NAV end of life really means, and what the realistic options are, can help leadership teams make informed decisions before time pressure limits their choices.

End of life does not mean the system suddenly stops working. Many organisations will continue operating NAV beyond support deadlines.

However, lifecycle milestones change the risk profile of the platform.

When extended support ends on 11 January 2028, organisations typically face:

For organisations with stable operating environments and strong internal support capability, NAV may remain serviceable for some time. But the platform will no longer evolve alongside modern ERP architecture.

This is why many organisations begin evaluating options well before the 2028 deadline.

One of the most common misconceptions is that moving from NAV to a newer platform is simply a technical upgrade.

In practice, many NAV environments have accumulated years of customisations, integrations, and workarounds. For organisations planning a move to Business Central online, Microsoft notes that the path typically involves first upgrading to Business Central on-premises, and that data from tables with code customisations cannot be carried forward where customisation is not handled by extensions.

Typical characteristics include:

Because of this, migration programs often become broader transformation projects rather than straightforward upgrades.

In many cases, organisations find that replicating a heavily customised NAV system in a modern platform creates unnecessary complexity. Instead, the project becomes an opportunity to redesign processes and simplify architecture.

This is why many ERP transformation programs take 18–36 months from initial planning through implementation.

Microsoft’s recommended path is migration to Dynamics 365 Business Central, the successor platform to NAV for small and mid-market organisations. For many businesses, this is the logical next step because Business Central continues the Microsoft mid-market ERP lineage while offering a modern cloud delivery model.

However, moving from NAV to Business Central is not always a simple like-for-like upgrade. In many cases, older NAV environments have accumulated customisations, modified objects, partner-developed modules, and legacy integrations that need to be redesigned or rationalised during the migration. Microsoft’s published guidance for Business Central online also makes clear that customers generally need to upgrade first to Business Central on-premises, and that code customisations must be extension-based for online migration.

For some organisations, this still makes Business Central the best fit. For others, particularly where operating complexity, international footprint, manufacturing depth, or broader transformation goals have changed materially since NAV was first implemented, it can be the right moment to reassess the ERP platform more broadly rather than defaulting to the Microsoft path.

The right decision depends on process complexity, growth plans, customisation footprint, integration requirements, and appetite for change.