Can you move from Dynamics AX to the cloud without disrupting operations?

Yes, you can migrate from Dynamics AX to the cloud without disrupting operations, but it requires careful planning. The biggest risks come from poor cutover timing, incomplete data migration, and underestimating the change management side. Whether you move in one go or in phases depends on your organisation’s size, complexity, and risk appetite. This article walks through the questions most organisations ask before making the move.

What are the biggest operational risks when migrating from Dynamics AX to the cloud?

The biggest operational risks in a Dynamics AX cloud migration are data loss during transfer, system downtime during cutover, and low user adoption after go-live. Each of these can derail daily operations if they are not addressed with a structured approach before you even begin the technical work.

Data integrity is usually where the most serious problems hide. Dynamics AX environments often carry years of accumulated data, custom fields, and integrations that were never properly documented. When you move that data to a new cloud environment, gaps in your As-Is analysis translate directly into errors in the new system. Rigorous data validation and testing before go-live is not optional here.

Beyond the technical layer, operational disruption often comes from the human side. Teams that are not prepared for a new system will work around it, revert to spreadsheets, or simply make mistakes. Change fatigue is a real risk, especially in organisations that have been through previous ERP projects. If adoption is low, the business case for the migration collapses regardless of how clean the technical delivery was.

Integration failures are another common source of disruption. Dynamics AX typically connects to a range of third-party systems, from warehouse management tools to financial reporting platforms. These integrations need to be mapped, tested, and validated in the new cloud environment before you switch off the old one.

What’s the difference between a greenfield and brownfield approach for Dynamics AX upgrades?

A greenfield approach means building your new cloud ERP environment from scratch, without carrying over configurations or customisations from Dynamics AX. A brownfield approach means migrating your existing setup, including configurations, data, and processes, into the new environment. The right choice depends on how much of your current setup is worth keeping.

Greenfield: starting fresh

Greenfield gives you the opportunity to redesign processes and adopt standard cloud functionality without the weight of legacy decisions. It tends to work well when your current Dynamics AX setup is heavily customised, outdated, or no longer aligned with how the business actually operates. The trade-off is that it requires more upfront design work and more intensive change management, because users are learning a genuinely new system.

Brownfield: building on what exists

Brownfield is faster to implement in theory, because you are working from an existing foundation. It suits organisations where the current processes are sound and the goal is to modernise the platform rather than redesign the business. The risk is that you carry legacy problems into the new environment if the migration is not paired with a proper As-Is/To-Be analysis. We see this regularly: organisations that skip the process review step end up with cloud infrastructure running outdated workflows.

Most mid-to-large organisations end up somewhere between the two. A business transformation approach that includes a proper maturity assessment at the start gives you the clarity to make this decision based on evidence rather than assumption.

How does cutover planning prevent go-live disruptions in a Dynamics AX migration?

Cutover planning prevents go-live disruptions by defining exactly what happens in the final hours and days before you switch from Dynamics AX to the new cloud environment. A detailed cutover plan sequences every technical task, assigns ownership, sets clear go/no-go criteria, and prepares rollback options if something goes wrong.

The cutover window is the highest-risk moment in any migration. You are running parallel systems, moving final data loads, and making the call to cut over in real time. Without a tested plan, decisions get made under pressure and mistakes happen.

Good cutover planning includes:

A detailed task list with owners, timings, and dependencies
Dry runs before the actual cutover weekend to test the sequence and timing
Go/no-go checkpoints so the team has clear criteria for proceeding or pausing
A rollback plan that specifies exactly what happens if a critical issue is discovered during cutover
Hypercare support immediately after go-live to catch and resolve issues before they affect operations

Our cutover management approach covers all of this end-to-end, including real-time monitoring during the cutover window and hypercare in the days that follow. Operational continuity is never something you want to leave to chance at this stage.

How long does a Dynamics AX to cloud migration typically take?

A Dynamics AX to cloud migration typically takes between 12 and 24 months for a mid-to-large enterprise, depending on the complexity of the existing environment, the number of integrations, and whether you choose a greenfield or brownfield approach. Smaller, less complex implementations can move faster, but rushing the timeline is one of the most common causes of go-live failures.

The main phases that drive the timeline are:

Discovery and design (2 to 4 months): mapping current processes, defining the To-Be state, and making key architecture decisions
Build and configuration (4 to 8 months): setting up the new environment, configuring workflows, and building integrations
Testing (2 to 4 months): unit testing, integration testing, user acceptance testing, and performance testing
Cutover preparation and go-live (1 to 2 months): dry runs, final data migration, cutover execution
Hypercare (1 to 3 months post go-live): stabilisation, issue resolution, and user support

Organisations that invest time in the discovery phase consistently deliver faster and cleaner go-lives. Skipping or compressing the design phase to save time almost always creates rework later.

Should you migrate Dynamics AX to the cloud in one go or in phases?

Whether to migrate Dynamics AX to the cloud in one go or in phases depends on your organisation’s risk tolerance, operational complexity, and the number of business units or geographies involved. A phased approach reduces risk and allows learning between waves, but takes longer. A single cutover is faster but concentrates all the risk into one go-live event.

A phased migration works well when:

You have multiple business units or regions that can go live independently
Some parts of the business are more ready than others
You want to limit the blast radius if something goes wrong
The organisation has limited capacity to absorb large-scale change all at once

A single cutover works better when:

Your processes are tightly integrated across the business and cannot easily be separated
Running parallel systems for an extended period is operationally or financially impractical
The organisation is smaller and the migration scope is manageable in one wave

There is no universally right answer. What matters is that the decision is made deliberately, based on a clear picture of where the organisation stands today. This is exactly why a maturity assessment before committing to a migration roadmap is so useful. It gives you the evidence to make this call with confidence rather than guesswork. You can explore our full range of services to see how we support each phase of the journey.

How Optinus helps with Dynamics AX cloud migration

We work with mid-to-large organisations navigating exactly this kind of transition. Our consultants have hands-on experience from real ERP migrations at leading multinationals, not just theoretical frameworks, and we cover the full spectrum from maturity assessment through to post-go-live hypercare. Here is what that looks like in practice:

Maturity assessment to give you a clear baseline before any budget or roadmap is committed
Greenfield and brownfield project and program management tailored to your environment
Data migration management with rigorous As-Is/To-Be analysis and testing to prevent data loss
Cutover management with real-time monitoring, dry runs, and hypercare included
Change management that drives genuine adoption across your organisation, not just training delivery
Available on-site and remote, in the Netherlands, Belgium, and internationally

If you are preparing for a Dynamics AX migration or are already mid-programme and need additional expertise, get in touch with our team or learn more about what we do.

home|

blog|