Dynamics NAV to Business Central Upgrade Guide: Timeline, Path and Support Dates in 2026.

If you run Dynamics NAV today, the open questions are the route and the date. This guide covers the four things teams ask first: when NAV support ends, how long the upgrade takes, which path your version takes, and what moves in each option.

When does Dynamics NAV support end?

NAV 2016 left extended support in April 2026. NAV 2017 follows in January 2027 and NAV 2018 in January 2028. Extended support includes security updates at no extra cost, so when it ends, Microsoft stops providing standard security updates for that version.

Source: Microsoft Lifecycle pages for NAV 2016, NAV 2017 and NAV 2018, and the Fixed Lifecycle Policy. Checked October 2026.

What end of support means for a NAV system

End of support does not switch NAV off. It changes what Microsoft provides. Under Microsoft’s Fixed Lifecycle Policy, extended support includes security updates at no extra cost. After extended support ends, the policy lists security updates only through an Extended Security Update program, and non-security updates are no longer available.

• Security: no further standard security updates for that NAV version.
• Platforms: Microsoft says in its Dynamics lifecycle FAQ that it cannot guarantee an older Dynamics version will support features that exist only in a newer Windows release. New operating system and database versions are a risk for an older NAV install.
• Help: Microsoft keeps self-help online content available for at least 12 months after a product reaches end of support.

So the deadline is about risk, not a hard stop. The longer NAV runs past its date, the more of that risk your team carries on its own.

How long does a NAV to Business Central upgrade take?

A focused upgrade with light customization usually runs 8 to 12 weeks. Most upgrades run 3 to 6 months, depending on data volume, customization and integrations. A heavily customized environment with multiple integrations can run 6 to 9 months.

Your starting version also matters. NAV 2013 and 2009 add steps before the main route starts (see below), and a multi-company setup can be phased by company to reduce risk.

Customizations, integrations, data history and ISV add-ons are what move a project between tiers. Each C/AL modification is converted to an AL extension, replaced by standard Business Central, or retired. Every connected system has to be rebuilt or reconnected, and each ISV add-on needs a Business Central version or a replacement. For project costs, a license price calculator and a fixed-price quote, see our NAV to Business Central upgrade services.

Which upgrade path applies to your NAV version?

NAV 2015 through NAV 2018 upgrade to Business Central 14 on-premises first, then to Business Central on-premises version 25 or later, then to Business Central online if you want the cloud. Older versions need extra steps to reach that starting line. Pick your version below to see the route.

Why Business Central 14 is the first step

Business Central 14 (April 2019) is the last version that supports hybrid mode, Object Designer and the Windows client. From version 15 on, development is AL only. That makes 14 the last point where C/AL code and AL code can still run side by side.

Understanding the versions

NAV 2018 (version 11) was the first version that could run in hybrid mode, a mix of the C/AL and AL development environments. Business Central 12, released in April 2018, was the first with the named-user licensing model. Business Central 13 followed in October 2018 and 14 in April 2019. Version 15 arrived in October 2019 with no Windows client, Object Designer or hybrid mode, and version 16 followed in April 2020. The timeline shows where the path forks.

Upgrade or re-implement: what moves in each?

Upgrade when your customizations and history are worth keeping. Re-implement when you want a clean start. A fresh implementation is a scoping option. Microsoft’s Business Central 14 reimplementation tool is a preview feature and is not meant for production use.

• Full migration: moves all data and customizations. C/AL customizations must be converted to AL extensions, and you upgrade to the latest version.
• Reimplementation: moves essential data only (master data, balances, a subset of posted history, setup). It skips extension conversion and does not carry legacy customizations forward. The specific BC14 tool is preview-only; use Microsoft’s reimplementation documentation when evaluating it.

The choice usually turns on how many of your customizations still earn their keep, and how much history your auditors and users need in the new system.

NAV vs Business Central at a glance

Sources: extensions in Business Central, Microsoft’s NAV migration guidance (online or on-premises), Dynamics 365 release plans (two release waves a year) and the NAV lifecycle pages. Checked October 2026.

Next steps

Start by finding out which version you run, how many customizations and integrations it carries, and how much history you need to keep. With those three answers, the timeline and the route are mostly decided. Running Dynamics GP instead? See our Dynamics GP to Business Central migration guide.