SAP Transition Option: Mechanics, Deadlines, and What the 20% Surcharge Really Means

The SAP Transition Option extends on-premise operations through end of 2033. For organizations whose IT landscape needs more time before completing a full migration to S/4HANA or RISE, that sounds like a manageable deferral. But the decision doesn't rest on the time window alone. A 20% surcharge on the comparable cloud price, a mandatory Max Success Plan, and strict EHP requirements change the picture substantially.

Understanding these mechanics before you subscribe keeps your options open. Discovering them after signing puts you in a position where you're governing under constrained conditions.

What the SAP Transition Option Is and Who It's For

The Transition Option is an additional subscription path within RISE with SAP (SAP ERP, private edition). It targets existing customers running SAP ERP 6.0 systems who cannot, or choose not to, fully convert to S/4HANA by end of 2030.

The key difference from a standard RISE contract: you subscribe your existing ECC environment into the private cloud without immediately migrating to S/4HANA. The system runs on SAP-managed infrastructure (hyperscaler of your choice) but functionally remains an ECC system.

Important context: the Transition Option is not a permanent state and not a substitute for S/4HANA migration. It is a time-limited instrument that gives organizations planning runway through end of 2033 at the latest.

The first governance moment appears here: if you are treating the Transition Option as a strategic extension, you need to link it to a realistic migration timeline from the start. Without that framework, the option simply runs toward its own expiration.

Subscription Window 2028 to 2030: When the Decision Must Be Made

The Transition Option is not available indefinitely. The subscription window opens on January 1, 2028, and closes on December 31, 2030. Contracts signed within this window can specify a service start from January 1, 2031, and run at most through December 31, 2033.

In practice: if you have migrated to RISE (PCE) by end of 2027, this window does not apply to you and you carry no extended maintenance surcharge. If you subscribe between 2028 and 2030, the Transition Option is an active choice. If you let the subscription window pass without signing, you lose the option with no replacement path.

The decision timeline for those accountable:

Date	Decision Point
2026-2027	Option evaluation: migrate to RISE by end of 2027, or pursue the Transition Option?
End of 2027	End of mainstream maintenance for SAP ERP 6.0 EhP 6-8
Jan 1, 2028	Transition Option subscription window opens; extended on-premise maintenance begins
Dec 31, 2030	Transition Option subscription window closes
Jan 1, 2031	Earliest possible service start under the Transition Option
Dec 31, 2033	Transition Option ends, no further extension path

The second governance moment: the decision for or against the Transition Option must be made before the subscription window closes. It does not happen automatically. Organizations that do not actively track this deadline lose the option without ever having evaluated it.

The 20% Surcharge: How It Is Calculated and What the Exception Means

The most frequently cited element of the Transition Option is the price surcharge. It amounts to 20% above a comparable SAP ERP Private Edition contract without Transition Option conditions.

What "comparable" means matters contractually: the reference price is SAP ERP Private Edition with equivalent user volume, the same edition, and the same infrastructure setup. The surcharge is calculated on that reference price, not on your current on-premise maintenance amount.

The exception: customers who subscribed to the Transition Option before December 31, 2025 do not carry this surcharge. That early-subscriber window is closed. For all subscriptions in the 2028 to 2030 window, the 20% surcharge applies without exception.

For budget planning, the surcharge is a governance moment in the cost dimension: the ACV of the Transition Option is structurally higher than a standard RISE contract. When you weigh extended maintenance (on-premise, plus two percentage points on maintenance base) against the Transition Option (cloud, plus 20% on cloud price), you are working with two different pricing logics. Which one is cheaper depends on your specific maintenance base volume and the ACV parameters of the Transition Option offer. A blanket answer is not possible. A structured calculation is.

Max Success Plan: What It Means and What It Costs

The Transition Option is contractually tied to signing a SAP Max Success Plan Transition Services agreement. This is not an optional add-on, it is a minimum requirement.

What a Max Success Plan concretely includes: enhanced SAP support for migration and transformation planning, dedicated technical advisory services, and access to SAP internal resources for S/4HANA preparation. The exact scope varies by contract version and customer size.

What it costs: the Max Success Plan is a separate line item. It is not folded into the 20% surcharge, it is billed independently. For budget planning, this means: Transition Option ACV plus Max Success Plan costs plus any applicable add-on costs equals the total amount that must be compared against the alternatives (standard RISE or extended on-premise maintenance).

