What are the 4 key decisions Microsoft Dynamics users face today?

Microsoft Dynamics users today face four key decisions: which version to migrate to, whether to move to the cloud or stay on-premise, whether to run a greenfield or brownfield implementation, and how to handle data migration safely. Each of these decisions has a direct impact on cost, timeline, and operational continuity. The sections below walk through each one in plain terms so you can approach your planning with confidence.

Which version of Microsoft Dynamics should you migrate to?

For most organisations, Microsoft Dynamics 365 is the target version for any migration today. It is the actively developed, cloud-native platform that Microsoft continues to invest in, while older versions such as Dynamics AX, NAV, GP, and CRM have either reached the end of mainstream support or are on a clear path toward it. If you are running one of those legacy versions, the direction of travel is toward Dynamics 365.

The practical question is not whether to move to Dynamics 365, but which modules fit your organisation. Dynamics 365 is a suite, not a single product. Depending on your business, you may need Finance, Supply Chain Management, Business Central, Sales, or a combination of these. The right selection depends on your size, industry, and the processes you need to support.

This is where starting with a proper baseline matters. Before committing to a roadmap or a budget, we recommend running a maturity assessment to understand where your organisation currently stands in terms of processes, people, and systems. It gives you a concrete starting point and prevents you from building a migration plan on assumptions.

Should Microsoft Dynamics users move to the cloud or stay on-premise?

For the large majority of organisations, moving to the cloud is the right direction. Microsoft has made its position clear: Dynamics 365 is cloud-first, and on-premise versions of the newer platform are either limited in functionality or no longer available. Staying on-premise typically means staying on an older product with a shrinking support window.

That said, some organisations have legitimate reasons to evaluate a hybrid approach or a slower transition timeline. Regulatory requirements, data residency rules, or deeply customised legacy environments can all influence the pace and shape of a cloud move. These are real constraints worth taking seriously, not obstacles to dismiss.

What matters most is making the decision based on your actual situation rather than a general preference. The organisations that run into trouble are usually those that delay the decision entirely, which leaves them managing an ageing system while the gap between their capabilities and the market widens.

What is the difference between a greenfield and brownfield Dynamics implementation?

A greenfield implementation means building your Dynamics environment from scratch, without carrying over configurations, customisations, or data structures from a previous system. A brownfield implementation means migrating from an existing Dynamics environment, preserving as much of the current setup as is useful while upgrading to the new platform.

The choice between the two is not just technical. It reflects how much of your current way of working you want to carry forward.

Greenfield gives you a clean slate. It is an opportunity to redesign processes, eliminate legacy workarounds, and align the system with how your business actually needs to operate today. It typically takes more time and investment upfront but can deliver a cleaner, more future-proof result.
Brownfield is faster to deliver in many cases because you are working with existing configurations and familiar processes. The risk is that you also carry forward outdated processes and technical debt if you are not careful about what you migrate and what you leave behind.

Neither approach is universally better. The right choice depends on how fit-for-purpose your current setup is, how much your business has changed since the original implementation, and how much disruption your organisation can absorb during the transition. We work with both greenfield and brownfield projects across our full range of services, and the approach always starts with understanding the specific context rather than defaulting to a standard template.

How should organisations handle data migration during a Dynamics transition?

Data migration needs to be treated as a project within the project, not an afterthought. The most common mistake organisations make is underestimating the time and effort required to cleanse, map, validate, and test data before it moves into the new system. Poor data quality in the new environment undermines everything else you have built.

A structured approach to data migration management typically includes these steps:

As-Is analysis of your current data structures, quality, and completeness
To-Be mapping to understand how existing data fields translate into the new system
Data cleansing to resolve duplicates, gaps, and inconsistencies before migration begins
Test migrations to validate that data arrives correctly in the target environment
Sign-off procedures so that business owners confirm data accuracy before go-live

The testing phase is where many teams cut corners under time pressure. Running rigorous test migrations and getting explicit business sign-off is what protects you from discovering data problems after you have already gone live, when the cost of fixing them is much higher.

When is the right time to start planning a Microsoft Dynamics transformation?

The right time to start planning is earlier than most organisations expect. A realistic Microsoft Dynamics transformation for a mid-to-large organisation takes anywhere from twelve to twenty-four months from the start of planning to go-live. If you are waiting until a support deadline is imminent or until a business problem becomes critical, you have already lost a significant portion of your planning runway.

In 2026, organisations still running Dynamics AX 2012 or older NAV versions should treat planning as an active priority, not a future agenda item. The longer you wait, the more constrained your options become in terms of implementation partners, internal capacity, and the ability to run a proper change management programme.

Good planning also gives you time to do things properly: running a maturity assessment, aligning stakeholders, defining your programme structure, and selecting the right implementation approach. Organisations that rush into execution without this foundation tend to face scope creep, budget overruns, and user adoption problems after go-live.

How Optinus helps with Microsoft Dynamics transformations

We support organisations through every stage of a Microsoft Dynamics transformation, from the first assessment through to post-go-live hypercare. Here is what that looks like in practice:

Maturity assessment to give you a clear, honest baseline before any budget is committed
Project and program management with consultants who have hands-on experience from real Dynamics migrations at leading multinationals
Data migration management using rigorous As-Is/To-Be analysis and structured testing to prevent data loss and errors
Cutover management with real-time monitoring and hypercare to protect operational continuity during go-live
Change management that addresses both the technical and human side of the transition, driving genuine adoption across your organisation
Available on-site and remote, across the Netherlands, Belgium, and internationally

If you are preparing for a Microsoft Dynamics transformation or trying to get clarity on where to start, get in touch with our team for a straightforward conversation about your situation. You can also learn more about what we do and the approach we bring to complex ERP transformations.

home|

blog|