A greenfield SAP S/4HANA implementation starts from scratch on a clean system, while a brownfield migration converts your existing SAP landscape to S/4HANA, carrying forward your current data, configurations, and processes. The right choice depends on how much of your current setup is worth keeping and how much organisational change you are prepared to manage. The sections below break down what each approach actually involves, where the risks sit, and how data migration works differently in each case.
Which SAP S/4HANA approach is right for your organisation?
The right SAP S/4HANA approach depends on how much your current processes align with SAP best practices and how much disruption your organisation can absorb. If your existing ERP setup is heavily customised, outdated, or misaligned with where the business is heading, a greenfield implementation often makes more sense. If your processes are largely sound and you need to minimise disruption, a brownfield migration is usually the faster, lower-risk route.
There is no universal answer. The decision turns on a few practical factors:
- Degree of customisation: Heavy custom code in your current SAP system can make brownfield migration technically complex and costly to clean up.
- Business process maturity: If your processes need a fundamental rethink, greenfield gives you a clean slate to design them properly.
- Timeline and budget: Greenfield projects typically take longer and require more change management effort. Brownfield is generally faster but carries its own technical debt.
- Organisational readiness: A greenfield implementation demands significant change management capacity. Brownfield requires strong technical preparation and data quality work.
Before committing to either route, it is worth taking stock of where your organisation actually stands. We typically start with a maturity assessment that gives you a clear baseline across processes, people, and systems before any roadmap or budget is locked in. That clarity makes the greenfield versus brownfield decision much easier to defend to the C-suite.
What does a greenfield SAP S/4HANA implementation actually involve?
A greenfield SAP S/4HANA implementation means building a new SAP environment from the ground up, without migrating your existing system configuration. You design your business processes from scratch, adopt SAP standard functionality where possible, and load only the data you need going forward. It is a full reimplementation rather than an upgrade.
In practice, greenfield projects involve several distinct phases:
- As-Is and To-Be analysis: Mapping your current processes and defining how they should work in the new system.
- System design and configuration: Building the new SAP S/4HANA environment based on your To-Be process design.
- Data migration: Selecting, cleansing, and loading only the data that is relevant to the new system, rather than carrying everything across.
- Testing: Validating that the new system behaves as designed before go-live.
- Cutover and go-live: Switching from the old system to the new one, with careful planning to avoid operational disruption.
- Hypercare: Post-go-live support to stabilise the system and resolve issues quickly.
The main advantage of greenfield is that you are not constrained by legacy decisions. You can adopt SAP S/4HANA’s standard processes and embedded best practices without working around years of accumulated customisation. The trade-off is time, cost, and the significant change management effort required when users move to entirely new ways of working.
What does a brownfield SAP S/4HANA migration involve?
A brownfield SAP S/4HANA migration converts your existing SAP system to S/4HANA, preserving your current configuration, custom code, and historical data. Rather than starting fresh, you are upgrading and transforming what you already have. SAP’s System Conversion tool is the standard technical mechanism for this approach.
Brownfield projects typically follow this pattern:
- System assessment: Analysing your current SAP landscape, custom code, and data quality to understand what will convert cleanly and what needs remediation.
- Custom code remediation: Reviewing and adapting custom developments that are incompatible with S/4HANA’s simplified data model.
- System conversion: Running the technical migration from your existing SAP version to SAP S/4HANA.
- Functional testing: Verifying that existing processes and integrations still work correctly in the new environment.
- Cutover and go-live: A more contained cutover than greenfield, but still requiring careful planning and real-time monitoring.
- Hypercare and stabilisation: Post-go-live support to address issues that surface in the live environment.
Brownfield is often faster and less disruptive to day-to-day operations because users largely continue working in familiar processes. However, it can perpetuate inefficiencies if existing processes are not reviewed as part of the migration. You also inherit the technical debt of your current system, which can create complications during and after conversion.
What are the main risks of each SAP S/4HANA migration approach?
The main risks of a greenfield implementation are scope creep, change fatigue, and underestimating the effort required to redesign and adopt new processes. The main risks of a brownfield migration are hidden technical complexity, data quality issues, and the tendency to carry forward processes that should have been improved.
Greenfield risks
- Scope creep: Starting from scratch creates the temptation to redesign everything, which can inflate timelines and budgets significantly.
- Change management burden: Users face entirely new processes, which increases resistance and the risk of low adoption after go-live.
- Data migration complexity: Deciding what data to bring across, cleansing it, and loading it into a new data model is time-consuming and error-prone.
- Longer timelines: Full reimplementations typically take longer than conversions, increasing exposure to business disruption.
Brownfield risks
- Custom code debt: Legacy customisations that are incompatible with S/4HANA can be expensive and time-consuming to remediate.
- Process lock-in: Migrating existing processes without reviewing them means you may carry inefficiencies into the new system.
- Data quality: Historical data accumulated over years often contains errors, duplicates, and inconsistencies that cause problems post-migration.
- Underestimated complexity: Brownfield projects can appear straightforward until the technical assessment reveals the true scope of remediation needed.
In both cases, cutover management is one of the highest-risk phases. A poorly planned cutover can disrupt operations, delay go-live, or result in data integrity issues that take weeks to resolve. Managing that phase with real-time monitoring, a tested rollback plan, and dedicated hypercare support significantly reduces that risk.
How does data migration differ between greenfield and brownfield projects?
In a greenfield implementation, data migration involves selecting, cleansing, and transforming data from your legacy system into a completely new data model. In a brownfield migration, the existing data structure largely transfers across, but data quality remediation is still needed because historical data rarely meets the standards required for a clean S/4HANA environment.
The difference matters in practice:
- Greenfield data migration requires a thorough As-Is analysis of your current data structures, a clear decision about which data to migrate (often only open items and master data rather than full historical records), and rigorous transformation and validation work to map legacy data to the new S/4HANA data model.
- Brownfield data migration is technically less complex because the data model is largely preserved during conversion. However, data quality issues in the existing system do not disappear. Duplicate master data, inconsistent records, and outdated entries all need to be addressed before or during migration to avoid carrying problems into the new environment.
In both scenarios, the quality of your data migration directly affects the stability of your system after go-live. Rushing the data preparation phase is one of the most common reasons SAP S/4HANA projects run into post-launch problems. You can explore our full range of services to see how data migration fits into the broader transformation picture.
How Optinus helps with SAP S/4HANA greenfield and brownfield migrations
We work with organisations across the full SAP S/4HANA migration journey, whether you are starting from scratch or converting an existing system. Here is what that looks like in practice:
- Maturity assessment: Before you commit to a greenfield or brownfield approach, we give you a clear baseline of where your processes, data, and systems actually stand. That removes guesswork from the decision.
- Program and project management: Our consultants have hands-on experience from real SAP migrations at leading multinationals, not just methodology knowledge. We manage end-to-end delivery from design through to post-go-live.
- Data migration management: We use rigorous As-Is/To-Be analysis and testing procedures to prevent data loss and errors, whether you are loading into a new data model or cleaning up an existing one ahead of conversion.
- Cutover management: We plan and monitor the cutover phase in real time, with hypercare and aftercare built in to protect operational continuity at go-live.
- Change management: We address both the technical and human side of transformation, driving genuine adoption rather than just delivering training sessions.
- Available on-site and remote: We work across the Netherlands, Belgium, and internationally, embedding with your team wherever the project needs us.
If you are weighing up your options for an SAP S/4HANA migration, get in touch with our team for a practical conversation about where to start. You can also learn more about what we do and the approach we bring to complex ERP transformations.
