ECC-to-S/4HANA migration playbook: paths, sequencing & licensing.
An ECC-to-S/4HANA move is two projects on one timeline: a technical transformation and a commercial re-licensing event. This note sets out the migration paths — brownfield, greenfield and bluefield — the RISE, GROW and on-premise commercial models, and the conversion, digital-access and FUE decisions that decide whether the project ends on budget or in an unplanned licensing bill.
There is no default S/4HANA path. Brownfield preserves a stable, well-run ECC estate at lowest disruption; greenfield buys process re-engineering at the cost of the heaviest change programme; bluefield splits the difference for large, heterogeneous landscapes. Whichever you choose, the decision that moves the money is the licence conversion — convert on a measured FUE baseline, settle digital access on the way in, and sequence it all against the 2027 maintenance cliff rather than discovering the bill at cutover.
01 Key findings
Migration is a re-licensing event, not a free continuation. Moving to S/4HANA generally requires converting legacy ECC entitlements into the new role-based model. The mapping of named-user types and engines to Full Use Equivalent (FUE) licences is where value is preserved or quietly lost.
The 2027 maintenance deadline paces everything. Mainstream ECC maintenance ends in December 2027 (extended to 2030 at an uplift). That cliff, not readiness, is what compresses timelines — and vendors use the pressure to push commitments.
Path and commercial model are one decision. Greenfield lends itself to a fresh RISE or GROW subscription; brownfield often aligns with carrying perpetual entitlements onto on-premise S/4HANA. Choosing the path without the commercial model invites a mismatched contract.
Conversion is the best right-sizing window in years. Contract conversion credits legacy licence value toward S/4HANA, but only against measured usage does it correct historic over-licensing. Converted passively, shelfware is translated straight into expensive FUE.
Digital access arrives with the move. Indirect and automated use shifts to document-based digital access on S/4HANA. Settle the indirect-access position on a measured document baseline during migration, not by estimate after go-live.
Interim maintenance funds the programme. What you do with ECC support across the migration window — extended maintenance versus third-party support — materially shapes the budget and can pay for the transformation itself.
02 Migration paths
Three established routes reach S/4HANA. The choice shapes cost, risk and timeline before a single licence is converted.
- Converts the existing system in place, keeping processes & data
- Lowest business-change and re-training burden
- Aligns naturally with carried-forward perpetual entitlements
- Carries forward legacy customisation and technical debt
- Little opportunity to re-engineer poor processes
- Custom-code remediation can still be substantial
- Clean design on standard, best-practice processes
- Leaves legacy customisation behind
- Fits a fresh RISE or GROW subscription commitment
- Largest change-management and adoption effort
- Data migration and reconciliation are demanding
- Longest elapsed timeline of the three
- Converts the core while re-implementing selected areas
- Moves markets on independent timelines
- Keeps history where it matters, resets where it does not
- Most complex to orchestrate and govern
- Tooling and partner dependency is higher
- Hybrid entitlement position can be hard to model
Decide the deployment model alongside the path, not after it. A greenfield build lends itself to a fresh subscription; a brownfield conversion may align more naturally with carrying forward perpetual entitlements. Settling path and commercial model together avoids a contract that fights the technical plan.
03 Path comparison
The same destination, three profiles of cost, risk and entitlement. Weight them against your legacy debt and appetite for change.
| Path | What it does | Best fit | Licence alignment | Trade-off |
|---|---|---|---|---|
| Brownfield | Convert existing system in place | Stable, well-run ECC to preserve | Contract conversion; perpetual carry-forward | Carries forward legacy complexity |
| Greenfield | New build, re-engineered processes | Heavy legacy debt; appetite for change | Fresh RISE / GROW subscription | Largest change-management effort |
| Bluefield | Selective convert plus re-implement | Large, heterogeneous markets | Hybrid: mixed perpetual & subscription | More complex to orchestrate |
04 Commercial models
The deployment and commercial model is the other half of the destination decision. RISE and GROW are subscription bundles; on-premise keeps the familiar named-user-and-engine world. Five dots = strongest fit on that dimension.
05 Licensing & the 2027 deadline
Migration surfaces licence value that ECC hid: the conversion mechanics, the FUE metric, the digital-access position, and the maintenance clock — the part buyers most often underplan and where mapping legacy licences to S/4HANA roles earns its keep.
Mainstream ECC maintenance ends December 2027, with extended support to 2030 at an uplift on a system you are leaving. Moving ECC to third-party support during the migration window typically lowers that interim cost and can fund the programme — the trade-off is set out in ECC extended maintenance vs third-party support. Either way, the maintenance decision and the migration plan share one timeline.
Convert on a measured FUE baseline, not the legacy count. Contract conversion credits legacy licence value toward S/4HANA, but only measured usage keeps professional-user shelfware from being translated into expensive role-based licences. The same window is the moment to settle digital access on a measured document baseline — see the Digital Access Adoption Program and SAP API and indirect-access changes.
06 Path-selection framework
Four considerations drive the path decision. Weight them to your situation before committing.
Legacy debt & custom code
Heavy customisation and poor process hygiene favour a greenfield reset; a clean, well-run ECC estate favours brownfield conversion that preserves what works.
Appetite for change
Genuine capacity to re-engineer processes and re-train the business unlocks greenfield value; limited change tolerance points to brownfield or a phased bluefield.
Commercial model fit
A subscription (RISE / GROW) commitment aligns with a fresh build; carried-forward perpetual entitlements align with in-place conversion. Decide both together.
Timeline vs the 2027 cliff
The elapsed time each path needs must fit inside the maintenance runway. Where it does not, plan the interim ECC support decision as part of the path choice.
07 Our recommendation
Your ECC is stable and well-run, legacy debt is contained, and disruption tolerance is low. Convert in place, carry perpetual entitlements forward, and use the conversion to right-size FUE against measured usage.
Legacy debt is heavy and the business will back real process change. Build clean on standard processes, pair it with a fresh RISE or GROW subscription, and lock the commercial terms before the 2027 pressure peaks.
You run a large, heterogeneous landscape where one path does not fit all markets. Convert the core, re-implement the weak areas, and model the hybrid entitlement position carefully before committing.
08 Cutover sequencing
The highest-value process choice once the path is set — how you land the change against risk and the maintenance clock:
Phased cutover Recommended
Discovery and readiness, then build and iterate in non-production on realistic masked data, rigorous integration testing, then staged go-live with a fallback plan. Risk is contained and the commercial workstream keeps pace with the technical milestones.
Big-bang cutover Weaker
Convert and switch the whole estate at once. Faster on paper, but concentrated risk, a single fallback point, and a licence conversion negotiated under go-live pressure rather than on a measured baseline.
De-risk your S/4HANA conversion
Our SAP practice models the migration path and the licence conversion on one plan, so the transformation does not become an unbudgeted commercial surprise.
The Licensing Edge
Weekly SAP and enterprise-licensing intelligence for IT leaders. 3,000+ subscribers.