Dynamics AX 2012 has been out of Microsoft extended support since January 2023. Many organizations still run it reliably, but every year the gap grows: no security fixes, ageing SQL Server and Windows versions underneath, and fewer people who know the system well. The destination for most AX customers is Dynamics 365 Finance and Supply Chain Management. This guide covers what to plan before the project starts.
Understand what actually changes
Finance and Supply Chain Management is the direct successor to AX, and much of the data model will feel familiar. Three things change fundamentally:
- No overlayering: in AX, partners modified the base code directly. In Finance and Supply Chain Management, customizations must be built as extensions. Every AX modification has to be reviewed, and many will be rebuilt or replaced.
- Continuous updates: Microsoft ships regular service updates. Your solution must be built so updates can be applied without rework.
- Cloud operations: environments, deployment and monitoring are managed through Microsoft's cloud tooling rather than your own servers.
Measure your technical debt
Start with an inventory of the AX solution:
- Customized objects, grouped by business area and by how often they are used.
- ISV solutions, and whether each vendor offers a version for Finance and Supply Chain Management.
- Reports, including SSRS reports and any external reporting built on the AX database.
- Integrations: how each one connects today, what data it moves and how failures are handled.
- Batch jobs and their schedules.
Many organizations find a large share of their customizations are rarely used, or now covered by standard features. Removing them is the single biggest lever on cost and risk.
Choose an approach: upgrade or reimplement
Microsoft supports a data upgrade path from AX 2012 to Finance and Supply Chain Management, which carries your data and setup across. Alternatively, you can implement fresh and migrate master data, open balances and history. The choice follows the same logic as any ERP move: an upgrade preserves history and reduces data migration effort; a reimplementation lets you correct old design decisions. Our AX upgrade page compares both in more detail.
Plan the areas that cause most delays
- Security: AX roles rarely map cleanly to the new security model, and licensing in Dynamics 365 is driven by the roles users hold. Redesign roles early, because it affects licence cost. See our licence governance guide.
- Integrations: replace direct database integrations with supported methods such as data entities, OData services, recurring integrations or business events.
- Data entities: data migration uses the data management framework. Confirm which entities you need and test them with real volumes.
- User acceptance testing: plan at least two full test cycles with real data, run by the people who will do the work after go-live.
Consider a phased migration
Not everything has to move at once. Common phasing options are by legal entity, by business unit, or finance first and operations second. Phasing reduces risk, but requires temporary integrations between AX and the new system, so weigh the extra effort carefully.
Build the plan around evidence
A realistic AX migration plan includes:
- A fit-gap of every customization and ISV.
- A target architecture for integrations and reporting.
- A data migration approach with at least two trial migrations.
- A security and licensing design.
- Test cycles, a cutover rehearsal and a hypercare plan.
Talk to us
Tech Sarwar's consultants have worked with Dynamics since the AX days. If you are planning a move, book a Finance and Operations migration consultation or read our Finance and Operations implementation readiness checklist.