Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Dynamics NAV, AX and GP End of Life: 5 Exit Options Compared

Verified Microsoft support dates, 5 exit paths (Business Central, F&O, third-party support, another vendor, coexistence) and a recommendation by profile for CIOs and CFOs.

Dynamics NAV, AX and GP End of Life: 5 Exit Options Compared

Dynamics NAV, Dynamics AX and Dynamics GP have a lot in common: they served their users well, they still run in many mid-sized companies, and their support clock is now plainly visible on Microsoft’s website. For a CIO or CFO, the question is no longer “do we need to move?” but “to what, and in what order?”

This article compares five exit paths and gives a recommendation by profile. It builds on three guides on this blog without repeating them: the Business Central vs Finance & Operations selection guide, the 8-step legacy ERP retirement plan and the replatforming business case. The scope here is strictly Microsoft legacy.

Where Each Product Stands: The Lifecycle

The dates below come from Microsoft’s official Lifecycle pages. Microsoft publishes them in Pacific time, which can shift a date by one day: retain the month and year, and check the exact version of your installation.

ProductEnd of mainstream supportEnd of extended supportSource
Dynamics NAV 2018January 2023January 2028Microsoft Lifecycle
Dynamics NAV 2013 (example of an earlier version)January 2018January 2023Microsoft Lifecycle
Dynamics AX 2012 R3October 2021January 2023Microsoft Lifecycle
Dynamics GP (product support and updates)December 31, 2029April 30, 2031 (security fixes)Microsoft, GP end-of-support announcement

Three practical takeaways.

NAV: the last release, NAV 2018, stays in extended support until January 2028. Earlier versions have older deadlines, to be checked one by one on the matching Lifecycle page. Many companies believe they are “covered” when they are on a version whose extended support has already ended.

AX 2012 R3: extended support ended in January 2023. Microsoft notes on its page that mainstream and extended support were extended compared with the original schedule. Older versions (AX 2009 and base AX 2012) do not get more favorable dates: check them against the same source. Microsoft publishes an upgrade guide from AX 2012 to Finance & Operations.

GP: this is the most recent and the most open-ended case. Microsoft announced the end of support in September 2024, then pushed the product update date from September to December 2029 so as to cover a full year of payroll and tax obligations. Security fixes run until April 30, 2031. Microsoft steers GP customers toward Business Central.

A useful point of vocabulary: “end of support” does not mean “the software stops working.” It means no more regulatory updates, no more fixes and, eventually, no more answers from the vendor when something breaks. For an ERP that carries your accounting, payroll or invoicing, that is exactly what matters.

The 5 Exit Paths

Option 1. Business Central (cloud or hosted)

Best for: SMEs and mid-market companies with a standard functional scope (finance, purchasing, sales, inventory, light manufacturing) coming from NAV or GP.

Strengths: it is the direct descendant of NAV, with a user experience and data logic your teams already know. Microsoft documents a migration path from NAV and positions Business Central as the recommended destination for GP. The partner ecosystem is broad and extensions are distributed through AppSource.

Risks: moving from C/AL code to AL extensions is a real undertaking if your NAV is heavily customized. Microsoft states that Business Central Online runs extensions only: all customization code has to be rewritten. And the continuous update model requires regular testing.

Typical timeline: a few months for a lightly customized NAV, noticeably longer for a heavily modified one. The extent of customization, not company size, is what moves this figure.

Option 2. Dynamics 365 Finance & Operations

Best for: AX 2012 users (the natural path) and multi-country, multi-entity groups with manufacturing, supply chain or advanced accounting needs.

Strengths: continuity with AX (same family, same concepts, a similar data model), functional depth and the ability to support an international group. It is the official destination documented by Microsoft for AX.

Risks: higher licensing and running costs than an SME solution, and a project that remains a full enterprise ERP project. Moving from the X++ customization model to extensions requires redesign work, and F&O skills are scarcer and more expensive than Business Central skills. To choose between the two Microsoft products, see the selection guide.

Typical timeline: that of an enterprise ERP implementation, generally more than a year as soon as several countries are involved.

Option 3. Stay put with third-party or extended support

Best for: companies whose version is stable and has little exposure (no open web portal, few integrations) and which need time to prepare a real migration. It is also the right answer for GP, whose end of support is far off.

Strengths: no immediate project, a smoothed budget and the chance to prepare the change properly. Third-party providers offer maintenance contracts for versions that have reached end of support.

Risks: third-party support is not a substitute for the vendor. It does not produce official regulatory updates (tax, e-invoicing) and cannot fix a flaw in the product itself. C/AL, X++ and GP skills are getting rarer as people retire. This is a holding solution, not a destination.

Typical timeline: a short-term decision that only makes sense with a written exit date.

Option 4. Switch vendors

Best for: companies that have to rework their processes anyway, that want to end their dependence on one vendor or whose Microsoft licensing model is becoming a drag.

Strengths: migration is a chance to reset your processes. Depending on the profile, there are several serious candidates: Odoo or Acumatica for SMEs that want flexibility, Sage X3 or Cegid for markedly French or European needs, NetSuite or Infor for more international or industry-specific organizations. For detailed comparisons, see our Cegid, Sage X3 and Dynamics 365 comparison (in French).

