SAP Third-Party Maintenance: The Complete Guide to Alternatives and Savings (2026)

What Is SAP Third-Party Maintenance?

SAP third-party maintenance (TPM) is an alternative support model in which an independent firm — not SAP itself — provides break-fix support, regulatory updates, tax and legal patches, and interoperability assistance for your existing SAP landscape. You stop paying SAP Enterprise Support and instead pay a TPM provider, typically at 30–50% of what SAP charges.

The most prominent providers in the market are Rimini Street and Spinnaker Support. Both offer support for SAP ECC, SAP ERP, SAP S/4HANA (on-premise), SAP BW, and many SAP-adjacent technologies including Oracle, JD Edwards, and PeopleSoft. The TPM model has existed since 2008 and is now used by thousands of enterprises globally, including Fortune 500 manufacturers, financial institutions, and government agencies.

The fundamental premise is straightforward: if you are running a mature, stable SAP environment and have no imminent plans to move to RISE with SAP or S/4HANA Cloud, you are paying SAP 22% of licence value annually for support that a specialist third party can deliver at a fraction of the price. This is not a fringe decision — it is an established procurement strategy that leading enterprises use to fund their actual modernisation work.

The SAP Enterprise Support Problem

SAP Enterprise Support costs 22% of your total net licence value every year. For an enterprise with €10M in SAP licences, that is €2.2M annually in maintenance fees — regardless of how much of that support you actually consume. SAP insists on this model because it generates approximately 30% of SAP's total global revenue. The commercial imperative is clear.

What does 22% actually buy? SAP will tell you it includes access to SAP Support Portal, Solution Manager diagnostics, the SAP Enterprise Support Academy, enhanced SLAs, and continuous improvement content. What it does not include — despite what SAP implies — is customisation support, support for heavily modified code, proactive guidance on your specific architecture, or meaningful advisory on your licensing position.

The reality experienced by most enterprises is that the majority of high-value support is consumed through SAP Notes and the SAP Support Portal, not through active engagement with SAP's global support teams. The critical regulatory and legal updates — tax tables, country-specific payroll changes, statutory reporting modifications — are provided as SAP Notes that any competent partner or TPM provider can implement. SAP does not send engineers to your data centre to apply patches.

Furthermore, SAP's support quality has declined measurably as the company has shifted its engineering resources toward cloud products and RISE migrations. Many enterprises report deteriorating ticket response times, front-line engineers without deep ECC expertise, and an increasing tendency for SAP support to close tickets with "upgrade to S/4HANA" as the resolution. If you are maintaining ECC through 2027 or beyond, this dynamic is going to get worse.

Our SAP support cost reduction advisory has consistently found that enterprises paying 22% Enterprise Support are getting 60–70 cents of value for every dollar they spend. TPM closes that gap aggressively.

Top Third-Party Providers Compared

Two providers dominate the enterprise SAP third-party maintenance market. Understanding their differences is essential before making a sourcing decision.

Rimini Street

Rimini Street is the largest and most established TPM provider globally, with over 5,000 clients and coverage for SAP, Oracle, and Salesforce. Founded in 2005, they have a significant history of litigation with both SAP and Oracle — cases that ultimately established the legal legitimacy of the TPM model. Rimini Street's SAP practice covers ECC, ERP 6.0, S/4HANA on-premise, BW, HR, CRM, and SCM.

Rimini Street's model includes full tax, legal, and regulatory updates; interoperability support; performance tuning; and access to senior engineers with deep product experience. Their standard SLA for critical issues is 10-minute response with 24/7 primary engineer coverage. Pricing is typically 50% of what you pay SAP — and that price is locked for the duration of your contract, with no annual escalators.

Spinnaker Support

Spinnaker Support is the second major player, with a smaller client roster but a strong reputation for deep technical expertise and white-glove engagement. Spinnaker tends to attract enterprises with more complex, heavily customised SAP landscapes where they want dedicated engineers who understand their specific architecture. Their pricing is comparable to Rimini Street, though contract structures differ.

What TPM Covers — and What It Doesn't

Third-party maintenance providers are contractually obligated to deliver everything in their SOW — but they are not SAP and they do not have access to SAP's proprietary development pipeline. This distinction matters in specific scenarios and is something SAP exploits heavily in sales conversations. Here is an objective breakdown.

What TPM Delivers Effectively

Tax, legal, and regulatory compliance updates are the cornerstone of the TPM value proposition. Rimini Street and Spinnaker Support employ teams of tax and regulatory specialists who monitor legislative changes globally and deliver custom patches for your specific release and configuration. In many cases, TPM providers deliver these updates faster than SAP because they are not dependent on SAP's release management cycle.

Break-fix support for known defects — including support for custom code, which SAP explicitly does not provide — is fully covered by TPM. If your company has a heavily modified SAP landscape (and most large enterprises do), this represents genuine incremental value over SAP Enterprise Support.

Performance tuning, interoperability support for third-party integrations, and security vulnerability analysis are also typically included at no additional charge.

What TPM Does Not Cover

The clearest limitation of TPM is new feature development. SAP releases new functionality in Enhancement Packages (EHPs) and subsequent releases. If you are on SAP ECC 6.0 EHP7 and want to move to EHP8, you would need to return to SAP support to receive that upgrade. TPM maintains your current release at peak quality — it does not evolve it.

