Who this is for
IT leaders, operations managers, and CFOs running Microsoft Dynamics AX who need to plan their migration off an end-of-life platform.
Question this answers
What are our realistic options for moving off Dynamics AX, and what should we plan for?
What you'll leave with
- Dynamics AX end-of-life timeline and what it means
- Migration paths — D365 F&O and alternative options
- How to handle X++ customisations and integrations
- Key risks and budgeting considerations
Platform overview
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.
Common version & support issues
End-of-life reality. Dynamics AX 2012 R3 mainstream support ended in October 2021. Extended support has expired for most versions. No new features, no security patches, no compliance updates. You're on your own.
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.
Upgrade and migration paths
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.
Customisation & integration challenges
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.
- AIF services → Replace with D365 OData or Data Entities
- Direct SQL integrations → Replace with API-based connections
- Flat file imports → Modernise with Data Management Framework or APIs
- Custom web services → Rebuild using D365's service model
Data migration. AX data needs extraction, cleaning, transformation, and loading into the target system. Master data, open transactions, and historical data all need planning.
Risks and decision points
Key risks
- Security exposure
Unpatched AX is a security liability. The longer you wait, the greater the exposure.
- Skills scarcity
AX expertise is disappearing. Budget for premium rates or act quickly.
- Customisation volume
Heavy X++ customisation means a longer, more expensive migration.
- Integration rebuild
All AIF-based integrations need replacing. This is often underestimated.
- Business disruption
Any ERP migration carries disruption risk. Plan UAT, training, and parallel running.
Decision points
- D365 F&O vs Business Central?
F&O for complex manufacturing/distribution. BC for simpler environments.
- Microsoft or alternative?
Evaluate based on fit, not brand loyalty.
- Big bang or staged?
Staged reduces risk but costs more in total and extends complexity.
- What to re-customise?
Many AX customisations filled gaps that standard D365 features now cover.
How HELLO PEOPLE can help
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.
- Customisation audit: Map all X++ customisations and assess which need migrating, replacing, or retiring
- Integration mapping: Document all AIF services, direct SQL connections, and custom integrations with migration plans
- Custom application development: Build portals, mobile apps, and specialised tools that connect to D365
- Data migration support: Extract, transform, and validate data for migration to any target platform
- Reporting modernisation: Rebuild SSRS reports as Power BI dashboards or custom reporting tools
Frequently asked questions
Is Dynamics AX still supported by Microsoft?
Dynamics AX 2012 R3 mainstream support ended in October 2021. Extended support continues until January 2023 (already expired for most versions). If you're still running AX, you're operating without vendor support — no more security patches, no more hotfixes, no more compliance updates.
Is moving to Dynamics 365 F&O the only option?
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.
How long does an AX to D365 F&O migration take?
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.
What happens to our AX customisations?
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.
Can you help with the non-ERP parts of our AX migration?
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.
Key takeaways
- Dynamics AX is end-of-life. If you haven't started migration planning, start now.
- The migration to D365 F&O is not an upgrade — it's a re-implementation on a different architecture
- X++ customisations need review: some can be replaced with standard features, others need rewriting
- Budget for 6-18 months depending on complexity, and don't forget the integration layer
- The longer you wait, the higher the risk and the fewer AX-skilled resources will be available