SAP Extended Maintenance Options 2027: Every Path Evaluated

The 2027 Deadline: What It Actually Means

SAP's mainstream maintenance deadline for ECC 6.0 (Enhancement Packages 6, 7, and 8) is December 31, 2027. This is not the end of the software — it is the end of SAP's obligation to deliver standard support services, including new legal and regulatory updates, new support packages, and new enhancement packages. Customers still running ECC after this date without a formal support extension will move automatically to Customer-Specific Maintenance (CSM), a much more limited and explicitly downgraded support tier.

It is critical to note one important eligibility distinction: customers on ECC 6.0 Enhancement Package 5 or earlier lost mainstream maintenance at December 31, 2025 — two years ahead of EHP6–8 customers. If your organisation falls into this group, the clock has already run out on standard SAP support, and your options are narrower.

SAP has confirmed it will not extend mainstream maintenance deadlines further. After multiple extensions over the past decade, this position appears firm. However, the post-2027 landscape is not a cliff — it is a structured set of time-limited options, each with distinct pricing, conditions, and strategic implications.

Option 1: SAP Extended Maintenance (2028–2030)

Customers on ECC 6.0 EHP6–8 who have not completed their S/4HANA migration by end of 2027 can elect Extended Maintenance, which runs from January 1, 2028 through December 31, 2030. This option keeps SAP delivering security, legal compliance, and stability fixes — but no new functionality, no new enhancement packages, and a progressively reduced investment from SAP's side relative to mainstream support.

The pricing mechanism is a two percentage point uplift on top of your existing maintenance basis. If you currently pay SAP Enterprise Support at the standard 22% of net licence value, Extended Maintenance brings that to 24% — roughly a 9% relative increase. For customers on Product Support for Large Enterprises at 17%, the rate moves to 19%, representing an 11% relative uplift.

There is an important eligibility condition that SAP has communicated, though it is not universally enforced: Extended Maintenance is intended for customers in active S/4HANA conversion phases. In practice, SAP may interpret this as requiring you to have already purchased S/4HANA licences before 2027 to remain eligible. Organisations planning to use Extended Maintenance purely as a deferral strategy — with no genuine migration timeline — may find SAP applying commercial pressure at renewal or using the eligibility language as negotiating leverage.

During the Extended Maintenance window, indirect access exposure continues to accumulate. Any third-party systems that document-create or read SAP data via non-SAP interfaces must be measured under SAP's Digital Document Lifecycle Count (DDLC) metric — the document-based measure SAP uses to quantify and price indirect access claims. Extended Maintenance does not pause audit risk; if anything, SAP's audit teams become more active as the 2030 expiry approaches. Conduct a DDLC position review before entering any Extended Maintenance agreement.

Option 2: Customer-Specific Maintenance (CSM) — The Default Fallback

If you take no action by December 31, 2030, your support automatically transitions to Customer-Specific Maintenance. This is not a purchased option — it is the default state for customers who remain on ECC with no active support agreement. The restrictions are severe:

• No legal and regulatory updates — SAP will not deliver changes required by new tax laws, payroll regulations, or statutory reporting requirements in your jurisdictions.
• No new support packages — There are no further patches or corrections outside your specific reported issues.
• No new kernel versions — New operating system and database versions supported by new kernels will not be delivered, creating a compounding technology gap over time.
• Break-fix only — SAP support responds only to specific customer-reported incidents, with no proactive maintenance.

CSM is unsustainable beyond a short period for any regulated enterprise. Legal and payroll updates alone typically require three to five support packages per year in active jurisdictions. Without them, compliance risk becomes acute within 12 to 18 months. CSM is best understood as a very short-term bridge — measured in months — while a migration or alternative support arrangement is finalised.

Option 3: SAP ERP Private Edition Transition Option (2031–2033)

In February 2025, SAP introduced the SAP ERP Private Edition Transition Option — a new subscription that allows customers to run ECC in a SAP-managed private cloud environment from 2031 through 2033. This is essentially ECC-as-a-service for the final three years before all SAP-provided support ends definitively.

The pricing for this option is structured as an uplift on the SAP ERP Private Edition subscription price, and the uplift level depends critically on when you commit:

• Commit to SAP ERP Private Edition by end of 2025 (start date no later than 2026): You are eligible for a 1:1 move to the Transition Option in 2031 with no additional uplift. This is the most favourable pricing available.
• Commit to SAP ERP Private Edition in 2026: A standard 20% uplift applies when switching to the Transition Option in 2031.
• Commit later or purchase the Transition Option directly from 2028: Pricing is set at SAP's discretion, and the favourable early-commitment terms no longer apply.

The 2025 commitment window has now passed, meaning the 20% uplift path is the minimum cost route for new commitments. Organisations still evaluating the Transition Option should move quickly — the longer you wait, the more pricing leverage shifts to SAP.

One important caveat: the Transition Option is a subscription, not a perpetual licence. Customers purchasing it do not acquire additional on-premise licence rights. It also bundles infrastructure and support in a way that makes cost comparison with on-premise or third-party alternatives complex. Engage independent advisors to model total cost of ownership over the 2031–2033 window before committing.

Option 4: Third-Party Maintenance (2028 Onwards)