Access to future S/4HANA capabilities, SAP BTP services, or SAP cloud products requires active SAP maintenance. Enterprises planning a RISE migration within 2–3 years should model carefully whether the savings from an interim TPM period outweigh the complexity of re-engaging SAP maintenance before their cloud transition.

Finally, SAP's contractual terms include what is commonly referred to as a "go-back" provision — enterprises that leave SAP support and later return are typically required to pay backdated support fees for the period they were off SAP. This can represent a material cost that must be factored into any TPM decision.

SAP's Tactics to Prevent TPM Adoption

SAP does not sit passively while enterprises evaluate third-party maintenance. SAP's commercial teams have a well-documented playbook for retaining maintenance revenue, and understanding it is essential before you enter any conversation with SAP about your support options.

The RISE migration threat: SAP's most common counter-move is to suggest that switching to TPM will make your RISE with SAP or S/4HANA migration more expensive or more complex. This is often true in a narrow sense — there are transition costs when returning to SAP support — but SAP typically overstates these costs and refuses to acknowledge the multi-year savings that fund them.

The roadmap access argument: SAP will tell you that TPM customers lose access to SAP's product roadmap and innovation. In practice, this means access to SAP's forward-looking presentations and advisory content — not to any current software functionality. Most enterprises on stable ECC landscapes have limited use for SAP's roadmap presentations.

The security vulnerability threat: SAP has increasingly argued that TPM providers cannot deliver adequate security patches because they lack access to SAP's internal vulnerability database. SAP's own security advisory bulletins are publicly released, and TPM providers have developed robust processes for monitoring and addressing SAP security notes. This argument carries some weight for zero-day vulnerabilities but is largely a commercial tactic.

Contractual lock-in: Some SAP contracts include provisions that restrict third-party access to your SAP environment. Before engaging a TPM provider, your SAP Master Agreement must be reviewed carefully by advisors who understand SAP's contract language. Our SAP contract negotiation team has reviewed hundreds of these agreements and can identify any provisions SAP might use to challenge your TPM transition.

How to Negotiate Your Switch to TPM

Switching to third-party maintenance is not a unilateral decision — it requires careful sequencing and, ideally, parallel negotiation with SAP to maximise your position. Here is the approach we recommend.

Step 1: Establish a Credible Alternative

Before entering any conversation with SAP, obtain a formal proposal from at least one TPM provider. Understanding the precise cost, scope, and terms of the alternative strengthens every subsequent conversation. SAP's commercial teams respond to credible alternatives — a detailed TPM proposal on the table changes the negotiating dynamic immediately.

Step 2: Initiate a Support Cost Review with SAP

Approach SAP with a formal request for a support cost review. SAP has a range of commercial levers including temporary support fee reductions, credits, and bundled incentives that are never proactively offered but are available when an enterprise demonstrates genuine intent to leave. These incentives are most meaningful for enterprises with large licence values — typically above €3–5M annual maintenance spend.

Step 3: Review Your Master Agreement

Engage specialist advisors to review your SAP Master Agreement, Order Forms, and T&Cs before making any switch. Specific attention should be paid to provisions governing third-party access, licence audits, and maintenance reinstatement fees. A clean exit from SAP support requires contractual clarity that many enterprises overlook.

Step 4: Execute or Use as Leverage

In our experience advising on over 50 SAP support cost reduction engagements, approximately 40% of enterprises achieve their target savings without switching to TPM — purely by using the TPM alternative as credible negotiating leverage with SAP. The remaining 60% that execute the TPM switch save an average of 48% on their annual maintenance spend.

Real Risks and How to Mitigate Them

Third-party maintenance is not the right decision for every enterprise. The following risk factors warrant serious consideration before proceeding.

Near-term S/4HANA or RISE migration: If your organisation has a credible plan to move to S/4HANA within 18–24 months, the complexity and cost of the TPM-to-SAP-support return journey may eliminate or reverse the savings. Model the full lifecycle cost, not just the annual savings.

Heavy use of SAP Innovation Programmes: Enterprises that actively consume SAP's Innovation Programmes — including SAP Value Assurance, SAP MaxAttention, or SAP Preferred Care — receive services embedded in their support contracts that have genuine value. TPM may not replicate this value at equivalent quality. Assess actual utilisation, not theoretical coverage, before making this judgement.

Contract complexity: SAP contracts for large enterprises can include supplemental provisions that complicate a TPM exit. Engage specialist advisors who understand SAP's contract architecture before proceeding.

Internal change management: Switching SAP support is a meaningful operational change. SAP support teams, SAP Basis administrators, and IT operations need clear communication and process updates. Factor implementation effort into your business case.

The Decision Framework

Based on our experience advising enterprises across multiple industries, the following framework identifies the strongest candidates for third-party SAP maintenance.

Enterprises that meet most of these criteria and choose not to evaluate TPM are, in our view, leaving material savings on the table. The fundamentals of SAP licensing reward informed, proactive buyers — and penalise those who accept SAP's commercial terms as fixed.

For a broader view of how to control SAP's 22% maintenance cost as part of a wider negotiation strategy, read our guide on SAP Enterprise Support alternatives and our analysis of SAP maintenance renewal negotiation tactics.

Frequently Asked Questions