Negotiating the RISE conversion: tactics that hold for the term

The SAP RISE conversion proposition has become, by 2026, the dominant commercial channel through which SAP closes large enterprise customers. The proposition packages the S/4HANA licence, the infrastructure, the operational support, and the migration services into a single subscription line, with a headline discount against the standalone equivalent. The negotiation focus, on the buyer side, defaults to the discount percentage. That is the easy number. The substantial value — positive and negative — sits in the clauses around audit rights, exit terms, indirect-access carve-outs, price escalation, and scope of subscription. The conversion is a multi-decade commitment. The clauses around the discount determine what the commitment actually costs.

What SAP is selling in the RISE proposition

The RISE bundle is a re-packaging of components SAP has sold separately for years: S/4HANA Cloud or Private Cloud, hyperscaler infrastructure, BTP credits, premium engagement support, and migration services. The commercial benefit to SAP is recurring subscription revenue, lock-in to a single hyperscaler footprint chosen by SAP, and the conversion of legacy ECC licence positions into the new commercial model on SAP’s terms. The commercial benefit to the buyer, at the headline level, is a single contract, a single relationship, and a discount against the sum of the standalone parts.

The detailed reading is less favourable. The bundle obscures the per-component pricing. The exit is on SAP’s terms. The audit rights are sometimes broader than the equivalent on-premise terms. The price escalation clauses, if not negotiated, accumulate at compound rates over the term. The buyer’s negotiation task is to unbundle the proposition mentally, price each component, and negotiate the clauses around the bundle independently of the discount.

The discount conversation — what it is and is not

The headline RISE discount, in the deals we see, lands between twenty and forty per cent against the sum-of-parts list. On large enterprise deals it can land higher, particularly when paired with a multi-year commitment and a reference-customer clause. The discount is real and worth negotiating, but it should not consume the negotiation bandwidth. The discount of forty per cent on a fifty-million-euro five-year subscription is worth twenty million. The exit clause, if mis-drafted, can carry a termination cost that exceeds the entire term value. The audit rights, if mis-drafted, can open up indirect-access exposure that did not exist under the on-premise contract. The arithmetic is asymmetric.

The negotiation discipline is to take the discount conversation seriously, but to spend at least equal time on the four clauses that follow. The broader pattern of contract clause negotiation is covered in the related article on contract clauses to remove or rewrite.

Clause 1: audit rights in the RISE contract

The RISE master subscription agreement, as drafted by SAP, typically grants SAP the same audit rights as the on-premise contract plus the right to use cloud-side telemetry to support audit findings. The cloud telemetry is the new exposure. Without negotiation, the contract permits SAP to use document-creation counts, integration topology, and user-activity logs collected by the SAP-managed infrastructure as direct evidence in an audit. The buyer’s on-premise audit defence playbook — including the data-exchange protocol covered in the audit letter response article — does not apply when the data is already in SAP’s hands.

The negotiation position is to limit the use of cloud telemetry in audit findings, to require buyer-side validation of any telemetry-derived numbers before they are used commercially, and to preserve the contractual data-exchange protocol from the on-premise model. SAP will resist these positions; they are achievable in mid-market and large-enterprise deals with negotiating discipline.

Clause 2: exit and reversion

The exit clause in the standard RISE contract gives the buyer the right to terminate at the end of the initial term, with notice, but does not address what happens to the buyer’s data, the buyer’s configurations, and the buyer’s licence position at exit. The contracts we have reviewed often default the buyer into a position where, at exit, the buyer has neither a working environment nor a licence to run S/4HANA elsewhere. The reversion clauses must be negotiated explicitly: data extraction at no additional cost, configuration export, transitional support, and a defined licence reversion path to on-premise S/4HANA at agreed economic terms.

This clause is the single most under-negotiated element of RISE conversions in our practice. The relevant case file is the bank renegotiates RISE mid-term matter, where the absence of a clean exit clause cost the buyer a seven-figure transitional payment to extract on its own terms.

Clause 3: indirect-access carve-outs in the RISE term

The RISE subscription, despite SAP’s positioning, does not automatically resolve historical or future indirect-access exposure. The contract must contain an explicit clause that addresses indirect-access treatment for the term: either a digital-access tier sized to measured volume, or a contractual carve-out for named integrations and named third-party systems, or both. Without this clause, the RISE conversion can preserve the indirect-access exposure in a new commercial wrapper. The mechanics are covered in the SAP RISE topic page and in the Indirect Access Survival Guide.

Clause 4: price escalation and renewal mechanics

The standard RISE contract includes an annual price escalation clause, often at a CPI-linked or fixed-percentage rate, that compounds over the term. A five-year contract with an unnegotiated four per cent annual escalation costs more than seventeen per cent more in year five than year one. Over a ten-year horizon the compounding becomes material. The negotiation position is to cap the escalation at a defined ceiling, to limit the components to which it applies (excluding, for example, the infrastructure component which has its own market trajectory), and to fix the renewal pricing methodology in writing rather than leaving it to the renewal negotiation. The pattern is covered in the article on renewal leverage strategies.

The negotiation sequence

A well-run RISE conversion negotiation takes four to six months and runs through six phases. Discovery of the buyer’s existing position. Sizing of the RISE proposition components independently of SAP’s bundle. Drafting of the buyer’s position on the four clauses above. Negotiation of the discount in parallel with the clauses. Drafting and red-line cycles on the master subscription agreement and the order forms. Sign-off and transition planning. Conversions closed faster than four months consistently land with the clauses unnegotiated and the buyer absorbing the downstream cost.

The preparation work before the proposal lands

The RISE negotiation is won and lost in the preparation. A buyer who arrives at the table with a measured baseline of the existing on-premise position, a sized estimate of the RISE proposition components, a benchmark set of comparable transactions, and a written position paper on the four clauses above is in a different conversation than a buyer who reacts to the SAP proposal as the starting point. The preparation work takes ten to fourteen weeks for a complex enterprise estate and should begin twelve to eighteen months before the renewal anniversary, not after the SAP proposal lands. The pattern is covered in the SAP audit triggers article.

The governance of the conversion programme

A RISE conversion programme needs governance discipline equivalent to a major M&A integration. The programme office should include procurement, legal, finance, internal audit, IT operations, and the SAP technical lead. Each function has decisions that must be made and recorded before the conversion closes. Finance must agree the cash impact and the depreciation treatment. Legal must approve the master subscription agreement and the order forms. Internal audit must confirm the audit-rights regime sits within the buyer’s risk appetite. IT operations must accept the operational support model. The SAP technical lead must validate that the proposed cloud footprint supports the existing architecture. Conversions closed without this governance pattern consistently surface internal disputes in the first six months of the term, when the cost of resolving them is materially higher than it would have been at the negotiation table.

The transition planning that runs after sign-off

The conversion does not end at signature. The transition plan that runs after sign-off determines whether the contract terms hold operationally in year one. The plan should include the migration timeline, the data extraction and load schedule, the cut-over of integrations to the new environment, the named-user reissue, the operational handover from the in-house team to the SAP-managed service, and the governance forum that will track delivery against the contracted commitments. Conversions that close without a documented transition plan routinely surface delivery gaps in the first six months — gaps that, under the master subscription agreement, often fall on the buyer to remediate.

For any RISE conversion above ten million euros in total contract value, the negotiation sequence above is the structural position that consistently protects the buyer through the term. The SAP contract negotiation service page describes how we structure the engagement.