Dynamics NAV (Navision) End of Life: Why Your Real Deadline Is Already Here

Dynamics NAV, the ERP many companies still call Navision, has reached the end of its product line. NAV 2018 was the last version Microsoft released, so Dynamics NAV end of life is really a series of end-of-support dates, one per version. Every version older than NAV 2017 is already out of support. NAV 2017 reaches the end of extended support in January 2027, and NAV 2018 follows in January 2028.

NAV won't stop running on those dates, and the support date isn't the one to plan around. From late 2026, a little more than a year of runway sounds workable. Count backward from how long a move to Business Central actually takes, add the time to choose an approach and a partner, and for most companies on NAV the real deadline is already here.

When Does Dynamics NAV Support End?

NAV follows Microsoft's Fixed Lifecycle Policy: roughly five years of mainstream support after a release, then up to five years of extended support. So whether your Navision system is still supported depends entirely on which version you run.

Extended support is thinner than its name suggests. Microsoft provides security updates and paid support, with no non-security fixes, new features, or design changes. Mainstream support for NAV 2018 ended in January 2023, which means every NAV version has gone years without regular updates.

There's one more date worth knowing. Microsoft has set April 30, 2031 as the end of sale for Dynamics NAV. After that, NAV customers can no longer renew Service Plans like the Enhancement Plan or add licenses and users. Some sources describe 2031 as continued maintenance. It's a commercial cutoff, and security updates for NAV 2018 still end in January 2028.

Is Dynamics NAV the Same as Business Central?

Mostly, yes. That's the biggest difference between a NAV situation and a Dynamics GP one.

Microsoft acquired Navision in 2002, in a deal that also brought in Axapta, and added it to the Great Plains business it already owned. Navision took the Dynamics NAV name in 2005. In 2018 Microsoft launched Dynamics 365 Business Central, online in April and on-premises in October, and its own documentation describes Business Central on-premises as Dynamics NAV renamed. People looking for "Navision Business Central" and "Navision 365" come from this product confusion.

The other two product lines went different ways. Axapta became Dynamics AX, then Dynamics 365 Finance and Supply Chain Management. Dynamics GP has no successor in its own line, so a company leaving it implements a different product, which is why Dynamics GP end of life is a migration story.

For a NAV company, moving to Business Central means moving to the next generation of the system it already runs. Data and history can come along, and much of the process logic carries over. It's still a real upgrade project, which matters once you start counting months.

What Changes When Your NAV Version Loses Support

Some of what companies expect to lose at end of support is already gone. Microsoft generally delivers tax and regulatory updates for Dynamics products during mainstream support, to customers with an active service plan. For NAV, mainstream support ended for every version by January 2023. Being in extended support doesn't mean Microsoft is keeping your US tax and regulatory changes current.

What goes at the end of extended support is the rest of support including new security updates and Microsoft's assisted support. Microsoft hasn't announced an extended security program for NAV like the ones it offers for SQL Server and Windows Server, and NAV has no security-only window after its end date. Once your version's support ends, newly discovered flaws in it stay unfixed.

Other parts of a NAV environment run on their own clocks:

• The servers and databases underneath. NAV runs on Windows Server and SQL Server, each with its own lifecycle. SQL Server 2016 left extended support in July 2026, and Windows Server 2016 leaves it in January 2027, so a supported NAV version can sit on an unsupported database. Upgrading the server doesn't reset NAV's clock, either.
• Add-ons. Each add-on vendor sets its own supported-version policy, so warehouse, EDI, shipping, and reporting tools may drop NAV on a different schedule than Microsoft.
• Payroll and tax filing. These often run through third-party products. Check with each vendor directly, since NAV's date won't tell you when they'll stop working.

Audit and insurance questions follow from the same gap. No rule turns unsupported financial software into an automatic audit finding. What auditors can ask is how you handle newly discovered vulnerabilities when the vendor no longer ships fixes, and what your plan is to replace the system. Insurers raise the same issue, and some cyber insurance applications have applicants confirm they have no end-of-life software or operating systems exposed to the internet.

NAV won't switch off, but it stops being maintained while everything around it keeps changing, and the distance grows every month.

Why Moving to Business Central Isn't a Simple Update

A direct successor makes the path clearer. It doesn't make it short.

Customizations come first. Most NAV environments were tailored over the years, and that work was written in C/AL, directly inside the base application. Business Central handles customization through AL extensions instead, so every customization has to be converted, replaced by standard functionality or an add-on, or retired. In our experience, that inventory shapes the size of the project more than anything else, and it's often where years of customization debt finally surface.

