SAP ECC to S/4HANA: The Migration Licensing Playbook
SAP ECC mainstream maintenance ends December 31, 2027. The path you pick, product conversion, contract conversion, RISE, or greenfield, swings the 5 year bill by $3.45M on the same estate, and most of that gap is decided before you sign.
Prepared by Redress Compliance · June 2026 · Representative SAP ECC estate scenario (benchmark scenario, not a quote)
Executive Summary
SAP set a hard date. Mainstream maintenance for SAP ECC 6.0 ends on December 31, 2027, with optional extended maintenance to December 31, 2030 at an uplift of two percentage points on the maintenance base. After that, you sit on customer specific maintenance with no new fixes.
That deadline is real, but it is also SAP's primary source of leverage. The account team uses the clock to push the most expensive path. The migration is a licensing event before it is a technical one, and the licensing decision is where the money is won or lost.
You have four real options: product conversion, contract conversion, RISE subscription, and greenfield rebuild. They are not priced alike. On the representative 2,500 user estate converting to 700 Full Use Equivalents, 5 year total cost of ownership ranges from $7.35M for an on premise conversion to $10.8M for greenfield, a $3.45M spread.
The single largest lever is the conversion credit. The net value of your legacy ECC perpetual licenses offsets the new S/4HANA portfolio, cutting a $5.5M list portfolio to $1.5M of net new license. Greenfield forfeits that credit entirely. RISE only honors it for the first three years.
The buyer side sequence is fixed. Value the legacy estate, settle the digital access baseline, model all four paths on your own numbers, then time the signature against the 2027 clock, not ahead of it. Each move below is anchored to a number you can defend in front of the SAP account team.
Background: What the 2027 Deadline Actually Means
SAP ECC is the on premise ERP that most large enterprises still run. S/4HANA is its successor, rebuilt on the HANA in memory database with a new data model and new license metrics. The migration is mandatory in practice, because support runs out.
SAP confirmed the dates in its maintenance strategy. Mainstream maintenance for SAP Business Suite 7 core applications, which includes ECC 6.0, ends December 31, 2027. Extended maintenance is available to December 31, 2030 for a premium.
What are the 2027 and 2030 dates, precisely?
- December 31, 2027: end of mainstream maintenance for ECC 6.0 EHP 6 through 8. No new legal, security, or functional updates after this.
- December 31, 2030: end of optional extended maintenance, priced at an extra two percentage points on the support base.
- After 2030: customer specific maintenance only. Existing fixes remain, no new corrections are produced.
SAP committed to maintaining S/4HANA through at least 2040, so the destination is stable. The pressure is entirely on the exit date from ECC, not the entry date to S/4HANA.
How Does SAP Measure the Conversion Credit From ECC to S/4HANA?
The conversion credit is the financial value SAP assigns to your existing ECC licenses when you move to S/4HANA. It is the single largest number in the negotiation, and it behaves differently across the conversion paths.
There are two credit mechanics, and confusing them costs money. SAP documents both in the three license model framework.
Product conversion versus contract conversion
- Product conversion: you keep the existing contract and swap the underlying ECC products for their S/4HANA equivalents, like for like. Your legacy discounts and terms survive.
- Contract conversion: you return all legacy licenses to SAP for a credit equal to their net value, then buy a fresh S/4HANA portfolio under current metrics such as Full Use Equivalent. Legacy discounts do not survive.
Contract conversion is a one time reset. You can drop obsolete modules, right size user counts, and adopt the FUE metric. The credit offsets the new portfolio, but the new portfolio is repriced at current list, so the discount you negotiate on the new deal matters as much as the credit itself.
The worked credit below assumes a contract conversion. The legacy ECC perpetual portfolio carries a credit basis of $4.0M. The new S/4HANA portfolio at list is $5.5M. The credit offsets the legacy value, leaving net new license payable.
| Line | Mechanic | Value |
|---|---|---|
| Legacy ECC perpetual portfolio | Credit basis returned to SAP | $4,000,000 |
| New S/4HANA portfolio at list | Contract conversion, current metrics | $5,500,000 |
| Conversion credit applied | Offset against the legacy value | −$4,000,000 |
| Net new license payable | $1,500,000 |
Conversion, RISE, or Greenfield: Which Path, and When?
The four paths differ in who owns the software, who runs the infrastructure, and what happens to your perpetual entitlement. The choice is commercial, not technical, and it should be made on your numbers, not the account team's roadmap slide.
| Path | License model | Conversion credit | Best when |
|---|---|---|---|
| Product conversion | Perpetual, keep contract | Full, terms survive | Stable estate, want to keep legacy discounts and run on premise |
| Contract conversion | Perpetual, new FUE portfolio | Full, terms reset | Estate needs redesign, want to drop shelfware and right size |
| RISE with SAP | Subscription, FUE per month | Honored years 1 to 3 only | Want SAP to run the infrastructure and accept a recurring cost |
| Greenfield | New license or subscription | Forfeited entirely | Business process overhaul justifies a clean rebuild |
RISE prices on the Full Use Equivalent metric. RISE with SAP private cloud list runs roughly 220 to 280 euros per FUE per month before discount, with discounts of 25 to 50 percent for the mid market and 50 to 70 percent for global enterprise.
What the FUE metric changes
- Users collapse into FUE: several ECC named user types map into a smaller FUE count, which is why 2,500 users can become 700 FUE.
- The ratio is negotiable: SAP publishes conversion ratios, but the mapping of your specific user mix is open to challenge.
- FUE is a subscription unit in RISE: in on premise S/4HANA it is a perpetual unit. The same word, two very different cost shapes.
What Is Your Indirect and Digital Access Exposure During Migration?
Indirect access is the charge for third party systems that read or write SAP data. The migration is the moment SAP revisits it, because the conversion repackages your entire entitlement. Settle the digital access baseline before you sign, never after.
SAP's digital access model charges by the document, not the user. Nine document types trigger a charge at initial creation, and two of them, Material and Financial documents, count at 0.2 each.
Why migration reopens the indirect question
- Repackaging resets the baseline: a conversion is a new contract, so the indirect exposure is measured fresh against the new metrics.
- RISE folds documents into the bundle: digital access entitlements move inside the subscription, where a wrong baseline compounds at every renewal uplift.
- The estimation note is contestable: SAP's measurement runs on a sample window and annualizes it. A peak window inflates the annual figure.
Two of the nine document types count at one fifth. In high volume estates this single rule cuts the document baseline by a third or more before any price is discussed.
Across the SAP engagements we benchmarked, the opening indirect measurement ran 25 to 40 percent above the defensible figure once direct use and duplicates were stripped.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.
How Do You Model 5 Year TCO Across the Three Options?
Total cost of ownership, not license price, decides the path. The representative estate is a mid market manufacturer running ECC 6.0 with 2,500 named users, converting to 700 FUE. The model below covers software, implementation, and infrastructure across five years.
The three columns are the live choices once greenfield is set aside as the rebuild option. Each column sums to its total, and the totals feed the chart that follows.
| Cost line, 5 years | On premise conversion | RISE private cloud | Greenfield rebuild |
|---|---|---|---|
| Software or subscription | $3,150,000 | $6,800,000 | $5,000,000 |
| Implementation and conversion | $2,800,000 | $2,400,000 | $5,500,000 |
| Infrastructure and operations | $1,400,000 | included | $300,000 |
| 5 year TCO | $7,350,000 | $9,200,000 | $10,800,000 |
On premise conversion carries the software at $1.5M net new license plus $1.65M of maintenance over five years, total $3.15M, but adds $1.4M of HANA infrastructure and basis operations you run yourself. RISE bundles the infrastructure but charges $6.8M of subscription net of the three year credit.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. FUE list runs 220 to 280 euros per FUE per month before discount; the figures above use a modeled blended rate for this volume tier and are not an SAP quote. Confirm your tier against your own order form.
How Does the 2027 Deadline Become Buyer Side Leverage?
The deadline cuts both ways. SAP uses it to push you toward RISE before you have modeled the alternatives. You use it by treating extended maintenance as a real, priced option that buys you time to negotiate properly.
Extended maintenance to 2030 costs two percentage points on top of standard maintenance. On a $3.0M license base at 22 percent, that is $660,000 per year rising to $720,000 per year. The chart below tracks the support bill across the deadline.
| Period | Maintenance basis | Annual support |
|---|---|---|
| 2026 to 2027, mainstream | 22% of $3.0M base | $660,000 |
| 2028 to 2030, extended | 24% of $3.0M base | $720,000 |
| 2031 onward, customer specific | No new fixes | $660,000 frozen scope |
Where the common advice on ECC migration is wrong
The standard reseller and account team pitch is that RISE is the simple, cheaper destination, and that you should sign before the 2027 deadline closes. We disagree.
Across the SAP conversions we benchmarked in 2024 to 2025, RISE was the lowest 5 year TCO in fewer than half of stable estates. The conversion credit lapses after year three, and the renewal resets at full subscription price.
For a stable estate with predictable growth, an on premise contract conversion plus self managed infrastructure often lands $1.5M to $2.0M cheaper over five years. The buyer side move is to model all four paths on your own numbers and let the 2027 clock work for you.
The deadline is SAP's leverage only if you arrive unprepared. Priced as an option, extended maintenance to 2030 turns a forced march into a negotiation you control.
The Migration Negotiation Timeline
Audit the legacy estate
Inventory every ECC entitlement, including shelfware, and establish the conversion credit basis. Settle the digital access baseline independently before SAP measures it. This is the evidence base for every later move.
Price all four paths
Build the 5 year TCO for product conversion, contract conversion, RISE, and greenfield on your own numbers. Map your user mix to FUE and challenge the ratio. Price extended maintenance to 2030 as a real alternative.
Time the signature
Negotiate the new portfolio discount and cap the RISE year three reset before signing. Time the deal to SAP's fiscal year end, December 31, when the same commitment discounts further, with the deadline as your option, not your trap.
Five Recommendations from Redress Compliance
Decide the path on your numbers, not the deadline. The 2027 clock is real, but it is a reason to model carefully, not a reason to sign the first RISE proposal the account team brings.
- Value the credit first. Audit every ECC entitlement, including shelfware, before SAP sets the conversion credit basis you can never recover later.
- Model all four paths. Product conversion, contract conversion, RISE, and greenfield price differently. Build the 5 year TCO on your own estate.
- Settle digital access before you sign. A wrong indirect baseline folded into RISE compounds at every renewal uplift.
- Cap the RISE year three reset. The conversion credit is a three year teaser. Cap the renewal uplift in the original signature.
- Price extended maintenance as an option. Two points to 2030 buys negotiating time and removes the forced march that hands SAP the leverage.
Redress Compliance runs this framework on your side of the table only: value, model, lock, against the SAP account team. We are glad to tie a meaningful part of the fee to delivered value.
