Greenfield versus Brownfield Implementation

The fundamental choice in ERP migration is between greenfield (fresh deployment with redesigned processes) and brownfield (technical conversion of existing system preserving customisations and history). Each approach has well-understood trade-offs. A third path, bluefield or selective data transition, combines elements of both. For DACH organisations migrating from legacy ERP — particularly SAP ECC to S/4HANA — the choice is one of the most consequential decisions in the implementation.

Greenfield approach

Greenfield deployment establishes a fresh system from scratch. Process design: based on the new ERP's standard best-practices rather than legacy patterns. Data migration: master data plus open transactions; historical data typically remains in legacy for audit access. Customisation: minimal, built only where business differentiation justifies it. Advantages: highest transformation potential, clean technical foundation for future evolution, lowest ongoing maintenance burden, opportunity for ERP-landscape consolidation. Disadvantages: highest implementation cost (typically 1.5-3x brownfield cost), longest duration, heaviest change-management burden, highest risk of go-live disruption. When greenfield fits: transformation-oriented projects, legacy systems with heavy outdated customisation, consolidation across subsidiaries, organisations with capacity for substantial process change.

Brownfield approach

Brownfield deployment performs a technical conversion of the existing system to the new platform. Process: preserved mostly unchanged with configuration migrated. Data migration: full historical data and customisations carried forward. Customisation: legacy customisations preserved (sometimes with conversion effort). Advantages: shorter implementation timeline (typically 30-50% faster than greenfield), lower implementation cost, business continuity preserved, historical data preserved. Disadvantages: legacy customisations perpetuated, missed transformation opportunity, technical debt carried forward, less business-process improvement. When brownfield fits: stable operations meeting business needs, limited change-management capacity, critical operational continuity, customisations central to operations. SAP-specific: SAP's System Conversion Tool provides a defined brownfield methodology for ECC-to-S/4HANA conversions.

Bluefield (selective data transition)

Bluefield combines elements of both. Process: selectively redesigned — some areas fresh design (typically financials, where new-platform best-practices justify change), other areas preserved with conversion. Data migration: structured selective data transition — not full historical migration, not purely greenfield. Specific data sets retained for audit, operational continuity or analytical purposes. Customisation: legacy customisations selectively retained and migrated; others retired or rebuilt on new-platform extension model. Advantages: combines transformation value with operational continuity; tailored to specific organisation needs. Trade-offs: higher complexity than pure-greenfield or pure-brownfield; requires specialist tooling (SNP CrystalBridge, Cbs Enterprise Transformer, SAP Data Services). When bluefield fits: organisations seeking transformation in some areas while preserving continuity in others; multi-entity rollouts where different entities deserve different approaches.

Choosing the right approach

Three decision factors. (1) Transformation ambition: high transformation goals favour greenfield; preservation goals favour brownfield; mixed goals favour bluefield. (2) Change-management capacity: strong organisational change capacity supports greenfield; limited capacity favours brownfield. (3) Operational risk tolerance: lower risk tolerance favours brownfield; higher tolerance enables greenfield. Common DACH patterns: large multinational enterprises often choose brownfield for risk management; mid-market and upper mid-market increasingly choose bluefield or greenfield to extract more business value from the migration; smaller mid-market with stable operations choose brownfield for efficiency. Hybrid within group: many multi-entity groups use different approaches per entity, with the rollout pattern shifting from one approach to another as learning accumulates.

Frequently Asked Questions

Is greenfield always better for transformation?

For transformation value, yes — greenfield enables process redesign that brownfield does not. For risk management and operational continuity, brownfield often wins. The right choice depends on what the organisation values more in the specific situation. Bluefield offers a middle path for organisations wanting balanced trade-offs.

What is the typical cost ratio?

Greenfield typically 1.5-3x brownfield cost for equivalent scope. The cost premium reflects: more comprehensive process analysis, change-management investment, training across redesigned workflows, longer implementation duration, more rigorous testing. The cost premium can be justified by greater business value capture; greenfield projects underdelivering on value capture do not justify the cost.

Can we change approach mid-project?

Difficult and expensive. Brownfield-started projects discovering they need transformation typically end up with messy hybrid outcomes. Greenfield-started projects discovering they cannot deliver the transformation may scale back to bluefield. The right strategic decision should be made upfront with informed analysis.