Dynamics NAV vs Business Central: what actually changes when you move

Business Central is NAV's successor, not a different product. Here is what changes in deployment, licensing, upgrades and customization, and why the 2028 support date matters.

TSTech Sarwar team4 min read · Published November 18, 2026

If you run Microsoft Dynamics NAV, Business Central will feel familiar. It grew out of NAV, so the chart of accounts, posting groups, item cards and most of the processes your team knows are still there. What has changed is everything around them: where the system runs, how you pay for it, how it is updated and how it is extended.

This guide walks through those differences so you can decide when and how to move.

Where NAV stands today

NAV 2018 was the last NAV release. Its mainstream support ended in January 2023 and extended support ends on January 11, 2028. Until then Microsoft ships security updates only: no new features, no regulatory changes. Older versions are already past that point; NAV 2016 left extended support in April 2026 and NAV 2017 follows in January 2027.

NAV will keep running after those dates. The risk is that each year it becomes harder to keep secure, harder to connect to modern tools and harder to find people who want to support it.

The key differences at a glance

AreaDynamics NAVBusiness Central
AvailabilityNo longer soldCurrent Microsoft product
DeploymentOn-premises, on your serversMicrosoft cloud (most customers) or on-premises
LicensingPerpetual licence plus annual maintenancePer-user monthly subscription
UpdatesUpgrade projects every few yearsTwo major release waves a year, plus monthly updates
CustomizationChanges made in the base codeExtensions that sit beside the base code
IntegrationMostly custom-builtNative links to Microsoft 365, Teams, Power BI and Power Platform
AINoneCopilot and AI agents built in

Deployment: from your server room to Microsoft's cloud

Most NAV systems run on a company's own SQL Server, with backups, patching and remote access handled by IT. Business Central online removes that work: Microsoft hosts the database, applies updates and provides the security and availability. You can still run Business Central on-premises if you have a strong reason, but most of the benefits below come with the cloud version.

Licensing: from perpetual to subscription

NAV was bought once and then carried an annual enhancement plan. Business Central online is a subscription. Business Central is licensed per named user: Essentials lists at US$80 per user per month, Premium (adds manufacturing and service management) at US$110 and Team Members at US$8 for light users. In Canada those are CA$108.50, CA$149.20 and CA$10.90. These list prices took effect on November 1, 2025.

The subscription covers hosting, updates and the platform, so when you compare costs, include what you currently spend on servers, SQL licences, backups and the upgrade projects NAV needs every few years.

Updates: no more big-bang upgrades

In NAV, moving to a newer version meant a project. Business Central receives two major release waves a year (spring and autumn) plus monthly updates, applied by Microsoft in a window you choose. New features, regulatory changes and Copilot capabilities arrive continuously, and you stop falling behind.

Customization: the biggest technical change

NAV allowed partners to change the standard code directly. That flexibility is the main reason NAV upgrades were expensive: every change had to be re-merged into each new version.

Business Central doesn't allow that. Custom features are built as extensions in the AL language, which sit beside the standard application and survive updates. Part of any NAV move is deciding which customizations to:

  • drop, because Business Central now does it as standard
  • replace with an app from Microsoft AppSource
  • rebuild as an extension, because it is genuinely unique to your business

Upgrade or re-implement?

There are two routes. A technical upgrade carries your data, history and setup across, converting customizations to extensions. A fresh implementation starts clean, bringing over open balances, master data and a defined amount of history. Heavily customized or very old NAV databases are often better served by a fresh start; well-kept, lightly customized ones can usually be upgraded. We cover the trade-offs in NAV to Business Central: upgrade vs re-implementation.

When to start

Allow at least six to nine months for a typical NAV move, including data clean-up, testing and training. Starting in 2026 or early 2027 leaves room to schedule go-live around your year-end rather than against the January 2028 deadline.

If you'd like a second opinion on your NAV database and the right route, see our Upgrade to Dynamics 365 service.

Sources: Dynamics NAV lifecycle dates (Encore) · NAV 2018 support timeline (ERP Research) · Business Central licensing and pricing (Encore)

Want to talk about your Dynamics 365 project?

Book a free 30-minute call with someone who'd actually work on it.