Switching to Third-Party Support for SAP — Complete Guide

Why Companies Are Switching Now

SAP's mainstream maintenance for ECC 6.0 ends in December 2027. Every customer still running ECC faces the same pressure point: pay SAP's fee to receive a dwindling set of patches and regulatory updates as SAP focuses engineering on S/4HANA, or redirect that spend to a third-party provider who will support the ECC estate indefinitely at roughly half the cost.

The economics have sharpened considerably in 2025 and 2026. SAP's annual support fee sits at approximately 22% of net licence value — often the single largest recurring line item in an IT budget after staffing. A customer with a £5 million net licence value is paying roughly £1.1 million per year for support. Third-party providers charge approximately 50% of that rate, with no annual uplift clause. Over a five-year period, the cumulative saving after compound SAP price increases can exceed 60% of total support spend.

The 2027 ECC deadline has also sharpened the S/4HANA migration debate. Many organisations have evaluated RISE with SAP and concluded that the cloud ERP migration costs, business disruption, and retraining investment are not justified within the current planning horizon. For those organisations, third-party maintenance buys time: real time, protected by contract, not subject to SAP's lobbying pressure at renewal.

What You Lose When You Leave SAP Support

Before signing any third-party support contract, every procurement and IT leader needs a clear-eyed inventory of what SAP support actually provides — and which of those items matter to their specific organisation.

SAP Support Portal (SAP for Me) Access

When you terminate SAP maintenance, your access to the SAP for Me portal (formerly SAP ONE Support Launchpad and OSS) is revoked. This means no access to SAP Notes, no official Security Advisories, no OSS ticket submission, and no access to software downloads or enhancement packages for your existing licences. If you have been accustomed to pulling SAP Notes to diagnose issues or downloading kernel patches directly, this is a meaningful operational change.

Official SAP Security Patches

SAP publishes Security Patch Day updates on the second Tuesday of every month, covering critical vulnerabilities across NetWeaver, ABAP kernel, and application layers. Once you leave support, those patches are not delivered to you via the standard channel. Reputable third-party providers commit to creating functionally equivalent mitigations for critical vulnerabilities — but these are not SAP-certified patches. Your information security team needs to understand and formally accept this distinction.

Legal Regulatory Updates

SAP delivers tax, legal, and regulatory updates — payroll tables, statutory reporting formats, VAT rate changes — as part of its standard maintenance offering. Third-party providers also deliver these, and their coverage is often faster and more granular for specific countries, but you are relying on the third party's regulatory intelligence network rather than SAP's. For multi-country deployments, verify specifically which countries your chosen provider covers before signing.

Upgrade Rights and New Software Purchases

Your perpetual SAP licences remain valid indefinitely after you leave support — SAP cannot revoke the right to run the software you have already licensed. However, you cannot upgrade to new SAP product versions, and SAP will not sell you additional SAP software until you are back on active support. This is the critical constraint for any organisation that intends to adopt S/4HANA, SAP BTP services, or additional SuccessFactors modules in the future. Third-party support is a strategic pause, not a permanent exit — the re-entry cost must be modelled before committing.

SAP Solution Manager and DDLC Measurement

SAP's Digital Document and Licence Compliance (DDLC) metric governs indirect access measurement in the ECC environment. SAP uses Solution Manager to measure system landscape connections and document exchange volumes that feed into DDLC calculations. When you leave support, SAP loses its standard measurement window — but you do not lose your licence compliance obligation. Your indirect access position must be documented and maintained independently. Some third-party support customers have found that leaving support reduces SAP's visibility into their estate, but this creates legal exposure, not protection, if SAP later conducts an audit.

The Switching Process: Step by Step

A well-executed transition from SAP maintenance to third-party support takes nine to twelve months from initial evaluation to go-live. Rushing the process creates avoidable risk — particularly around licence compliance documentation and vendor selection due diligence.

Step 1: Licence Compliance Audit (Months 1–2)

Before you exit SAP support, establish a clean baseline of your licence position. This means verifying named user licence types against actual system usage — particularly the distinction between Professional, Limited Professional, Functional, Productivity, and Worker User classifications. Misclassified users are common; they represent the primary audit exposure SAP will target once you are no longer a paying maintenance customer. Run your USMM licence measurement report, reconcile output against your contract schedules, and remediate any shortfalls before giving SAP notice of termination. A clean licence position eliminates SAP's strongest leverage point in any post-termination interaction.

