Greenfield, brownfield or selective — choosing honestly
The three S/4HANA transition approaches compared on what actually differentiates them: history, custom code, process debt and appetite for disruption.
Written by APx Technology
Every S/4HANA conversation reaches this question early, and it is frequently answered by preference rather than evidence. Here is what genuinely separates the three approaches.
Brownfield — in-place conversion
You convert the existing system. Configuration, history, custom developments and master data all carry forward. The technical conversion is well-tooled and the path is well-trodden.
Choose it when your current configuration still reflects how the business works, your custom code volume is manageable, and your appetite for business disruption is low.
The trap: you bring everything, including twenty years of accumulated workarounds, unused configuration and Z-programs nobody can explain. You arrive on S/4HANA with the same process debt you had before, now harder to unpick because it has been validated by surviving a migration.
Greenfield — clean implementation
A new system built on SAP best-practice processes, with selected master and transactional data migrated in.
Choose it when your processes genuinely need rethinking, your configuration carries significant historical debt, or your organisation has changed shape enough that the current design no longer matches it.
The trap: it is a business transformation programme, not an IT project. It needs business ownership, sustained executive attention and a real change management effort. Organisations that scope it as a technical migration consistently under-resource it and then struggle at adoption.
Selective data transition — the middle road
Carry forward the configuration and data that still earn their place; leave the rest. Technically the most complex of the three, requiring specialist tooling.
Choose it when you have multiple systems to consolidate, a carve-out or merger has left you with landscape you do not need, or parts of your configuration are excellent and parts are a liability.
The trap: it is the hardest to scope and the easiest to underestimate. The decisions about what to carry forward are business decisions requiring sustained business input over months, and the cost of getting them wrong is discovered late.
How to decide on evidence
Four questions, each answerable with data rather than opinion.
How much of your configuration still reflects reality? Not how much exists — how much is actively used and correct. Process mining or a structured review will tell you.
How much custom code do you have, and how much of it runs? Usage statistics over twelve months usually reveal that a substantial share of custom objects have not executed at all.
How much does your historical data matter operationally? Legal retention is one question; whether anyone actually transacts against five-year-old documents is a different and more useful one.
What disruption can the business genuinely absorb? Not what it would prefer — what it can absorb, given its calendar, its other change programmes and its capacity for parallel running.
The pattern we see
Organisations that have invested consistently in their SAP landscape and kept custom code under control tend to find brownfield the right answer. It is faster, cheaper and lower risk, and there is less to fix.
Organisations whose system has drifted — where the configuration documents a business that no longer exists — usually benefit from greenfield, even though it costs more. Migrating process debt is paying twice for the same problem.
Selective transition suits a narrower set of circumstances than it is proposed for, typically consolidation and carve-out scenarios.
Most importantly: this is not a decision to make before the readiness assessment. The assessment exists precisely to answer it.