Still on Dynamics AX 2012 after end of support: ERPNext vs Dynamics 365 Finance and SCM for mid-size manufacturers

Who this guide is for

This guide is for finance directors, IT heads and operations leaders at manufacturers and distributors of roughly 100 to 1,000 people who still run Dynamics AX 2012, usually R3, on their own servers or with a hosting partner. AX probably runs your ledgers, purchasing, inventory, production orders and warehouse, with X++ modifications a partner built over many years.

We implement ERPNext, so read our view with that in mind. We also tell AX customers when Dynamics 365 Finance and Supply Chain Management (SCM) is the better destination, and for a good share of AX estates it is. What we offer is a plain reading of Microsoft’s own documents, official prices in USD and GBP, and a way to test ERPNext on your data before anyone signs a multi-year contract.

This guide is part of our series on legacy ERP deadlines. The legacy ERP end-of-support hub lists every vendor date we have confirmed. If part of your group runs Business Central 14 or SAP ECC, see our Business Central 14 guide and our SAP ECC EHP 5 guide.

Sources, checked on Nov 15, 2026: the Microsoft Lifecycle: Dynamics AX 2012 R3 page, the Microsoft Lifecycle FAQ for Dynamics, Microsoft’s AX 2012 to finance and operations upgrade overview, Microsoft’s AX 2012 data upgrade guide, Microsoft’s finance and operations extensibility documentation, the Dynamics 365 Finance pricing page (US) and Dynamics 365 Finance pricing page (UK), the Dynamics 365 Supply Chain Management pricing page (US) and Dynamics 365 Supply Chain Management pricing page (UK), the Frappe Cloud pricing page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.

What Microsoft says about AX 2012

The AX 2012 R3 lifecycle page follows the Fixed Lifecycle Policy and shows its dates as Pacific Time timestamps (extended end displayed as 1/11/2023 6:59:59 AM). The Lifecycle FAQ states the date in words, January 10, 2023, so we use that.

Microsoft’s advice in the same FAQ is direct: customers “are advised to upgrade to the latest version of finance and operations apps, such as Dynamics 365 Finance, Supply Chain Management, Commerce, and Project Operations”. AX 2012 and AX 2012 R2 customers should upgrade through AX 2012 R3 using the upgrade tool.

What nearly four years unsupported means

Many AX 2012 sites still run well day to day. The risk is not that the system stops; it is that nothing new arrives and every problem is yours. In practice:

• No security hotfixes from Microsoft since January 2023. Any new vulnerability in AX itself stays open unless you mitigate it around the application.
• Your stack ages with it. AX sits on Windows Server, SQL Server and, for many sites, SQL Server Reporting Services and other Microsoft components, each with its own lifecycle date. Check each version you run on Microsoft’s lifecycle site; an unsupported database or operating system under an unsupported ERP is a common audit and cyber-insurance finding.
• Tax and regulatory changes are on you. With no Microsoft updates, changes to tax reporting, e-invoicing or statutory formats have to be built and tested by your own team or partner.
• Skills get scarcer. The people who know your X++ layers and AX 2012 infrastructure are retiring or moving to Dynamics 365 work.
• The upgrade window narrows. Microsoft’s upgrade tooling is aimed at the current finance and operations release, and its documentation asks you to be on the latest AX 2012 R2 or R3 cumulative update first. The further your system drifts, the more clean-up the upgrade needs.

None of this forces a move this quarter. But if you are reading this, someone has probably asked “what is our plan?”, and “keep going” is a plan only if you can defend it to your auditor and your insurer.

Your four realistic options

For smaller AX entities, Microsoft also sells Business Central, and our NAV 2018 guide covers how ERPNext compares with it. Most 100 to 1,000 person AX sites, though, are choosing between the two Dynamics 365 routes and a non-Microsoft ERP.

The Dynamics 365 upgrade path, from Microsoft’s own documentation

