Search for “Dynamics ERP” and the results are a mix of names spanning two decades: NAV, AX, GP, SL, Business Central, Dynamics 365 Finance. For anyone outside the Microsoft partner ecosystem, that’s confusing enough to stall a research project before it starts — is AX still a thing? Is NAV the same as Business Central? Which one is actually current?

The short answer is that Dynamics ERP has one continuous history, not four separate stories. Microsoft assembled its ERP business by acquiring a handful of independent software companies in the early 2000s, ran those products in parallel under the Dynamics brand for over a decade, and then consolidated everything into a single cloud platform starting in 2016. Understanding that timeline makes sense of why the old names still surface in searches, job postings, and support forums — and which modern product actually replaced each one.

Where “Dynamics ERP” Came From

Microsoft didn’t build its ERP business from scratch — it bought it. Between 2001 and 2002, Microsoft acquired Great Plains Software and Navision A/S, the latter having already merged with Damgaard (maker of the Axapta ERP system) in 2000. Together with the earlier acquisition of Solomon Software, these deals gave Microsoft four separate, mature ERP products overnight, each with its own codebase, customer base, and target market.

The Four Original Dynamics ERP Products

Dynamics GP (from Great Plains Software, founded in Fargo, North Dakota) was strongest in the US mid-market, known for its accessible finance and accounting functionality and a large network of independent resellers across North America.

Dynamics SL (from Solomon Software) targeted project-based businesses and government contractors, with strong project accounting and job costing — a smaller, more specialized product than the other three, but a durable one in its niche.

Dynamics NAV (from Navision, a Danish company) was a highly configurable mid-market ERP with a large international partner network — the product most businesses outside North America associated with “Microsoft ERP” for years, thanks in part to its flexible, partner-customized deployment model.

Dynamics AX (from Damgaard’s Axapta, also Danish in origin) was built for larger, more complex organizations with multi-country, multi-currency operations — Microsoft’s answer for enterprise-scale manufacturing and distribution, and generally the most technically sophisticated of the four original products.

For over a decade, Microsoft sold and supported all four in parallel, each on its own release cycle, with separate partner channels, separate certification paths, and no shared cloud architecture between them. A NAV consultant and a GP consultant were, in practice, working with entirely different products that happened to share a corporate parent.

A Similar Story Played Out on the CRM Side

Dynamics ERP’s naming history isn’t unique — Microsoft’s CRM product went through a nearly identical consolidation. Dynamics CRM was rebranded as Dynamics 365 for Customer Engagement in 2016, then split further into standalone applications like Dynamics 365 Sales and Dynamics 365 Customer Service. Recognizing this pattern helps explain why “Dynamics 365” today isn’t one application at all — it’s an umbrella brand covering a whole family of separately licensable business applications, ERP and CRM alike, unified mainly by shared platform, identity, and data infrastructure.

The Shift to the Cloud: Dynamics 365

That changed in 2016, when Microsoft introduced Dynamics 365 as a unified cloud platform bringing CRM and ERP together under one brand, one subscription model, and — eventually — one common implementation approach across every application in the family. Rather than maintaining four disconnected ERP codebases indefinitely, Microsoft began consolidating its ERP investment around cloud-native successors to NAV and AX specifically.

What NAV and AX Became

Dynamics NAV was rebuilt and rebranded as Dynamics 365 Business Central, released publicly in 2018. It kept NAV’s mid-market positioning and much of its underlying logic, but moved to a modern cloud architecture with regular update cycles instead of multi-year version releases.

Dynamics AX followed a similar path, first rebranded as Dynamics 365 for Finance and Operations, then split in 2020 into two more focused products: Dynamics 365 Finance and Dynamics 365 Supply Chain Management. Together, they cover the same enterprise-scale ground AX did, now as separately licensable, cloud-native applications.

Dynamics GP and Dynamics SL took a different path. Rather than being rebuilt as new cloud products, they’ve continued as on-premise offerings with a defined support horizon — Microsoft chose to consolidate its cloud ERP investment around the NAV and AX lineages rather than modernize all four legacy platforms in parallel. Microsoft has confirmed that mainstream support for Dynamics GP ends December 31, 2029, with extended security-only support running through April 2031 — and new subscription licenses for GP stop being sold after April 2026. Microsoft’s stated migration path for GP customers is Business Central.

Why This History Still Matters When You’re Searching for “Dynamics ERP”

If you’re evaluating ERP today and keep running into references to NAV or AX — in old case studies, job descriptions, or a competitor’s implementation history — it helps to know exactly what you’re looking at. A “Dynamics NAV consultant” is doing largely the same work a “Business Central consultant” does today, just on an older version of related technology. A company that says it “runs Dynamics AX” is very likely either on Dynamics 365 Finance and Supply Chain Management already, or is a near-term migration candidate.

This matters practically during vendor evaluation and RFPs: a partner with deep NAV experience typically transfers that expertise directly to Business Central implementations, and the same is true for AX-to-Finance-and-Operations experience. The underlying product logic didn’t disappear — it moved to the cloud.

How to Tell Which Version You’re Actually Dealing With

A quick way to orient yourself: if a system is described as on-premise, tied to a specific numbered version, or supported by a local reseller rather than through a Microsoft-managed cloud subscription, it’s almost certainly one of the four legacy products still running. If it’s licensed monthly per user through Microsoft, updated automatically several times a year, and accessed through a web browser, it’s Business Central or Dynamics 365 Finance and Supply Chain Management — the current generation. Job titles and consultant CVs are usually the clearest signal, since most partners list the specific product versions they’ve implemented rather than just “Dynamics ERP” as a catch-all.

Where Dynamics ERP Is Headed

Microsoft’s ERP roadmap today is entirely focused on Business Central and Dynamics 365 Finance and Supply Chain Management, with Copilot and AI agents being layered into both at a fast pace — automated reconciliation, natural-language reporting, and anomaly detection are now standard parts of the roadmap rather than experimental features. The legacy products aren’t being modernized in the same way; they’re being supported on a fixed timeline while customers move to the cloud platform.

For businesses in the GCC specifically, this consolidation is worth watching closely, since regional partner networks — including long-standing NAV and AX implementation partners — have themselves been shifting their specializations toward Business Central and Dynamics 365 Finance and Supply Chain Management over the past several years. A partner still marketing deep expertise in the original on-premise products, without a clear cloud migration practice alongside it, is a signal worth asking about directly during vendor selection.

Key Takeaways

Dynamics ERP isn’t four unrelated products that happen to share a brand name — it’s one continuous history that started with four separate acquisitions and consolidated into two modern, cloud-native platforms: Business Central (from NAV) and Dynamics 365 Finance and Supply Chain Management (from AX). GP and SL remain supported on a defined timeline, with Business Central as Microsoft’s recommended landing spot. Knowing this lineage turns a confusing mix of old and new product names into a straightforward map of where your organization sits today — and where Microsoft expects it to go next.