Greenfield versus brownfield versus selective conversion to RISE.

Once the decision to move to RISE with SAP has been made, the second decision is the conversion path. Three principal paths exist. A greenfield conversion rebuilds the SAP system from scratch on the new platform. A brownfield conversion lifts the existing system and converts it in place. A selective conversion combines elements of both, taking some configuration and customisation forward and rebuilding others. Each path has different cost, timeline, risk, and outcome characteristics, and the right path depends on the buyer's estate, capability, and strategic intent. This article walks through the three paths, the decision criteria that distinguish them, and the contractual provisions that protect the buyer regardless of which path is chosen.

The greenfield path

Greenfield rebuilds the SAP system from a clean configuration, with new data, new processes, and new code where required. The path is the longest in duration and the highest in implementation cost. It is also the path that produces the cleanest end state. A greenfield conversion forces the buyer to re examine every business process, to re evaluate every customisation, and to take only what justifies its inclusion. The output is a system that fits the future state, not the historical state.

Greenfield is the right path when the existing system carries significant technical debt, when the business processes need re engineering, when the data quality is poor enough to require cleansing, and when the buyer has the change capacity to absorb a re engineering programme in parallel with a system migration. The path is also the right one for a buyer that wants to standardise across previously divergent business units, using the conversion as the forcing function for harmonisation.

The risks of greenfield are well known. The timeline is long, often three to five years for large enterprises. The cost is high. The change management burden is heavy. The risk of a stalled programme is real, and the cost of a stalled programme is significant. The buyer that chooses greenfield should be deliberate about the choice and well resourced for the execution.

The brownfield path

Brownfield converts the existing system in place. Configuration, master data, transactional data, and custom code move forward, with technical conversion to the new database and platform but with minimal functional change. The path is the shortest in duration and the lowest in implementation cost. It is the path that preserves the maximum continuity for the business.

Brownfield is the right path when the existing system is technically healthy, when the custom code estate is well understood and worth preserving, when the business cannot absorb a re engineering programme, and when the buyer wants to capture the RISE platform benefits without a multi year transformation. The path is also right for regulated buyers that cannot afford the validation effort of a full rebuild and need to maintain operational continuity through the conversion.

The risks of brownfield are different. The technical debt carries forward. The custom code remediation work is required regardless. The opportunity to re engineer is lost, or at least deferred. A brownfield conversion that does not produce significant capability improvement may have the disruption of a migration without the benefit. The buyer should set the success criteria honestly, with brownfield treated as a platform move rather than a transformation.

The selective conversion path

Selective conversion combines elements of both. The buyer takes a subset of the existing configuration forward, rebuilds another subset, and decides at a granular level which parts of the system go which way. The path is more complex to plan than either greenfield or brownfield in pure form. The output is a system that preserves what is valuable in the existing estate and rebuilds what is not.

Selective conversion is the right path when the existing system has both healthy components and components that need re engineering, when the buyer has the analytical capability to distinguish between them, and when the project management capability exists to manage the hybrid approach. The path is also right when the buyer is consolidating multiple SAP environments, taking the best of each forward and harmonising the result.

The risks of selective conversion are around scope discipline. The flexibility to take some things forward and rebuild others is also the temptation to make scope decisions ad hoc as the project progresses. A selective conversion that lacks scope discipline becomes a greenfield in disguise, with the cost of greenfield and the timeline of greenfield, but without the deliberate intent. The buyer should set the scope rules in advance and govern them rigorously.

The decision criteria

The decision among the three paths should be driven by several criteria. The custom code estate is the first. A deep and well maintained custom code estate favours brownfield. A shallow or technically degraded code estate favours greenfield. A mixed estate favours selective conversion. The business process maturity is the second. Mature, well documented processes favour brownfield. Processes that need re engineering favour greenfield. A mix favours selective conversion.

The data quality is the third criterion. High quality master and transactional data favours brownfield. Poor data quality forces some level of cleansing, which is easier in a greenfield rebuild. The organisational change capacity is the fourth. A buyer with constrained change capacity favours brownfield. A buyer with the capacity for transformation favours greenfield. The strategic intent is the fifth. A buyer using the conversion as the forcing function for transformation favours greenfield. A buyer pursuing a platform upgrade favours brownfield.

Contractual provisions that protect the buyer

Regardless of the conversion path, the buyer should negotiate contractual provisions that protect the conversion outcome. The RISE contract should specify the migration support SAP commits to provide, the timeline expected, the success criteria for the conversion, and the remedies if the conversion misses the criteria. The buyer should also negotiate continued access to the source system for a defined period after cutover, to allow validation and to support rollback if required.

The buyer should negotiate cost protection for any scope expansion that is required to make the conversion successful. SAP often quotes the conversion at a price that assumes a smooth path. If the path is not smooth, the additional cost should not be at SAP discretion. A defined cost escalation mechanism with a cap is more defensible than an open ended time and materials arrangement.

Conclusion

The conversion path to RISE with SAP is a decision that shapes the cost, the timeline, the risk profile, and the eventual outcome of the migration. Greenfield, brownfield, and selective conversion each have a place, and the right path depends on the buyer's estate, capability, and strategic intent. The buyer that chooses without analysing the criteria, or that chooses based on vendor advice without independent verification, often arrives at a path that does not fit. The work is to map the estate honestly, to evaluate the criteria deliberately, and to choose the path that aligns with the conversion outcome the buyer actually needs. The right path is not the most ambitious one. It is the one that delivers the value the buyer expects within the constraints the buyer accepts.