For organisations planning an eventual move to S/4HANA, document how user types map under the new licence model. S/4HANA consolidates ECC's extended user taxonomy into four principal types, and the licence baseline resets at migration. Knowing your current ECC position informs your migration negotiation before you need it.

Step 2: Run an RFP for Third-Party Providers (Months 2–4)

The third-party SAP support market has two dominant enterprise providers: Rimini Street and Spinnaker Support. Both offer approximately 50% savings against SAP's maintenance fee, fixed-price contracts of three to five years with no annual escalation, and coverage for ECC, S/4HANA, and adjacent SAP products including SuccessFactors (on-premise HCM modules).

The differentiation between providers lies in: geographic regulatory coverage (country-specific payroll and statutory updates), response SLA commitments (Rimini Street offers a 10-minute response SLA for Priority 1 issues), support scope (whether custom code support is included or priced separately), and the provider's long-term financial stability. Rimini Street has committed to supporting SAP ECC 6 and S/4HANA through 2040, which addresses the most common objection to switching: that the provider may exit the market before the customer is ready to migrate.

Evaluate both providers across all dimensions, negotiate both contracts to best and final offer, and use the competitive tension. The pricing floor for third-party SAP support is not publicly listed — it is negotiated. A well-run RFP should yield pricing at the lower end of each provider's standard range.

Step 3: Give SAP Written Notice (Month 4–5)

SAP's standard maintenance contracts renew annually on December 31 — aligned to SAP's fiscal year end. The notice period for termination is typically 90 days before renewal, which means the deadline for most customers to notify SAP is September 30. Failing to notify by that date results in automatic renewal through the following December, adding twelve months of SAP maintenance fees to your cost base.

Notice must be given in writing through the correct SAP contract channel — not verbally to an account executive. Review your specific SAP GSLA (General Software Licence Agreement) and any Order Form schedules for the exact notice provisions that apply to your contract. Some contracts have shorter notice periods; some legacy contracts require 180 days. Do not assume the standard applies.

When you give notice, expect your SAP account team to respond with a retention offer. Standard tactics include temporary fee discounts, credit towards future S/4HANA licensing, and bundled RISE with SAP proposals. These offers should be evaluated against the full five-year financial model, not against the immediate year-one saving. The RISE with SAP offer in particular requires careful scrutiny: many elements presented as "included" in RISE — BTP credits, cloud infrastructure, hyperscaler fees — are in practice separately priced or subject to consumption limits that exceed standard enterprise usage.

Step 4: Transition Technical Access (Months 5–8)

Before your SAP support contract terminates, download or archive any SAP Notes, documentation, and software versions you will need after your portal access is revoked. Establish the technical connectivity that your chosen third-party provider requires to access your systems for remote diagnosis and fix delivery. This includes configuring appropriate network access, agreeing a data processing agreement under GDPR (mandatory if the provider accesses EU-hosted systems), and completing the provider's system onboarding process.

Ensure your internal SAP Basis team is briefed on the new escalation path. The third-party provider replaces SAP Support Services as the first call for production incidents, break-fix issues, and regulatory update delivery. Internal processes, runbooks, and escalation matrices must reflect this before go-live.

Step 5: Go Live on Third-Party Support (Month 9–12)

The SAP maintenance contract terminates, the third-party contract activates, and the saving is realised from day one of the new arrangement. Budget the savings explicitly in the IT financial plan for the next three to five years — the primary purpose of the switch is to free capital for either migration investment or other strategic IT priorities, not simply to reduce the IT budget.

The Reinstatement Trap: Modelling the Cost of Going Back

The most important financial analysis in any third-party support decision is not the saving — it is the cost of return. If you leave SAP support and later need to resume it (typically because you have committed to S/4HANA migration or need to purchase additional SAP software), SAP's standard reinstatement policy requires payment of all back-maintenance fees for the period you were off support, plus a reinstatement surcharge.

The back-maintenance calculation is straightforward: for each year off support, you owe SAP the maintenance fee you would have paid in that year, including any uplift that would have applied. The reinstatement surcharge is typically 15–20% of the accumulated back-maintenance total. For an organisation with £1 million per year in SAP maintenance fees, three years off support produces a reinstatement bill of approximately £3 million in back fees plus £450,000–£600,000 in surcharge — a total of £3.45 million to £3.6 million.

This figure must be compared against the cumulative saving achieved during the third-party support period. Three years at 50% saving on £1 million generates £1.5 million in savings. If the reinstatement cost is £3.5 million, the net position after reinstatement is negative by £2 million. The only way this arithmetic works in the customer's favour is if the reinstatement cost is negotiated down — which it can be, but only with leverage.

