RISE contracts run for three to five years on standard terms, and the contract event that matters at the end of that term is the exit. Either the buyer renews on commercially acceptable terms, or the buyer exits and migrates the estate to another platform. The buyer’s position at that point depends almost entirely on the exit terms negotiated at the original sign. SAP’s standard exit provisions are unfavourable to the buyer in ways that are visible at end of term and barely visible at sign. We see this pattern across our contract negotiation engagements, and the recurring observation is that buyers negotiate exit terms with at most ten per cent of the attention they pay to the headline pricing.
Why exit terms matter at sign
The negotiation leverage on exit terms exists only at contract sign. At sign, the buyer is a prospective customer with a credible alternative position; SAP needs to win the deal. At end of term, the buyer has an installed estate on RISE, the operational dependencies of three to five years of integration, and a switching cost that erodes the alternative position. The leverage asymmetry is structural. The provisions that the buyer signs at the start of the contract are the provisions that govern the end of the contract, and the negotiation window for those provisions closes at sign.
The provisions matter even if the buyer expects to renew. A buyer with no exit leverage at end of term has no renewal leverage either; SAP’s renewal pricing is a function of what the buyer’s alternative position looks like, and the alternative position is shaped by the exit provisions. The RISE topic page covers the broader contract architecture.
Provision one — data extraction format
The data extraction provision sets out the format in which the buyer’s data is delivered on termination. Standard SAP terms specify a vendor-defined export format, with no commitment to specific data completeness, no warranty of usability in another system, and no service-level commitment on extraction timing. The standard position is that the buyer receives a database export in SAP’s preferred format, with the buyer responsible for any subsequent transformation.
The buyer-side ask should include an explicit format specification (typically an open or industry-standard format), a completeness warranty against the data inventory recorded during the contract, a defined extraction timeline measured in business days, and an SAP commitment to extract any custom data structures introduced during the contract. The four sub-provisions are negotiable individually; together they convert the standard provision from a permission to receive data into a contractual right to receive usable data in a specified time.
Provision two — post-termination access
The post-termination access provision sets the window in which the buyer can access the RISE environment after the contractual end date. Standard terms typically permit a thirty-day window for data retrieval, after which SAP terminates access and the environment is decommissioned. The thirty-day window is the smallest typically negotiated; for buyers with complex data extraction requirements it is inadequate.
The buyer-side ask should target a ninety-day post-termination access window as standard, with a separately defined extension provision in the event of extraction delays. The provision should also specify the level of access available during the window (read-only at minimum, with the operational interface available for data exploration) and the cost basis for the extended access period (typically the pro-rated subscription rate).
Provision three — transition assistance
The transition assistance provision sets the scope of SAP’s support to the buyer during the transition out of RISE. Standard SAP terms either omit the provision entirely or specify it at a level that is too thin to be useful. The buyer migrating off RISE then faces SAP either declining to assist with the migration or assisting at billable consulting rates outside the contract.
What transition assistance should cover
The transition assistance provision should cover: the data extraction execution (not just the format), the documentation of the integration architecture as it stands at termination, the support for testing the extracted data in the receiving environment, and a defined hours-of-assistance allocation that the buyer can draw on during the transition. The hours allocation typically scales with the size of the original contract; for larger deals it can be material. The bank renegotiation case file documents a transition-assistance provision negotiated mid-term.
Provision four — residual licence rights
The residual licence rights provision sets out what the buyer retains after the RISE subscription ends. The buyer’s pre-RISE on-premise entitlement, if it existed, is the central question. SAP’s standard position varies across deals; in some cases the on-premise entitlement is preserved alongside the RISE subscription, in others it is replaced by the RISE subscription and lost on termination.
The buyer-side preparation here is to understand the position at sign and to negotiate explicitly. Where the pre-RISE entitlement exists and represents material value, the contract should specify its preservation on termination, with a defined fall-back to the on-premise terms. Where the pre-RISE entitlement has been replaced, the buyer should understand the consequence: termination of the RISE subscription leaves the buyer with no SAP entitlement at all, and the alternative position must include a new licence acquisition.
Exit terms determine the renewal negotiation position more than they determine the actual exit. A buyer with weak exit provisions has weak renewal leverage; a buyer with strong exit provisions can negotiate renewals from a position of credible alternative. The exit terms are not just about leaving. They are about staying on better terms.
Provision five — SAP-initiated termination
The provision governing SAP’s right to terminate the contract is asymmetric in standard SAP terms. SAP retains broad termination rights on the customer’s default, breach, or non-payment, with limited cure periods and broad definitions of qualifying events. The buyer’s reciprocal termination rights are typically narrow and confined to SAP’s material non-performance.
The buyer-side ask should rebalance the asymmetry. Specifically: the cure periods for buyer-side breach should be extended; the qualifying events should be narrowed; the data-extraction provisions should apply on SAP-initiated termination as well as on buyer-initiated termination; and the residual rights provisions should survive SAP termination. The RISE contract negotiation tactics white paper covers the rebalancing framework in detail.
Provision six — renewal notification
The renewal notification provision sets the window in which the parties exchange renewal notices. SAP’s standard position is that renewal is automatic in the absence of buyer notice to terminate, with the buyer notice window opening sixty to ninety days before expiry. The structure favours SAP: a buyer that misses the notice window is locked into the renewal on whatever pricing SAP proposes.
The buyer-side ask should reverse the structure. Renewal should be by mutual agreement rather than automatic; the SAP renewal proposal should be due no later than six months before expiry; the buyer should have a defined window after receipt of the proposal to evaluate alternatives; and the buyer’s decision to terminate should not require a specific notice form but should be expressed by silence or by counter-proposal. The structural change converts the renewal from an automatic SAP advantage into a negotiated event. The RISE pricing model piece covers the renewal trajectory framing.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
Before sign the buyer-side team should set out the six provisions in a checklist, populate the SAP standard position against each, define the desired buyer position against each, and run a single-pass negotiation with explicit prioritisation. The provisions are negotiable individually; the strongest outcome comes from negotiating them together as a package. Estates that arrive at end of term having negotiated the six provisions at sign navigate the renewal or exit from a defensible position. Estates that arrive without that preparation are negotiating from inside the lock-in. The credit roll-over piece covers a related negotiation pattern.