The right SAP S/4HANA migration path is not decided by a preference for “brownfield” or “greenfield.” It is decided by evidence about process fit, data quality, custom code, landscape complexity, regulatory history and the organization’s tolerance for change at cutover.
Direct answer
- Choose system conversion (brownfield) when the current ERP design largely supports the target business, historical data must remain in place and the organization can remediate existing custom code and technical debt.
- Choose new implementation (greenfield) when process redesign and fit-to-standard are primary goals, the legacy design should not be carried forward and only selected data must enter the new system.
- Consider selective data transition when the target requires consolidation, staged organizational moves, selected historical data or a controlled mixture of reuse and redesign.
SAP describes these as distinct transition options and notes that the applicable choices also depend on the target deployment. For example, SAP S/4HANA Cloud Public Edition uses new implementation rather than system conversion or selective transition. See SAP’s transition-path documentation and clean-core transition lesson.
Comparison by decision evidence
| Decision factor | System conversion | New implementation | Selective transition |
|---|---|---|---|
| Process design | Preserve and remediate | Redesign around target standard | Preserve selected processes and redesign others |
| Historical data | Retain broadly | Migrate defined master data, balances and open items | Select history by scope and business need |
| Custom code | Analyse, retire or adapt | Do not inherit legacy modifications by default | Reuse selected assets after assessment |
| Consolidation | Limited as a conversion objective | Possible through a new target design | Often relevant for split, merge or phased scenarios |
| Cutover model | Commonly one major conversion event | Big-bang or phased rollout | Can support selective or phased moves |
| Main risk | Carrying forward avoidable debt | Underestimating business redesign and data preparation | Tooling, service and reconciliation complexity |
This table is a starting hypothesis, not a selection result. SAP’s own guidance says selective-transition outcomes are customer-specific and commonly delivered with specialist services. Review the official Selective Data Transition engagement guidance.
A defensible selection sequence
- Define the target deployment. Confirm public cloud, private cloud or on-premises constraints before comparing routes.
- Measure process fit. Identify which end-to-end processes should be retained, standardized, redesigned or retired.
- Profile data. Quantify data volume, quality, retention obligations, active documents and reconciliation requirements.
- Classify custom code and integrations. Record usage, business criticality, target compatibility and clean-core disposition.
- Model cutover and business continuity. Compare allowable downtime, phased rollout needs, rollback boundaries and period-close constraints.
- Calculate delivery exposure. Estimate remediation, testing, business change, dual-running and specialist-tool costs for each option.
- Record assumptions and stop conditions. Do not present an option as selected while critical evidence remains unvalidated.
What should the migration assessment produce?
A useful assessment is a decision pack, not a presentation of product features. It should contain the current landscape, target constraints, process-fit findings, data profile, custom-code inventory, integration dependencies, security implications, option comparison, cost range, delivery risks and a recommendation with named assumptions.
The recommendation should also identify what could reverse the decision. A newly discovered regulatory retention requirement, an unsupported add-on or a severe data-quality issue can materially change the route.
Practical lab: build the option paper
In the S/4HANA Readiness Lab, learners inspect a synthetic ECC landscape, compare the three transition paths and build an initial risk register. The exercise tests whether a participant can connect technical findings to a business decision rather than repeat migration terminology.
Frequently asked questions
Is brownfield always faster than greenfield?
No. System conversion can reduce the amount of process redesign, but elapsed time depends on custom-code remediation, data quality, integrations, testing, downtime constraints and organizational readiness. “Faster” is an assumption until those factors are measured.
Is selective data transition simply a compromise between brownfield and greenfield?
No. It is a distinct approach with its own data-selection, transformation, tooling, service and reconciliation requirements. It should be chosen because those capabilities match the target outcome, not because stakeholders cannot agree on another route.
Does a migration path guarantee a clean core?
No. SAP states that all transition options can support clean-core objectives, but governance and extension decisions determine whether the core remains upgrade-ready after go-live.
Study the complete SAP S/4HANA migration curriculum or enquire about a corporate cohort.