Dynamics NAV Upgrade: Is Business Central the Right Successor?

Every Dynamics NAV release reaches the end of Microsoft support by 12 January 2028. NAV 2016 has been out of support since April 2026, NAV 2017 follows on 12 January 2027, and NAV 2018 a year later. Microsoft's answer is an upgrade to Dynamics 365 Business Central, and for many NAV customers that is the right call. For a manufacturer, a multi-country group or a company that needs parallel accounting standards, it often is not.

This guide lists every deadline with its Microsoft source, explains what the end of support actually changes, and shows when Business Central fits. The last part comes from running ERP Pilot's knockout scoring engine, the same one behind our quiz, on a typical NAV customer profile and changing one answer at a time. The partner pages that dominate this search all sell the Business Central upgrade; none of them tests whether it fits.

When does support end for your NAV or AX version?

For the three NAV releases still in use most often, support ends between April 2026 and January 2028. All of them follow Microsoft's Fixed Lifecycle Policy, and all of them are already past mainstream support. Dynamics AX 2012 R3, the predecessor of Dynamics 365 Finance & Supply Chain Management, left extended support in January 2023.

Microsoft support end dates for Dynamics NAV and AX

Date	What ends
11 Jan 2023	AX 2012 R3: extended support ends. Mainstream support already ended Oct 2021
11 Jan 2023	NAV 2018: mainstream support ends. From here: security updates only
15 Apr 2026	NAV 2016: extended support ends. No more security updates either
12 Jan 2027	NAV 2017: extended support ends. Last NAV 2017 security updates
12 Jan 2028	NAV 2018: extended support ends. The last NAV release goes out of support

Sources: Microsoft Lifecycle pages for NAV 2016, NAV 2017, NAV 2018 and AX 2012 R3, checked 4 Oct 2026. Dates as listed by Microsoft (Pacific Time).

Older NAV releases such as NAV 2009, 2013 and 2015 have been out of support for years. If you run one of them, the dates above matter less than the upgrade route, which is longer for you (see the section on upgrade paths below).

What actually changes when NAV support ends?

Your system keeps running. What stops is Microsoft's servicing. Under the Fixed Lifecycle Policy, extended support already means security updates only: Microsoft does not accept requests for design changes or new features, and non-security updates are not available. After the extended end date, the security updates stop too.

For a NAV 2017 or 2018 customer that has three practical consequences:

• No more security patches for the application after the end date. Auditors and cyber insurers increasingly ask about unsupported software in finance systems.
• Regulatory change becomes your partner's problem. Microsoft stopped shipping non-security updates when mainstream support ended. New tax rules, e-invoicing mandates and reporting formats have to come from your partner or an add-on, and you carry the risk that nobody builds them for an unsupported release.
• The platform underneath ages with it. NAV depends on SQL Server and Windows Server versions that have their own end dates, so staying on NAV eventually means staying on an unsupported stack.

Is Business Central the right successor for your company?

For a small, single-country NAV customer without complex manufacturing, yes: Business Central ranks first in ERP Pilot's scoring and stays first even when on-premise hosting or heavy customisation is required. Three answers move it down clearly: manufacturing depth, operating in several countries, and the need for parallel accounting standards. Company size moves it down more gently.

We ran the replay on 4 October 2026 with our scoring engine across all 20 ERP systems in the quiz. The baseline profile is a typical NAV customer: wholesale distribution, 21 to 100 employees, one country and one legal entity, local GAAP, cloud is fine, moderate customisation, moderate use of Microsoft 365, and "Dynamics NAV / Business Central" as the current system. We then changed one answer at a time and recorded where Business Central lands.

Business Central's score for a NAV customer when one answer changes

	Score and rank of Business Central (of 20 systems)
Baseline (distributor, 21 to 100 staff, 1 country)	105, rank 1
On-premise or private hosting required	110, rank 1
Heavy or unique customisation	105, rank 1
101 to 500 employees	100, rank 2
2 to 5 countries	95, rank 2
Standard discrete manufacturing	80, rank 6
501 to 2,000 employees	65, rank 3
6 to 20 countries	45, rank 3
Parallel accounting standards	knocked out

Source: ERP Pilot scoring engine, replay of one stated NAV profile with one answer changed per row, 4 Oct 2026. Base: the 20 ERP systems in the ERP Pilot quiz. Dark bars: Business Central loses first place.

What the replay shows, answer by answer:

