Practical guide to migrating from Dynamics AX, covering end-of-life planning, migration to D365, customisation remediation, and integration challenges.
IT leaders, operations managers, and CFOs running Microsoft Dynamics AX who need to plan their migration off an end-of-life platform.
What are our realistic options for moving off Dynamics AX, and what should we plan for?
Microsoft Dynamics AX was Microsoft's on-premises ERP for mid-to-large enterprises, covering manufacturing, distribution, retail, and services. It was a powerful system: deep functionality, strong customisation capabilities, and broad integration with the Microsoft stack.
Then Microsoft moved everything to the cloud. Dynamics AX became Dynamics 365 Finance and Operations (F&O), and the on-premises product entered end-of-life. If you're still running AX, you're running a platform that Microsoft is no longer meaningfully investing in.
This isn't a gradual decline. It's a binary situation. AX works until it doesn't, and when something breaks, the support options are limited.
Support timeline by version. AX 2009 extended support ended October 2018. AX 2012 RTM ended October 2021. AX 2012 R2 ended October 2023. AX 2012 R3 extended support ends January 11, 2028. If you are not on R3, you are already out of support. If you are on R3, you have less than two years. Either way, the migration project needs to start now.
Security exposure. Without security patches, known vulnerabilities remain unpatched. This is a particular concern for businesses handling financial data, personal information, or supply chain data.
Compliance risk. Australian tax and reporting requirements change regularly. An unsupported ERP can't keep up with BAS changes, STP Phase 2 updates, or new regulatory requirements without manual workarounds.
Shrinking skills pool. AX developers and consultants are migrating their skills to D365. Finding AX expertise is getting harder and more expensive every year.
Migration to Dynamics 365 Finance & Operations. The official Microsoft path. D365 F&O is functionally the successor to AX, but architecturally it's a different beast: cloud-native, continuous updates, extension-based customisation (no more overlayering). Plan for a re-implementation, not an upgrade.
Migration to Dynamics 365 Business Central. If your AX implementation was relatively simple and you don't need the full complexity of F&O, Business Central might be a better (and cheaper) fit. Worth evaluating.
Migration to an alternative ERP. NetSuite, SAP Business One, Pronto Xi, or industry-specific ERPs may be better fits depending on your business. Don't assume Microsoft-to-Microsoft is the only path.
Staged migration. Migrate core financials first, then other modules over time. This reduces risk and spreads the cost, but extends the timeline and means running parallel systems temporarily.
X++ code migration. AX customisations are written in X++, and while D365 F&O also uses X++, the customisation model has fundamentally changed. AX allowed overlayering (modifying base code directly); D365 requires extensions (building on top without modifying the base). This means most customisations need re-engineering, not just recompiling.
SSRS reports. Reporting built in SSRS needs reviewing. Some reports translate well; others need redesigning for D365's data model.
AIF and custom services. AX's Application Integration Framework (AIF) and custom web services don't exist in D365 F&O. Integrations need rebuilding using D365's OData endpoints, Data Entities, or custom APIs.
Data migration. AX data needs extraction, cleaning, transformation, and loading into the target system. Master data, open transactions, and historical data all need planning.
Unpatched AX is a security liability. The longer you wait, the greater the exposure.
AX expertise is disappearing. Budget for premium rates or act quickly.
Heavy X++ customisation means a longer, more expensive migration.
All AIF-based integrations need replacing. This is often underestimated.
Any ERP migration carries disruption risk. Plan UAT, training, and parallel running.
F&O for complex manufacturing/distribution. BC for simpler environments.
Evaluate based on fit, not brand loyalty.
Staged reduces risk but costs more in total and extends complexity.
Many AX customisations filled gaps that standard D365 features now cover.
We don't replace your Dynamics partner for core ERP work. We focus on the surrounding ecosystem: the custom applications, integrations, and automation that make the ERP useful.
It depends on your version. AX 2009 extended support ended October 2018. AX 2012 RTM extended support ended October 2021. AX 2012 R2 extended support ended October 2023. AX 2012 R3 extended support ends January 11, 2028 — still active as of 2026, but less than two years away. If you are on any version other than R3, you are already operating without vendor support.
It's the official Microsoft path, but not the only option. Some businesses migrate to other ERPs (NetSuite, SAP Business One, Pronto) depending on their industry and requirements. The right answer depends on your specific situation. Don't assume D365 F&O is automatic.
Typically 6-18 months depending on complexity, customisation volume, and data migration requirements. Simple environments can be faster; heavily customised AX installations with many integrations take longer.
X++ code needs to be reviewed and potentially rewritten for D365 F&O. Some customisations can be replaced with standard D365 features that didn't exist when AX was deployed. Others need re-engineering using D365's extension model instead of overlayering.
That's exactly where we focus. Custom applications, integrations, reporting, portals, and automation that sit around the ERP. Your Dynamics partner handles the core ERP migration; we handle everything else.
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
