SAP S/4HANA Migration: Brownfield vs Greenfield vs Selective

A clear comparison of the three SAP S/4HANA migration approaches — brownfield system conversion, greenfield new implementation and selective data transition — how each works, the tools involved, costs and risks, how companies choose, and what each means for consultants.

  SAP Training   Nov 9, 2026   2  Add to Reading List
Quick Answer: There are three ways to move from SAP ECC to S/4HANA. Brownfield (system conversion) converts the existing system in place, keeping history and configuration — fastest, but it carries old complexity forward. Greenfield (new implementation) builds a fresh system around standard processes — cleanest, but the most disruptive. Selective data transition builds a new target and moves only chosen data and configuration — flexible, but technically complex. The right choice depends on process fit, data quality, custom code and how much change the business wants.

With mainstream maintenance for ECC ending in 2027, the question for most SAP customers is no longer whether to move to S/4HANA but how. The choice of approach shapes everything that follows: budget, timeline, the size and skills of the project team, the amount of business change and the quality of the system the company will live with for the next fifteen years.

It is also one of the most common SAP interview topics in 2026. This guide explains each approach properly — what happens technically, which tools are used, the trade-offs — and how companies decide.

Brownfield: System Conversion

In a brownfield move, the existing ECC system is technically converted into an S/4HANA system. Configuration, custom code, master data and full transactional history come across. Users log in to essentially the same system on the Monday after go-live, with the new data model, Fiori apps and simplifications underneath.

How it works

The project begins with SAP Readiness Check, which analyses the system and highlights relevant simplification items, add-on compatibility, custom code impact and data volume. The Simplification Item Check then identifies mandatory preparation steps, such as converting customers and vendors to Business Partners through customer–vendor integration, which must be complete before conversion.

Custom code is analysed with the ABAP Test Cockpit using S/4HANA checks, and unused code is retired. The technical conversion itself runs through the Software Update Manager (SUM); where the source system is not already on HANA, the Database Migration Option moves the database in the same procedure. Finance then runs a dedicated data migration to populate the Universal Journal and new asset accounting structures, followed by reconciliation.

Strengths and weaknesses

Brownfield is usually the fastest and least disruptive route, preserves all history for audit and reporting, and protects investment in configuration and custom development. Its weakness is the flip side: years of workarounds, unused fields and outdated custom code come across too, unless the project deliberately cleans them up. Many brownfield programmes therefore run as "convert first, then innovate," with process improvements in later phases.

Greenfield: New Implementation

In a greenfield move, the company implements S/4HANA as a new system. Processes are designed around SAP's standard functionality using the SAP Activate methodology and best-practice content, with fit-to-standard workshops deciding where the business adopts the standard and where it genuinely needs something different.

How it works

Master data and open items — open invoices, open orders, current balances, active assets — are migrated into the new system, typically with the SAP S/4HANA Migration Cockpit, using staging tables or direct transfer from the source. Full transactional history usually stays behind. Companies keep the old system read-only for a period or move history to an archive or data warehouse for reporting and audit access, and eventually decommission the old system.

Strengths and weaknesses

Greenfield delivers the cleanest result: standard processes, minimal custom code, a clean core that upgrades easily and the full benefit of new capabilities from day one. It is the natural choice when the current system no longer fits the business, has become too customised to maintain, or when the business is changing anyway. The costs are time, disruption and change management: every process is redesigned, every user retrained, and historical comparisons across the go-live date need extra reporting effort.

Selective Data Transition

Selective data transition sits between the two, and it is less a single method than a family of approaches. The common idea is to build a new S/4HANA target and move into it only what you choose — specific company codes, selected years of history, chosen configuration — rather than all or nothing.

One common pattern is the shell conversion: copy the existing system without transactional data, convert that empty shell to S/4HANA, rework the configuration where needed, then migrate selected data into it. Another is mix and match: combine a cleaned-up template with selected configuration and data from several source systems. Selective approaches are also used for carve-outs, when part of a business is sold, and for consolidating several ECC systems into one S/4HANA system after mergers.

These projects rely on specialised tooling and services from SAP and from specialist partners. That brings flexibility — keep five years of history for one division and start fresh for another — but also complexity and dependency on scarce expertise. Selective transitions are most common in large groups with multiple systems and complicated organisational change.

Side-by-Side Comparison

FactorBrownfieldGreenfieldSelective
What happensExisting ECC system converted in placeNew S/4HANA system built from scratchNew target; chosen data and config carried across
Historical dataAll keptUsually only open items and balancesWhat you choose — e.g. selected years or company codes
Process redesignMinimal unless planned separatelyFull redesign around standardPartial — redesign where needed
Custom codeCarried forward; must be remediatedRebuilt only where justifiedSelected and remediated
Typical durationShortestLongestIn between, varies widely
Disruption to usersLowerHighestModerate
Main riskCarrying old complexity into the new systemScope, change management and timelineTechnical complexity and specialist dependency
Best forStable systems with sound processesOutdated or heavily customised systems; business changeLarge groups, carve-outs, mergers, phased moves

