SAP’s commitment to end mainstream maintenance for ECC in 2027 has reshaped the contract calendar for thousands of buyers. The deadline is well known. The licensing implications are less well understood, and the difference between mainstream maintenance, extended maintenance, and customer-specific maintenance has been blurred by both sides of the conversation. This article works through what the 2027 date actually changes, what it does not change, and how the buyer should re-plan the negotiation calendar around the deadline. Our migration compliance engagements have been organised around the 2027 date for several years; the framing below is what we apply.
What the 2027 date means
The 2027 date is the end of mainstream maintenance for ECC. Mainstream maintenance is SAP’s standard support tier: legal-change updates, security patches, code corrections, and the broader scope of corrective and adaptive maintenance. After 2027 the system continues to function and the contractual rights continue to operate, but mainstream maintenance ends. Buyers who wish to retain SAP-provided maintenance after 2027 enter either extended maintenance (a paid add-on through 2030) or customer-specific maintenance (a bilateral arrangement priced individually).
The date does not affect the entitlement itself. The buyer’s ECC licence does not expire at the date; the buyer retains the right to use the licensed system under the existing contract terms. The 2027 date affects only the maintenance that SAP provides; the entitlement to run continues. The ECC topic page covers the broader contract framework.
What changes at the date
Three things change. The buyer’s legal-change updates stop unless extended maintenance is purchased. The buyer’s security patches stop unless extended maintenance is purchased. The buyer’s code-correction support stops unless extended maintenance is purchased. Together these mean that an ECC system operated past 2027 without extended maintenance is operating without ongoing vendor support for the regulatory, security, and functional changes that the system would normally absorb.
For regulated industries the loss of legal-change updates is material. Country-specific tax rules, country-specific reporting requirements, and country-specific regulatory frameworks all change over time; without legal-change updates the SAP system stops absorbing those changes and the buyer must apply them through customer development or through a third-party maintenance arrangement. The migration audit risk piece covers the audit implications of running unsupported.
The extended maintenance arithmetic
Extended maintenance runs from 2027 through 2030. SAP’s standard pricing for extended maintenance is a premium over the existing maintenance rate, with the premium increasing year over year through the extended-maintenance period. The arithmetic for the buyer is to compare the cumulative extended-maintenance cost against the migration cost to S/4HANA (in any of its delivery forms) and to make the trade-off explicit.
The recurring observation across our reviews is that the extended-maintenance arithmetic is often presented by SAP as the simple comparison but is rarely run by the buyer as the full comparison. The full comparison includes: the cumulative extended-maintenance cost; the migration cost; the post-migration run cost; the post-2030 customer-specific maintenance cost; and the regulatory-risk cost of running on extended maintenance. Done in full the arithmetic typically favours migration before the 2030 hard deadline, but the timing within the window depends on the specifics. The migration license risks white paper covers the full comparison.
The negotiation calendar
The 2027 date creates a negotiation calendar that buyers should be following deliberately. The calendar has three phases, each with its own buyer-side preparation requirements and SAP-side leverage profile.
Phase one — 2026 to early 2027
In this phase the buyer is preparing for the maintenance transition. The decisions are: migrate before 2027 (close out ECC before the maintenance change), extend maintenance through 2030 (defer the migration into the extended window), or commit to a longer-term ECC strategy with customer-specific maintenance after 2030. The decision should be made on the full arithmetic above; the negotiation with SAP at this phase concerns the price and terms of whichever path is chosen.
Phase two — 2027 to 2029
In this phase the buyer is executing the chosen path. For estates on extended maintenance the negotiation focus is on the renewal of extended maintenance each year, with the rate escalators tested against the available alternatives. For estates migrating, the negotiation focus is on the migration economics and the post-migration contract terms. The RISE conversion economics piece covers the migration-side commercial mechanics.
Phase three — 2030 onward
In this phase the buyer is either on S/4HANA in some form or on customer-specific maintenance for ECC. Customer-specific maintenance is bilateral, priced individually, and increasingly hard to obtain on commercially attractive terms. Buyers who plan to be on customer-specific maintenance after 2030 should be negotiating the terms during phase two, not at the start of phase three. The pharma migration case file documents the phased approach in practice.
The 2027 date does not force migration; it forces a decision. The decision can be migration, extended maintenance through 2030, or customer-specific maintenance beyond 2030. The cost of not deciding is that the default outcome — extended maintenance at SAP’s standard pricing — is the one that least matches most buyers’ commercial interest.
Third-party maintenance as an option
Third-party maintenance providers offer an alternative to SAP’s extended maintenance for buyers who plan to remain on ECC past 2027. The third-party offering typically includes the security patching, the country-specific legal-change support, and the code-correction support that SAP would otherwise provide, at a price meaningfully below SAP’s extended-maintenance rate.
The decision to use third-party maintenance has commercial, technical, and contractual implications. The commercial implication is the cost saving against extended maintenance. The technical implication is that the buyer loses SAP’s support for new SAP-delivered functionality (the system is functionally frozen at the third-party transition date). The contractual implication is that the SAP contract terms around maintenance, the SAP audit rights, and the SAP licence-management framework continue to apply even when third-party maintenance is in place. The decision should be made on a documented comparison of the three implications.
The migration-window negotiation
For buyers committing to migrate before 2030 the contract event around the migration is the major commercial moment of the 2027 window. SAP’s standard pricing for migration to RISE (or to GROW, or to private-edition S/4HANA) carries the standard transition incentives, and those incentives are negotiable. The recurring pattern across our engagements is that the SAP initial offer is materially below the achievable position; the gap can be ten to twenty per cent of the post-migration contract value.
The buyer-side preparation for the migration-window negotiation includes the full estate inventory, the FUE conversion analysis, the T-shirt sizing review, and the exit-terms preparation that would apply to any RISE or GROW contract event. The brownfield licensing risks piece covers the preparation in more detail.
— 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
Begin with the explicit decision: migrate now, extend through 2030, or plan for customer-specific maintenance beyond 2030. Run the full arithmetic on each. The default outcome is rarely the best outcome; the explicit decision is almost always meaningfully better economically. Then sequence the contract events according to the chosen path, with the buyer-side preparation matching the SAP-side leverage at each event.