SAP Enterprise Support costs 18–22% of licence value annually — and rising. Third-party providers deliver equivalent maintenance at roughly half the price, with dedicated engineers, custom code support, and no forced upgrade timelines. This guide gives CIOs and CTOs the complete framework for evaluating, planning, and executing a switch to third-party SAP support.
SAP Enterprise Support fees typically run at 18–22% of the net licence value per year. For a large enterprise with $10M in SAP licences, that translates to roughly $2.2M annually — a figure that has been increasing with SAP’s recent inflation-indexed price adjustments (3.3% in 2023, 5% in 2024, with further increases signalled). Over a five-year period, an enterprise can easily spend $12M+ on SAP support alone, with diminishing returns for mature, stable ECC environments.
Simultaneously, SAP ECC is approaching end of mainstream maintenance in 2027, with extended support available until 2030 at a premium surcharge. This creates a “forced upgrade” timeline that many organisations are not ready for — and a growing number of CIOs are questioning whether paying full SAP support fees on a system with a diminishing roadmap makes strategic sense.
Third-party support providers — Rimini Street, Spinnaker Support, and others — have emerged to fill this gap. They maintain SAP systems at roughly 50% of SAP’s fees, extend support for ECC well beyond SAP’s own deadlines, and provide services (such as custom code support) that SAP’s standard offering does not include.
“The question is no longer whether third-party SAP support works — hundreds of Fortune 500 companies have proven that it does. The question is whether your specific situation favours the switch, and what the optimal timing and structure look like.”
The decision is not binary. Some organisations switch entirely, some move a portion of their estate to third-party support while keeping SAP support on strategic systems, and some use the credible threat of switching as a negotiation lever to reduce SAP’s own fees. All three approaches are valid, and this guide covers each.
The primary appeal of third-party support is cost reduction. Independent providers typically charge 50% or less of SAP’s annual maintenance fee, with multi-year fixed-rate contracts that eliminate the annual escalation problem.
| Support Model | Annual Cost (on $10M licence estate) | 5-Year Total | Annual Increases | Key Inclusions |
|---|---|---|---|---|
| SAP Enterprise Support (22%) | ~$2.2M | ~$12M (with escalation) | 3–5% per year | Patches, upgrades, notes, OSS portal |
| Third-Party Support (~11%) | ~$1.1M | ~$5.5M (fixed rate) | 0% (locked) | Break-fix, custom code support, tax/legal updates, security advisories |
| Savings | ~$1.1M/year | ~$6.5M over 5 years | — | Savings increase each year due to SAP’s escalation vs fixed 3P rate |
50%+ reduction in annual support fees from day one. No ramp-up period. Savings begin the moment the SAP support contract terminates and the third-party agreement activates.
SAP increases fees 3–5% annually. Third-party contracts are typically fixed for 3–5 years. The gap widens every year — year-five savings are materially higher than year-one.
Fixed multi-year contracts eliminate budget uncertainty. No surprise escalations. No inflation indexing. Total cost of ownership is known at contract signature.
Freed capital can fund digital transformation, cloud migration planning, analytics, or innovation — investments that drive business value rather than maintaining a status quo.
Situation: A global retail enterprise with $14M in SAP ECC licences was paying $3.1M annually to SAP for Enterprise Support. With no S/4HANA migration planned before 2028, the CIO evaluated third-party alternatives.
Approach: After a 90-day evaluation process, the company transitioned to Rimini Street for its ECC environment. The third-party contract was structured at 50% of the SAP fee with a 4-year fixed rate.
For a detailed case study, see Case Study: Saving $8M on SAP Support.
Cost reduction means nothing if service quality suffers. Third-party providers differentiate themselves by offering a more personalised, responsive support experience than SAP’s standard offering. Below is a direct comparison of what each model delivers.
| Capability | SAP Enterprise Support | Third-Party Support |
|---|---|---|
| Break-fix support | ✅ Via OSS notes and tickets | ✅ Dedicated engineers, faster resolution |
| Custom code / ABAP support | ❌ Customer responsibility | ✅ Included in standard contract |
| Tax & regulatory updates | ✅ Via standard notes | ✅ Proactive updates for all jurisdictions |
| Security patches | ✅ Monthly security notes | ✅ Security advisories + virtual patching |
| New feature packs / upgrades | ✅ Access to new versions | ❌ No access to new SAP releases |
| Performance optimisation | Limited / self-service | ✅ Proactive recommendations included |
| Dedicated account engineer | ❌ Shared pool model | ✅ Named engineer familiar with your landscape |
| SLA response time (P1) | ~4 hours initial response | ~15 minutes (some providers) |
| Interoperability / integration support | Limited to SAP products | ✅ Covers SAP + surrounding ecosystem |
The most significant service advantage of third-party support is custom code coverage. Most SAP environments contain hundreds of thousands of lines of custom ABAP. When that code breaks, SAP’s official response is “custom code is the customer’s responsibility.” Third-party providers treat custom code as part of the core system and support it accordingly. For organisations with extensive customisations, this alone can justify the switch.
Switching to third-party support is not without trade-offs. CIOs must understand exactly what they lose and assess whether those losses are material to their specific situation.
You lose the right to apply new patches, enhancement packs, and version upgrades. Your system is frozen at its current release. For stable ECC environments this is often acceptable — for organisations planning near-term S/4HANA adoption, this is the primary constraint.
If you later want to return to SAP support, SAP requires payment of all back-maintenance fees for the period you were off support (potentially years of accumulated fees at full rate). This makes rejoining expensive and effectively makes the switch a long-term commitment. See Rejoining SAP Support After Third-Party.
SAP views third-party support transitions negatively. Your SAP account team may become less collaborative, and future negotiations for new SAP products (RISE, BTP, cloud) may be more adversarial. Factor this into your broader SAP relationship strategy.
Redress Compliance provides independent SAP licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic licence optimization, Digital Access negotiation, and contract restructuring.
Explore SAP Advisory Services →The decision to switch to third-party support is fundamentally different depending on whether you are running ECC or S/4HANA, and where you are in your migration timeline.
If your S/4HANA migration is 3+ years away, third-party support on ECC is the highest-ROI decision available. You save 50%+ annually on a system that SAP itself is deprioritising, and the savings can fund your eventual migration.
If migrating within 1–2 years, the savings window is shorter. You still benefit, but ensure the third-party contract has flexible exit terms. Some organisations use a short-term (18–24 month) third-party arrangement as a bridge.
Third-party support for S/4HANA is emerging but less mature. If running S/4HANA on-premises with no plans for new feature adoption, it can work. If you need SAP’s innovation roadmap (AI, embedded analytics), stay on SAP support.
Third-party support is not anti-migration — it is pro-timing. The enterprises that achieve the best outcomes use third-party support to control their migration timeline rather than being forced into SAP’s preferred schedule. They save money during the bridge period, invest those savings in a well-planned S/4HANA migration, and re-enter SAP’s ecosystem at the point of maximum leverage (signing a new RISE or S/4HANA contract). The worst outcome is paying full SAP support on ECC for 3–4 years while doing nothing, then migrating under time pressure.
For S/4HANA migration planning, see CIO Playbook: Migrating from ECC to S/4HANA and SAP ERP Private Edition Transition Option — Extending ECC to 2033.
The third-party SAP support market is concentrated among a small number of established providers. Each has different strengths, coverage models, and commercial approaches.
| Provider | SAP Coverage | Global Presence | Differentiator | Typical Pricing |
|---|---|---|---|---|
| Rimini Street | ECC, S/4HANA, HANA, BW, CRM | Global (45+ countries) | Largest independent provider; publicly traded; most extensive SAP reference base | ~50% of SAP fees |
| Spinnaker Support | ECC, S/4HANA, HANA | Global (25+ countries) | Boutique approach; highly personalised account management; strong mid-market presence | ~50–60% of SAP fees |
| Origina | Limited SAP coverage | EMEA / NA | Multi-vendor focus (IBM, VMware, SAP); emerging SAP practice | Varies |
| USU / Aspera | SAP licence management + support advisory | EMEA | SAP licence management tools; advisory-led rather than break-fix support | Varies |
For a detailed provider comparison, see Best SAP Third-Party Support Providers Compared.
The mechanics of exiting SAP Enterprise Support are more complex than simply not renewing. Understanding the contractual requirements, timing windows, and SAP’s likely response is essential for a clean transition.
Many enterprises adopt a hybrid model — keeping SAP support on strategic systems while moving stable environments to third-party support. This approach captures 60–80% of the savings while maintaining access to SAP’s innovation roadmap where it matters.
Systems where you are actively adopting new SAP features, planning S/4HANA migration within 12–18 months, or running RISE with SAP cloud subscriptions. These need SAP’s upgrade path and innovation roadmap.
Stable ECC environments with no near-term migration, legacy BW systems, CRM systems being replaced, SAP environments in acquired companies pending decommission, and any system where you are paying maintenance on shelfware.
If 60% of your SAP estate qualifies for third-party support, the savings on that portion are still 50%+. On a $3M annual support bill, moving 60% saves ~$900K/year while maintaining SAP support on the strategic 40%.
The hybrid approach requires separating your SAP support contract by product/system. This may involve restructuring your SAP agreement — SAP sometimes bundles support to prevent selective cancellation. Address this during exit negotiations.
The hybrid approach also works as a negotiation tool. Telling SAP you are moving 60% of your estate to a third party creates pressure for SAP to offer concessions on the remaining 40% to avoid further migration. This dynamic consistently produces better commercial terms than a full stay or full switch.
Even if you ultimately decide to stay on SAP support, the credible threat of switching is one of the most powerful negotiation levers available to CIOs. SAP’s retention economics are simple: losing a $2M annual support customer permanently is far worse than offering a 25% discount to keep them.
Conduct a real evaluation with at least two third-party providers. Get formal proposals, reference calls, and a draft contract. SAP’s retention team can tell the difference between a genuine evaluation and a bluff.
Prepare a detailed comparison showing SAP’s current fees vs the third-party alternative over 5 years. Present this to SAP as a business case their management must beat.
Inform your SAP account team that you are evaluating alternatives. Do this 120+ days before your support renewal date. SAP will escalate internally, and their retention team has budget authority to offer concessions.
Typical SAP retention offers include: 15–25% support fee reductions, multi-year rate locks (0% increases for 3–5 years), enhanced support tiers (Premium Engagement at no extra cost), and RISE migration credits. Evaluate the total value against the third-party option.
Situation: A large financial services firm paying $4.8M annually in SAP Enterprise Support conducted a formal evaluation of Rimini Street and Spinnaker Support, including reference calls and draft contracts.
Approach: Armed with concrete third-party proposals, the CIO presented the alternatives to SAP’s global account team and requested a matching commercial offer. Negotiations ran for 8 weeks.
Below is the complete execution framework for evaluating and executing a switch to third-party SAP support.
Document every SAP product under support, the annual fee per product, the support contract renewal date, and the notice period. Calculate your total annual SAP support spend.
Determine which systems are migrating to S/4HANA (and when) and which will remain on ECC for 3+ years. Only stable, non-migrating systems are strong third-party candidates.
Request proposals from at least two providers. Evaluate coverage, SLAs, custom code support, regulatory update capabilities, global presence, and reference clients. Allow 45–60 days for evaluation.
Build a 5-year TCO comparison: SAP support (with escalation) vs third-party (fixed rate) vs hybrid. Include transition costs, potential reinstatement fees (if returning), and opportunity cost of freed capital.
Use your evaluation as leverage. Engage SAP’s retention team and negotiate their best counter-offer. Compare SAP’s retention deal against the third-party option on a total-value basis.
Choose: (a) switch fully, (b) hybrid approach, or (c) stay with SAP at renegotiated terms. All three are valid outcomes. The evaluation process improves your position regardless of the decision.
Finalise terms with your chosen provider. Ensure SLAs, termination rights, data portability, custom code scope, and regulatory coverage are explicitly defined. Legal review is essential.
If switching, submit formal written notice within the contractual window (typically 90–180 days before renewal). Before sending, download all needed SAP Notes, patches, and documentation from the SAP Support Portal.
Allow 30–60 days for onboarding. The provider will conduct a landscape assessment, assign dedicated engineers, and establish communication protocols. Run in parallel with SAP support for the overlap period.
After transition, review third-party service quality quarterly. Reassess the decision annually against your evolving S/4HANA migration timeline. Maintain the option to bring specific systems back to SAP support if business needs change.
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →