Greenfield, brownfield, bluefield: which S/4HANA call is the real one?
Three words sit together on a slide. In production they do not. The call is data and close discipline, not a slogan.
Atilla Kuruüzüm · March 12, 2026 · 8 min read
Most S/4HANA tables open with the same sentence: greenfield or brownfield. Bluefield is appended because someone said ‘the middle’. The middle is not a method name. It is a selection pack: which data, which process, which Z-code travels. This piece puts the three paths next to each other. It does not crown a winner.
When is greenfield actually green?
If you can live in the standard, your add-on list is short, and close is not an Excel empire run by three people, greenfield buys speed. The gain is not a ‘clean S/4’ romance: being born properly into the Universal Journal, not postponing Business Partner, not faking old asset accounting. The cost is history. Ten years of open items, disputes and old cost estimates are not in the new system — archive and reporting are a separate call.
What brownfield keeps — and what it hides
Brownfield promises to move a working factory. Under the promise sit Z-code and dirty master. You may be moving habit, not process. If document types, the chart and close roles do not change, ‘technical conversion is done’ will cut you on the first close. Do not sign conversion without a dry run and account-level balance checks. A signature is not a slide.
Bluefield: selective, not indecisive
Bluefield is sold as ‘new here, convert there’. That needs governance. Otherwise every team declares its own green and the template dies. If you select, write the criteria: legal must, volume, Z-dependence, close criticality. ‘Sales wants it’ is not a criterion.
Where RISE and GROW sit
They replace none of the three. RISE is an operating and contract model; GROW is a product for mid-market teams who will live in the standard; on-premise is data residency and add-on control. Mapping greenfield to GROW is sometimes right; mapping brownfield to RISE is sometimes right. There is no automatic pairing. Another article covers the contract; this one is method.
Türkiye localization cannot be phase 2
e-Invoice, e-ledger, e-despatch and the GİB calendar are go-live criteria. Postponing them because you chose greenfield means running the first legal month in Excel. Saying ‘we already had it’ because you chose brownfield means missing the break on S/4 objects. Localization is a rail independent of method. Do not pull the rail.
At Conforcus we take the call in a workshop: add-on inventory, close calendar, BP and assets. Ticking three boxes on a slide is not a decision. The decision is who you will close the first period with.
Frequently asked questions
Which is faster, greenfield or brownfield?
Brownfield usually looks shorter because processes are not redesigned; however migrated custom code and dirty master data give that time back. In greenfield the timeline depends on data migration scope. The real answer comes from the custom-code inventory in the readiness assessment.
Is bluefield a real method?
Bluefield is the marketing name for selective data transition approaches. It is technically possible but demands governance: unless written criteria decide which company code is rebuilt and which is migrated, the template falls apart.
What is the first step in deciding?
A picture of the system: which custom objects ran how often in the past 12–24 months, what master data quality looks like, which statutory requirements are critical. A method decision without this inventory tends to be revised mid-project.