If your business still runs Microsoft Dynamics NAV, you’ve probably noticed the support conversation getting more urgent over the past couple of years — fewer updates, fewer partners actively developing for it, and a growing sense that the clock is running out. That instinct is correct. NAV isn’t being actively developed anymore, and for several of its most common versions, the support clock has already run out entirely.

This isn’t really bad news, though. NAV didn’t disappear — it evolved directly into Dynamics 365 Business Central, and for most NAV customers, the upgrade path is more straightforward than starting an ERP evaluation from scratch. Here’s exactly where things stand and what a realistic migration actually looks like.

Where Dynamics NAV Stands Today

Mainstream support for Dynamics NAV ended in early 2023. Since then, individual NAV versions have been running out their extended support windows on a rolling basis: NAV 2015 reached the end of extended support in January 2025, and NAV 2016 reached its own end of extended support in April 2026 — meaning both are now past the point of receiving any further updates. NAV 2017 follows in January 2027, and NAV 2018 in January 2028.

If you’re running NAV 2015 or NAV 2016 today, your system is no longer receiving security updates, regulatory patches, or critical bug fixes of any kind. If you’re on NAV 2017 or 2018, you have a defined but shrinking window before the same becomes true.

Why the Deadlines Matter More Than They Seem

It’s tempting to treat an end-of-support date as a soft deadline — the system still runs, after all, and nothing breaks the day support ends. The real risk shows up later and less predictably: a security vulnerability that never gets patched, a regulatory change that the system can’t accommodate, or a critical bug that has no fix path because Microsoft has stopped producing them for that version.

For GCC businesses specifically, this collides directly with the region’s tightening e-invoicing and VAT compliance requirements. Saudi Arabia’s phased ZATCA e-invoicing mandate and the UAE’s confirmed e-invoicing rollout both assume systems capable of generating structured, compliant digital invoices — a requirement that an unsupported, frozen version of NAV simply cannot be updated to meet without expensive custom workarounds that themselves carry risk.

What NAV Became: Business Central

Dynamics NAV didn’t get replaced by an unrelated product — it was rebuilt into Dynamics 365 Business Central, Microsoft’s cloud-native successor that carries forward much of NAV’s core logic and mid-market positioning. This lineage matters practically: a NAV implementation partner’s expertise transfers directly to Business Central, and the underlying financial and operational concepts your team already knows don’t need to be relearned from zero the way they would with a switch to an entirely different ERP vendor.

Business Central runs as a cloud subscription rather than an on-premise deployment tied to a specific version, which is precisely what ends the recurring end-of-support cycle NAV customers have been managing for years. Updates happen automatically on a regular schedule instead of requiring a major, disruptive version upgrade every few years.

The Typical Upgrade Path

Microsoft’s own guidance, including a documented process for migrating Dynamics NAV to Business Central online, describes a fairly consistent upgrade sequence for NAV customers: moving from NAV to an early cloud-compatible version of Business Central, then progressing to current Business Central releases, while converting older C/AL-based customizations to modern AL extensions that are easier to maintain and upgrade going forward. According to Microsoft, this migration journey typically takes four to six months for organizations working with an experienced partner.

That timeline varies with how heavily customized your current NAV environment is. A relatively standard NAV deployment with light customization can move faster; a NAV environment with years of accumulated custom code, especially older C/AL modifications, needs more time to assess which customizations are still necessary and which can be replaced by standard Business Central functionality or a pre-built AppSource extension.

What a NAV-to-Business-Central Migration Actually Involves

Beyond the software itself, three things determine how smoothly a migration goes. Data migration — moving historical transactions, master data, and open balances accurately — is usually the largest single work item, and it’s worth budgeting real time for data cleansing rather than migrating years of accumulated inconsistencies as-is. Customization assessment comes next: cataloguing what your NAV environment currently does that standard Business Central doesn’t, and deciding case by case whether each customization gets rebuilt, replaced by configuration, or dropped because it’s no longer actually needed.

User change management is the third, and most often underestimated. Staff who’ve used NAV for a decade need structured training and hands-on practice time before go-live, not just a walkthrough on launch day — the interface and workflow are recognizably related to NAV, but different enough that skipping training creates avoidable friction in the first weeks after go-live.

Choosing the Right Time to Move

If you’re already on NAV 2015 or NAV 2016, the honest answer is that the right time to start planning was some months ago — extended support has already ended, and every day running on an unsupported version is accumulating unmanaged risk rather than saving money. If you’re on NAV 2017, January 2027 is close enough that a migration project should already be in active planning, given the typical four-to-six-month timeline plus the lead time needed to select a partner and assess customizations properly. NAV 2018 customers have more room, but “more room” is relative — starting the assessment now avoids a rushed migration later.

Why Businesses Delay — and Why That’s Getting Riskier

The most common reason NAV customers delay migration isn’t disagreement about the destination — most accept that Business Central is the right move eventually. It’s the perceived disruption of a migration project competing for attention against other business priorities. That calculation made more sense when regulatory pressure was lower. With e-invoicing mandates now active or imminent across multiple GCC markets, the cost of delay isn’t just accumulating support risk — it’s increasingly a compliance risk with a hard deadline attached, which changes the urgency calculation for finance and compliance teams specifically, not just IT.

The Cost of Doing Nothing

It’s worth being specific about what “doing nothing” actually costs, because it rarely shows up as a single line item. An unsupported NAV environment usually means a shrinking pool of consultants willing to work on it, since partners naturally shift their expertise and certifications toward Business Central over time — meaning the cost of any custom development or troubleshooting on old NAV tends to rise even as the system itself stays static. It also means accumulating technical debt: every workaround built to patch around an unsupported limitation is one more thing that has to be unwound during an eventual migration, making that future project more expensive than if it had happened on schedule.

There’s a talent dimension too. Finance and operations staff hired in the last few years are increasingly trained on modern, cloud-based systems, not on legacy on-premise NAV — making it gradually harder to hire and onboard people who are comfortable with the system your business still depends on.

Choosing a Migration Partner

Not every Microsoft partner has deep NAV migration experience specifically, as distinct from general Business Central implementation experience. Ask directly how many NAV-to-Business-Central migrations a prospective partner has completed, what their approach to legacy C/AL customization assessment looks like, and whether they can show a realistic project plan rather than a generic timeline. A partner with genuine migration experience will be able to talk specifically about how they handle historical data volume, multi-currency conversion, and the practical tradeoffs between rebuilding a customization versus replacing it with standard functionality — details that separate real experience from a sales pitch.

Key Takeaways

Dynamics NAV’s support timeline is winding down on a version-by-version basis, with NAV 2015 and NAV 2016 already past extended support and NAV 2017 following in January 2027. The migration path to Business Central is well-defined, typically takes four to six months, and carries forward much of what your team already knows about NAV rather than starting an ERP decision from scratch. The organizations moving comfortably are the ones treating data migration and change management as real project phases and starting well before their support deadline forces the timeline.