SAP Practice
SAP ECC to S/4HANA migration. The buyer playbook.
SAP ECC support ends in 2027. The migration to S/4HANA is unavoidable, and it is the moment SAP tries to reprice the estate. Read the playbook before the conversion quote lands.
SAP ECC support ends in 2027. The migration to S/4HANA is unavoidable, and it is the moment SAP tries to reprice the estate. Read the playbook before the conversion quote lands.
SAP ECC support runs to 2027 with extended maintenance to 2030. This playbook covers the conversion paths, how licensing converts, the real cost, and the buyer side moves that keep a migration from becoming a price reset.
SAP ECC is the legacy ERP that most large enterprises still run. S/4HANA is the successor, built on the HANA in memory database. The migration is unavoidable for ECC customers who want SAP support past 2030.
The technical project gets the attention. The commercial reset gets the money. This playbook treats the migration as a negotiation event first and a technical event second.
A migration is two projects running together. One moves the technology. One converts the contract. Buyers who plan only the first lose control of the second.
The technical work moves the system onto the HANA in memory database, simplifies the data model, and reworks custom code. The Fiori interface replaces much of the classic SAP GUI. Scope depends on how much custom development sits in the existing ECC system.
The commercial work converts ECC licenses into the S/4HANA model. SAP measures users in Full User Equivalents rather than the old named user tiers. This conversion is where price moves.
Data cleansing, process redesign, and testing absorb most of the effort. The list below sets the order that protects budget.
Three paths exist. The choice drives both the technical effort and the license conversion mechanics.
S/4HANA conversion paths compared
| Path | What happens | License treatment | Best fit |
|---|---|---|---|
| Brownfield | Technical conversion of the existing system | Contract Conversion of existing entitlement | Clean ECC estates wanting speed |
| Greenfield | New build with reimplemented processes | New S/4HANA licenses, possible credits | Heavy customization or process reset |
| Selective | Phased move of chosen processes and data | Mixed conversion and new licensing | Large multi entity groups |
Brownfield converts the existing system in place. It is the fastest path and usually the cheapest on direct license cost. It carries forward existing technical debt.
Greenfield rebuilds on a clean S/4HANA system. It costs more and takes longer. It removes legacy debt and lets the buyer reset the process landscape.
Selective transition moves chosen company codes or processes in phases. It suits large groups that cannot take a single cutover. It is the most complex to license.
SAP offers two commercial programs to convert legacy entitlement. The choice shapes the cost and the audit posture for years.
Contract Conversion maps existing named user and engine licenses into S/4HANA value, then applies a conversion ratio. It preserves prior investment. SAP publishes the framework on its RISE with SAP and conversion materials.
Conversion to the New World retires the legacy contract and issues a fresh S/4HANA agreement. SAP often pushes this path because it resets discount baselines. Read the commercial terms before signing.
Conversion recounts users in Full User Equivalents. A clean recount is the single largest lever. The points below recur in our engagements.
The standard system integrator pitch is that you should convert the contract at the same time you cut over the technology, because it is simpler. We disagree. In roughly seven out of ten conversions we have benchmarked, bundling the commercial signature into the technical go live handed SAP the leverage and reset discounts upward. The buyer side move is to separate the two events, lock the FUE baseline and indirect access position 9 to 12 months ahead, and sign the commercial conversion against a defended count rather than an SAP proposed one. Convenience at cutover is the most expensive convenience in the program.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A conversion is not a technology upgrade with a price tag attached. It is a repricing event with a technology upgrade attached. Treat it that way.
Cost splits into three buckets: licenses, implementation, and run. The license bucket is the one the buyer controls most directly.
License cost depends on the FUE count, the engine set, and whether the buyer chooses RISE or on premise. A defended recount moves this bucket more than any discount conversation.
Implementation runs through a system integrator. Brownfield is cheaper and faster. Greenfield costs more but resets the landscape. Selective sits in between with the most coordination overhead.
Run cost includes infrastructure, support, and the annual maintenance or subscription fee. The points below shape the five year view.
Five moves recur in every well run conversion. They are commercial, not technical.
Build the defensible FUE and engine baseline 9 to 12 months before any conversion quote. The baseline is the anchor for every later conversation.
Decouple the go live from the contract signature. SAP gains leverage when both land in the same quarter.
Keep digital access out of the conversion bundle. Negotiate it as a separate, measured item using SAP's published licensing terms.
Conversion ratios vary widely. Benchmark the proposed ratio against comparable deals before accepting it.
Cap annual uplift and align the term to a realistic adoption curve. Avoid committing to volume the project will not consume in year one.
Mainstream SAP ECC maintenance ends in 2027. SAP offers paid extended maintenance through 2030 for customers who need more time. After that, customers must move to S/4HANA or third party support.
Brownfield converts the existing ECC system in place. Greenfield rebuilds on a clean S/4HANA system with reimplemented processes. Brownfield is faster and cheaper on direct license cost. Greenfield removes legacy technical debt.
A Full User Equivalent, or FUE, is the S/4HANA user metric. It weights different user types into a single count. The conversion from legacy named users to FUE is where most pricing movement happens.
It can, if you let it. SAP often bundles a digital access reset into the conversion quote. Negotiate indirect access as a separate, measured item rather than accepting it inside the conversion.
No, where it can be avoided. Bundling the commercial signature with the technical go live hands SAP leverage. Separate the two events and sign the conversion against a defended baseline.
Contract Conversion maps your existing named user and engine licenses into S/4HANA value using a conversion ratio. It preserves prior investment and is usually the stronger buyer side path compared with a fresh agreement.
A brownfield conversion can complete in 9 to 14 months for a clean estate. Greenfield and selective programs at large enterprises run 18 to 30 months. The commercial preparation should start well before the technical work.
No. RISE is one delivery option, but on premise and private cloud paths remain available. Compare RISE against on premise on total cost before committing, since the subscription model changes the long term economics.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The conversion is where SAP tries to reset the deal. The buyer who walks in with a defended baseline converts on their own numbers.
