Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

Brownfield vs greenfield SAP migration

Three routes to S/4HANA, and the evidence that should decide between them rather than a vendor preference.

In short

A brownfield migration converts your existing SAP system in place, keeping configuration and history. A greenfield build starts from a clean system and reimplements the processes. Selective data transition sits between them, taking some entities across and rebuilding others. The right answer depends on whether your current configuration is an asset or a liability.

Why It Matters

Why this matters in practice

This decision is usually made on who is advising rather than on what the system contains. Implementation partners tend to prefer greenfield because it is cleaner work; internal teams tend to prefer brownfield because it preserves what they built. Both preferences are about the people, not the estate. The honest input is a custom code and configuration assessment.

Brownfield preserves history and configuration, including its problems
Greenfield rebuilds process but carries a change-management cost
Selective transition is flexible and the most complex to scope
The assessment should precede the decision, not justify it
How It Works

How it works in practice

Assess the custom code

How much there is, how much still runs, how much reads tables that no longer exist. This is the single largest input.

Assess the configuration

Whether the current design reflects how the business works now, or how it worked when the system was implemented.

Weigh the data history

Brownfield keeps it. Greenfield requires a deliberate decision about how much history to carry and in what form.

Cost both honestly

Greenfield is usually more expensive in change management and less in remediation. Brownfield inverts that.

Decide, then write it down

Whichever route, the reasoning should be documented so it survives a change of sponsor.

Worked example

A worked example: the same decision, two businesses

Two manufacturers of similar size both run ECC and both need to move. They reach opposite conclusions, correctly.

The first has around 400 custom objects, most of them still in use, and fifteen years of configuration that genuinely reflects how it operates. Its processes are unusual for good commercial reasons. Rebuilding that on standard would mean re-deriving decisions nobody remembers making, and the business case for changing them does not exist. Brownfield is right: convert, remediate what the data model breaks, retire the dead code, keep the rest.

The second has around 1,100 custom objects, perhaps half of them dead, and a configuration shaped by two acquisitions that were never properly harmonised. Its finance team maintains three chart-of-accounts conventions. Carrying that forward means paying to remediate complexity it wants to be rid of. Greenfield is right, and the migration project becomes the vehicle for the harmonisation it has been deferring. The deciding evidence in both cases was the same inventory — which is why that inventory comes before the decision, not after it.

Key terms

The vocabulary, briefly

Term What it means
Brownfield System conversion in place — configuration, history and custom code carried forward and remediated.
Greenfield A new implementation on standard processes, with selected data migrated in.
Bluefield / hybrid Selective data transition: a new system that takes chosen configuration and data from the old one.
Technical debt Accumulated customisation and workaround. Brownfield inherits it; greenfield is the chance to leave it.
Downtime window The outage required to convert. Often the practical constraint that decides the approach.
What Goes Wrong

Common mistakes worth avoiding

Deciding before assessing

The assessment is three to five weeks and determines a multi-year programme. Skipping it to save time is a false economy.

Assuming brownfield is cheaper

It is cheaper only if the existing configuration is sound. Converting a bad design costs more over the life of the system.

Underestimating greenfield change

A clean build means new processes, retraining and resistance. The technical work is often the smaller half.

Choosing selective by default

It offers the appeal of both, and the complexity of both. It needs the clearest scope of the three.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Custom object count and usage The core input. Objects that exist but are never executed should not drive the decision. Counting without usage statistics, which overstates brownfield effort.
Configuration divergence from standard How much of your setup is genuinely business-specific versus historical accident. Treating all divergence as valuable because somebody once chose it.
Data volume and archivable share What you would carry versus what you could leave. Often changes the downtime estimate materially. Estimating before an archiving assessment.
Acceptable downtime Frequently the binding constraint, and it should be established early rather than discovered. Taking the IT answer rather than the business one.
FAQ

Questions we are asked about this

Brownfield remains common where the existing estate is in reasonable shape, because it protects history and avoids reimplementation. Greenfield is chosen more often where the configuration has drifted badly from current process.
In practice, rarely without significant cost. The route determines the project structure, the team and the timeline, which is why the assessment matters so much.
Brownfield usually costs less upfront, because you are converting rather than rebuilding and you are not re-running design workshops. Greenfield can cost less over time if your current system carries complexity you would otherwise pay to maintain for another decade. Comparing only the project cost systematically favours brownfield; comparing total cost over the expected life of the system is the fairer test and is harder to do honestly.
With greenfield and hybrid approaches, yes — by entity, by region or by process, running old and new in parallel for a period. Pure brownfield conversion is closer to a single event, because you are converting one system. Phasing reduces risk per cutover and increases total cost and elapsed time, since you carry two landscapes and the integration between them for the duration. That trade is usually worth it for large multi-entity businesses and rarely worth it for single-entity ones.
Both vary so widely with scope that a quoted range is close to meaningless without your inventory. What is reliably true is the shape of the work: brownfield is dominated by custom code remediation and testing, greenfield by design decisions and data migration. Whichever dominates your situation is where the schedule risk sits, and that is what an assessment tells you before anyone commits to a date.
That is the normal starting position, and it is what the assessment is for. Inventory the custom code with usage statistics, measure data volumes, score process fit against standard, and establish the downtime the business can actually tolerate. Those four pieces of evidence decide it in most cases without argument. A partner who recommends an approach before gathering them is recommending their preference rather than your answer.
Related

Where to read next

SAP ECC to S/4HANA migration guide

Read more

What is SAP S/4HANA?

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.