How do you choose the right upgrade path from Dynamics AX?

To upgrade from Dynamics AX, you have two main paths: migrate to Microsoft Dynamics 365 Finance and Operations (the cloud-based successor) or implement a new ERP system entirely. For most organisations still running AX 2012 or earlier, Microsoft Dynamics 365 F&O is the natural next step, either through a technical upgrade or a full reimplementation. The right choice depends on your data complexity, business process maturity, and how much of your current setup you want to carry forward. This article walks through the key questions to help you make that decision with confidence.

What are the available upgrade paths from Dynamics AX?

Organisations moving off Dynamics AX have two primary options: a technical upgrade to Microsoft Dynamics 365 Finance and Operations, or a full reimplementation on Dynamics 365 or another ERP platform. A technical upgrade carries existing configurations and customisations forward. A reimplementation starts from a clean slate, redesigning processes around the new system’s standard capabilities.

A third option exists for organisations that have heavily customised their AX environment: a brownfield migration, which preserves selected data, configurations, and business logic while modernising the underlying architecture. This sits between a pure technical upgrade and a full greenfield build.

Beyond these three routes, some organisations use a Dynamics AX migration as a trigger to evaluate whether Dynamics 365 is still the right platform at all. SAP S/4HANA, Oracle, and other enterprise platforms are legitimate alternatives, particularly for organisations with complex manufacturing or supply chain requirements. That said, for companies already invested in the Microsoft ecosystem, Dynamics 365 F&O typically offers the smoothest transition path.

Optinus works across both SAP and Microsoft Dynamics environments, covering project management from initiation through to post-go-live, so the advice you receive reflects real experience with both platforms, not a preference for one over the other.

What happens when Dynamics AX reaches end of support?

When Microsoft ends mainstream support for a Dynamics AX version, you no longer receive security updates, regulatory updates, or bug fixes. For AX 2012 R3, mainstream support ended in 2018, with extended support running until October 2023. Running an unsupported ERP system exposes your organisation to compliance risk, security vulnerabilities, and an inability to adapt to new regulatory requirements.

In practice, many organisations continue running AX beyond end of support for longer than planned. The system does not stop working, but the risk profile changes significantly. Tax and legal updates that Microsoft would previously have delivered automatically now require custom development. Audit and compliance teams increasingly flag unsupported ERP systems as a risk item.

The business case for migration therefore strengthens over time. The longer an organisation delays, the larger the gap between its current system and modern platform capabilities, and the more complex the eventual migration becomes.

What’s the difference between a greenfield and brownfield migration from AX?

A greenfield migration treats the new Dynamics 365 implementation as a clean start. You redesign business processes from scratch, adopt standard system functionality where possible, and carry across only the data you need. A brownfield migration carries existing configurations, customisations, and data structures forward into the new environment, preserving more of what has already been built.

Greenfield projects typically take longer upfront but result in a cleaner, more maintainable system. They work well when the organisation wants to standardise processes, reduce technical debt, or align with Microsoft’s standard best-practice model. The trade-off is a higher change management burden, since users and teams need to adapt to new ways of working rather than recognising familiar screens and flows.

Brownfield migrations are faster to execute and feel less disruptive to end users, but they carry legacy complexity into the new system. Customisations that made sense in AX may conflict with Dynamics 365’s architecture, creating technical debt from day one. Brownfield is often the right choice when timelines are tight or when specific business-critical customisations genuinely cannot be replaced by standard functionality.

Neither approach is universally better. The right choice depends on your process maturity, the degree of customisation in your current AX environment, and your organisation’s appetite for change.

How does data migration work when moving off Dynamics AX?

Data migration from Dynamics AX involves extracting data from your legacy system, transforming it to match the data structures of your target platform, and loading it into the new environment. This process runs in parallel with the broader implementation and typically goes through multiple test cycles before the final cutover load.

The most common failure points in AX data migration are data quality issues discovered late in the project, mapping errors between legacy and target data structures, and volume and performance problems during the final load window. Each of these is manageable with the right preparation.

A thorough As-Is analysis of your current data is the starting point. This means understanding what data exists in AX, what condition it is in, what you actually need to carry forward, and how it maps to the target system. Running multiple mock migrations before go-live lets you identify and resolve issues without the pressure of a live cutover.

Optinus applies rigorous As-Is/To-Be analysis and structured testing procedures specifically to prevent data loss and mapping errors during migration. Our data migration management approach is built around minimising downtime and protecting data integrity throughout every stage of the transition.

How do you decide which upgrade path is right for your organisation?

The right upgrade path from Dynamics AX depends on four factors: the state of your current system, your business process maturity, your timeline and budget constraints, and your organisation’s readiness for change. Answering these honestly before committing to a path will save significant cost and disruption later.

Start by assessing how heavily customised your AX environment is. If you have built significant custom functionality, a brownfield approach may seem attractive, but it is worth asking whether those customisations reflect genuine business requirements or workarounds for processes that could now be standardised. A clean greenfield build often delivers a better long-term result even when it feels harder in the short term.

Consider also your data quality. Organisations with years of accumulated, poorly maintained master data in AX often underestimate the effort required to migrate it cleanly. A data quality assessment early in the planning phase gives you a realistic picture before budgets are set.

Finally, be honest about your organisation’s change capacity. A greenfield reimplementation is a significant change management exercise. If your teams are already stretched, or if the organisation has recently been through major change, the timing and pace of the programme matters as much as the technical path.

A maturity assessment at the start of the process gives you a structured baseline across all of these dimensions, so you are making decisions based on evidence rather than assumptions.

How Optinus helps with your Dynamics AX upgrade

We support organisations through every stage of a Dynamics AX migration, from the initial decision on upgrade path through to post-go-live hypercare. Here is what that looks like in practice:

Maturity assessment to establish a clear baseline before any roadmap or budget is committed, covering process maturity, data quality, and organisational readiness
Greenfield and brownfield project management, with consultants who have run real ERP migrations at leading multinationals, not just applied frameworks from a distance
Data migration management using structured As-Is/To-Be analysis and multiple mock migration cycles to protect data integrity throughout the transition
Cutover management with meticulous planning and real-time monitoring, so the final go-live is controlled and operational continuity is never at risk
Change management that addresses both the technical and human side of the transition, driving genuine user adoption rather than just delivering training
Available on-site and remote, across the Netherlands, Belgium, and internationally

We cover our full range of services under one roof, so there are no handover gaps between specialisms and no need to coordinate multiple vendors across your programme. If you are planning a Dynamics AX upgrade and want a clear starting point, get in touch with our team or learn more about what we do.

home|

blog|