Greenfield versus Brownfield Implementation

The terms greenfield and brownfield describe two contrasting strategies for introducing or renewing an ERP system. A greenfield approach builds the new system from a clean slate, redesigning processes and master data without carrying over the old configuration. A brownfield approach converts an existing installation in place, preserving historical data, customising and process logic. The distinction became widely used during large platform changes such as the move to S/4HANA, where organisations must decide between a fresh start and a technical conversion. Each path involves different trade-offs in cost, risk, project duration and the degree of process change the organisation is willing to absorb.

Greenfield: a clean start

In a greenfield implementation the organisation designs the target system from first principles. Process flows are redefined around current best practice and standard functionality, often reducing accumulated customising from earlier years. Master data is cleaned, restructured and selectively migrated rather than copied wholesale.

• Opportunity to simplify and standardise long-grown processes.
• Lower technical debt because legacy modifications are not carried forward.
• Higher change-management effort, as users face new screens and workflows.
• Selective data migration rather than a full technical transfer.

Brownfield: conversion in place

A brownfield approach performs a technical conversion of the existing system. Configuration, custom code and transactional history are retained, so the familiar process landscape continues largely unchanged after the upgrade.

• Faster initial go-live because existing logic is reused.
• Continuity for users and existing integrations.
• Risk of carrying forward obsolete customising and data-quality issues.
• Limited opportunity to redesign processes during the same project.

Hybrid and selective approaches

Many projects combine elements of both. A selective or "bluefield" transition migrates chosen organisational units, processes or data sets onto a freshly configured target while leaving others on the converted basis. This allows phased modernisation, for example moving one company code at a time. The choice often interacts with deployment decisions such as on-premise versus SaaS ERP, and with whether the project is treated as a fresh implementation or an ERP migration.

Choosing between the two

The decision is rarely purely technical. Greenfield suits organisations whose processes have drifted far from standard, who want to retire heavy customising, or who are restructuring the business anyway. Brownfield suits stable organisations that value continuity, have manageable customising and need a predictable upgrade rather than a transformation. Key inputs include the volume and quality of master data, the extent of custom code, regulatory or audit constraints, available budget and the appetite for organisational change. A structured assessment of the existing landscape, including a review of master-data quality, usually precedes the choice. Whichever path is taken, the underlying objective is the same: a maintainable, standards-aligned ERP platform that supports the business without perpetuating avoidable complexity.

Related Topics

• Greenfield implementation
• Brownfield implementation
• ERP migration