Two clocks govern this decision, and they run in opposite directions: ECC mainstream maintenance ends with 2027, while the credit SAP applies for your existing licenses in a conversion has stepped down year after year and keeps shrinking. The licensing question is therefore not whether to leave ECC but on whose timetable — and whether you convert with a cleaned-up, measured estate or donate years of shelfware and unmeasured indirect use to the new contract’s baseline.
Published 14 October 2025 · Last reviewed 1 January 2026
The dates first, because every SAP renewal conversation now orbits them. Mainstream maintenance for ECC 6.0 (on the covered enhancement packages) runs to the end of 2027. After that, extended maintenance is available to the end of 2030 at a premium on the annual support fee. Beyond 2030, customer-specific maintenance keeps the lights on but narrows what SAP will fix, and a transition option attached to a RISE private-edition commitment can carry ECC operation toward 2033 for customers who have contractually committed to the move. SAP has also told investors it intends to wind down the perpetual-license business over time — a factual statement of direction that frames every conversation below.
What the dates do not do is switch anything off. ECC licenses are perpetual; the system runs in 2031 exactly as it ran in 2026. What lapses is the maintenance envelope: security notes, legal and tax updates in jurisdictions that require them, and the support relationship itself. That distinction matters because it defines your real alternatives — including running ECC on third-party support for an interim period, a path with its own trade-offs (lower fee, no new versions or conversion credit accrual on the support relationship) that should be evaluated factually rather than emotionally. The point of pinning the dates down is leverage arithmetic: SAP’s account team knows your deadline; the only question is whether your plan arrives before their proposal does.
This guide is general information about SAP licensing programs as they stand in 2026, not licensing or legal advice for your situation; maintenance policies and conversion terms change, and your contract governs. It names no firms; the firm directory lists SAP-capable advisors with balanced pros and cons, listed, not ranked.
| MECHANIC | ECC (CLASSIC ESTATE) | S/4HANA (THE DESTINATIONS) |
|---|---|---|
| Ownership model | Perpetual licenses plus annual support at roughly a fifth of license value | On-premise: perpetual plus support. Cloud editions: subscription only, no perpetual fallback |
| User metric | Classic named-user types (Professional, Limited Professional, Employee and kin) plus engines and packages | On-premise: simplified named-user categories plus line-of-business products. Cloud: Full User Equivalents (FUE) |
| Database | AnyDB — the database is your choice and your contract | HANA required: runtime edition priced as a percentage of application value, or full-use HANA licensed separately; bundled inside cloud subscriptions |
| Indirect use | Historically licensed via named users behind third-party systems; contracts vary | Document-based digital access is the standard model on new paper |
| Maintenance horizon | Mainstream to end-2027; extended to 2030 at a premium; transition option toward 2033 with a RISE commitment | Current product line; cloud editions upgraded on SAP’s cadence |
| Compliance posture | Classic measurement: user classification, engine metrics, indirect-use exposure | On-premise: similar, plus document counting. Cloud: subscription governance at true-up and renewal |
Read the table column-wise and the migration resolves into three licensing moves happening at once: a user-metric translation (every ECC user type must be mapped to a new category, or to a FUE fraction in the cloud — the FUE vs classic named users guide covers those ratios), a database decision (runtime HANA is cheaper but locks the database to SAP applications; full-use costs more and frees it), and an indirect-use re-basing (the document model replaces user-based indirect licensing — mechanics in the digital access guide). Each translation has defaults, and the defaults were not drafted in your interest.
Product conversion was the gentle path: keep the contract, swap ECC components for S/4HANA equivalents, take credit for like-for-like functionality. It was always scope-limited — not every ECC product had an equivalent — and as a broadly available option it is now largely retired. Customers who took it early kept their commercial terms; customers reading this in 2026 are, in most cases, choosing between the two remaining doors.
Contract conversion is the main on-premise route: the old agreement terminates and a new S/4HANA contract is negotiated from scratch, with a percentage of your existing license investment applied as credit. Two facts dominate. First, the credit has stepped down over time — market observers have tracked the typical offset falling from around ninety percent of existing value in the early program years toward seventy percent and below, with the direction of travel firmly downward as 2027 approaches. Treat any specific percentage as a negotiated outcome, not an entitlement. Second, because the whole contract reopens, everything reopens: shelfware can finally be shed from the support base, legacy engine metrics can be retired, and the indirect-use position can be re-based deliberately. Conversion is the one moment in an SAP relationship when the support annuity is genuinely on the table — which is exactly why the vendor prefers the conversation to happen on its template and its timetable.
Conversion into RISE (or GROW) is the third door, and it is a different kind of transaction: your perpetual licenses are retired into a negotiated credit against a subscription, and there is no fallback to them at exit. The considerations — bundle scope, FUE ramp, renewal caps, exit terms — are covered in the RISE vs on-premise S/4HANA and RISE vs GROW guides; for this page’s purposes the point is that the ECC decision and the cloud decision are one negotiation in SAP’s eyes, and should be modelled as one on yours.
Staying on ECC longest fits organisations with stable, heavily customized estates, no regulatory pressure for current legal patches, and a deliberate plan — extended maintenance or third-party support as a bridge, with the migration budgeted on their own calendar. The factual trade-off: deferral is cheap now and expensive later, because the conversion credit erodes while the counterparty’s pricing power grows as the deadline nears.
On-premise S/4HANA fits estates that need the current product line but cannot or will not move their core to a subscription: sovereignty constraints, hardware investments, a preference for perpetual ownership economics. It preserves the asset model — perpetual plus support — at the price of running the migration project and the HANA decision yourself.
The cloud editions fit buyers ready to trade ownership for operation — and that trade is examined program by program in the sibling guides rather than re-argued here. What belongs here is the warning that applies to all three paths equally: fit is determined by the estate you measured, not the estate you remember. User classifications drift over a decade; engines get switched on and forgotten; integrations multiply. An effective license position built before the negotiation — not SAP’s measurement, run after it starts — is what turns the conversion from an exposure event into a clean-up event.
The credit base is negotiable before the credit percentage is. Whether shelfware counts toward the offset, how engine licenses are valued, and what the comparison price for the new position would have been are all drafted positions. A high credit percentage against an inflated new-license baseline is worth less than a moderate one against an honest baseline — model the net position, never the headline.
The user mapping is worth more than the discount. Translating classic named users into the new categories (or into FUE fractions) involves judgement calls on thousands of records, and the difference between mapping a population to the expensive category versus the appropriate one compounds across the whole term. Audit the proposed mapping line by line; this is the core of what SAP licensing advisory firms are engaged to do in migration season.
Digital access should be negotiated, not inherited. Conversion paper typically adopts the document model for indirect use. Measure your document volumes first, then negotiate the position — adoption-program discounts for regularising existing use have been deep, and they are signature-time items. Compliance exposure peaks during the migration itself: conversions trigger measurement, and unmeasured indirect use or drifted classifications surface at exactly the moment the vendor has maximum leverage. Sequencing the clean-up before the conversation is most of the game; the SAP renewals coverage tracks how these cycles run, and the compliance-assessment provider guide covers picking who runs the baseline.
Negotiating against the deadline instead of ahead of it. Every quarter closer to end-2027 transfers leverage to the seller. The estates that convert well start the measurement and modelling eighteen months before they intend to sign.
Converting the shelfware. A contract conversion that rolls a decade of unused licenses into the credit base looks generous and locks in support on value you never consumed. Shed first, convert second.
Accepting the vendor’s user mapping. The default translation of classic user types into new categories is rational for the drafter. Reclassify against actual usage records before agreeing to anything.
Treating the HANA runtime decision as a formality. Runtime pricing tied to application value is economical until you want the database to do anything beyond SAP applications. Decide with the database team, not just procurement.
Letting the migration absorb the indirect-use question. Document-model exposure measured after signature is a true-up; measured before, it is a negotiating position with a deep program discount attached.
Modelling RISE against ECC instead of against on-premise S/4HANA. The honest comparison set is all three destinations, costed over the same horizon, with exit terms included. A subscription quote beats a maintenance bill in year one and needs to be tested in year seven — and choosing who builds that model is its own decision.
Subscription or perpetual at the destination →
The user-metric translation in detail →
The indirect-use re-basing →
How to pick the firm for this work →
Firms that model these conversions →
Every field guide on the site →
Mainstream maintenance for ECC 6.0 (on the covered enhancement packages) runs to the end of 2027. SAP offers extended maintenance to the end of 2030 at a premium on the support fee, and a transition option tied to a RISE private-edition commitment can carry ECC operation further, toward 2033, for customers contractually on the move. None of these dates switches the software off — ECC keeps running — but past them you carry the compliance, security and regulatory-update consequences of an unsupported core.
Product conversion kept your existing contract and swapped ECC components for S/4HANA equivalents, with credit for like-for-like functionality. It was always scope-limited and is now largely retired as a broadly available path. Contract conversion replaces the old agreement entirely: your ECC contract terminates, a new S/4HANA contract is negotiated, and a percentage of your existing license investment is applied as credit against the new position. Because the whole contract reopens, conversion is simultaneously the biggest risk and the biggest clean-up opportunity in the migration.
There is no published entitlement — credit is a negotiated outcome inside the conversion deal. Market observers have tracked the typical offset stepping down over time, from around ninety percent of existing value in the early program years toward seventy percent and below as 2027 approaches, and the direction of travel is downward. Two things matter more than the headline percentage: what base it is calculated on (shelfware included or excluded) and what the new position would have cost without it.
Not automatically. On-premise S/4HANA uses its own, simplified user categories plus line-of-business and engine products, so every ECC user type must be mapped to a new category during conversion — a mapping exercise with real money attached, since the categories price differently. In the cloud editions the model changes entirely: subscription in Full User Equivalents (FUE) replaces perpetual named users, and your perpetual licenses are retired into a negotiated credit rather than carried.
In practice, usually yes. New S/4HANA paper is written with the document-based digital access model for indirect use, replacing the older approach of licensing named users behind third-party systems. Conversion is therefore the natural moment to measure your document volumes and negotiate the digital access position deliberately — including any adoption-program discount — rather than inheriting a default. The digital access versus indirect named users guide covers the mechanics.
Yes — the licenses are perpetual and the system keeps running. Extended maintenance buys supported operation to 2030 at a premium; beyond that, customer-specific maintenance narrows what SAP will fix. Some organisations also weigh third-party support for the interim. The trade-offs are factual ones: lower or deferred migration cost against a shrinking maintenance envelope, regulatory-update risk in jurisdictions that require current tax and legal patches, and a negotiation counterparty that knows your deadline as well as you do.
Sequencing an ECC exit — measuring the estate, modelling three destinations, timing the conversion against the credit curve — is exactly what an SAP licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.