The third-party SAP support market has matured significantly since SAP's 2027 deadline became fixed. Rimini Street and Spinnaker Support are the two dominant providers, with several regional specialists also active. Both offer broadly equivalent services to SAP Extended Maintenance — security patching, regulatory compliance updates, break-fix support — at approximately 50% of SAP's maintenance fee.

For an organisation paying €10 million annually in SAP support, moving to third-party maintenance generates approximately €5 million per year in savings. Over a three-year post-2027 bridge period, that amounts to €15 million in cost avoidance — significant capital that can be redeployed toward the S/4HANA migration itself.

Third-party maintenance also removes the migration pressure that SAP uses as commercial leverage during support negotiations. Once you leave SAP's support ecosystem, SAP no longer has a renewal conversation through which to push RISE with SAP or cloud conversion. This is both a financial advantage and a strategic one: it gives your organisation the time to evaluate S/4HANA on your own terms rather than against an artificial support deadline.

There are genuine limitations to consider. Third-party providers deliver localisation and regulatory updates for major jurisdictions but may have gaps in smaller markets or highly specialised industries. Certain SAP-specific technical capabilities — new kernel versions, compatibility with new hardware or OS versions — may not be available. Evaluate the specific regulatory update coverage for your jurisdictions before switching, and negotiate SLA terms contractually.

Option 5: S/4HANA Migration — The Strategic Endpoint

All of the above options are bridges. SAP's long-term direction is unambiguous: S/4HANA is the platform, and all investment — in development, AI capabilities, and integration with BTP and SAP's cloud applications — is concentrated there. Customers remaining on ECC face a compounding technology gap that no maintenance arrangement can fully close.

S/4HANA migration changes the licence baseline materially. Customers moving from ECC to S/4HANA typically need to renegotiate their entire user licence position, as ECC named user licences do not map cleanly to S/4HANA user types. The introduction of the Full Use Equivalent (FUE) metric in RISE with SAP further complicates baseline calculations. Budget for a licence remediation exercise as part of your migration business case, not as an afterthought.

For organisations in RISE with SAP, the annual support component is bundled into the subscription and sits at approximately 22% of the total contract value — consistent with SAP's traditional on-premise support rate. However, the all-in RISE subscription typically includes infrastructure, managed services, and access to SAP BTP credits, making direct cost comparison with on-premise maintenance complex.

How to Choose Your Path: A Framework

The right maintenance strategy depends on your migration readiness, regulatory complexity, and risk tolerance. Use the following framework as a starting point:

• Migration within 2 years (by 2028–2029): Extended Maintenance is the appropriate bridge. Negotiate it as part of your overall SAP contract, insisting that the 2% uplift applies only to the licences actively in use, not your full licence inventory including shelfware.
• Migration timeline of 3–5 years: Evaluate third-party maintenance from 2028. Use the savings to fund the migration, and return to SAP support (or move directly to RISE) when you go live on S/4HANA.
• Migration unlikely before 2031: Evaluate the SAP ERP Private Edition Transition Option for the 2031–2033 window. Given the 20% uplift now in effect, model total cost carefully against third-party alternatives through the same period.
• Highly regulated, multi-jurisdiction environments: Third-party maintenance carries localisation coverage risk. Audit the provider's specific country coverage before committing, and consider a hybrid approach where SAP support is retained for high-risk jurisdictions.

Negotiation Priorities Regardless of Path

Whether you elect Extended Maintenance, pursue third-party support, or commit to the Private Edition Transition Option, several negotiation principles apply across all scenarios:

Separate the maintenance conversation from the migration conversation. SAP sales teams routinely bundle Extended Maintenance offers with RISE with SAP commitments, presenting them as a package. The maintenance extension has value independent of any cloud migration commitment, and you should be able to negotiate the bridge terms without signing a cloud transformation agreement simultaneously.

Audit your licence position before entering any negotiation. SAP will know your usage data. If your DDLC numbers show undeclared indirect access, SAP may use the maintenance renewal as an opportunity to raise an audit claim or include a forced true-up. Establish your own independent DDLC position before SAP tables its first proposal.

Negotiate the scope of maintenance carefully. Extended Maintenance and the Transition Option are priced on your full maintenance basis, which may include licences you are no longer using. Insist on a right to exclude shelfware from the maintenance scope, or use the negotiation as an opportunity to formally retire unused licences and reduce your base.

Align timing with SAP's fiscal year. SAP's fiscal year ends December 31. The highest leverage window for maintenance negotiations is Q4 — particularly October through December — when SAP account teams are under maximum pressure to close deals. Use this timing deliberately.

Conclusion

The SAP 2027 deadline is not a binary choice between migrating to S/4HANA and being left without support. There are four distinct paths available — Extended Maintenance, Customer-Specific Maintenance (as a fallback only), the Private Edition Transition Option, and third-party maintenance — each suited to different migration timelines and risk profiles. The cost differential between the best and worst choices over the 2027–2033 window runs into tens of millions of euros for a typical large enterprise. Acting now, with independent advice and a clear negotiation strategy, is worth far more than waiting for SAP to make the first move.

Redress Compliance has supported over 80 organisations through SAP audit disputes, maintenance renegotiations, and migration contract negotiations. Our advisors operate exclusively on the buyer side. If you are facing the 2027 deadline and have not yet modelled your maintenance options in detail, contact us for an independent assessment.