If your organisation is still running Dynamics AX, you're operating on borrowed time. Microsoft ended mainstream support in October 2021 and extended support in January 2023, which means no more security patches, no regulatory updates and no access to the product roadmap that's driving competitive advantage for businesses already on Dynamics 365. The longer a Dynamics AX upgrade is deferred, the higher the exposure to security vulnerabilities, compliance gaps and rising maintenance costs that come with propping up unsupported infrastructure.
The good news is that the path from Dynamics AX to Dynamics 365 Finance and Supply Chain Management is well-established. With disciplined planning, clean data migration practices and the right partner model, the transition can be predictable, controlled and faster than most teams expect. This 6-step roadmap breaks down exactly how to approach it.
Why Dynamics AX End of Support Changes Everything
The end of Dynamics AX support doesn't mean AX stops working overnight. It means Microsoft is no longer investing in the platform — no hotfixes, no tax or regulatory updates, no compatibility patches for evolving infrastructure. Organisations that remain on AX carry risk across several dimensions.
Security is the most immediate concern. Unpatched systems become increasingly vulnerable to exploits, and the regulatory landscape doesn't pause because your ERP is out of support. Compliance requirements in finance, VAT reporting, data privacy and industry-specific regulations continue to evolve, and without vendor updates, the burden of staying compliant shifts entirely to your internal team or a third-party Dynamics AX support provider — at significantly higher cost and risk.
Then there's the opportunity cost. While competitors on Dynamics 365 are leveraging AI-driven forecasting, embedded Power BI analytics, continuous feature updates and native integration across the Microsoft stack, AX environments are locked into a static architecture that limits what's possible. Every month on AX is a month of widening capability gap.
What You Gain by Moving to Dynamics 365
The Dynamics AX upgrade to Dynamics 365 is not a like-for-like swap. It's an architectural shift from on-premise or hosted infrastructure to Microsoft's cloud-native platform, which brings a fundamentally different operating model.
Dynamics 365 Finance delivers real-time financial visibility, automated close processes, multi-entity consolidation and regulatory compliance tooling that updates continuously. Dynamics 365 Supply Chain Management adds demand forecasting, warehouse automation, production scheduling and end-to-end traceability — all on the same unified platform.
The integration benefits alone justify the move for many organisations. Dynamics 365 connects natively with Microsoft 365 productivity tools, Power BI for analytics, Power Automate for workflow automation and Power Apps for rapid application development. Where Dynamics AX ERP required custom integrations and manual data movement between systems, Dynamics 365 delivers this out of the box.
For a deeper breakdown of the business case, read GO-ERP's whitepaper: Top 10 Reasons to Upgrade Dynamics AX.
The 6-Step Dynamics AX Upgrade Roadmap
Step 1: Assess Your Current Dynamics AX Environment
Every successful upgrade starts with a clear picture of where you are today. This means cataloguing your current Dynamics AX ERP configuration — every customisation, ISV solution, integration, report and business process that runs through the system.
The assessment should answer several critical questions. Which customisations are still actively used and which are legacy artefacts? What integrations exist with third-party systems, and are they documented? Where does your current data sit, and what's its quality? Which business processes are standard AX functionality and which depend on bespoke code?
This baseline determines everything downstream — your upgrade path, your data migration strategy, your testing scope and your realistic timeline. Skipping or shortcutting this step is the single most common cause of budget overruns and delivery delays in ERP transitions.
Step 2: Define Your Upgrade Path
The technical route from Dynamics AX to Dynamics 365 depends on your starting point. AX 2012 R3 estates typically follow a structured code-and-data migration path using Microsoft's Lifecycle Services (LCS) tools, which analyse existing code, identify deprecated APIs and map customisations to the Dynamics 365 architecture.
Older versions — AX 2009 and earlier — often require a re-implementation approach rather than a direct migration, because the architectural differences are too significant for automated tooling to bridge reliably. This isn't necessarily a disadvantage; re-implementation provides an opportunity to rethink processes, eliminate accumulated technical debt and adopt standard Dynamics 365 functionality rather than recreating legacy customisations that may no longer serve the business.
Regardless of version, this step should also challenge which customisations should be carried forward, which can be replaced by standard D365 features, and which should simply be retired. Every customisation migrated is a customisation that must be maintained, tested and upgraded through future service updates.
Step 3: Clean, Validate and Prepare Data for Migration
Data migration is where many Dynamics AX upgrades stumble — not because the tooling is inadequate, but because the source data isn't ready. Years of accumulated records, duplicate entries, orphaned transactions, inconsistent coding and undocumented manual workarounds create a dataset that's far messier than most teams realise until they try to move it.
The approach should be methodical. Start with a complete backup of the production database as your safety net. Then systematically clean the data: archive historical transactions that aren't needed in the live D365 environment, resolve duplicate vendor, customer and item records, standardise coding conventions and validate referential integrity across tables.
This is also the right moment to rationalise what migrates. Not every historical record needs to move to Dynamics 365. Migrating seven years of closed purchase orders adds complexity and cost without delivering value. Define clear cutover rules — typically open transactions, master data and a defined period of financial history — and archive the rest.
Step 4: Execute the Technical Migration
With the upgrade path defined and data prepared, execution follows a structured sequence. Your implementation partner uses LCS to analyse and refactor code and metadata from Dynamics AX for compatibility with Dynamics 365. Custom code is reviewed, deprecated patterns are replaced and ISV solutions are either upgraded or substituted with D365-native alternatives.
Data migration is executed in iterative test cycles — not as a single big-bang event. Each cycle surfaces mapping errors, transformation issues and edge cases that can be resolved before the final cutover migration. This iterative approach de-risks delivery dramatically compared to organisations that attempt a single migration run and discover problems on go-live day.
Integration points are reconnected and validated during this phase too. Every data flow between Dynamics 365 and external systems — whether that's a WMS, CRM, e-commerce platform or banking interface — must be tested under realistic conditions before the switch is flipped.
Step 5: Test Rigorously and Train Thoroughly
Testing should cover three layers: unit testing of individual customisations and configurations, integration testing of end-to-end processes across connected systems, and user acceptance testing (UAT) where business users validate that their day-to-day workflows perform correctly in the new environment.
Training is equally critical and often underestimated. Dynamics 365 looks and behaves differently from Dynamics AX, and even experienced AX users need structured enablement to work confidently in the new platform. Role-based training programmes that focus on day-one tasks — rather than exhaustive feature walkthroughs — deliver the fastest adoption and protect productivity through the transition period.
Step 6: Go Live, Monitor and Optimise
Go-live is a milestone, not a finish line. The first weeks in production require active monitoring of system performance, data quality, integration reliability and user adoption metrics. A dedicated hypercare period — typically two to four weeks — ensures that issues are identified and resolved quickly before they compound.
Post-stabilisation, the focus shifts to optimisation. This is where the real value of Dynamics 365 starts to compound: automating manual processes, building Power BI dashboards that deliver insights AX never could, extending functionality through the Power Platform and taking advantage of Microsoft's continuous feature releases without the disruptive upgrade cycles that characterised AX.
Many organisations choose a Managed Service Provider for ongoing optimisation and support, ensuring the platform continues to evolve with the business rather than stagnating after implementation.
The Cost of Waiting
Every quarter spent on unsupported Dynamics AX is a quarter of compounding risk — security exposure, compliance drift, integration limitations and an ever-widening gap between what your ERP can do and what the business needs it to do. Third-party Dynamics AX support can provide a temporary safety net, but it doesn't close the capability gap and it doesn't reduce long-term total cost of ownership.
The organisations getting the most value from Dynamics 365 today are the ones that treated the Dynamics AX upgrade not as a forced migration but as a strategic investment — an opportunity to clean up technical debt, modernise processes and build a platform that scales with the business.
Start Your Dynamics AX Upgrade with GO-ERP
GO-ERP is a Microsoft partner specialising in Dynamics 365 implementation, upgrade and managed services across the UK, Europe and internationally. Whether you need an assessment of your current AX environment, a risk-controlled data migration plan, or end-to-end delivery of your Dynamics AX upgrade, the team brings deep platform expertise and a structured methodology built to de-risk delivery and accelerate time-to-value.
Contact GO-ERP for an AX-to-Dynamics 365 advisory workshop and take the first step toward a modern, scalable ERP platform.
