The Deadline Many Navision Users Overslept

The countdown is on for Dynamics NAV 2016: on April 14, 2026, security and tax updates, along with all support, will come to an end. Companies still running Navision now face a decision that goes far beyond a simple version upgrade. Microsoft’s long-term path leads to Dynamics 365 Business Central-and that’s where the critical questions begin that SMEs need to answer now.

Key Takeaways

• The deadline is set: NAV 2016 will exit Extended Support on April 14, 2026. NAV 2018 gets a temporary reprieve until January 2028-but that’s it.
• Business Central is the next generation: Built on the same codebase as Navision, it’s the direct successor. In the cloud, it operates under the Modern Lifecycle Policy, meaning no fixed end date.
• Migration is a project, not a push-button task: Partners typically estimate six to twelve weeks if customizations are manageable. Custom code and data quality drive up the effort.

Related:Cloud Repatriation: When Bringing Workloads Back Pays Off  /  When AI Inference Costs Blow Your Cloud Budget

What Really Ends on April 14

Microsoft manages Dynamics NAV under its Fixed Lifecycle Policy: ten years of support per version, split into five years of Mainstream and five years of Extended Support. NAV 2016 launched in January 2016, with its Mainstream phase ending back in 2021. On April 14, 2026, Extended Support will also expire.

This isn’t a gradual phase-out. From that date forward, Microsoft will no longer provide security updates, regulatory or tax adjustments, bug fixes, or technical support. Any vulnerability discovered after the cutoff remains unpatched. For a system that handles finance, inventory, and procurement, that’s an operational risk-not just a minor inconvenience.

Companies still on NAV 2018 gain a little breathing room: Extended Support runs until January 2028. That offers some planning buffer, but it’s no excuse for delay. Migration takes time, and 2028 is closer than it seems.

Cloud, On-Premise or Hybrid: three paths to the same successor

What is Dynamics 365 Business Central? Business Central is Microsoft’s ERP system for small and medium‑sized enterprises. It combines financial accounting, procurement, inventory and sales on a single platform and is the direct successor to Dynamics NAV, which many still know as Navision.

Business Central is not the break that some fear. The platform is the direct successor to NAV, grown from the same code base. The real decision point lies in the operating model, and here midsize companies have three options.

In the cloud, Business Central runs as SaaS under the Modern Lifecycle Policy. That means: no fixed support end as long as the subscription is active, and two release waves per year. On-Premise remains possible, but shifts responsibility for updates and infrastructure back to your own house, including the next lifecycle milestone. Hybrid combines both, e.g., local data storage and cloud analytics, and is usually a transition rather than a target architecture.

For most midsize users, the cloud variant is the target picture because it solves the problem that is becoming acute: the next support milestone disappears. On-Premise remains the choice for organisations with strict data‑retention requirements or deep specialised customisation, but then it needs a genuine justification beyond habit.

Where the migration gets expensive

The version jump itself is not the cost driver. What becomes expensive is what has grown onto Navision over the years. Every individually programmed customization must be translated into the Extension model of Business Central, because the old C/AL interventions in the standard no longer work that way.

The second driver is data quality. Anyone who carries over obsolete records, duplicate master data and historic legacy items one‑to‑one pays for dead weight and drags problems into the new system. Migration is the rare moment when a spring cleaning of the data set is economically justifiable.

Six to twelve weeks if everything runs smoothly

As a rough ballpark, partners estimate six to twelve weeks for a migration from NAV to Business Central, including tests and training. This range holds only when the customization depth is manageable. In heavily customized installations with many interfaces, it quickly turns into several months.

The non‑technical side is regularly underestimated. An ERP switch changes screens, processes and reports that teams have built routines around for years. Cutting training and test operation at the end saves in the wrong place and ends up costing you in live operation. The schedule should be calculated backwards from the cut‑over date, not forwards from the desired date.

What the cut‑over date means for the roadmap

The obvious reflex is the one‑to‑one lift‑and‑shift: map the old system, add a hook. That is the most expensive option because it carries every legacy item and forfeits the opportunity inherent in any forced switch. A better question is a different one: Which processes do we no longer want to run the way they do today?

The cut‑over date is therefore less an IT milestone than a business‑strategic waypoint. It forces a decision that many organisations would otherwise keep postponing. Treating the migration as a pure compliance task ends up with a new system riddled with old problems. Using it as a lever modernises processes that were already overdue. April 14 forces the choice of whether to move. The choice of how well remains.

Frequently Asked Questions

Image source: AI-generated (Juli 2026)