RISE with SAP versus traditional licensing.

RISE with SAP bundles S/4HANA, infrastructure, and managed services into one subscription, while traditional licensing keeps the software you own separate from the cloud you choose.

What does RISE with SAP actually bundle?

RISE with SAP packages the S/4HANA Cloud software, cloud infrastructure, and a layer of managed services into a single subscription. SAP describes the offer on its RISE with SAP page.

The bundle is convenient and opaque. One number replaces software license, maintenance, hosting, and basis services, which makes it hard to see what each component costs.

Who is RISE a good fit for?

RISE fits organizations that want SAP to own the migration and run, and that lack the internal basis capacity to manage S/4HANA. The trade is leverage for convenience.

Who should stay on traditional licensing?

Organizations with strong internal SAP teams, existing hyperscaler agreements, or a need to keep components negotiable separately usually retain more value outside the bundle.

How does the FUE metric reprice your user base?

RISE prices on Full Use Equivalent users, which converts your existing named user types into a new unit. SAP sets out the digital and FUE framework in its agreement and pricing materials.

• Map before you sign: convert your current user mix into FUE and compare to today.
• Challenge the ratio: the default conversion favors SAP, so negotiate the mapping.
• Strip inactive users: reclaim dormant accounts before the conversion baseline is set.

The FUE baseline becomes your contract floor. Setting it on an inflated user count locks overspend for the whole term.

How should you value a perpetual to RISE conversion credit?

SAP offers a credit for converting owned perpetual licenses into RISE. The headline credit usually undervalues what you paid, especially if you negotiated a deep original discount.

1. Document the original net price you paid, not the list price.
2. Demand the credit reflect negotiated value, not a standard percentage.
3. Compare the credit against simply keeping perpetual on a third party support path.

S/4HANA migration deadlines, tracked on the SAP S/4HANA page, create urgency that SAP uses in conversion talks. Urgency is not a reason to accept a weak credit.

What lock in does RISE introduce and how do you limit it?

RISE ties your software to SAP chosen hyperscaler hosting and bundled services, which reduces your ability to negotiate infrastructure separately. SAP news, on its newsroom, frames RISE as the strategic path, which is precisely why exit terms matter.

• Negotiate exit: define data extraction and workload return before signing.
• Cap increases: fix renewal uplift caps in the original contract.
• Keep benchmarks: retain the right to benchmark bundled service quality.

The cheapest time to negotiate your exit from RISE is before you enter it. After signing, your leverage drops sharply.

Where the common advice on RISE with SAP is wrong

The standard SAP account team position is that RISE is the only viable path to S/4HANA and that staying on traditional licensing is simply deferring the inevitable. We disagree. In roughly 16 of the 25 plus RISE evaluations we ran, the bundle traded away infrastructure leverage and component visibility for a convenience the client could have bought separately at lower total cost. The buyer side move is to price the components individually, software, hosting, and services, and only enter RISE when the bundle genuinely beats the sum of its parts. Convenience has a price, and SAP sets it high when you stop comparing.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Map your current SAP user base into FUE before any RISE quote.
2. Reclaim dormant user accounts before the baseline is set.
3. Document original net prices paid on perpetual licenses.
4. Demand conversion credits reflect negotiated value, not list percentages.
5. Price software, hosting, and services as separate components.
6. Negotiate exit, extraction, and renewal caps before signing.

Related advisory: Our SAP contract negotiation service, SAP negotiation advisors, and RISE with SAP negotiations playbook cover the full cycle.

White Paper · SAP

SAP BTP Licensing. BTPEA versus consumption strategy

How to control SAP BTP cost: when a CPEA cloud credit commit beats pay as you go subscription, the consumption traps, and the drawdown levers. Read it free.

Read the white paper

Frequently asked questions

What is RISE with SAP?

RISE with SAP is a single subscription that bundles S/4HANA Cloud software, cloud infrastructure on an SAP chosen hyperscaler, and managed services. It replaces separate software license, maintenance, hosting, and basis costs with one metric priced on Full Use Equivalent users.

What is the FUE metric?

Full Use Equivalent is the RISE pricing unit that converts your existing named user types into a single equivalent count. The default conversion tends to favor SAP, so map your current user mix into FUE and negotiate the ratio before signing.

Is RISE cheaper than traditional SAP licensing?

Not automatically. RISE bundles convenience that can cost more than buying the components separately. Price software, hosting, and services individually and only choose RISE when the bundle genuinely beats the sum of its parts on total cost.

How much is a perpetual to RISE conversion credit worth?

The headline credit usually undervalues what you actually paid, landing 15 to 40 percent below negotiated original value in our engagements. Document your original net price and demand the credit reflect it, not a standard percentage.

What lock in does RISE create?

RISE ties software to SAP chosen hyperscaler hosting and bundled services, reducing your ability to negotiate infrastructure separately. Define data extraction, workload return, and renewal caps before signing, because leverage drops sharply afterward.

Does RISE remove the 22 percent maintenance fee?

Maintenance moves inside the subscription rather than disappearing. Compare total subscription cost against the prior license plus maintenance plus hosting, not line by line, to see the real difference.

Who should stay on traditional SAP licensing?

Organizations with strong internal SAP teams, existing hyperscaler agreements, or a need to keep components negotiable usually retain more value outside RISE. The bundle trades leverage for SAP managed convenience.

Does the S/4HANA deadline force a move to RISE?

No. Migration deadlines create urgency, but they do not require the RISE bundle. You can move to S/4HANA on traditional licensing or evaluate third party support paths. Urgency is not a reason to accept a weak conversion.