The third governance moment: the Max Success Plan is not a purely administrative requirement. It commits resources on SAP's side and sets an expectation for the organization's readiness to migrate. If you subscribe to the Transition Option without pursuing active migration planning, you are investing in a contractual obligation that delivers no operational value.

EHP Prerequisite: EHP7 and EHP8 Only

Not every SAP ERP system qualifies for the Transition Option. SAP has restricted supported Enhancement Packages to EHP7 and EHP8.

Systems running EHP6 or earlier do not meet the prerequisites. They must be upgraded to at least EHP7 before the Transition Option becomes available. That is a project step with its own timeline, costs, and risks.

For decision preparation: if you are considering the Transition Option, the first step is confirming which Enhancement Package your system is running. If an EHP upgrade is required, it belongs in your project plan before the 2028 subscription window becomes relevant.

Available Add-on Product Versions in the Transition Option

A frequently underestimated aspect: not all add-ons active in your current on-premise system are available in the Transition Option. SAP has published a defined list of supported add-on product versions.

The available categories include:

Supply Chain and Logistics EWM 9.5 (Extended Warehouse Management), APO 7.0 EHP4 as a connector add-on (not standalone), Digital Manufacturing Cloud Integration 6.0.

Finance and Treasury SAP Revenue Accounting 1.3 (IFRS 15), SAP Treasury and Risk Management (US), Financial Services Network Connector, Corporate Performance Management 2.0.

HR and HCM HR Renewal 2.0, SAP Fiori for HCM 2.0, SuccessFactors Employee Central Integration, Manager Self-Service 1.0.

Compliance and Invoicing Global Invoicing 2.0, Document Builder Management 8.1.

Integration and Platform SAP Cloud for Customer Integration 2.0, Configure Price Quote Integration, PLM System Integration 2.0, Multi-System Payment Connector.

Anything not on this list is not available in the Transition Option. Older add-on versions without an S/4HANA equivalent create a separate migration problem: they cannot be carried forward in the Transition Option and require either a replacement or a deliberate decision to retire them.

The fourth governance moment, in the infrastructure dimension: every active add-on affects infrastructure sizing and therefore ACV. An add-on inventory before the Transition Option decision is not optional, it is the foundation for any valid cost calculation.

When the Transition Option Is the Right Choice and When It Is Not

The Transition Option is an instrument for specific situations, not a default path.

It makes sense when: Complex system landscapes with many add-on dependencies require more than three years of migration runway. When regulatory requirements, ongoing transformation projects, or resource constraints make a migration by end of 2027 infeasible. When the organization has a clear S/4HANA migration plan and simply needs to extend the timeframe.

It is less suited when: The primary reason for considering it is planning uncertainty rather than a concrete migration intent. Or when the calculation shows that standard RISE migration before the end-of-2027 deadline is more cost-effective. And explicitly: the Transition Option is not a permanent state. It ends on December 31, 2033, with no further extension path.

Decision Timeline and Next Steps for Those Accountable

Five steps toward a structured Transition Option decision:

Confirm EHP status: Is your system running EHP7 or EHP8? If not, an EHP upgrade needs to be included in the plan.
Add-on inventory: Which add-ons are active? Which of them appear on the Transition Option list? Which require an S/4HANA equivalent?
Calculate Transition Option vs. alternatives: Run the numbers for Transition Option ACV (including Max Success Plan) against extended on-premise maintenance (plus 2%) and standard RISE (migration by end of 2027).
Link to migration planning: The Transition Option has a hard end date of December 31, 2033. Without a migration plan, it remains an open-ended obligation.
Track the subscription window actively: The 2028 to 2030 window does not trigger automatically. If you intend to subscribe, you act deliberately.

Who Governs This Decision After Signing?

The Transition Option decision is not a one-time contract event. It opens a multi-year governance responsibility.

In ongoing operations, governance moments arise across all four dimensions: user license consumption under the new contract structure, authorization design with the future S/4HANA conversion in mind, infrastructure SLAs in the RISE environment, and ACV tracking including add-on costs and Max Success Plan line items.

What is missing after signing, when no systematic approach is in place: the subscription window has been used, the contract is running, but the management of live contract parameters happens reactively. Derived charges, ACV variances, and add-on developments have no counterpart in monitoring.

This is exactly where the question that structures every governance discussion comes in: who governs your SAP contracts after signing?

Bernhard Mändle is Managing Consultant at FinOptory and supports SAP contract governance after signing. Connect on LinkedIn

Schedule a first conversation: finoptory.ai/contact