• Deployment and customisation do not change the verdict. Business Central is still sold for on-premises use, so "on-premise required" knocks out seven more systems that are cloud-only, but not Business Central, which gains five points. Heavy customisation leaves its score unchanged.
• Manufacturing is the biggest single shift. With standard discrete manufacturing, Business Central drops to sixth place behind manufacturing specialists: proALPHA leads with 100 points, Epicor Kinetic and SYSPRO follow with 90. With complex, variant-based manufacturing its score falls to 50.
• International growth favours other systems. At two to five countries Oracle NetSuite leads with 115 points; at six to 20 countries NetSuite (110) and Dynamics 365 Finance & Supply Chain Management (100) are far ahead of Business Central (45).
• Size moves the line towards Dynamics 365 Finance & SCM. At 101 to 500 employees the two Microsoft products tie on 100 points. At 501 to 2,000, Finance & SCM leads with 105 against 65.
• Parallel accounting standards are a hard knockout. If you need true parallel ledgers, for example local GAAP and IFRS posted side by side, our engine rules Business Central out because it has no parallel-ledger architecture. Adding IFRS reporting without parallel ledgers does not change its rank.

When is Dynamics 365 Finance & SCM the better Microsoft option?

When the company has outgrown the mid-market. In our replay, Dynamics 365 Finance & Supply Chain Management overtakes Business Central from about 500 employees and in groups operating in six or more countries. It is also the official successor for Dynamics AX customers.

The trade-off is cost and deployment. Finance & SCM is cloud-only in ERP Pilot's data, so an on-premise requirement rules it out, and its list price of $210 to $300 per user and month is more than twice Business Central's $80 to $110. Microsoft prices Finance and Supply Chain Management as separate apps, so a manufacturer that needs both pays for both. Our Dynamics 365 Finance & SCM review covers the functional differences, and the SAP vs Dynamics 365 comparison covers the most common alternative at this size.

When should a NAV customer look beyond Microsoft?

When manufacturing or multi-country finance is the core of the business. Those are the two areas where Business Central's lead disappears in our scoring, and where specialised systems score higher than either Microsoft product.

The last row needs a word of caution. With parallel accounting standards in an otherwise small distribution profile, only the S/4HANA editions survive in our engine and none of them scores well, because they are built for much larger companies. That is a signal to test the requirement itself: many groups report IFRS through consolidation rather than parallel ledgers in every entity, which keeps the mid-market systems in play. Your own answers will move all of these rankings, so treat the profiles here as a starting point, not a recommendation.

Upgrade or clean start: how does the move to Business Central work?

Microsoft documents two routes, and both start the same way. According to Microsoft's NAV migration guide (updated June 2026), NAV 2015 to 2018 first upgrade to Business Central version 14 on-premises, then to a current on-premises version, and only then to Business Central online. NAV 2013 and older add one or two intermediate steps.

• Full migration carries over all data and customisations. Every C/AL customisation has to be rewritten as an AL extension first; data from tables with code customisations cannot be carried forward otherwise.
• Reimplementation moves only master data, balances, setup and a subset of posted history, and does not require converting customisations. It is the route for companies that want to return to standard processes.

Two points that rarely make it into partner material:

• On-premise is still possible, but the treadmill is faster. Business Central on-premises follows Microsoft's Modern Lifecycle Policy. Each release is supported for about 18 months, for example version 29.x from 1 October 2026 to 6 April 2028 according to the Business Central on-premises lifecycle page. Staying supported on-premises means upgrading roughly once a year instead of once a decade.
• The customisation question decides the cost. A NAV system with years of C/AL changes is closer to a reimplementation than an upgrade, whichever target you choose. That is also the moment where comparing Business Central with other systems costs the least, because you are rebuilding either way. Our ERP migration guide covers both approaches in detail.

What does the move from NAV cost?

For 50 users over three years, ERP Pilot's pricing data puts Business Central at roughly $169K to $348K including implementation, Dynamics 365 Finance & SCM at $478K to $940K and proALPHA at $194K to $570K. The implementation range is wide because it depends mostly on how many NAV customisations you rebuild.

Source: ERP Pilot pricing data (Microsoft list prices, market research for proALPHA), last verified September 2026. 3-year total = licences for 36 months plus implementation, calculated with the method of our TCO calculator. Real quotes depend on your partner and negotiated discounts.

Two cost items are specific to NAV customers. First, licences: NAV was mostly bought as a perpetual licence with an annual enhancement plan, while Business Central online is a subscription, so the fair comparison is your current enhancement fee against the new monthly fee, not zero against the new fee. Second, the customisation rebuild, which is usually the largest single item. For every system in this table, see the ERP pricing guide.

What should a NAV customer decide before support ends?

Four decisions, in this order, because each one narrows the next:

1. Which NAV version are you on, and when does its support end? NAV 2016 is already out of support, NAV 2017 ends on 12 January 2027 and NAV 2018 on 12 January 2028. That sets your timeline.
2. Does your business still fit Business Central? Check the three answers that moved it in our replay: manufacturing depth, number of countries, and parallel accounting standards.
3. Upgrade or reimplementation? Count the customisations you still need. If most of them exist to work around old limitations, a reimplementation is cheaper and opens the field to other systems.
4. Cloud or on-premises? Both remain possible for Business Central. On-premises means a yearly upgrade cycle to stay supported; decide whether your IT can carry that.

Once those four are answered, the shortlist usually has two to four systems on it, and the evaluation can start from your requirements rather than from Microsoft's upgrade path.