SAP Transition Option Application: The Process and Documents You Need

The SAP Transition Option extends on-premise operations on SAP ERP Private Edition through the end of 2033. The subscription window opens between 2028 and 2030, with service start no earlier than January 1, 2031. What happens between the decision to proceed and a signed contract is far less documented than the option itself. This article walks through the application process, the required documentation, and what the Max Success Plan commitment means in practice.

What the Transition Option Requires: Eligibility at a Glance

Before the application process begins, SAP verifies technical and contractual eligibility. Three prerequisites must be met.

Enhancement Package. Only systems running EHP7 or EHP8 for SAP ERP 6.0 qualify for the Transition Option. Older enhancement packages, EHP6 and earlier, are not supported. If you are still running EHP5 or EHP6, you need to complete an EHP upgrade before subscribing to the Transition Option. This is not an optional preparatory step; it is a formal entry requirement.

System size. The Transition Option requires a minimum size of 2 terabytes. Systems below this threshold are not eligible. In practice, this primarily affects smaller subsidiaries or regional systems running as technically independent instances.

Existing customer status. The Transition Option is available exclusively to existing SAP ERP customers with an active maintenance contract. A new subscription to SAP ERP through this route is not available.

Clarify all three points before any further planning. An EHP upgrade typically takes several months. If you identify the need only in 2028, you lose valuable time within the subscription window.

Step 1: Document Your SAP System Landscape and Build the Application Basis

The first operational step is taking stock of your system landscape. SAP expects a complete description of all systems to be included in the Transition Option as part of the application process.

This includes:

System ID (SID) and installed enhancement package for each system
Current infrastructure sizing (SAPS, RAM, database size)
List of activated Add-on Product Versions (PVs)
Overview of existing maintenance contracts and their terms

The last point matters because the Transition Option only covers systems and add-ons that appear on the official Available Add-on List. Add-ons outside this list, such as certain third-party extensions or unlisted SAP custom developments, are not included in the transition scope. If you operate these add-ons, you need a separate solution for them.

Infrastructure governance moment: Current infrastructure sizing determines not only technical eligibility but directly influences the ACV of the Transition Option. An incomplete or outdated sizing document generates follow-up questions from SAP and slows the process. Current sizing data from the SAP Readiness Check or a recent system measurement provides the most reliable foundation.

Step 2: Review the Add-on Scope and Identify Incompatible Components

The Available Add-on List for the SAP ERP Private Edition Transition Option covers components from Supply Chain, Finance, HCM, Compliance, and Integration. Typical examples: SAP EWM 9.5, SAP Revenue Accounting 1.3, HR Renewal 2.0, SuccessFactors EC Integration, and SAP C4C ERP Integration 2.0.

Not included are older custom developments without an S/4HANA path, unlisted industry solutions, and add-ons SAP has already discontinued. For these components, there is no maintenance path within the Transition Option. They must either be migrated or decommissioned before service start.

The S/4HANA Compatibility Pack, available to certain cloud customers through the end of 2030, does not automatically apply within the Transition Option. Confirm explicitly with your SAP Account Executive which compatibility rules apply to your specific system configuration.

Practical tip: Build a two-column list: add-ons that appear on the Available Add-on List, and add-ons that do not. The second column is your migration plan. The earlier this list exists, the earlier you can build dependencies into transformation projects for affected add-ons.

Step 3: Understand and Request Max Success Plan Transition Services

The Transition Option is contractually tied to a mandatory Max Success Plan Transition Services commitment. This is not an optional add-on; it is a condition of the subscription.

What the Max Success Plan covers in this context:

Max Success Plan Transition Services includes prioritized SAP support capacity for the transition phase, access to SAP expertise for technical migration guidance, and SLA guarantees for critical incidents. In practice, this means faster response times on support requests and a dedicated Customer Success Manager.

The cost of Max Success Plan Transition Services increases the total cost of the Transition Option. It is not negotiated separately; it is included as a mandatory component in the offer structure. What is often underestimated in practice: the Max Success Plan also creates a governance requirement on the customer side. SAP expects regular checkpoints, a named point of contact, and a documented migration roadmap.

