SAP has publicly committed mainstream maintenance for SAP Business Suite 7 (the ECC generation) through the end of 2027, with optional extended maintenance available for an additional fee through the end of 2030, after which customers move to customer-specific maintenance unless they have migrated to S/4HANA. That timetable, published by SAP, is the single fact that frames every ECC customer's decision in 2026. You can pay SAP for extended maintenance, you can migrate to S/4HANA, or you can move to an independent third-party support provider. None of these is automatically right - the correct answer depends on your migration timeline, your customisation depth, and how much value SAP's ongoing patches actually deliver to your specific estate. This sub-pillar sits under our complete SAP licensing guide and lays out the buyer-side comparison.
The ECC maintenance timetable
SAP's maintenance commitment for Business Suite 7 applications runs in two phases. Mainstream maintenance is included in the standard support fee through the end of 2027. Extended maintenance is then available, for an additional percentage uplift on the maintenance base, through the end of 2030. Beyond that, customers remaining on ECC fall to customer-specific maintenance - a status in which SAP no longer guarantees new patches or legal and regulatory updates for the release. By contrast, SAP has committed maintenance for S/4HANA through at least 2040. Those dates are the fixed points; everything else in the decision is a judgement about cost, risk, and timing.
The three paths
Every ECC customer is choosing among three destinations, and it helps to name them plainly. The first is staying on SAP maintenance - mainstream now, extended later - while you plan or execute a migration. The second is migrating to S/4HANA, which ends the maintenance question by moving to a product with a long committed support horizon. The third is switching to independent third-party support, in which a provider other than SAP maintains your ECC system, typically at a lower annual cost, for as long as you choose to run it. These are not mutually exclusive over time: many organisations use third-party support to fund and de-risk a migration they will complete later.
| Path | Maintenance source | Typical fit | Main trade-off |
|---|---|---|---|
| SAP standard / extended maintenance | SAP | Migrating soon; want full vendor patches and legal updates | Extended maintenance carries an additional fee; ECC still ends |
| Migrate to S/4HANA | SAP (committed to 2040+) | Ready to invest in transformation now | Largest cost and project risk; re-licensing required |
| Independent third-party support | Rimini Street, Spinnaker Support, others | Stable ECC estate; migration deferred or undecided | No new SAP versions; SAP relationship changes |
The economics of third-party support
The headline appeal of third-party support is cost. Independent providers typically price annual support below SAP's standard maintenance rate, and they generally hold annual increases flat or capped rather than letting them compound. For a large ECC estate, the difference between SAP maintenance and third-party support over a multi-year deferral period can be substantial, and that saving is often what funds the eventual S/4HANA programme. The non-cost appeal is coverage of customisations: independent providers support the custom ABAP and configuration in your system directly, where SAP's standard support focuses on standard code.
The economics only work, though, when the estate is genuinely stable. Third-party support makes most sense when you are not planning major new SAP functionality on ECC during the support period, when your customisations are mature, and when SAP's quarterly patching is no longer delivering features you need. If you are actively developing on the platform or expect to consume new SAP innovation, the value of staying on SAP maintenance rises.
The independent providers
The two best-known independent SAP support providers are Rimini Street and Spinnaker Support. Both maintain SAP ECC and related applications, deliver security and tax/legal/regulatory updates through their own engineering rather than SAP's binary patches, and support customisations. They differ in scale, geographic coverage, and the breadth of adjacent products they support, and buyers weigh those factors differently. We do not treat either as a universal default; the right provider depends on your product mix, regions, and service expectations, and we encourage clients to evaluate providers directly against their own estate. This page is vendor-neutral by design - the goal is to frame the decision, not to rank suppliers.
Third-party support and S/4HANA are not opposites. The most common mistake is treating "switch to third-party support" and "migrate to S/4HANA" as a binary. In practice, moving ECC to third-party support can be the funding and breathing room that makes a well-planned S/4HANA migration possible - you stop paying full SAP maintenance on a system you are about to replace, and you redirect that money into the migration. The two decisions should be modelled on one timeline.
The risks and what to verify
Leaving SAP maintenance changes the SAP relationship, and buyers should go in with eyes open. You forgo new SAP releases and enhancement packages while on third-party support. You rely on the provider's own patches for security and for legal and regulatory changes - so you should verify, for your specific countries and industries, that the provider delivers the statutory updates you depend on (payroll, tax, e-invoicing, and similar). You should also understand the contractual mechanics of returning to SAP later if you choose to, and how a future S/4HANA purchase would be priced. None of these is necessarily a blocker, but each should be confirmed before you commit, not after.
Where indirect access fits
An ECC exit decision cannot be made without considering indirect and digital access. SAP's licensing of third-party systems that read or write SAP data - through APIs and integrations - has evolved significantly, and it interacts with both the maintenance decision and any migration. If you move to third-party support, your indirect-access position on ECC is effectively frozen with your last SAP agreement; if you migrate to S/4HANA, digital-access document licensing becomes part of the new commercial. We cover the mechanics in our guides to the SAP Digital Access Adoption Program and to SAP API and indirect-access changes, both of which should inform an ECC exit.
A buyer-side decision sequence
The disciplined sequence is straightforward. First, fix your honest S/4HANA timeline - not the aspirational one. Second, model the cost of each maintenance path across that timeline: SAP mainstream then extended, versus third-party support, versus accelerating the migration. Third, stress-test the third-party option against your statutory-update and customisation needs. Fourth, fold in the licensing consequences - indirect access, and the re-licensing involved in mapping legacy ECC licences to S/4HANA roles, which we cover in mapping legacy SAP licences to S/4HANA user roles. Fifth, decide maintenance and migration as one linked choice.
Common myths about leaving SAP support
Several misconceptions distort the third-party support decision, and clearing them up sharpens the analysis. The first myth is that third-party support is legally risky in itself. Independent maintenance of software you have licensed is a long-established and lawful practice; the diligence is about how a specific provider delivers fixes and updates without infringing SAP's intellectual property, which mature providers have structured carefully. The second myth is that you can never go back to SAP. Returning is possible, but it carries commercial consequences - typically reinstatement terms - that you should understand in advance rather than discover later. The third myth is that third-party support means no support innovation; in practice providers compete on responsiveness, named engineers, and tailored service levels, which some customers find more attentive than standard vendor support.
The fourth and most expensive myth is that the maintenance decision is reversible at no cost at any time. It is not frictionless. Switching providers, or switching back, involves knowledge transfer, contractual notice, and transition effort. This is why the decision rewards being made deliberately, on a multi-year view, rather than as a reflex to a single renewal invoice.
Security without SAP's binary patches
The question buyers ask most often about third-party support is how security is handled when SAP's own patches are no longer applied. Independent providers address this through a combination of their own engineered fixes for genuine product vulnerabilities and a layered, compensating-controls approach - hardening, monitoring, and virtual patching at the network and application layer - that protects the system without altering SAP binaries. For many stable ECC estates this is sufficient, but it is a different security posture from receiving SAP's quarterly patch day, and your information-security and audit functions should be brought into the decision early. Ask the provider for specifics on how they handle newly disclosed vulnerabilities affecting your release, and validate that approach against your own risk appetite and regulatory obligations.
Building the internal business case
An ECC-exit decision usually needs sign-off from finance, IT, security, and procurement, and the business case has to speak to all of them. For finance, the case is the multi-year cost comparison across the three paths, with the cumulative saving from third-party support set against the eventual migration cost it helps fund. For IT, it is the support-experience and customisation-coverage comparison, plus the migration readiness picture. For security, it is the compensating-controls posture described above. For procurement, it is the contract mechanics - term, exit, reinstatement, and the indirect-access position. A business case that addresses each stakeholder on their own terms is far more likely to survive scrutiny than one built on headline savings alone.
For the direct cost-and-coverage comparison between SAP's own extended maintenance and independent support, continue to SAP ECC extended maintenance vs third-party support. For the migration that ultimately retires the question, see the ECC-to-S/4HANA migration playbook, and for the re-licensing detail, mapping legacy licences to S/4HANA roles. For an engagement that models all of this against your estate, see our SAP licensing experts service and the SAP vendor hub.