Concept card

Brownfield vs Greenfield Migration

As of 2026-09-27

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

Brownfield vs Greenfield Migration: what is the difference?

Brownfield vs greenfield is the first S/4HANA migration decision and the costliest to get wrong — each path carries a 12-24 month and €5-30M budget swing, the largest controllable variable in the programme.

Should I choose brownfield or greenfield for SAP BW migration?

Choose brownfield (conversion) when the BW model is sound, the ABAP is worth keeping and the deadline is tight — it is faster and keeps history. Choose greenfield when the model has decayed, the target is Datasphere or Business Data Cloud rather than BW/4HANA, or most objects are unused. Many programmes mix both: convert the core, rebuild the rest, and decommission what the usage inventory shows is dead.

What it is

Brownfield versus greenfield is the first and most consequential strategic decision in any S/4HANA migration programme, and it is also the decision most frequently made for the wrong reasons — political convenience, a vendor's preferred delivery model, or an arbitrary corporate mandate — rather than a clear-eyed read of the source system's actual condition. Brownfield means converting the existing ECC system in place: the same data, the same custom code, the same number ranges and organisational structures, upgraded onto S/4HANA's data model and code line. Greenfield means starting from a clean S/4HANA tenant, redesigning processes against SAP's best-practice content, migrating only the data that earns its way across, and leaving legacy custom code behind. A third path, hybrid, defers the choice by letting different parts of the organisation take different routes on different timelines. Each path carries a twelve-to-twenty-four-month timeline and a budget that can run from a few million to tens of millions of euros depending on scope, and choosing the wrong one is, more than any technical risk, the single largest controllable variable in how a migration programme performs.

Why it matters

Brownfield (SUM/DMO conversion, 6-18 months, €3-10M + €2-10M Clean Core refactoring) carries forward every accumulated technical debt — 'lift everything good and bad', including bad master data and outgrown structures.
Greenfield redesigns processes against SAP best practice and starts Clean Core from day one, but absorbs significant business disruption and rebuilds change-management muscle from scratch.
Regulated industries where every process change needs re-validation are a structural argument for brownfield, independent of technical debt.

Key points

Brownfield: SUM/DMO in-place conversion · 6-18mo · €5-20M Tier-1 · preserves processes + custom code (good and bad).
Greenfield: new tenant + redesign · 12-30mo · €10-30M Tier-1 · clean slate but absorbs major business disruption.
Five-driver matrix: ECC entropy · process maturity · concurrent business transformation · disruption tolerance · timeline pressure.
Migration Cockpit + Activate compress greenfield from 24+mo to 12-18mo for many customers.
Custom-code split during migration: 60-80% retire · 15-25% migrate to RAP · 5-10% redesign side-by-side.
Greenfield change-management budget = 20-30% of programme; undersized = revert to spreadsheets.
Analytics architecture (Datasphere) must be sequenced WITHIN the migration programme, not after.
Hybrid (C035) is the slowest path overall — 21-39 months total — but lowest-risk for some customers.

Terms used on this page

Brownfield migration: ECC → S/4HANA conversion in place via SUM/DMO. Same data, custom code, processes carry forward.
Greenfield migration: New S/4HANA tenant with process redesign and selective data migration. Clean slate.
Hybrid migration: Phased approach combining elements of both — federation + selective migration. Companion C035.
SUM/DMO: Software Update Manager + Database Migration Option — SAP's brownfield technical toolchain.
Migration Cockpit: SAP-delivered data migration objects + validation rules + mapping templates for greenfield.
SAP Activate: Methodology spanning brownfield and greenfield with phase templates, accelerators, deliverable catalogue.
RISE with SAP: Managed-service contracting bundle including migration as a service. Not a brownfield/greenfield decision.
ECC entropy: Accumulated technical debt in legacy ECC — custom code, fragmented master data, dead processes. Drives greenfield tilt.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →