Dynamics AX 2009, four years past support: is ERPNext the replacement?
Short answer
Microsoft ended extended support for Dynamics AX 2009 SP1 on April 12, 2022, per its Lifecycle FAQ for Dynamics; mainstream support had ended on October 9, 2018. AX 2009 sites have now run for more than four years with no security hotfixes. Microsoft’s recommended destination is the finance and operations apps, Dynamics 365 Finance and Supply Chain Management, listed at $210 / £161.50 per user per month each (paid yearly; UK price excludes VAT). But the route there is different from AX 2012: Microsoft says its AX 2009 Data migration tool is the only supported upgrade path, and its own documentation describes moving data, not code. So whichever way you go, you are re-implementing. That puts ERPNext (open source, GPL-3.0, no licence fee) on a more level footing than it is for AX 2012 sites. For 50 to 500 person manufacturers and distributors with mostly standard processes, it deserves a proposal next to Dynamics 365.
Contents
- Who this guide is for
- AX 2009 support dates, from Microsoft
- What four years without support means
- Microsoft’s path: the AX 2009 Data migration tool
- Why this levels the field for ERPNext
- Licence prices: Dynamics 365 vs ERPNext, in USD and GBP
- How AX 2009 concepts land in ERPNext
- Getting data out of AX 2009
- What to do with your X++ customisations
- A phased plan for leaving AX 2009
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, operations managers and IT leads at mid-size manufacturers and distributors still running Microsoft Dynamics AX 2009, usually SP1, often on servers and a SQL Server version that are themselves past support. Many of these sites stayed on AX 2009 because it worked, the X++ customisations encoded how the business runs, and the jump to AX 2012 or Dynamics 365 always looked bigger than the problem.
We implement ERPNext, so read our view with that in mind. Dynamics 365 Finance and Supply Chain Management is a strong product and, for larger, multi-entity or heavily regulated businesses, often the right destination. This guide sets out when it is and when it is not.
If you are on AX 2012 rather than AX 2009, read our Dynamics AX 2012 guide instead: AX 2012 R2 and R3 have a Microsoft upgrade path that carries data and code, which changes the comparison. Smaller Microsoft sites may also find our Navision guide and Dynamics GP guide useful. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 19, 2026: the Microsoft Lifecycle FAQ for Dynamics, Microsoft Lifecycle: Dynamics AX 2009, Microsoft’s AX 2009 Data migration tool (DMT) overview, Microsoft’s “Install the Data migration tool” article, Microsoft’s “Migrate to Dynamics 365 online” overview, 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 and Frappe Cloud server plans page, the ERPNext repository on GitHub, and the ERPNext documentation linked in each section.
AX 2009 support dates, from Microsoft
| Item | Date | Source |
|---|---|---|
| AX 2009 start date | August 14, 2008 | Microsoft Lifecycle page |
| Original release (pre-SP1) support ended | January 2011, under the service pack policy | Microsoft Lifecycle page |
| Mainstream support ended (AX 2009 SP1) | October 9, 2018 | Microsoft Lifecycle FAQ for Dynamics |
| Extended support ended (AX 2009 SP1) | April 12, 2022 | Microsoft Lifecycle FAQ for Dynamics |
Microsoft’s Microsoft Lifecycle: Dynamics AX 2009 page says AX 2009 follows the Fixed Lifecycle Policy and notes that the end of support for AX 2009 SP1 was extended from October 12, 2021 to April 12, 2022. The page shows its dates as timestamps (for example, extended end displayed as 4/13/2022 6:59:59 AM); we use the calendar dates from the Microsoft Lifecycle FAQ for Dynamics, which says security hotfixes were provided through the extended support period that ended on April 12, 2022.
The same FAQ says AX 2009 SP1 customers “should use the migration tool that is available” to move to the finance and operations apps, while AX 2012 and AX 2012 R2 customers should upgrade through AX 2012 R3. That difference is the heart of this guide.
What four years without support means
- No security hotfixes since April 2022. AX 2009 itself gets nothing new. Any vulnerability found since is permanent unless you can mitigate it around the system.
- An ageing stack underneath. AX 2009 runs on Windows Server and SQL Server versions of its era. Keeping them patched and supported is a separate problem that grows each year.
- No regulatory updates. Tax, e-invoicing and reporting changes since 2022 are handled with your own X++ changes or outside AX.
- Fading skills. X++ and MorphX developers who know AX 2009 well, and know your layers of customisation, are increasingly hard to hire.
Auditors and cyber insurers ask about unsupported software more often than they used to. If AX 2009 holds your financial ledger, expect the question.
Microsoft’s path: the AX 2009 Data migration tool
Microsoft’s Microsoft’s AX 2009 Data migration tool (DMT) overview says you can use the tool to migrate your data from AX 2009 to finance and operations, and that “using the DMT is the only supported upgrade path from AX 2009.” The process it describes is a data mapping exercise:
- Map source tables to target data entities with an Excel mapping file, which includes default data required in some tables.
- Apply conversions, default values and query filters to the source data.
- Select which legal entities to migrate, review source tables and row counts, and analyse virtual companies and their tables.
- Choose target dimensions for the source dimensions in use, review inventory dimensions, and select a chart of accounts for each legal entity, or consolidate several into one.
- Complete the basic ledger setup in the target, and apply data conversions by extended data type.
Microsoft’s Microsoft’s “Migrate to Dynamics 365 online” overview draws the contrast directly: AX 2012 customers can “move their data and code” through the upgrade path, while AX 2009 customers can use the DMT “to migrate your data”. In other words, your AX 2009 customisations are not carried forward; anything you still need has to be rebuilt as extensions in the finance and operations apps.
Check the tool’s status
Microsoft’s Microsoft’s “Install the Data migration tool” article still says, at the time we checked, that “the DMT is in private preview” and that its public release date is not set. Its prerequisites include AX 2009 SP1 5.0.1000.52 or later and SQL Server 2008 to 2016, and Microsoft says installation takes about seven hours. The Lifecycle FAQ describes the tool as available. Ask Microsoft or your partner which is current before you plan around it. The DMT overview also mentions a no-charge, no-obligation migration assessment through the Dynamics 365 Migration Program.
Why this levels the field for ERPNext
For AX 2012 sites, the case for Dynamics 365 includes an upgrade path that carries code and full history. AX 2009 sites do not have that. Both of their realistic options look like this:
| Step | To Dynamics 365 Finance and SCM | To ERPNext |
|---|---|---|
| Process design | Redesign in finance and operations terms | Redesign in ERPNext terms |
| Data | Mapped and moved with the DMT (data only) | Extracted from SQL Server, mapped and loaded with Data Import (ERPNext Data Import documentation) |
| Customisations | Rebuilt as extensions (Microsoft’s finance and operations extensibility documentation) | Dropped, configured, or rebuilt as Frappe apps and scripts |
| History | What you choose to migrate; archive the rest | Opening balances and open items; archive the rest |
| Licence | Per-user subscription (published prices below) | No licence fee |
| Hosting | Microsoft cloud (Microsoft’s migration overview covers Dynamics 365 online) | Self-host or Frappe Cloud |
So the decision is not “upgrade versus replace”. It is “which new system fits us better, at what running cost”. That is a fairer comparison than most AX sites assume.
Licence prices: Dynamics 365 vs ERPNext, in USD and GBP
Microsoft publishes US and UK list prices for the finance and operations base plans. Checked on Nov 19, 2026, paid yearly, UK prices excluding VAT:
| Plan | US price | UK price | Source |
|---|---|---|---|
| Dynamics 365 Finance | $210 per user/month | £161.50 per user/month | Dynamics 365 Finance pricing page (US); Dynamics 365 Finance pricing page (UK) |
| Dynamics 365 Finance Premium | $300 per user/month | £230.70 per user/month | Dynamics 365 Finance pricing page (US); Dynamics 365 Finance pricing page (UK) |
| Dynamics 365 Supply Chain Management | $210 per user/month | £161.50 per user/month | Dynamics 365 Supply Chain Management pricing page (US); Dynamics 365 Supply Chain Management pricing page (UK) |
| Dynamics 365 Supply Chain Management Premium | $300 per user/month | £230.70 per user/month | Dynamics 365 Supply Chain Management pricing page (US); Dynamics 365 Supply Chain Management pricing page (UK) |
| ERPNext | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud | Sites from $5/month; servers from $40/month | Indicative £3.79 / £30.29 | Frappe Cloud pricing page; Frappe Cloud server plans page |
A worked example at list price, assuming every user is on one base plan at $210 or £161.50. Real estates mix Finance users, SCM users and lighter licences under Microsoft’s licensing guide, which we have not modelled, and Microsoft notes that the prices shown may not reflect your actual price:
| Users | US list price (base plan) | UK list price (base plan, excl. VAT) |
|---|---|---|
| 25 users | $5,250 / month; $63,000 / year | £4,037.50 / month; £48,450 / year |
| 50 users | $10,500 / month; $126,000 / year | £8,075 / month; £96,900 / year |
| 100 users | $21,000 / month; $252,000 / year | £16,150 / month; £193,800 / year |
Microsoft’s Finance pricing page says Finance Premium comes with higher capacity and storage entitlements than Finance; the Supply Chain Management page describes SCM Premium as adding advanced planning, analytics and insights. UK prices are Microsoft’s own published GBP prices, not conversions. Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.79) and servers from $40 a month (about £30.29), checked on Nov 19, 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.3205 per £1 for 17 Nov 2026, the latest published figure when we checked on Nov 19, 2026. They are not official UK prices: Frappe does not publish a GBP list price for these plans, and your invoice currency, rate and VAT treatment may differ.
Licence is not the whole cost on either side. Implementation, data migration, extensions, testing and training usually dominate the first two years; we do not estimate them here because they depend entirely on your scope.
How AX 2009 concepts land in ERPNext
| AX 2009 | ERPNext | Notes |
|---|---|---|
| Legal entities (companies) | Companies | One ERPNext site can hold several companies |
| Virtual companies (shared tables) | Masters shared across companies on one site | Items, customers and suppliers are shared; check per-company defaults |
| Financial dimensions | Accounting Dimensions (ERPNext accounting dimensions documentation) and Cost Centres (ERPNext Cost Center documentation) | Usually simplified in the move |
| Inventory dimensions (site, warehouse, location, batch, serial) | Warehouse tree (ERPNext Warehouse documentation), Batch (ERPNext Batch documentation), Serial No (ERPNext Serial No documentation) | Locations become child warehouses; test bin-level needs |
| Product dimensions (configuration, size, colour) | Item Variants (ERPNext Item Variants documentation) | Good for size/colour; not a constraint-based configurator |
| Trade agreements | Price Lists and Pricing Rules (ERPNext Pricing Rule documentation) | Rebuild, do not copy blindly |
| BOMs and routes | BOMs (ERPNext Bill of Materials documentation), Routings (ERPNext Routing documentation), Workstations (ERPNext Workstation documentation) | Good |
| Production orders | Work Orders (ERPNext Work Order documentation), Job Cards (ERPNext Job Card documentation) | Good |
| Master planning | Production Plan (ERPNext Production Plan documentation), Material Request (ERPNext Material Request documentation) | Test with real demand |
| Projects | Projects (ERPNext Project documentation), Timesheets (ERPNext Timesheets documentation) | Good for project tracking and costing |
| Fixed assets | Assets (ERPNext Asset documentation) | Good |
| Inter-company, multi-currency | Inter-company invoices (ERPNext inter-company invoices documentation), multi-currency (ERPNext multi-currency accounting documentation) | Good |
The AX 2009 features that most often need extra work in ERPNext are complex trade agreement hierarchies, warehouse management with directed picking, and any industry add-on from an ISV. List them early.
Getting data out of AX 2009
AX 2009 stores its data in SQL Server, which makes extraction straightforward for anyone with SQL skills and the AX data dictionary to hand. The traps are meaning, not access: enumerations stored as integers, data split across companies and virtual companies, financial dimensions held in array fields, and inventory dimensions held in a separate combination table. Plan the move like this:
| AX 2009 data | ERPNext target | How |
|---|---|---|
| Customers, vendors, items | Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation), Items (ERPNext Item documentation) | Extract, decode enums, clean, load with Data Import |
| Active BOMs and routes | BOMs, Routings, Workstations | Only for items you will make again |
| Open sales, purchase and production orders | Sales Orders (ERPNext Sales Order documentation), Purchase Orders (ERPNext Purchase Order documentation), Work Orders | Close what you can in AX before cut-over |
| On-hand stock by dimension | Stock Reconciliation (ERPNext Stock Reconciliation documentation) | Count before go-live |
| Open receivables and payables | Opening invoices (ERPNext opening balance documentation) | Reconcile to AX aged reports |
| GL balances | Opening trial balance on a redesigned chart of accounts (ERPNext Chart of Accounts documentation) | Keep AX read-only or archived for history |
What to do with your X++ customisations
Most AX 2009 sites have years of changes in the customer and partner layers. Export the list from the AOT and sort every object:
Customisation triage
- Drop: no longer used, or worked around a limitation that the new system does not have.
- Standard: met by standard ERPNext (or Dynamics 365) functionality.
- Configure: met by custom fields (ERPNext Custom Field documentation), workflows (ERPNext Workflows documentation), print formats or reports.
- Rebuild: genuine business logic, rebuilt as a Frappe app or server script (Frappe Server Script documentation).
Do the same triage for both destinations. The list of “rebuild” items is the best single predictor of cost on either path, and it is the number to compare between proposals.
A phased plan for leaving AX 2009
| Phase | What happens | Output |
|---|---|---|
| 1. Inventory | Legal entities, modules in use, X++ objects by layer, ISV add-ons, interfaces, reports, infrastructure | A scope and customisation list |
| 2. Data proof | Extract and decode items, customers, BOMs and open orders from SQL Server | Clean sample data |
| 3. Fit tests | Rebuild one product family, a month of orders and a period close in each candidate | Pass, configure or develop, per area |
| 4. Proposals | Dynamics 365 and ERPNext proposals on the same scope, including the customisation triage | Five-year cost comparison using the published licence prices |
| 5. Build and test | Configure, rebuild what you kept, two full trial loads, user testing | Signed-off test cycles |
| 6. Cut-over | Go live at a period end; AX 2009 read-only or archived | Live system, history preserved |
Questions worth asking Microsoft or your partner before phase 4: which DMT release you would use and whether it is in preview; which AX 2009 tables and modules it covers for your legal entities; and which licence mix (Finance, SCM, Premium or lighter licences) your users actually need. Ask the ERPNext side to show your data loaded in a working system and to name every item that needs development.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Many legal entities, complex consolidation, heavy regulation | Dynamics 365 Finance and SCM | Depth at the top end; Microsoft ecosystem |
| Heavy Microsoft stack (Power BI, Power Platform, Entra ID) | Dynamics 365 | Native integration |
| 50 to 500 people, mostly standard manufacturing and distribution | ERPNext worth pricing | Core processes map cleanly; no per-user licence |
| Want to self-host or own the code | ERPNext | GPL-3.0; self-host or Frappe Cloud |
| Customisation list mostly reports and small changes | Either; compare licence | Rebuild cost similar on both |
Best for, and wrong choice when
Dynamics 365 Finance and SCM is best for
Larger AX 2009 estates with many legal entities, complex consolidation, advanced warehousing or regulated processes, and a business already invested in Microsoft’s cloud.
ERPNext is best for
Mid-size AX 2009 manufacturers and distributors with mostly standard processes who accept that either path is a re-implementation and want to stop paying per-user licence fees.
ERPNext is the wrong choice when
You depend on ISV add-ons or advanced warehouse management with no ERPNext equivalent, your consolidation is genuinely complex, or nobody in the business can own the new system after go-live.
Want a second opinion before you commit? Our ERP Engineering practice runs fit tests like the one above on your own data, and we will tell you if the incumbent vendor’s path is the better answer.
Frequently asked questions
When did Dynamics AX 2009 support end?
Microsoft’s Lifecycle FAQ for Dynamics says mainstream support for AX 2009 SP1 ended Oct 9, 2018 and extended support ended Apr 12, 2022 (checked Nov 19, 2026).
Can AX 2009 be upgraded to Dynamics 365?
Not as an in-place upgrade. Microsoft says its AX 2009 Data migration tool is the only supported upgrade path, and describes it as migrating data; customisations must be rebuilt.
Is the AX 2009 Data migration tool generally available?
Microsoft’s install article still says the tool is in private preview with no public release date set, while the Lifecycle FAQ calls it available. Confirm the current status with Microsoft or your partner.
How much does Dynamics 365 Finance cost?
Microsoft lists Dynamics 365 Finance at $210 per user per month in the US and £161.50 per user per month in the UK (excluding VAT), paid yearly; Premium is $300 / £230.70. Supply Chain Management has the same base and Premium prices (checked Nov 19, 2026).
Can ERPNext replace AX 2009?
For mid-size manufacturers and distributors with mostly standard processes, often yes. Test trade agreements, warehouse management and any ISV add-ons first.
What does ERPNext cost?
No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (about £3.79 and £30.29 at the Bank of England rate for Nov 17, 2026; checked Nov 19, 2026). Implementation is separate.