Greenfield Implementation

Greenfield implementation describes the approach of deploying a new ERP system from scratch, with business processes redesigned to fit the new platform's standard model. Greenfield contrasts with brownfield implementation (technical conversion of existing ERP preserving customisations and history) and bluefield / selective data transition (hybrid). For DACH organisations migrating from legacy ERP — particularly SAP ECC to S/4HANA — greenfield is the transformation-oriented option, delivering the most business value at the highest implementation effort.

Greenfield methodology

Greenfield deployments follow several distinguishing principles. (1) Clean core: new ERP installation, no carried-over customisations from legacy. Customisation built only where business-process differentiation justifies it. (2) Standard processes: business processes redesigned to align with the new ERP's best-practice templates (SAP Best Practices, Microsoft Dynamics 365 standard configurations, Oracle Cloud ERP reference implementations). Change management is substantial. (3) Selective data migration: only master data and open transactions migrate; historical transactions remain in legacy system for audit access. (4) Phased rollout: by entity, geography, or module rather than big-bang where feasible. The approach typically delivers 12-36 month implementation duration depending on scope.

Trade-offs

Greenfield advantages: greatest transformation potential (rethink processes, eliminate legacy technical debt), clean foundation for future evolution, lowest ongoing maintenance burden, opportunity to consolidate group ERP landscapes. Trade-offs: highest implementation cost (typically 1.5-3x brownfield cost for equivalent scope), highest change-management burden (business processes change), longest implementation duration, highest risk of go-live disruption. The choice between greenfield and brownfield reflects organisational priorities: transformation ambition versus risk management, business-change capacity versus speed-to-target.

SAP greenfield with S/4HANA

SAP ECC-to-S/4HANA greenfield migrations follow a defined methodology. SAP Activate: SAP's implementation methodology combining best-practice processes, deployment tools and accelerators. SAP Best Practices: pre-configured business processes covering common scenarios per industry. Fit-to-standard workshops: early-phase workshops align business processes with standard SAP configurations; gaps identified for custom development. RISE with SAP: commercial offering bundling S/4HANA Cloud Private Edition with services for greenfield migrations. For DACH organisations selecting greenfield, the typical implementation partner is one of the large SAP-services firms (Accenture, Deloitte, Capgemini, SoftwareONE, NTT DATA Business Solutions, msg systems, T-Systems, All for One Group, EY).

Practical considerations

Three patterns for successful greenfield projects. (1) Strong executive sponsorship: greenfield is business-led transformation more than IT project. Without active executive sponsorship driving process change, the project drifts toward technical replacement that fails to capture greenfield value. (2) Discipline on customisation: greenfield's value comes from clean-core implementation. Every customisation request must be challenged: is the business value sufficient to justify the ongoing-maintenance cost? Mature greenfield governance typically rejects 60-80% of initial customisation requests. (3) Manage data-migration scope: the temptation to migrate 'just in case' data inflates effort without proportional benefit. Strict scope discipline (master data plus 12-24 months of transactions, legacy retained for audit access) is the standard. Companies attempting to migrate 10+ years of detailed history consistently overrun timelines.

Frequently Asked Questions

When is greenfield better than brownfield?

Greenfield wins when: business transformation is a strategic priority, existing ERP customisation is heavy and outdated, change-management capacity is available, group ERP-consolidation is desired. Brownfield wins when: existing ERP works well, downtime risk must be minimised, change-management capacity is constrained, key customisations are central to operations.

How long does greenfield S/4HANA typically take?

For DACH mid-market: 18-30 months. For upper mid-market: 24-36 months. For large enterprise with multi-country rollout: 36-60+ months including pilot, hardening and rollout phases. The duration scales with entity count, geographical complexity and degree of process change.

What is the typical cost premium for greenfield versus brownfield?

Typically 50-100% higher implementation cost for greenfield. The cost premium reflects: more comprehensive process analysis and design, 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 that underdeliver on value capture do not justify the cost.