The decision rule sits at a one-way door: moving to RISE converts perpetual licenses you own into a subscription you rent — software, infrastructure and operations bundled into one escalating annual fee with no fallback rights if you leave — while on-premise S/4HANA keeps the perpetual asset, the support relationship and the operational burden in your hands. Choose RISE when transferring operations and exiting the data-centre business is genuinely worth surrendering the asset; keep the perpetual route when control, a strong infrastructure capability or the option value of ownership outweighs the bundle.
Published 15 December 2025 · Last reviewed 10 March 2026
Most organisations confronting this comparison are not choosing between two attractive futures; they are being pushed off a third. Mainstream maintenance for SAP ECC ends at the end of 2027, with extended maintenance available to 2030 at a premium on the support fee, and a private-edition transition option that can carry ECC workloads under subscription as far as 2033. The deadline is real, but it is a support deadline — not a contractual obligation to buy any particular successor. The full option set runs wider than the two compared here: extended maintenance, the transition option, third-party support for the legacy estate, or a phased conversion. The companion guide on ECC vs S/4HANA licensing covers the migration mechanics; this page compares the two destinations most buyers shortlist.
The clock matters commercially because urgency is leverage, and in this negotiation the leverage runs in one direction by default. SAP’s cloud strategy is explicit — the company has told investors it intends to wind down the perpetual business over time, and several recent innovations ship only in its cloud editions. That is stated here factually, not critically: a vendor is entitled to a strategy. The buyer’s job is to keep the strategy from doing the buyer’s arithmetic.
This guide is general information about SAP commercial models as they stand in 2026, not licensing or legal advice for your situation; SAP’s policies and packaging change frequently and your contract governs. It names no firms; the firm directory lists SAP-capable advisors with balanced pros and cons, listed, not ranked.
On-premise S/4HANA is the classical shape: a perpetual license bought upfront, an annual support fee of roughly a fifth of the license value, and the HANA database licensed alongside — either as a runtime restricted to SAP applications and priced as a percentage of the application value, or as a more expensive full-use license. Users are licensed as classic named users plus engine and digital access metrics, not FUE. You run it where you like, including on hyperscaler infrastructure you contract yourself; upgrade timing is yours within SAP’s maintenance windows; and the license survives as an asset whether or not you keep paying support — though dropping support has its own consequences, explored on the equivalent Oracle dispute in the support vs third-party support guide, whose logic transfers in outline.
RISE — on new paper, SAP Cloud ERP Private — replaces all of that with one subscription. S/4HANA Cloud Private Edition, the HANA database, hyperscaler infrastructure of your choice and a defined managed-services layer arrive as a single FUE-denominated contract, negotiated case by case with no public price list. The operational transfer is genuine: patching, infrastructure operations and a defined slice of basis work move to SAP. So is the commercial transfer: when you convert, existing perpetual licenses and their support contracts are retired into the deal as negotiated credit, and they do not come back if you leave. The conversion credit policy has been stepped down in successive revisions since 2023, which is worth knowing as a factual trend when someone tells you the current offer is time-limited.
How the private edition differs from SAP’s public-cloud offering — and how the FUE metric works in each — is covered in the sibling comparisons RISE vs GROW and FUE vs classic named users; this page holds the frame at subscription-versus-perpetual.
| MECHANIC | ON-PREMISE S/4HANA (PERPETUAL) | RISE / CLOUD ERP PRIVATE (SUBSCRIPTION) |
|---|---|---|
| What you hold | A perpetual usage right that survives the commercial relationship | A term subscription; rights end when the contract does |
| Cost shape | Capital purchase plus annual support around a fifth of license value | Single annual fee, FUE-denominated, escalating by negotiated terms |
| User metric | Classic named users + engines + digital access | Full User Equivalents (FUE) + digital access allotment |
| Database | HANA licensed separately (runtime or full-use) | Bundled in the subscription |
| Infrastructure & operations | Yours — on-premise or a hyperscaler contract you hold | Inside the bundle; SAP operates, hyperscaler of choice |
| Existing licenses at entry | Carried forward; conversion credits apply within policy limits | Retired into the deal as negotiated credit; no fallback if you exit |
| Renewal dynamics | No renewal cliff; support is the recurring negotiation | Term renewal with re-platforming switching costs behind it |
| Compliance shape | Annual measurement, named-user classification, digital access | FUE consumption governance at true-up and renewal |
| Roadmap exposure | Some innovations reserved for cloud editions; perpetual business being de-emphasised | Full cloud roadmap; exposure is commercial, not functional |
Read the table bottom-up and the trade is clear: the perpetual route carries roadmap exposure and operational burden; the subscription route carries commercial exposure — an escalating fee, a renewal with no fallback, and exit terms that are only as good as the day they were drafted. Neither exposure is imaginary. The question is which one your organisation is better equipped to manage.
Honest modelling of this choice produces an unfashionable answer: over a five-to-seven-year horizon, a well-run perpetual estate — license capital amortised, support at the standard rate, infrastructure on a competently negotiated hyperscaler contract — frequently comes out cheaper than the equivalent RISE subscription. RISE’s case does not rest on being cheaper; it rests on operational transfer, contractual simplicity, balance-sheet shape (opex over capex) and access to the cloud-only roadmap. Whether those are worth the premium is a judgement only the buyer can make, and it depends heavily on a variable vendors cannot see from outside: how good your infrastructure and basis operations actually are.
Three things bend the arithmetic. First, the entry credit. What your existing licenses are worth as conversion value is negotiated, against a published policy trend that has reduced credit percentages in successive steps since 2023 — establishing that value independently, before the proposal frames it, is the cheapest leverage available. Second, the escalator. A subscription’s year-one price is the least important number in it; the uplift cap, ramp schedule and renewal mechanics decide the decade. Third, the exit. The perpetual route’s worst case is an aging but owned estate; the subscription’s worst case is a renewal negotiation with no fallback rights and a re-implementation as the alternative. Price all three, not just the year-one quote — this modelling is the core of an SAP licensing advisory engagement, and stress-testing it before signature is what the negotiation work is for.
The perpetual route suits organisations with real infrastructure capability or strong existing hyperscaler relationships, estates with heavy customization and integration that benefit from full landscape control, regulated environments whose isolation requirements they prefer to engineer themselves, and any buyer for whom the option value of an owned license — including the factual existence of a third-party support market for owned SAP estates — is worth preserving. It also suits buyers who simply do not accept the renewal-cliff risk profile of a subscription with no fallback.
RISE suits organisations that want out of ERP operations: estates where basis and infrastructure work competes for scarce engineering attention, ECC conversions where bundling migration, hosting and operations into one negotiation is genuinely simpler, opex-preferring CFOs, and buyers who value the cloud-edition roadmap enough to rent it. For a buyer with weak infrastructure operations, the bundle’s premium can be cheaper than the failure modes it replaces — that is a legitimate, factual case for the subscription.
The discriminator is operational, not financial. If running SAP infrastructure is something your organisation is good at and wants to remain good at, ownership compounds in your favour. If it is a burden you are funding reluctantly, the transfer is the product and the question becomes purely one of negotiated terms. What it is never about is the brochure — both routes end in S/4HANA; only the contract differs.
On the perpetual side, the live clauses are the conversion credit applied to your ECC estate, the HANA licensing route (runtime versus full-use), named-user classification — the price difference between user types makes classification the real spend lever — and digital access, where the digital access vs indirect named users guide covers the exposure in detail. Compliance keeps its classic shape: annual measurement, user audits, engine metrics. A periodic independent effective license position is the standing defence.
On the RISE side, the live clauses are the FUE ramp (subscribe to your onboarding curve, not your final state), the renewal uplift cap, the managed-services boundary (what “operations” includes is a schedule, not a vibe), service credits, data-egress and transition assistance at exit, and the digital access document allotment. Compliance becomes consumption governance, surfacing at true-up and renewal — which makes the renewal itself the audit, with switching costs as the vendor’s leverage. Everything protective in a RISE contract is negotiated at signature; nothing is added at renewal.
The traps repeat across deals. Comparing the RISE quote against a padded on-premise straw man rather than your actual run costs. Accepting the vendor’s valuation of licenses you already own. Signing a year-one price with an uncapped escalator. Treating the 2027 deadline as a deadline for this particular contract rather than for a decision. Letting the conversion retire licenses for parts of the estate that were never moving to the cloud. And negotiating a one-way door on the vendor’s quarter-end calendar without independent support — choosing who provides that support is its own decision, and the renewal-negotiator guide covers the recurring version of it.
If cloud, then which cloud contract →
The migration mechanics behind the clock →
The two metrics on either side of this choice →
How to pick the firm for this work →
Firms that work these contracts →
Every field guide on the site →
They are effectively retired. Moving to RISE converts the commercial relationship to subscription: existing perpetual licenses and their support contracts are terminated or credited into the deal as negotiated conversion value, and the unlimited-duration usage right they represented does not survive. If you later leave RISE, you do not get the old licenses back — re-licensing or reverting to an unsupported legacy position are the realistic outcomes. This one-way mechanic is the single most important fact in the comparison.
Yes. SAP continues to sell perpetual on-premise S/4HANA licenses with annual support, alongside its strong strategic push toward cloud subscription. SAP has signalled to investors that it intends to wind down the perpetual business over time and reserves several innovations for its cloud editions, so buyers should weigh long-run roadmap exposure factually — but as of 2026 the perpetual purchase route exists and large customers continue to use it.
Mainstream maintenance for SAP ECC ends at the end of 2027. That is a support deadline for the old product, not a legal requirement to buy RISE: the options include converting to on-premise S/4HANA under perpetual licensing, subscribing to RISE, paying for extended ECC maintenance to 2030 at a premium, moving to the private-edition transition option that can carry ECC to 2033, or running unsupported or via third-party support — each with different risk and cost profiles. The deadline creates urgency; it does not choose the destination for you.
The published trend has been downward: SAP’s contract-conversion credit policy has been stepped down in successive revisions since 2023, reducing the proportion of historical license value that can be carried into a new agreement. The practical reading is that waiting has had a price. The exact credit available to you is deal-specific and negotiable — which is precisely why the conversion value of your existing estate should be established independently before the vendor’s proposal frames it.
Not as a rule. Over a five-to-seven-year horizon, well-run perpetual estates with competent infrastructure operations frequently model cheaper than the equivalent RISE subscription; RISE’s value case rests on bundling, operational transfer and balance-sheet shape rather than raw cost. The comparison is acutely sensitive to your infrastructure capability, existing hyperscaler commitments, and the discount and ramp you negotiate. Model both at realistic terms over at least ten years — including the renewal you will face with no perpetual fallback.
It changes form. On-premise S/4HANA keeps the classic regime: annual measurement, named-user classification and digital access exposure. Under RISE, the same questions reappear as subscription governance — FUE consumption against entitlement, user-type classification, digital access documents — surfacing at true-up and renewal rather than in audit correspondence. Renewal itself becomes the compliance event with money attached, which is why entering it with an independently verified consumption position matters.
Deciding whether to surrender a perpetual asset for a bundled subscription 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.