Risks: you lose continuity of data and business logic, you rebuild your integrations and you train everyone. C/AL or X++ customizations are not “migrated”: they are redefined or dropped. The risk is recreating the old spaghetti in the new tool.

Typical timeline: that of a full ERP project, with a longer scoping phase than for a version upgrade.

Option 5. Phased replatforming and coexistence

Best for: groups with several entities, several ERPs or a heavy reliance on bespoke modules, which cannot do a single cutover.

Strengths: you reduce risk by migrating entity by entity or domain by domain (finance first, then purchasing, then production), keeping the old system in read-only mode or in partial production. We detail this approach in our article on legacy ERP and cloud coexistence and on modernization without replacement.

Risks: two systems to maintain, temporary interfaces that become permanent, and more complex data governance. Without a switch-off date for the old system, coexistence becomes a permanent and costly state.

Typical timeline: the longest in calendar time, but the lowest risk per step.

Comparison Table and Recommendation by Profile

Criterion1. Business Central2. F&O3. Third-party support4. Another vendor5. Coexistence
Continuity with the existing systemStrong from NAV and GPStrong from AXTotalLowGradual
Code redesign effortHigh if NAV is heavily customizedHigh (X++)NoneFull redefinitionSpread out
Multi-country coverageMediumStrongThat of the existing systemDepends on the vendorDepends on the target
Main riskC/AL rewrite into ALCost and skillsObsolescenceLoss of continuityDouble maintenance
HorizonShort to mediumMedium to longShort term onlyMedium to longLong

SMEs under 100 people: path 1 is the default answer, whether you are on NAV or GP. If your ERP is lightly customized and you are on GP, path 3 buys you time, but set a decision date. If your processes need rethinking and you have no reason to stay with Microsoft, look at path 4 without preconceptions.

Industrial mid-market: if you are on AX 2012, path 2 is the most coherent functionally. If you are on NAV with complex production, compare Business Central and Finance & Operations honestly on your production requirements, not on the price tag alone. Path 4 deserves a serious comparison if your processes have changed a lot.

Multi-country group: path 5 is generally the most realistic, with Finance & Operations or another group-level ERP as the target and a subsidiary-by-subsidiary migration. A single big-bang cutover is rarely defensible.

What Is Specific to Microsoft Legacy

C/AL and X++ customizations. This is the topic that derails budgets. Business Central requires AL extensions, Finance & Operations requires X++ extensions. Before choosing, inventory your customizations and sort them into three categories: those the standard product now covers (to remove), those that carry a competitive advantage (to refactor as extensions) and those no one uses anymore (to drop). This inventory often changes the option you pick.

Data migration. Migrating the full history is rarely useful. Define what must live in the new ERP (balances, items, parties, open items) and what can be archived read-only, within your legal retention obligations. The 8-step decommissioning plan covers archiving in detail.

ISVs and add-ons. Many NAV, AX and GP installations rely on third-party solutions (payroll, logistics, EDI, manufacturing). For each one, check whether a compatible version exists on the target, whether the vendor is still active and whether its licensing model has changed. An ISV with no equivalent can weigh more in the decision than the ERP itself.

Integrations. Connectors built on old interfaces (flat files, direct SQL database access) have to be rebuilt on APIs. This item is consistently underestimated.

What It Costs Not to Decide

Not deciding is a decision, with three costs.

Security risk. Once mainstream and extended support are over, newly found vulnerabilities are no longer fixed by the vendor. For GP, Microsoft states that security fixes are issued only at its discretion and for critical vulnerabilities until April 2031, which leaves little margin.

Regulatory risk. Without official updates, it is up to you to track changes in tax rules, e-invoicing and filings. That is costly and error-prone.

Skills risk. C/AL, X++ and GP developers are becoming fewer, and partners are redirecting their teams to current products. Every internal departure increases dependence on a handful of people.

There is also a less visible cost: the longer you wait, the more customization debt piles up, and the harder the eventual migration becomes.

A 5-Step Roadmap and Decision Criteria

  1. Inventory. Exact version, end-of-support date (Microsoft Lifecycle source), customizations, ISVs, integrations, data volumes.
  2. Qualify the scope. Sort each customization: now standard, to refactor, to drop.
  3. Choose the path. Apply the criteria below and explicitly rule out two of the five options, so the decision is documented.
  4. Frame it with a pilot. Migrate one domain or one small entity to measure the real effort before committing to the overall budget.
  5. Plan the shutdown. Switch-off date for the old system, archiving, access revocation.

Decision criteria: depth of customization, multi-country footprint, ISV dependence, skills available in-house and at the partner, the support calendar of your version, appetite for process change.

Going Further

To dig deeper, read our Business Central vs Finance & Operations selection guide, the 8-step decommissioning plan and the replatforming business case. If you want an opinion on your own situation, contact us for a path audit: an inventory of your versions, customizations and ISVs, followed by a reasoned recommendation.