The older the version, the more steps the upgrade takes. NAV has been around longer than GP, and some companies still run releases from a decade or more ago. Microsoft's documented path takes NAV 2015 through 2018 to Business Central version 14, the last release built for C/AL code, then through an intermediate modern release to the current one, with the C/AL code converted to AL along the way. NAV 2013 and 2013 R2 have to reach NAV 2018 first. Each stop is real work, and none of them is a place to wait: Business Central 14 on-premises lost support in October 2025.

Even a company headed for the cloud goes through these steps, because Microsoft's cloud migration tools don't take NAV directly. The upgrade to Business Central on-premises comes first, and the move online follows.

Banking, EDI, payroll, reporting, and CRM connections all move with NAV, so each one has to be rebuilt or retested. Business Central also looks and works differently from older NAV clients, so the people who run the business on NAV need to relearn routine tasks while still doing their jobs.

Whether to carry your current system forward or start clean on Business Central is a separate decision, and it changes how much of this work you take on.

How Long a Move to Business Central Takes

For a mid-market NAV environment with real customizations and integrations, a full move usually takes six to nine months in our experience. A recent version with light customization and few integrations can go faster. An old version, heavy C/AL customization, or a long list of connected systems pushes it out longer and could take over a year.

The factors that stretch a timeline show up early, if you look for them:

• How old your version is, and how many upgrade steps it needs
• How many customizations you have, and how many still matter
• Add-ons that need a Business Central equivalent
• Integrations and the systems that depend on NAV data
• Data cleanup, and which history you want in the new system
• Your team's availability for decisions, testing, and sign-off

Why Your Real Deadline Is Already Here

Project time is only part of the calendar, because the decisions before kickoff and the timing of the cutover need room too.

NAV 2018's extended support ends in January 2028, days after a calendar year-end. A company still on NAV at that point closes its 2027 books on a system Microsoft no longer supports. A safer plan puts you live on Business Central around the third quarter of 2027, so at least one quarter-end close happens on the new system before year-end. Six to nine months of project work puts kickoff in late 2026 or early 2027. Evaluating options, choosing a partner, and contracting all come before that.

For most NAV 2018 companies, that means the decision work belongs in the next few months.

For NAV 2017 and older, the supported window has effectively closed. The practical step is to set a date for the move and decide how to manage the risk until then.

Microsoft's main cloud incentive runs out at nearly the same moment. Bridge to Cloud 3 discounts Dynamics 365 cloud licenses for eligible on-premises Dynamics customers, NAV included, and enrollment ends December 31, 2027. To qualify, a company generally needs NAV licenses bought before September 2024 and an Enhancement Plan that's still active. That plan matters for on-premises moves as well, because Microsoft ties its license transition from NAV to Business Central on-premises to an active Enhancement Plan. Letting it lapse while you decide can take options off the table.

Your Options

NAV companies generally choose among four paths, and each fits a different situation.

Stay on NAV for now. This works for a short, planned window, not as a strategy. Partners can keep you running after Microsoft stops, though no partner can ship a Microsoft security patch. Moving NAV to Azure or new hardware modernizes the infrastructure without changing any support date.

Upgrade to Business Central. An upgrade carries your data, history, and converted customizations forward. It fits when your processes still work and your customizations are manageable. Landing on-premises or online is a separate choice you'll make along the way.

Start clean on Business Central. A clean start rebuilds on standard Business Central and brings over essential data, such as master data, opening balances, setup, and some history, rather than the entire old database. Microsoft documents it as its own route. It fits when years of customization no longer match how the business runs. Partners disagree about which of these two paths is usually right, which is a fair sign the answer depends on your environment.

Re-evaluate the platform. A company that has grown into multiple entities, international operations, or complex supply chains may be better served by Dynamics 365 Finance and Supply Chain Management, and nothing requires staying with Microsoft at all. That question deserves a structured ERP selection. Your support date should decide when you evaluate, not what you pick.

Start With Your Version and Your Customizations

Microsoft's lifecycle dates are fixed, but the date that matters for your plan comes from your own environment. Start by confirming exactly which NAV version and build you run. Then take stock of what has been customized, which add-ons and integrations depend on NAV, how much history you need to keep, and how much of your team's time the move can realistically take. Those answers tell you how long the project will run, and how much time you actually have.

Ascendex helps NAV companies plan the move to Business Central and carry it through go-live and the months after, usually beginning with an ERP assessment that inventories what you're running and turns it into a timeline you can plan around. Learn more about our approach to NAV to Business Central upgrades and migrations.