Cart is empty Every organisation still running Microsoft AX faces the same fundamental question: do we migrate what we have to Dynamics 365, or do we start fresh with a reimplementation? It's a decision that shapes budget, timeline, risk profile and — most importantly — whether the new platform actually delivers the operational improvements the business needs.
The answer is rarely obvious. Both paths lead to Dynamics 365, but they get there through very different routes, with very different trade-offs. A Dynamics 365 upgrade through migration preserves your current design, minimises disruption and gets you onto a supported platform faster. A reimplementation resets design choices, eliminates accumulated technical debt and builds the system around how the business operates today — not how it operated when AX was first configured.
This guide walks through the factors that determine which path is right for your Microsoft AX ERP environment, so you can make the decision with clarity rather than guesswork.
Why the Decision Matters More Than Most Teams Realise
The upgrade-or-reimplement question isn't just a technical choice. It's a strategic one that affects every function that touches the ERP — finance, supply chain, operations, procurement, HR and IT. Get it right and you accelerate time-to-value, control cost and build a platform that scales. Get it wrong and you either carry legacy constraints into the new system (migration done badly) or blow budget and timeline on a redesign the business didn't need (reimplementation done unnecessarily).
The stakes are heightened by the end of Microsoft AX support. With mainstream support ended in October 2021 and extended support concluded in January 2023, organisations remaining on AX carry escalating risk across security, compliance and operational reliability. The question is no longer whether to move — it's how to move with the least risk and the most return.
When erp migration Is the Right Call
ERP migration — moving your existing AX configuration, customisations, data and integrations to Dynamics 365 through a structured upgrade path — is typically the right choice when several conditions are met.
Your AX Configuration Is Largely Standard
If your Microsoft AX ERP runs primarily on standard functionality with relatively few customisations, migration is straightforward. Microsoft's Lifecycle Services (LCS) tooling can analyse your codebase, identify deprecated patterns and map existing configurations to their Dynamics 365 equivalents. The fewer customisations you carry, the cleaner the migration path and the lower the delivery risk.
Your Business Processes Haven't Fundamentally Changed
Migration preserves your current operating model. If the processes encoded in AX still reflect how the business actually works — same chart of accounts structure, same procurement workflows, same production planning logic — then there's limited value in redesigning them from scratch. ERP migration gets you onto a modern, cloud-native platform with continuous updates and stronger integration, while keeping the proven processes intact.
Speed and Minimal Disruption Are Priorities
Migration is almost always faster than reimplementation. Because you're carrying forward existing configuration and data rather than designing from a blank sheet, the project timeline is shorter, the change management burden is lighter and the retraining requirement is lower. For organisations under time pressure — approaching a compliance deadline, facing infrastructure risk, or needing to free IT capacity for other initiatives — the speed advantage of ERP migration can be decisive.
You're Running AX 2012 R3
The technical migration path from AX 2012 R3 to Dynamics 365 Finance and Supply Chain Management is well-established and tooling-supported. LCS provides code analysis, data migration frameworks and validation tools specifically designed for this upgrade route. While it still requires careful planning and testing, the path is predictable and proven across thousands of deployments globally.
When Reimplementation Is the Better Path
Migration carries forward what you have. Reimplementation questions what you have — and that questioning process is sometimes exactly what the business needs.
Heavy Customisation and Technical Debt
If your Microsoft AX ERP has accumulated years of customisations — bespoke modules, heavily modified standard processes, custom reports layered on top of custom reports — migrating all of that to Dynamics 365 can be more expensive and risky than starting clean. Every customisation migrated must be tested, maintained and upgraded through future service updates. If many of those customisations were built to work around AX limitations that Dynamics 365 has already solved natively, migrating them is paying to preserve problems.
Reimplementation allows you to evaluate each customisation against current Dynamics 365 standard functionality. In many cases, what required bespoke code in AX is now available out of the box in D365 — meaning you can retire the customisation entirely, reduce complexity and lower ongoing maintenance cost.
Business Processes Have Evolved Significantly
Organisations change. Acquisitions, new markets, product line shifts, regulatory changes and operational restructuring all create drift between how the ERP was originally configured and how the business actually operates today. If that drift is significant, migrating the old configuration means codifying outdated assumptions into the new platform.
Reimplementation provides the opportunity to redesign processes around current and future requirements rather than historical ones. It's more disruptive and more expensive upfront, but it delivers a system that fits the business as it is — not as it was five or ten years ago.
You're Running AX 2009 or Earlier
Older AX versions — 2009 and earlier — have architectural differences too significant for Microsoft's automated migration tooling to bridge reliably. The gap between these legacy architectures and Dynamics 365's cloud-native platform means a reimplementation approach is often the only practical route. While this requires more investment, it also provides the cleanest possible starting point on D365.
Multi-Country Complexity or Major Integration Overhaul
If your AX environment serves multiple legal entities across different countries, each with localised configurations, tax rules and reporting requirements, migration can become extremely complex. Similarly, if your integration landscape has grown organically into a tangle of point-to-point connections that need rationalising, reimplementation provides a cleaner opportunity to redesign the integration architecture using modern patterns — Dataverse, Power Automate, Azure Integration Services — rather than recreating legacy connection logic.
For organisations planning multi-country rollouts, reimplementation often aligns better with a phased deployment strategy where each entity is brought onto D365 with standardised processes and localisation from day one.
The Hybrid Approach: Migrate First, Optimise Later
In practice, many organisations land somewhere between the two extremes. A pragmatic approach is to migrate the core system to Dynamics 365 to get off unsupported infrastructure quickly, then progressively optimise, standardise and extend the platform post-go-live.
This hybrid model delivers the speed and risk reduction of ERP migration with a built-in roadmap for the process improvements that reimplementation would have delivered. It works particularly well when paired with a managed services engagement that provides ongoing optimisation, development capacity and advisory support beyond the initial go-live.
The hybrid approach also spreads cost and change management across a longer timeline, which can be easier for the business to absorb than a single large-scale programme.
How to Make the Decision: A Practical Framework
The upgrade-or-reimplement decision should be driven by evidence, not instinct. A structured assessment of your current Microsoft AX ERP environment provides the data you need to make the call with confidence.
Start by cataloguing your customisations. How many are there? How many are still actively used? How many address requirements that Dynamics 365 now handles natively? The ratio of "must-migrate" to "can-retire" customisations is one of the strongest predictors of whether migration or reimplementation delivers better value.
Assess your data quality. Clean, well-structured data migrates efficiently. Messy, duplicated, inconsistent data — the kind that accumulates over years of manual workarounds — requires significant cleanup regardless of path, but the cleanup scope influences timeline and cost for both options.
Map your integrations. How many external systems connect to AX? Are the integrations documented? Are they stable, or are they fragile connections that break with every update? Integration complexity is often the hidden cost driver that tips the decision toward reimplementation.
Finally, align with business strategy. If the business is stable and the primary goal is getting onto a supported platform, migration is usually sufficient. If the business is transforming — new markets, new operating models, new capabilities needed — reimplementation provides the design freedom to build the platform around where the business is headed.
For a detailed walkthrough of the technical migration steps, see GO-ERP's Dynamics AX to D365 upgrade guide. For a broader view of the business case, the Top 10 Reasons to Upgrade Dynamics AX whitepaper provides additional context.
What Both Paths Have in Common
Regardless of whether you choose migration or reimplementation, several fundamentals apply. Both paths require rigorous data cleansing before cutover. Both require structured testing — unit, integration and UAT — to validate the new environment. Both require training to prepare users for the Dynamics 365 experience. And both benefit significantly from working with an experienced Dynamics 365 implementation partner who has delivered both migration and reimplementation programmes and can advise objectively on which path suits your situation.
The worst outcome is choosing migration because it seems cheaper, only to discover mid-project that the customisation debt makes it more expensive than reimplementation would have been. Or choosing reimplementation because it feels more ambitious, when migration would have delivered 90% of the value in half the time. The assessment phase exists to prevent both mistakes.
Make the Right Call with GO-ERP
GO-ERP delivers both Dynamics 365 upgrade migrations and full reimplementations across Finance, Supply Chain Management, Business Central and the broader Dynamics 365 ecosystem. The team brings deep experience in both paths — including hybrid approaches — with a structured assessment methodology that gives you a clear, evidence-based recommendation before any commitment.
Whether your Microsoft AX ERP is a clean AX 2012 R3 environment ready for migration or a heavily customised legacy estate that needs reimagining, GO-ERP provides the implementation, development, managed services and advisory expertise to de-risk the transition and accelerate time-to-value.
Contact GO-ERP for an ERP migration assessment workshop and take the first step toward a decision you can defend with data.