Before contract signing, clarify internally: who takes on the role of Customer Success Plan Owner on your side? Without this assignment, it becomes unclear during operations who communicates with the SAP counterpart.

Step 4: Structure the Request for Proposal and Contract Negotiation

The formal application process begins with a request for proposal through your SAP Account Executive. The Transition Option is not ordered through the SAP Store or a self-service portal; it is agreed upon exclusively through a direct contract with SAP.

What you need to prepare for the request for proposal:

Completed system landscape documentation from Step 1
Confirmed add-on list from Step 2
Internal decision on the Max Success Plan Owner
Desired service start date (between January 1, 2031 and December 31, 2033; termination with 90 days' notice to the contract end date)

The offer SAP then prepares contains the ACV of the Transition Option and any applicable surcharge. Customers who subscribed before the end of 2025 carry no surcharge. Customers subscribing between 2028 and 2030 carry a 20 percent surcharge relative to the comparable SAP ERP Private Edition price. This difference is shown in the offer.

Cost governance moment: The offer from SAP is not a fixed price without room to negotiate. Add-on scope, sizing, and contract term structure all influence the ACV. If you have fully documented the scope before the offer phase, you have a solid negotiating foundation. If the sizing is outdated, SAP calculates based on internal estimates, which tend to be conservative.

Step 5: Close the Contract and Anchor the Migration Deadline

After accepting the offer, the Transition Option is set up as an addendum to the existing RISE or on-premise contract. Three points should be explicitly addressed in the contract text.

Subscription window and service start. The contract must clearly state the subscription start (no earlier than 2028), the service start (January 1, 2031), and the latest end date (December 31, 2033). An open end date is not permissible; the Transition Option is designed as a time-limited bridging model.

Add-on scope. The list of Add-on Product Versions covered by the Transition Option must be attached as a complete annex. Add-ons not listed in this annex are not covered, even if they technically appear on the Available Add-on List.

Migration commitment and S/4HANA path. The Transition Option contains no option to extend beyond the end of 2033. The contract text documents the expectation that you will have migrated to S/4HANA by the end of 2033. SAP anchors an explicit migration plan as an annex in many Transition Option contracts. If that is the case, build this plan realistically: an overly ambitious plan that needs revision later creates contract amendment work.

What Begins After Contract Signing

The contract is signed. The Transition Option runs from 2031. What begins now is governance.

The Transition Option pushes the migration pressure out to the end of 2033, but it does not eliminate it. Four governance moments remain active throughout the entire transition period.

Usage. FUE development and user growth on the on-premise system must be monitored continuously. Anyone who substantially expands user numbers or usage intensity during the Transition Option period changes the foundation of the later S/4HANA calculation.

Authorizations. Role design and authorization structures established today in the ERP system influence the FUE profile during the later S/4HANA migration. Role consolidation and authorization cleanup are not migration projects; they are ongoing governance tasks.

Infrastructure. SLA monitoring on the on-premise system and planning the hyperscaler environment for S/4HANA run in parallel. Starting infrastructure planning for S/4HANA during the Transition Option period gives you more flexibility for sizing decisions.

Costs. ACV tracking, add-on costs, and planned S/4HANA investments need to be brought together within a single budget framework. The Transition Option generates costs in 2031 through 2033 that run in parallel with migration costs. Mapping this early in financial planning prevents budget constraints at the worst possible moment.

Conclusion: Process Clarity as the Foundation for Governance

The Transition Option is a documentation-intensive decision. Working through the five steps systematically leaves you with more than just a contract: you have a complete system landscape documentation, a verified add-on scope, and a negotiated foundation for the S/4HANA migration path. Starting the process with outdated data or unresolved internal questions extends the application timeline and weakens your negotiating position.

The 2028 to 2030 subscription window may feel distant. The EHP upgrade work, the add-on inventory, and internal decision alignment are tasks that can begin today.

If you want to know which of your SAP systems meet the Transition Option requirements and where add-on dependencies exist, reach out to us. A Contract Check identifies your current position, your option space, and the data foundation you need for the application process, all within four weeks. EUR 7,900, fixed price.

Start your Contract Check

Further reading: SAP Transition Option: Mechanics, Deadlines, and the 20% Surcharge and Hub Pillar 7: SAP On-Premise Migration.