SAP S/4HANA Migration: Greenfield vs Brownfield vs Selective
Once you decide to move to S/4HANA, the next question is how. There are three paths, and the right one depends on how much you want to change. Here is a plain comparison.
- Greenfield is a fresh build with new processes and only the data you choose to bring.
- Brownfield converts your existing SAP system in place, keeping history and customization.
- Selective mixes both, moving some areas fresh and converting others, often region by region.
- The choice comes down to how much you want to redesign versus how fast you need to move.
If you have read about the move off SAP ECC, you already know the deadline is real. The harder decision is the approach. Pick the wrong one and you either carry forward years of clutter or take on more change than the business can absorb. Here is how the three options compare.
The three approaches at a glance
| Approach | What it is | Best for | Trade-off |
|---|---|---|---|
| Greenfield | A fresh S/4HANA build | Redesigning processes, dropping old customization | More business effort to rethink ways of working |
| Brownfield | A conversion of your current system | Keeping history, moving quickly | Carries forward existing complexity |
| Selective | A mix of fresh and converted | Large groups moving in stages | More planning to scope each wave |
Greenfield, a fresh start
With greenfield you build S/4HANA new, design processes around current best practice, and bring across only the data you actually need. It is the cleanest option and the best chance to retire years of workarounds.
- Strengths: clean processes, less legacy clutter, a chance to standardize.
- Watch for: more change for the business, and careful data selection so nothing vital is left behind.
- Suits: companies whose old system no longer fits how they work today.
Brownfield, a system conversion
With brownfield you convert your existing SAP system to S/4HANA in place, keeping transaction history and much of your customization. It reaches S/4HANA faster and with less disruption.
- Strengths: keeps history, faster to reach, less retraining at first.
- Watch for: you inherit the complexity and custom code you already carry.
- Suits: companies whose processes work well and who need a low-disruption path.
Selective, the middle path
A selective move takes some processes or company codes fresh while converting others, often one region at a time. It balances cleanup with speed and lets a large group move without switching everything at once.
- Strengths: clean up where it matters, keep what works, move in waves.
- Watch for: more planning to scope each wave and manage the period when both run.
- Suits: large or multi-country groups that cannot afford a single big switch.
How to choose
Three questions usually settle it:
- How well do your processes fit today? A poor fit points to greenfield.
- How much history and customization must you keep? A lot points to brownfield.
- How fast must you move, and across how many entities? Many entities point to selective.
There is no single right answer. The best approach is the one that matches how much you want to change against how much disruption the business can take right now.
Common mistakes to avoid
- Choosing brownfield only to avoid change, then carrying clutter into the new system.
- Choosing greenfield without the time to redesign properly, so it stalls.
- Skipping the data cleanup, whatever the path, and paying for it at go-live.
- Deciding on cost alone instead of fit, then reworking it later.
Frequently asked questions
Not sure which path fits your business?
Book a short call with our SAP team. We will assess your processes and data and recommend the right approach.
Book a Free Consultation →