When an organisation decides to migrate its Dynamics CRM from on-premises to the cloud, one of the first and most consequential decisions is how to approach it. Two broad strategies dominate the conversation: brownfield migration, which preserves and migrates existing functionality, and greenfield deployment, which starts over with a fresh implementation. Both have legitimate use cases. Choosing the wrong one for your specific context is one of the most expensive mistakes a technology programme can make.

This post explains what each approach means in practice, what determines which is right for your organisation, and why the decision matters far more than most pre-migration assessments acknowledge.

What Brownfield Migration Actually Means

A brownfield migration - sometimes called an "Upgrade and Transform" approach, takes your existing Dynamics CRM platform as the starting point. It migrates current functionality, data, integrations, and configuration to the cloud with high fidelity, while systematically remediating everything that is not cloud-compatible.

The core principles of a well-executed brownfield migration are:

• Preserve business logic: workflows, plugins, business process flows, and custom entities that the organisation depends on are migrated, not rebuilt from scratch.

• Remediate for cloud compatibility: components that use deprecated APIs, deprecated features, or on-premises-only capabilities are identified and re-engineered before migration proceeds.

• Eliminate technical debt in transit: the migration is an opportunity to address accumulated debt - unmanaged solutions, obsolete integrations, oversized data volumes, rather than simply carry it to the cloud.

Brownfield is the appropriate strategy when an organisation has a mature, heavily customised platform with significant institutional knowledge embedded in its configuration. The business case is not to rethink the CRM - it is to get the existing CRM to a supported, cloud-native state while preserving continuity.

What Greenfield Deployment Actually Means

A greenfield deployment treats the migration as an opportunity to start over. Rather than migrating existing configuration, the organisation implements Dynamics 365 from scratch - using out-of-the-box features where possible and re-building customisations only where necessary.

Greenfield is the right choice when:

• The existing platform is so poorly structured that migration would simply be moving technical debt to a new location.

• The organisation's business processes have changed so significantly that the existing CRM no longer reflects how the business actually operates.

• The organisation has the capacity and tolerance for a substantial change management programme - because a greenfield deployment means staff are learning a materially different system, not an upgraded version of the one they know.

The appeal of greenfield is often stated as "clean slate." The risk is that it underestimates how much institutional value is embedded in a mature CRM. Twelve years of workflow configuration, custom entity relationships, and embedded business logic represent real knowledge that took real time to develop. Discarding it is a legitimate choice - but only when the cost of rebuilding it is understood and accepted, not assumed to be minimal.

The Decision Framework: Five Questions to Ask

The right migration strategy depends on the answers to five questions. Being honest about each of them is more valuable than any vendor recommendation.

1. How much institutional knowledge is embedded in your existing configuration?

If your CRM has been developed over many years with significant input from business users and process experts, it encodes knowledge that is not documented anywhere else. A brownfield approach preserves that knowledge. A greenfield approach loses it and requires its recreation - at cost and risk.

2. What is the actual state of your technical debt?

Every long-lived on-premises CRM accumulates technical debt: deprecated components, unmanaged solutions, inconsistent plugin patterns, oversized data volumes. Brownfield migration addresses this debt systematically in transit. Greenfield sidesteps it. But greenfield only works if the organisation has the discipline to not recreate the same debt patterns in the new implementation - which requires honest assessment of why the debt accumulated in the first place.

3. What is your change management capacity?

Greenfield deployments require users to learn a new system. For large organisations - particularly membership bodies and professional associations where CRM users span multiple departments and levels of technical confidence - the change management burden of a greenfield migration is substantially higher than a brownfield one, where the familiar interface and process structure is preserved.

4. What are your integration dependencies?

Organisations with complex integration landscapes - connections to portals, finance systems, external platforms, legacy middleware - will find brownfield migration significantly less disruptive. Integrations can be re-engineered progressively alongside the platform migration, rather than requiring a parallel complete integration rebuild alongside a greenfield CRM implementation.

5. What is your risk tolerance for go-live?

Brownfield migrations, executed well, go live with a system that users recognise. Greenfield deployments go live with a system that everyone is learning for the first time. The risk profile at go-live is materially different. For organisations where CRM downtime or user error at go-live carries significant operational consequences, the brownfield approach is inherently lower risk.

The Hybrid Reality: Most Complex Migrations Are Neither Pure Brownfield Nor Pure Greenfield

In practice, the most sophisticated migrations sit somewhere between the two extremes. A brownfield foundation - migrating the core platform with high fidelity - can be combined with selective greenfield redesign of specific processes that genuinely benefit from a fresh approach. This is the "Transform" in the "Upgrade and Transform" methodology: once the foundational migration is complete and the platform is stable, targeted optimisation sprints address processes that were always problematic or that the cloud platform enables to be done better.

The organisations that do this well treat the initial migration as a foundation-laying exercise, not a transformation programme. Transformation comes after the foundation is solid - not during the migration itself, when risk is already elevated.

A Practical Note on Customisation Complexity

One of the most common errors in migration planning is underestimating what "cloud compatibility" actually requires for a heavily customised on-premises CRM. It is not enough to confirm that your data can be migrated and your integrations can be repointed. Every custom plugin, every JavaScript web resource, every workflow configuration must be assessed against the cloud platform's current API standards and execution model.

For platforms with 800+ plugins and 1,500+ custom components - not unusual for organisations with ten or more years of CRM development - this assessment and remediation is a substantial programme of work in its own right. It is the work that separates a migration that goes live cleanly from one that goes live and then spends six months in stabilisation.

Choosing brownfield is the right decision for most mature, complex platforms. But it is only the right outcome if the brownfield approach is executed with the rigour that the platform's complexity demands.

VE3 helps organisations assess their Dynamics 365 migration strategy and execute complex brownfield migrations with the rigour that mature, customised platforms require. Contact our team to discuss the right approach for your environment.

Get in touch now.