Brownfield Implementation

A brownfield implementation is an approach to deploying or upgrading enterprise software, in particular ERP, in which the existing system is converted and carried forward rather than rebuilt from a clean slate. Configuration, historical data, custom developments and integrations are migrated and adapted to the new release or platform. It is the counterpart to a greenfield implementation, which starts fresh with standard processes. The term became widely used in the context of moving to next-generation ERP suites, where organisations had to choose between a technical conversion of what they already ran and a redesign. The trade-off, examined in greenfield versus brownfield, is continuity against the chance for a clean reset.

What a brownfield approach involves

In a brownfield implementation, the project converts the current productive system to the new target, preserving as much of the existing investment as feasible. This typically means a technical migration of master and transactional data, retention or adaptation of existing customising and custom code, and continuation of established processes. Functional change, if any, is introduced in later phases. The result is that users recognise the system after go-live, and many configurations behave as before, while the underlying platform or release has changed.

Brownfield versus greenfield

The two approaches sit at opposite ends of a spectrum, and many real projects are a hybrid:

• Brownfield minimises business disruption and reuses proven configuration, but also carries forward legacy complexity and any accumulated technical debt.
• Greenfield allows process redesign and adoption of standard, best-practice flows, at the cost of more change-management effort and a larger reimplementation project.
• Hybrid or selective approaches convert parts of the landscape while redesigning others, for example keeping finance configuration but rebuilding logistics.

The right choice depends on how fit-for-purpose the existing system is, the appetite for organisational change, timeline, budget and risk tolerance.

Advantages and risks

The principal advantage of brownfield is continuity: shorter business disruption, reuse of working configuration and integrations, and a lower change-management burden because processes stay familiar. It is often attractive where the current system is broadly sound and the priority is a technical platform move rather than transformation. The principal risk is that it perpetuates the past. Obsolete customisations, redundant data and outdated process design are carried into the new environment, and the opportunity to simplify is missed. A disciplined brownfield project therefore usually pairs the conversion with a clean-up: archiving or deleting stale data, retiring unused custom code, and reviewing configuration against current standard functionality.

Practical considerations

Successful brownfield projects start with a thorough analysis of the existing landscape, including a custom-code inventory and a data-quality assessment, so that the team knows what is being carried forward and why. Data migration is still a major workstream, even though structures are reused, because data must be cleansed and made compatible with the target. Realistic testing of converted processes and custom developments is essential, as is a sandbox to rehearse the conversion. Organisations should also decide deliberately what not to migrate; the discipline of pruning during a brownfield move is what prevents it from simply replicating an ageing system on newer infrastructure.

Related Topics

• Greenfield implementation
• Data migration
• S/4HANA