None of these is inherently better. A well-run brownfield conversion with planned clean-up can deliver more value than a poorly scoped greenfield project, and vice versa.

How Companies Decide

A sound decision weighs evidence rather than preferences. The main factors:

Process fit. If current processes still match how the business works and largely follow standard, brownfield is attractive. If they reflect a business that has since changed — new channels, new entities, new operating model — greenfield is often worth the disruption.

Custom code and modifications. A system with modest, well-documented custom code converts cleanly. Thousands of custom objects, many unused or modifying standard code, push towards greenfield or selective approaches.

Data quality and history. If the business needs full history in the system for legal, analytical or operational reasons, brownfield or selective approaches preserve it. If data quality is poor, greenfield is an opportunity to start clean.

Organisational complexity. Many company codes across countries, several ECC instances, or pending divestments point towards selective transitions or phased approaches.

Appetite for change, budget and timeline. The ECC deadline compresses timelines, and some companies choose brownfield to reach a supported platform quickly, planning transformation afterwards. Others decide the deadline is the moment to modernise properly.

SAP's Readiness Check, a custom code analysis and process assessment workshops give the evidence. The decision is then a business one, owned by leadership, not a technical default.

A Worked Example

Consider an Indian manufacturing group with three businesses on one ECC system: a mature auto-components division with stable, largely standard processes; a consumer products division that has grown through acquisitions and runs on heavy workarounds; and a small trading unit about to be sold.

A single approach would fit none of them well. A plausible plan is a selective transition: build a new S/4HANA target, carry across the auto-components configuration and five years of its history largely as-is, redesign the consumer products processes around standard during the move, and leave the trading unit out entirely so it can be carved out cleanly. The group gets a supported platform for its core business quickly, a genuine redesign where it is needed, and a clean separation for the divestment.

Many real programmes are also phased: one country or division goes live first as a pilot, lessons are applied, and others follow in waves. Phasing reduces risk and lets the business absorb change, at the cost of a longer overall timeline and temporary interfaces between old and new systems.

Where RISE With SAP Fits

Many customers combine their move with SAP's cloud offering, RISE with SAP, under which S/4HANA runs as a private cloud edition with infrastructure and technical operations bundled. RISE is a commercial and operating model, not a fourth migration method — brownfield, greenfield and selective transitions are all possible within it. SAP has also introduced extended options for some customers who need more time, so confirm current terms for any specific situation.

What Each Approach Means for Consultants

On brownfield projects, functional consultants spend much of their time on preparation and validation: Business Partner conversion, simplification items in their module, finance data migration and reconciliation, and regression testing of existing processes. ABAP developers are in heavy demand for custom code remediation. Our SAP ABAP course covers both the classic code being remediated and the modern techniques replacing it.

On greenfield projects, the emphasis shifts to fit-to-standard workshops, solution design, configuration from scratch and data migration with the Migration Cockpit. Strong business process knowledge matters most: a FICO consultant designing ledgers and closing from first principles, an MM consultant designing procure-to-pay around standard. Our SAP FICO and SAP MM courses teach these processes on S/4HANA.

On selective projects, there is a strong data and technical focus, with specialists in transformation tools working alongside functional consultants who define what moves and validate the results.

In every approach, the same skills are prized: understanding S/4HANA's changes in your module, data discipline, thorough testing, and the ability to explain trade-offs to business users.

How to Answer This in an Interview

A strong answer has three parts. Define each approach in one sentence. Compare them on two or three factors — history, process redesign, custom code, disruption. Then show judgement: "The choice depends on process fit, custom code volume, data quality and organisational complexity; I would start with Readiness Check and a process assessment." If you have project experience, give one example; if not, say what you have studied and practised.

Expect follow-ups such as "What happens to vendors in a brownfield conversion?" (Business Partner conversion through customer–vendor integration), "How do you migrate data in greenfield?" (Migration Cockpit, open items and balances), and "Why would a company choose selective?" (carve-outs, mergers, keeping chosen history).

Explore ZebLearn India's SAP courses to learn S/4HANA the way migration projects actually use it.

People Also Ask / FAQ

Which S/4HANA migration approach is most common?

Brownfield conversions are very common because of the ECC deadline and lower disruption, but greenfield and selective approaches are widely used, especially by companies modernising or reorganising.

Is bluefield the same as selective data transition?

Broadly, yes. "Bluefield" is an informal industry term for approaches that mix elements of brownfield and greenfield, which is what selective data transition does.

Does greenfield mean losing all historical data?

Not losing it — history usually stays in the old system kept read-only, an archive or a data warehouse, rather than being loaded into the new S/4HANA system.

What is the first step in any S/4HANA migration?

An assessment — typically SAP Readiness Check plus custom code and process analysis — to provide evidence for choosing the approach and scoping the project.

Can a company switch approaches mid-project?

It is possible but expensive and disruptive, which is why the assessment phase deserves serious time and leadership ownership.

Prepare for S/4HANA Migration Projects

Live classes on S/4HANA systems, online and in select cities across India Explore SAP Courses