Every organization still running SAP ECC eventually faces the same question: how do we get to S/4HANA? There are three well-established approaches, each with different implications for timeline, cost, risk, and how much of your current landscape you carry forward. This guide breaks down all three so you can have an informed conversation with your implementation partner.
The Three Migration Approaches
SAP recognizes three official paths to S/4HANA, and most real-world projects are a variation of one of these:
- System Conversion — a technical, in-place conversion of your existing ECC system, preserving history, configuration, and custom code.
- Greenfield Implementation — a fresh S/4HANA build from the ground up, adopting standard best-practice processes rather than migrating existing configuration.
- Selective Data Transition — a hybrid approach that migrates selected organizational units, data, or processes into a new S/4HANA system, leaving others behind or migrating them in later phases.
System Conversion
A system conversion uses SAP's Software Update Manager to technically convert an existing ECC system to S/4HANA in place. This is generally the fastest path for organizations that are largely happy with their current processes and configuration.
- Best for: organizations with stable, well-functioning ECC processes who want the S/4HANA data model and Fiori UX without re-implementing from scratch.
- Key risk: custom code compatibility — years of Z-programs need assessment and remediation against the simplified data model.
- Typical timeline: 6-12 months depending on customization depth and data volume.
Greenfield Implementation
A greenfield implementation starts from a clean S/4HANA system and builds configuration fresh, typically following SAP's Best Practice process content, with only master and limited historical transactional data migrated across.
- Best for: organizations with heavily customized, "worked-around" legacy processes, those undergoing significant business model change, or post-merger organizations consolidating multiple legacy SAP systems into one.
- Key risk: change management — users accustomed to legacy processes need genuine buy-in for new standard processes, not just training.
- Typical timeline: 9-18 months depending on scope and number of business units involved.
"Greenfield isn't just a technical reset — it's an opportunity to retire years of process debt. But only if the organization is genuinely willing to change, not just technically capable of it." — SAP Delivery Lead, Y2NC Technologies
Selective Data Transition
Selective data transition sits between the two extremes — using specialized tools to migrate specific company codes, business processes, or historical data selectively into a new or converted S/4HANA system. This is particularly relevant for:
- Organizations divesting or acquiring business units and needing to separate or consolidate SAP landscapes.
- Phased rollouts where some business units convert now and others migrate in a later wave.
- Situations where only recent historical data needs to move, with older history archived rather than migrated.
Decision Framework
We typically walk clients through four questions to narrow down the right approach:
- How healthy is your current configuration? Stable and well-understood favors system conversion; accumulated workarounds favor greenfield.
- How much custom code do you have, and how well is it documented? Extensive, poorly documented custom code increases system conversion risk and cost.
- Is this purely a technical upgrade, or an opportunity to change how the business operates? If the latter, greenfield is usually the more honest starting point.
- Are multiple systems, mergers, or divestitures involved? If so, selective data transition tooling is usually worth evaluating regardless of which broad approach you lean toward.
Our recommendation: run a formal assessment (custom code analysis, simplification item check, and a process fit-gap review) before committing to an approach — the right answer is rarely obvious from organizational instinct alone.
Common Pitfalls
Regardless of which path you choose, a few mistakes show up repeatedly across real projects:
- Underestimating custom code remediation effort in a system conversion because the initial assessment was done too early or too shallow.
- Underestimating change management effort in a greenfield project because the team assumes "training" is the same as "adoption."
- Choosing selective data transition for its flexibility without budgeting for the additional tooling and specialist expertise it requires.
Whichever path fits your organization, the assessment phase is where the real decision gets made — not the kickoff meeting. If you'd like help running that assessment, our team is glad to talk through what it would look like for your landscape.
