The brownfield vs. greenfield question is the first major strategic decision in any S/4HANA migration — and it's also one of the most frequently misunderstood.
I've seen organisations choose brownfield because they're afraid of a clean-sheet start. I've seen others choose greenfield because they want to use the migration as an excuse to redesign processes they should have redesigned years ago. Neither of those is a good reason. The answer should come from a clear-eyed assessment of where your organisation actually is.
Defining the Terms
Before we go further, let's be precise about what these terms mean in the SAP context, because they're used loosely in the market:
Brownfield (System Conversion): You take your existing ECC system and convert it to S/4HANA. Your data, configurations, customisations, and integrations all come across. The advantage is continuity and speed. The disadvantage is that you inherit everything — including the problems.
Greenfield (New Implementation): You build a new S/4HANA system using SAP's best-practice templates and migrate only the data you need. You get a clean slate and the opportunity to redesign processes. The disadvantage is cost, time, and the organisational upheaval of changing every process at once.
Bluefield / Selective Data Transition: A hybrid approach where you do a system conversion but selectively re-implement certain areas. This is often the pragmatic choice — but it requires the most sophisticated project management of the three.
The Questions That Drive the Decision
Rather than defaulting to one approach, I use a set of diagnostic questions:
How clean is your current ECC system?
If your ECC instance is well-maintained, with limited custom development, clean master data, and processes that are largely aligned with SAP standard — brownfield is probably the right starting point. You have something worth converting. If your ECC is a decade of accumulated workarounds and custom code built on top of custom code, converting it just moves the problem into a new container.
What is the business appetite for change?
Greenfield requires the business to learn new processes. Not just adapt — actually change how things work. That level of change management requires executive sponsorship, user readiness, and tolerance for disruption that not every organisation has. Honestly assess your organisation's capacity for change before committing to an approach that depends on it.
What are your regulatory and integration constraints?
Some industries have regulatory requirements that are deeply embedded in their ECC configurations. Converting those configurations preserves compliance. Rebuilding them from scratch introduces risk. Understand your constraints before assuming a clean slate is available to you.
What is your timeline and budget?
A greenfield implementation almost always costs more and takes longer than a brownfield conversion — all else being equal. If you have a hard timeline (2027 ECC end-of-life is concentrating minds) or a constrained budget, that shapes your options.
The Answer Most Organisations Get Wrong
The most common mistake I see is choosing greenfield as a proxy for process transformation — deciding to start fresh because it feels like the ambitious, forward-looking choice, without properly accounting for the cost and disruption involved.
Process transformation is a legitimate goal. But it doesn't require a greenfield S/4 implementation to achieve it. You can redesign processes on a brownfield conversion. You can adopt SAP best practices without rebuilding everything from scratch. If the goal is process improvement, separate that goal from the migration approach decision and pursue it deliberately — don't assume one automatically enables the other.
The right field to play on is the one that matches your organisational capability, your system's current health, and the business outcomes you're actually trying to achieve — not the one that sounds most impressive in a board presentation.
A Practical Starting Point
Before you decide, invest in a proper assessment. This means a custom code analysis (how much customisation do you actually have?), a data quality review (is what you have worth keeping?), a process review (are your current processes worth converting, or do they need redesigning regardless?), and an honest conversation with the business about their readiness for change.
Most organisations that do this assessment carefully end up in the middle — a selective conversion that preserves what works and rebuilds what doesn't. Not the cleanest story to tell, but usually the right answer.