If you go the Microsoft way, read Microsoft’s AX 2012 to finance and operations upgrade overview before you talk to partners. The points that matter for planning:

• Upgrade is supported only from AX 2012 R2 or AX 2012 R3, and Microsoft asks you to apply the latest cumulative update first.
• The process brings forward custom code and runs a data upgrade, so you can keep your full transactional history. That is the biggest practical advantage over any reimplementation, ERPNext included.
• Some deprecated features block the upgrade: Microsoft names virtual companies and data partitions as examples. It recommends running the Upgrade analyzer tool if you are unsure.
• Microsoft is candid that AX 2012 upgrades “are complex” and that the tools “should be seen as a framework rather than a complete solution”. Expect data clean-up, tuning and rework.
• Microsoft’s data upgrade guide requires the AX 2012 database collation to be SQL_Latin1_General_CP1_CI_AS (or changed to it) and recommends running the first data upgrade in a development environment, because sandbox iterations take hours.
• Customisation changes shape. Microsoft’s extensibility documentation says extensibility is “the only customization framework” in Finance, Supply Chain and Commerce and “overlayering isn’t supported”. X++ that modified standard AX code in layers has to be refactored into extensions or dropped.

That last point is why “upgrade” can cost close to a reimplementation for heavily modified AX systems. Ask your partner to size the extension refactoring from the Upgrade analyzer output, not from a slide.

How AX 2012 concepts map to ERPNext

ERPNext is a full ERP on the Frappe framework. The mapping below is what we test first with AX manufacturers and distributors. Where ERPNext is thinner, we say so.

Data moves through ERPNext Data Import documentation (CSV or Excel, insert or update), the ERPNext Chart of Accounts documentation importer, ERPNext opening balance documentation and ERPNext Stock Reconciliation documentation for stock. That is a reimplementation: you bring masters, open items and balances, and keep AX read-only (or an archive) for history.

Where Dynamics 365 Finance and SCM is the better fit

We would rather lose a deal than sell ERPNext into the wrong estate. Dynamics 365 Finance and SCM is usually the better choice when:

• You need your full AX transactional history in the live system, not in an archive. Only the Microsoft upgrade path keeps it.
• You run many legal entities across countries with heavy intercompany, consolidation and local statutory requirements that Microsoft and its partners already cover.
• Your manufacturing relies on advanced planning and finite scheduling, process or mixed-mode manufacturing, or deep warehouse automation. ERPNext’s capacity planning is basic: its documentation says each operation should start and end on the same day for scheduling to work.
• Your group is standardised on Microsoft (Dataverse, Power Platform, Microsoft 365) and wants one vendor and one support model.
• Your X++ extensions encode real competitive advantage and your partner can refactor them as extensions at a cost you accept.

ERPNext is the better fit when the opposite is true: a few legal entities, discrete make-to-stock or make-to-order manufacturing, standard distribution, history you are happy to archive, and a willingness to cut customisations you no longer need.

Licence costs: official prices in USD and GBP

Microsoft publishes base-plan list prices for both finance and operations apps. Checked on Nov 15, 2026, paid yearly, UK prices excluding VAT:

A worked example at list price, assuming every user is on one base plan at the same price (real estates mix Finance users, SCM users and lighter licences, and Microsoft’s licensing guide sets the rules for users who need both apps, so ask your partner for a line-by-line licence breakdown):

These figures are list price × users × 12 from Microsoft’s own pages. They exclude implementation, the upgrade or reimplementation project, partner support, Copilot credits and any discounts.

Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.22), checked on Nov 15, 2026. The GBP figures are indicative conversions, not Frappe prices.

Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3238 per £1 for 12 Nov 2026, the latest published figure when we checked on Nov 15, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.

ERPNext’s cost is implementation, hosting and support, not licences. Ask for written proposals on the same scope for both paths and compare five-year totals, including the cost of staying on AX while you decide.

A practical plan for AX 2012 sites

Decision table

Best for, and wrong choice when

Frequently asked questions

Related articles