Migration to SAP S/4HANA: Brownfield, Greenfield or Bluefield?

In brief

Brownfield converts your existing SAP ECC system, Greenfield starts from a new installation, Bluefield migrates selectively.
The choice depends on the quality of the current system, the volume of custom developments and how far you want to transform processes.
The end of standard maintenance for SAP ECC, on 31 December 2027, sets the timeline.
An SAP Readiness Check and an analysis of actual processes let you decide on facts.

The move to SAP S/4HANA is one of the major programmes for IT departments. The first question is not when, but how: three paths exist, and the right choice depends on your current landscape, your technical debt and your business objectives.

Three paths, three logics

SAP calls Brownfield a system conversion, Greenfield a new implementation, and the so-called Bluefield approach a selective data transition. SAP presents the latter as an alternative that combines the advantages of the other two, and set up a dedicated expert group in 2020 with cbs, Natuvion and SNP.

Criterion	Brownfield	Greenfield	Bluefield
Principle	Conversion of the existing ECC system	New installation, only useful data carried over	New system, selective transfer of data and processes
History	Kept in full	No transactional history	Kept according to the chosen scope
Processes	Largely kept as they are	Redesigned on SAP standards	Harmonised by entity or by process
Custom code	To be adapted to S/4HANA simplifications	Rewritten only if still essential	Sorted: kept, adapted or dropped
Main tooling	SAP Readiness Check, Software Update Manager	SAP S/4HANA migration cockpit	Specialised selective transition tools
Typical profile	Healthy system, satisfactory processes, tight deadline	Old, highly customised system, appetite for transformation	Multi-entity group, need to phase or consolidate

Brownfield: converting the existing system

A conversion turns your SAP ECC system into SAP S/4HANA while keeping data, configuration and history. It is often the fastest route when the system is healthy and processes work well. It does, however, require real remediation work: handling S/4HANA simplification items, such as the business partner replacing customer and vendor master records, and adapting the custom code that is actually used.

Greenfield: starting from a blank page

A new implementation reinstalls SAP from scratch, based on standard best practices. It lets you get rid of years of developments that have become useless and redefine target processes. In return, the project is more far-reaching: heavier change management, data migration to organise, history to be consulted elsewhere. It is also the mandatory path to SAP S/4HANA Cloud Public Edition.

Bluefield: migrating selectively

A selective transition carries over what has value, such as certain company codes, fiscal years or processes, and starts afresh for the rest. It suits groups that want to consolidate several systems, harmonise their charts of accounts or migrate entity by entity. It requires specialised tools and expertise, because every transferred piece of data must remain consistent with the rest.

The ECC timeline sets the pace

SAP has set the end of standard maintenance for SAP ECC at 31 December 2027, with optional extended maintenance until the end of 2030. In February 2025, SAP announced a transition option, SAP ERP, private edition, which covers 2031 to 2033 for large customers whose systems have moved to that edition before the end of 2030. For a large scope, allow twelve to twenty-four months between scoping and cut-over: decisions are being made now.

How to decide: four preliminary analyses

SAP Readiness Check: SAP’s free tool lists the simplification items, add-ons and custom code affected by a conversion.
Actual processes: process mining measures the gap between your processes and the standard, and therefore the value of a redesign.
Custom code: usage statistics often show that a large share of custom code is no longer called.
Data: volume, quality and the history to keep point to a full, partial or minimal carry-over.

These analyses take four to eight weeks and produce a reasoned recommendation, including the choice of target edition, Public or Private, and a realistic plan given the ECC deadlines.

Frequently asked questions

Which path is the fastest?

Usually Brownfield, because it carries over the existing system without redesigning processes. Its duration depends mainly on the volume of custom code to adapt and the simplification items to handle. An SAP Readiness Check, run upfront, gives a first measure of this work before committing to a plan.

Can history be kept with Greenfield?

Not in the new system: a new implementation does not carry over transactional history. You keep the old system for display, archive the data or expose it in a data warehouse. If history is essential in S/4HANA, a selective transition is a better fit.

Is Bluefield only for large groups?

It is most common there, because it meets the needs of system consolidation, divestments or entity-by-entity migration. A mid-sized company can also use it to carry over only a few fiscal years, but the tooling and expertise required weigh more heavily in the budget of a small project.