If you're in the early stages of planning your move to S/4HANA, you may have noticed that your system integrator is leaning one way, SAP is nudging you another, your internal team is split, and underneath all of it is a decision that will shape your programme for the next three to five years.
This is our honest, independent take with no preferred approach to sell and no delivery methodology to protect.
We're offering a clear explanation of what each option actually means, what it costs in practice, and how to think about the decision for your specific situation.
Before comparing the approaches, it's worth being precise about what they mean. The terminology gets used loosely, and that looseness causes real confusion in planning conversations.
Greenfield, means starting fresh. You implement S/4HANA as a new system, redesigning your business processes from the ground up, and migrate only the data you need to take with you. Essentially, your existing SAP landscape is left behind.
Brownfield means converting what you have. Your existing SAP system, including its configuration, custom code, and data, is technically converted to S/4HANA, i.e. the system is simply upgraded rather than being replaced. SAP's formal term for this is a System Conversion.
Bluefield, sometimes called selective data transition, sits between the two. You move to a new S/4HANA environment but selectively carry across the processes, configuration, and data that are worth keeping. It offers more flexibility than a straight brownfield conversion but more continuity than a full greenfield reimplementation.
Each approach has a legitimate use case and none are universally right.
A brownfield conversion is often the fastest route to S/4HANA because you're converting an existing system rather than rebuilding one; you carry across your existing configuration, your integrations, and your data. The technical lift is significant, but the business disruption is lower than a greenfield approach.
Brownfield tends to work well when:
The honest trade-offs:
A brownfield conversion brings your technical debt with you. The inefficiencies, workarounds, and legacy customizations that have accumulated in your existing system don't disappear, they arrive in S/4HANA, just slightly repackaged.
This matters most if your real objective is business transformation rather than technical compliance. If you want S/4HANA to drive meaningful change in how your organization operates, a brownfield conversion is unlikely to deliver it.
There's also the clean core question. SAP's strategic direction is toward a clean core model, where the core system is kept as close to standard as possible and customizations live in a separate extension layer.
A brownfield conversion that carries significant custom code into S/4HANA can create tension with that direction and limit your ability to benefit from SAP's ongoing innovation, including AI-driven capabilities built on SAP Business AI.
A greenfield reimplementation gives you a genuine fresh start. You design your S/4HANA processes from scratch, using current best practice as your baseline, and build a system that reflects how you want to operate, not how you used to.
Greenfield tends to work well when:
The honest trade-offs:
Greenfield can take longer and cost more. That's not a reason to rule it out, but it needs to be an honest input to your decision. You're not just migrating a system; you're redesigning processes, retraining your organization, and managing a much higher volume of business change.
Data migration is also significantly more complex in a greenfield approach because you're not converting data from one system to another; you're extracting, cleansing, transforming, and loading data into a new environment. This work is routinely underestimated in early business cases.
An organizational readiness question that doesn't get asked enough. A
greenfield implementation requires your business to engage deeply with process design decisions. If your organization doesn't have the capacity or the appetite for that level of involvement, the programme will struggle regardless of how strong the technical delivery is.
Bluefield, or selective data transition, is the approach that gets the least airtime in SAP conversations, often because fewer system integrators have deep experience delivering it. That's not a reflection of its merit.
A bluefield approach lets you cherry-pick – you can take the processes and configuration that work well from your existing system and redesign the ones that don't.
You can migrate the data that's clean and valuable, and leave behind what isn't, and you can do this in a new S/4HANA environment, which means you're not inheriting the technical constraints of a converted system.
Bluefield tends to work well when:
The honest trade-offs:
Bluefield is more complex to plan and govern than either brownfield or greenfield, precisely because it requires careful decisions about what moves and what doesn't.
Those decisions need active business involvement and strong programme governance. Without both, the approach can drift toward greenfield complexity without greenfield discipline.
It also requires an SI with genuine selective data transition experience. Not all do, and the ones that don't will sometimes steer you away from it, not because it's wrong for your situation, but because it's harder for them to deliver.
When you're evaluating your migration approach, it helps to understand the context in which different perspectives are formed.
SAP's guidance naturally reflects their strategic direction, and that direction is: clean core architecture, modern extensions, and customers well-positioned to consume ongoing innovation. For many organizations, that aligns closely with a greenfield or bluefield approach.
SAP's recommendations in this area are well-intentioned, and the clean core vision is the right long-term destination for most businesses running S/4HANA.
Where it gets more nuanced is when that strategic direction meets the specific constraints of your programme. A greenfield approach may be the right long-term answer and still not be the right answer for your timeline, your budget, or your organizational capacity right now.
SAP's guidance is best understood as a view of where you should aim, not necessarily a prescription for how fast you should get there.
Your system integrator's perspective is shaped by a different set of factors. The best SIs will give you an honest assessment based on what they've seen work in situations like yours. But it's reasonable to understand what their preferred delivery methodology is, where their deepest experience lies, and how that might be influencing the recommendation you're receiving.
None of this means the advice you're getting is wrong. It means an independent view, from someone with no preferred approach to sell and no methodology to protect, is a genuinely useful addition to the conversation before you commit.
There is no formula that produces the right answer. But there are questions that consistently separate a well-reasoned approach selection from one that was decided by whoever spoke loudest in the room.
Start with your real objective – Are you moving to S/4HANA primarily for technical compliance, to get off ECC before end of mainstream maintenance? Or is this a genuine business transformation programme? The answer shapes everything else.
Be honest about your custom code footprint – A large, complex custom code landscape isn't an automatic reason to avoid brownfield, but it does need to be assessed properly before you decide. How much of that code will need to be remediated for S/4HANA compatibility? How much of it reflects processes that should be redesigned anyway?
Assess your organizational change capacity honestly – Greenfield requires more from your business than brownfield. Not just more training, but more active involvement in process design, more tolerance for disruption, and more sustained leadership attention. If your organization is already stretched, that's a relevant input.
Consider your clean core ambition – If you want to be well-positioned for SAP's AI-driven innovation roadmap over the next five to ten years, clean core architecture matters. Brownfield conversions that carry significant custom code into S/4HANA can constrain your ability to stay current with SAP's development.
Think about your data – If your existing data is clean, well-structured, and valuable, carrying it forward in a brownfield conversion is an asset. If it's messy, incomplete, or structured around processes you're about to redesign, the case for carrying it forward weakens considerably.
Get the timeline right – If you have a hard deadline, that's a real constraint and it needs to be factored in honestly. But be careful about letting an artificial sense of urgency push you into an approach that's faster to start but slower to deliver value.
|
Criteria |
Brownfield |
Bluefield |
Greenfield |
|
Speed to go-live |
Fastest |
Moderate |
Slowest |
|
Business disruption |
Lower |
Moderate |
Higher |
|
Process transformation |
Limited |
Selective |
Full |
|
Technical debt carried forward? |
Yes |
Partial |
No |
|
Clean core readiness |
Lowest |
Moderate |
Highest |
|
Data migration complexity |
Lowest |
Moderate |
Highest |
|
Cost |
Lower |
Moderate |
Higher |
|
Organizational change required |
Lowest |
Moderate |
Highest |
No column in this table is uniformly better than the others; the right answer depends on your starting point, your objectives, and your constraints.
Approach selection is one of the most consequential decisions in any S/4HANA programme. It shapes your timeline, your budget, your organizational change requirements, and your long-term architectural position. Getting it wrong is expensive and difficult to reverse once the programme is underway.
The right time to seek an independent view is before you've committed to an approach, not after. Once an SI is engaged and a methodology is locked in, the options narrow quickly.
Our independent migration options assessment is a fixed-price engagement that gives you a clear, evidence-based view of which approach is right for your situation. We review your existing landscape, your business objectives, your organizational constraints, and your clean core ambition, and we give you a recommendation you can take to your board with confidence.
No preferred approach, no SI relationship to protect, just a straight answer to a question that deserves one.
Book an independent S/4HANA migration options assessment.