SAP has consistently reduced back-maintenance fees for customers returning with a confirmed S/4HANA commitment and a competitive RISE with SAP evaluation on the table. In our engagements, we have seen reinstatement surcharges waived entirely and back-maintenance reduced by 50–100% when the customer brings real commercial leverage to the table. The key is structuring the re-entry negotiation before you need SAP's cooperation, not after.

Licence Compliance During the Third-Party Period

Leaving SAP maintenance does not suspend your SAP licence compliance obligations. Your perpetual licence agreement remains in force, and SAP retains the right to audit your estate at any time. In fact, organisations that have left SAP support have reported receiving audit notification within the first 12–24 months of the transition — a pattern that suggests SAP uses audit as a retention mechanism.

The DDLC (Digital Document and Licence Compliance) metric governs how SAP measures indirect access — the use of SAP system data and functionality through third-party applications, interfaces, and bots. Without active SAP support, you will not receive DDLC measurement guidance or SAP's standard licence reconciliation assistance. This means your internal compliance programme must become self-sufficient. Maintain accurate records of named users, user type classifications, and interface connections. If USMM measurement reveals overages during the third-party period, remediate them internally — do not wait for SAP to discover them during an audit.

If your estate will change significantly during the third-party support period — through acquisitions, divestitures, or infrastructure moves — document every change against your licence entitlement schedule. Changes that would normally be reported to SAP through the standard support channel must now be tracked internally and would need to be disclosed cleanly at any future reinstatement negotiation.

S/4HANA Migration and the Third-Party Support Intersection

The most common objection to third-party support is that it blocks S/4HANA migration. This is partially true: you cannot migrate to S/4HANA while on third-party support without first returning to SAP maintenance. But the practical constraint is narrower than it appears.

Most organisations evaluating third-party support are not planning an S/4HANA migration within the next three to five years. The realistic S/4HANA migration timeline for a complex enterprise — including greenfield implementation or system conversion, data migration, integration rebuild, and user retraining — is typically 24 to 48 months from project kick-off to go-live. An organisation that signs a three-year third-party support contract today, returns to SAP support in 2029, and begins S/4HANA implementation in 2030 is working to a timeline that is entirely consistent with SAP's stated 2027 ECC support end (noting that extended maintenance arrangements exist beyond that date).

The key is not to make the third-party support decision in isolation from the migration roadmap. A five-year third-party contract signed without modelling the migration scenario creates financial exposure. A three-year contract aligned to a modelled migration window creates optionality and savings simultaneously.

Decision Checklist: Is Third-Party SAP Support Right for You?

Before committing to a third-party support transition, validate the following conditions against your specific circumstances:

• Licence compliance is clean. Your named user counts and user type classifications are accurate and documented. No known DDLC or indirect access exposure. Remediating compliance issues before exit eliminates SAP's primary audit lever.
• No planned SAP software purchases in the next 3 years. Third-party support blocks additional SAP product acquisitions. If your roadmap includes SuccessFactors expansion, SAP BTP projects, or Ariba adoption, those purchases require active SAP maintenance.
• No S/4HANA migration committed within the support contract period. Or if migration is planned, the reinstatement cost has been modelled and is financially acceptable.
• Your chosen provider covers your regulatory jurisdictions. Country-specific payroll, statutory reporting, and tax update coverage has been verified for every country in your ECC deployment footprint.
• Your information security team has accepted the patching approach. Third-party providers create mitigations for SAP vulnerabilities, but these are not SAP-certified patches. The security risk acceptance must be documented and formally approved.
• Your notice period has been reviewed. The exact termination notice requirement in your SAP GSLA has been confirmed. The September 30 deadline for December 31 renewal applies to standard contracts; your contract may differ.
• The five-year financial model is positive. After including reinstatement costs at standard (not negotiated) SAP rates, the cumulative saving over the contract period is still positive. Never rely on negotiating the reinstatement surcharge — model it at full rate and treat the negotiated outcome as upside.

Related SAP Support and Licensing Topics

Third-party maintenance is one element of a broader SAP support strategy. The decision intersects directly with several other licensing and contract topics that organisations should review in parallel: understanding SAP third-party support best practices, the implications of SAP's shift from RISE with SAP to Cloud ERP licensing, and how SAP vendor management frameworks govern the overall relationship with SAP during and after a support transition.