The 2027 end of SAP ECC mainstream maintenance, the Extended Maintenance window through 2030, the Customer-Specific Maintenance position beyond, and the route-choice sequencing against the timeline. The Admodum read on the buyer-side commercial calendar.
The SAP Business Suite 7 (ECC) mainstream maintenance closes at the end of 2027. The 31 December 2027 horizon is the SAP-published date for the end of the bug-fix, the regulatory-update and the Service Pack delivery under the standard maintenance fee. The closure does not stop the ECC system from running; it stops the SAP-side delivery of fixes and updates against the standard fee.
The closure is the principal driver of the SAP route-choice discussion across the installed base. A buyer with a heavy ECC estate and a regulatory-update requirement (the typical financial-services, life-sciences or public-sector buyer) cannot stay on standard maintenance past the 2027 horizon. The wider S/4HANA conversion planning spoke reads the conversion routes against the horizon.
Extended Maintenance is the SAP-defined extension of mainstream-equivalent maintenance through the end of 2030. The Extended Maintenance fee carries an uplift above the standard maintenance fee (typically two to four percentage points of the licence base). The Extended Maintenance scope includes the bug-fix delivery, the regulatory-update delivery and the Service Pack delivery, against the same product code as the mainstream-maintenance scope.
The Extended Maintenance is an enrolment construct: the buyer enrols by an SAP-published cutoff and pays the uplift fee against the existing maintenance base. The Extended Maintenance window defers the route-choice decision by three years (from end of 2027 to end of 2030) at the cost of the maintenance-fee uplift. The deferral reads against the buyer's commercial-readiness profile.
Customer-Specific Maintenance is the SAP-defined position beyond the 2030 horizon. The position provides system stability and SAP-side support against the existing code line. The position does not include the regulatory-update delivery (the buyer accepts the regulatory-update absence) and does not include the bug-fix delivery beyond critical fixes.
The position is appropriate for the buyer with a defined ECC end-of-life timeline beyond 2030: the parallel-running scenario (the ECC estate runs alongside an S/4HANA estate during the transition tail), the divestiture scenario (the ECC estate runs against a divested entity that is being wound down), the legal-entity-specific scenario (the ECC estate carries one legal entity that exits independently). The Customer-Specific Maintenance is not the appropriate position for the buyer with a continuing-business ECC estate.
The SAP-side conversion-credit policy (the policy under which the existing on-premise licence value applies as a credit against the RISE, GROW or PCE subscription) is positioned against the timeline. The principal commercial position is that the conversion-credit recovery rate is most favourable in the pre-2027 window and declines through the Extended Maintenance window.
The buyer-side artefact at the conversion-credit moment is the on-premise valuation schedule: every licence, every original price, every Software Maintenance attachment. The schedule reads against the SAP-side recovery-rate proposal. The SAP cloud conversion credits spoke reads the credit mechanic in detail.
The buyer-side schedule sequences the technical readiness, the commercial readiness and the SAP-side conversion-credit positioning against the horizon. The schedule reads the buyer's S/4HANA readiness state (the Simplification List remediation, the custom-code adjustment, the unicode-conversion-if-needed), the commercial readiness (the FUE-conversion arithmetic, the hyperscaler position), and the SAP-side conversion-credit positioning (the recovery-rate model against the calendar).
The route choice (RISE, GROW, PCE-outside-RISE, on-premise plus BYO-hyperscaler, brownfield-stay-on-prem) is read against the schedule. The pre-2027 route choice preserves the conversion-credit and the negotiation BATNA; the 2027-to-2030 window defers the choice at a maintenance-fee cost; the post-2030 position is the Customer-Specific Maintenance position. The RISE versus on-premise read documents the route-choice framework.
The horizon negotiation surface has five axes: the Extended Maintenance enrolment timing (and the maintenance-fee uplift); the conversion-credit recovery-rate (against the calendar position); the route-choice timing (pre-2027, 2027-to-2030, post-2030); the BATNA preservation (the multi-year extension closes the BATNA, the one-or-two-year extension preserves it); and the parallel-running negotiation (the Customer-Specific Maintenance scope against the SAP-side support obligation).
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; the renewal-cycle mechanic continues in SAP renewal cycle; the conversion-planning read continues in S/4HANA conversion planning.
A senior Admodum SAP advisor will read your ECC estate state, your Extended Maintenance enrolment position and your route-choice readiness against the 2027 horizon on a private call. Active renewal moments route to Renewal Programme.