SAP Third-Party Support in 2026: Rimini Street vs Spinnaker vs Staying with SAP

The Third-Party Support Decision: Why It Matters in 2026

For ECC customers facing SAP's December 31, 2027 deadline, third-party support is no longer a fringe option—it's a mainstream strategic choice. SAP's standard maintenance costs 22% of net licence value annually. Extended maintenance (2028-2030) costs approximately 24%. Third-party providers like Rimini Street and Spinnaker Support deliver equivalent support at 11-13% annually, representing 40-50% cost savings.

For a €10 million ECC licence, the difference is stark: €2.2 million annually with SAP versus €1.1-1.3 million with third-party support. Over three years of extended maintenance, that's €900,000 to €1.1 million in savings. This isn't theoretical—hundreds of enterprises are making this choice in 2026, and the decision is reshaping how organizations approach the 2027 transition.

SAP's Legal and Lobbying Campaign Against Third-Party Support

Before examining the providers themselves, it's important to address the elephant in the room: SAP actively opposes third-party support and has taken legal action against Rimini Street multiple times. However—and this is crucial—courts have consistently ruled that third-party support is legal and that customers have the right to choose it.

SAP's argument is that third-party support violates intellectual property rights and support contracts. The reality, confirmed repeatedly by courts across multiple jurisdictions, is that once you own a software licence, you are entitled to seek maintenance and support from providers other than the vendor. SAP cannot force you to buy extended maintenance.

What this means practically: third-party support is legal, legitimate, and increasingly normalized in enterprise IT. SAP's sales team may argue against it during negotiations, but that's commercial pressure, not a technical or legal constraint. If your organization chooses third-party support, you are on solid legal ground.

The Market Leaders: Rimini Street vs Spinnaker

Rimini Street: The Comprehensive Choice for Global Enterprises

Rimini Street is the #1 ranked third-party support provider globally, with clients across every major industry and geography. They specialize in complex, multi-region enterprise deployments and have the largest engineering team dedicated to legacy SAP systems.

What Rimini Street covers:

• All core ECC modules (FI, CO, SD, MM, PP, HR, etc.)
• Custom code maintenance and optimization
• Third-party integration support
• Legal and regulatory updates
• Proactive system monitoring and performance tuning
• 24/7 support for P1 and P2 issues

Rimini's typical deployment model: Large enterprises with €50M+ licence spend assign a dedicated Rimini account team on-site or virtually embedded in their organization. This team becomes an extension of your IT department, managing day-to-day support while your organization plans the S/4HANA migration. Response times for critical issues are 30 minutes or less for P1 severity.

Pricing: Rimini's rates for ECC 11-12% of licence value are fixed for multi-year terms (typically 3-5 years). This predictability is valuable—you lock in costs while you plan your migration without SAP's annual price increases (which typically run 2-4% annually). Multi-year commitments also reduce effective rates to 10-11% for enterprises willing to lock in contracts.

Spinnaker Support: The Flexible, Boutique Alternative

Spinnaker Support is ranked #2 globally and takes a fundamentally different approach than Rimini Street. Rather than embedding large teams on-site, Spinnaker operates a more streamlined, flexible model designed for mid-market and upper-mid-market enterprises (€10-50M licence spend).

What makes Spinnaker distinctive:

• 1-year flexible contracts: No multi-year lock-in. This appeals to organizations with uncertain migration timelines.
• 15-minute P1 response time: Industry-leading response guarantees.
• Transparent pricing: No surprise escalations or hidden fees.
• Custom code coverage: Full support for modifications and customer enhancements.
• Streamlined engagement: Smaller dedicated teams reduce overhead and decision-making delays.

Spinnaker's typical deployment model: A dedicated team of 2-4 engineers is assigned to your account. Unlike Rimini, they're not embedded full-time on-site; instead, they work virtually with your team through defined engagement windows and SLAs. This works well for mid-market organizations that want expert support without the overhead of large on-site teams.

Pricing: Spinnaker's rates are 12-13% of licence value for 1-year terms. The flexibility of 1-year contracts is valuable if you're uncertain whether you'll complete migration in 2028 or 2029. You can evaluate progress annually and adjust your support strategy as migration progresses.

The Core Use Case: ECC Customers on a Delayed Migration

Here's where third-party support becomes strategically critical. The Horváth & Partners 2025 study showed that 60%+ of SAP migrations run over budget and behind schedule. That means a significant portion of the 21,350 ECC customers won't be ready by December 31, 2027.

For those customers, the choice is binary:

Option 1: SAP Extended Maintenance (2028-2030)
Cost: 24% of licence value annually
Timeline: You stay on ECC through 2030, forced to migrate by then
Downside: You're paying premium rates (24% vs 22%) for a compressed timeline, with no flexibility

Option 2: Third-Party Support (Rimini or Spinnaker)
Cost: 11-13% of licence value annually
Timeline: You can stay on ECC with equivalent support quality while continuing your migration at a realistic pace
Advantage: 50% cost savings, genuine support continuity, no compressed deadlines, ability to plan phased migration

The TCO Story: Why 90% Reduction Is Realistic (But Not the Way You Think)

You may have seen marketing claims that third-party support delivers "90% TCO reduction." That's technically true, but it requires context. The 90% figure assumes you compare full extended maintenance costs (24% of licence value) plus forced migration rush costs against third-party support plus a planned, phased migration.

Here's how that breaks down:

Scenario A: SAP Extended Maintenance + Rushed Migration
- Extended maintenance 2028-2030: €3.6M annually (€10.8M total)
- Rushed migration 2029-2030: €2M (consulting, integration, change management)
- Go-live disruption and post-implementation stabilization: €1.5M
- Total cost: €15.3M
- Plus: Higher operational risk due to rushed implementation

Scenario B: Third-Party Support + Planned Migration
- Rimini Street support 2028-2030: €1.2M annually (€3.6M total)
- Planned migration 2028-2030: €1.5M (phased modules, lower consulting intensity)
- Lower disruption costs due to realistic planning: €0.3M
- Total cost: €5.4M
- Plus: Lower operational risk, higher success probability

The delta is €9.9M, or approximately 65% savings. Add in avoided disruption costs and timeline extension benefits, and the "90% TCO reduction" claim becomes defensible. But the reality is simpler: third-party support is 50% cheaper than extended maintenance and enables you to migrate at a realistic pace, reducing overall programme costs by 30-40%.

Support Quality and Coverage: Are They Equivalent?

This is the critical question: does third-party support truly replace SAP's support quality? The answer is nuanced.

What Rimini and Spinnaker do equally well or better than SAP:

• Response time: Third-party providers typically respond faster to P1/P2 issues than SAP
• Custom code support: SAP's standard support explicitly excludes customer customizations; Rimini and Spinnaker include it
• Integration support: Third-party providers cover integration points and third-party systems; SAP often pushes these to external consultants
• Proactive monitoring: Rimini and Spinnaker offer proactive performance tuning; SAP's extended maintenance is reactive

Where SAP retains an advantage:

• Early access to updates: SAP releases patches to their own customers first; third-party providers receive them within 24-48 hours
• Direct access to engineering: On complex issues, SAP's global engineering team may have deeper institutional knowledge than third-party providers (though this advantage is diminishing)
• Roadmap alignment: If you're planning to migrate to S/4HANA, SAP's own team understands their migration tools more deeply

In practice, the difference is negligible for most ECC customers. The vast majority of issues are well-defined module problems, integration issues, or custom code bugs—all areas where third-party providers excel.

Migration Credits and Extended Runway

One of the strategic advantages of third-party support is that it doesn't accelerate your migration timeline—it allows you to migrate when you're ready. This matters because migration credits decrease year-over-year. A customer migrating in 2025-2026 receives better credits than one forced to migrate in 2030.

However, third-party support actually enables you to negotiate better credits by extending your runway. Here's why: if you have third-party support locked in through 2030, you can negotiate S/4HANA migration starting in 2028-2029 at a more measured pace. This allows you to avoid the 2027 rush and negotiate under less desperate circumstances. You're not forced to migrate in 12 months; you have 24-36 months to plan.

This paradoxically improves your migration credit negotiations because SAP knows you have a viable alternative (third-party support) and aren't desperate to migrate immediately.

Contract Structure and Key Negotiation Points

Length and flexibility: Rimini Street offers 3-5 year contracts; Spinnaker offers 1-year terms. Neither locks you into unrealistic obligations. Most customers sign 3-year agreements with either provider, aligned with their expected migration timeline.

Scope coverage: Ensure your contract covers:

• All instances and enhancements (test, production, sandbox)
• Custom code and modifications
• Integration with third-party systems and cloud platforms
• Regulatory and legal updates (country-specific)
• Escalation paths for critical issues

SLAs and escalation: Both providers offer clear SLAs. For P1 (critical production down), expect 30-60 minute response and 4-hour resolution targets. For P2 (degraded functionality), 2-4 hour response. P3/P4 are lower priority with 24-48 hour responses. Ensure escalation paths are documented and that escalations actually reach engineering (not just sales).

Cost negotiations: Standard rates are 11-13% of licence value. For large enterprises (>€50M), rates can be negotiated down to 10-11%. Multi-year commitments reduce effective costs by 10-15% (e.g., 3-year contract at 10.5% vs annual rates at 12%).

The Migration Path: How Third-Party Support Enables Phased Migration

One of the most valuable aspects of third-party support is that it removes the artificial deadline pressure and allows phased migration. Rather than attempting to migrate your entire ECC estate in 12 months (the forced approach if you stay with SAP), you can migrate in waves:

Year 1 (2028): Migrate non-core modules (SD, MM) to S/4HANA on a cloud or on-premise deployment. Keep FI/CO and custom components running on ECC with Rimini Street support.

Year 2 (2029): Complete FI/CO migration after validating first-year changes and resolving integration issues. This staged approach dramatically reduces go-live risk and allows your organization to build S/4HANA expertise gradually.

Year 3 (2030): Final cutover and retire ECC. If you've completed migration by then, cease third-party support. If delays occur (common in real projects), you can extend another year at minimal cost.

This phased approach is only possible if you're not forced to migrate by a hard deadline. Third-party support buys you that flexibility.

Why SAP Opposes Third-Party Support (And Why That Doesn't Matter)

SAP's lobbying and legal opposition to third-party support is worth understanding because it shapes how your sales team will respond if you mention it.

From SAP's perspective, third-party support is existential: if 30% of ECC customers migrate to third-party support instead of extended maintenance, SAP loses €2-3 billion annually in maintenance revenue. This is why SAP has taken Rimini Street to court in multiple jurisdictions and lobbied regulators to restrict third-party support.

However, courts have consistently ruled that intellectual property rights do not extend to preventing customers from choosing their own support vendors. This legal principle is settled. SAP cannot prevent you from using Rimini Street or Spinnaker.

What SAP can do—and will do—is pressure you during negotiations. Their sales team may:

• Claim third-party support is "risky" (it's not; it's been legal for 15+ years)
• Suggest integration issues will arise (they rarely do with experienced providers)
• Offer marginally better extended maintenance rates if you commit to SAP (common negotiation tactic)
• Imply that S/4HANA licensing will be punitive if you use third-party support (false; licensing is independent)

These are commercial arguments, not technical ones. Your legal and procurement teams should be comfortable that third-party support is legitimate.

The Real Question: When Is Third-Party Support the Right Choice?

Third-party support makes sense if:

1. You won't migrate by 2027. If there's genuine uncertainty about your migration timeline, third-party support eliminates the cost premium of extended maintenance.

2. Your migration timeline is 2-3 years, not 18 months. If you need runway beyond 2027-2028, third-party support is dramatically cheaper than SAP's extended maintenance.

3. You have custom code and complex integrations. Third-party providers actually cover custom code; SAP doesn't. This is a quality-of-support advantage.

4. You want to reduce dependence on SAP during transition. Locking in third-party support at known rates gives you pricing certainty while negotiating S/4HANA migration terms separately from SAP.

5. Your CFO cares about cost control. 50% reduction in maintenance spend over 2-3 years is material to any enterprise budget.

Third-party support is NOT the right choice if:

• You're genuinely ready to migrate by 2027 (just use SAP extended maintenance as a safety net)
• Your organization has no custom code or integrations (rare, but simplifies support)
• You prefer single-vendor relationships and want to avoid split support responsibilities

Vendor Comparison: Beyond Cost

While cost is the primary driver of third-party support adoption, non-financial factors matter too.

Rimini Street vs Spinnaker—when to choose each:

Choose Rimini if:

• You're a large global enterprise (€50M+ licence spend)
• You have multiple instances, regions, or complex integrations
• You prefer on-site or heavily embedded support teams
• You want industry-leading scale and brand recognition

Choose Spinnaker if:

• You're mid-market or upper-mid-market (€10-50M)
• You prefer flexible, 1-year contracts
• You want a more streamlined, less overhead-heavy engagement model
• You value flexibility and rapid decision-making over massive support teams

Making the Decision: A Practical Framework

If you're a CFO or IT director evaluating third-party support, here's the framework:

Step 1: Establish your realistic migration timeline. Be honest. If Horváth says 60% of migrations miss deadlines, yours probably will too.

Step 2: Calculate the cost delta between SAP extended maintenance and third-party support. For a €10M licence, the 3-year delta is €1.8-2.1M. Is that material? For most enterprises, yes.

Step 3: Evaluate support requirements. Do you have custom code and integrations? If yes, third-party support is actually superior. If no, support quality is equivalent.

Step 4: Get references. Both Rimini and Spinnaker can provide peer references from companies in your industry. Talk to them. Ask about response times, issue resolution, and engagement quality.

Step 5: Negotiate contract terms. Lock in rates for 2-3 years. Include escalation paths and SLA guarantees. Don't accept vague terms.

Step 6: Communicate your decision to SAP during licensing negotiations. This changes SAP's discount authority—they'll likely improve extended maintenance or migration terms if they know third-party support is a genuine option. This is your leverage.

Getting Help: Redress Compliance's Advisory Support

Navigating the third-party support landscape requires vendor knowledge and contract negotiation expertise. Many organizations benefit from external guidance through SAP audit defence specialists or independent SAP licensing advisory.

Our team at Redress Compliance has evaluated both Rimini Street and Spinnaker contracts for hundreds of enterprise customers and can help you:

• Model the cost impact of third-party support vs extended maintenance
• Structure third-party support agreements to maximize coverage while controlling cost
• Negotiate SAP terms with third-party support as a credible alternative
• Plan phased migration timelines that work with third-party support

If you're facing the 2027 deadline and haven't yet evaluated third-party support, now is the time. The decision impacts your budget, timeline, and overall migration strategy.

Conclusion: Third-Party Support Is Mainstream in 2026

Third-party support for ECC is no longer a niche option or a "risky" alternative. It's a mainstream, legally legitimate, and commercially intelligent choice for enterprises that can't migrate by 2027. Rimini Street and Spinnaker both deliver support quality equivalent to SAP while cutting costs in half.

For CFOs, the decision is straightforward: if you need extended runway beyond 2027, third-party support saves €1-2M annually compared to SAP's extended maintenance. For IT leaders, the decision is about support quality and coverage—areas where third-party providers actually excel due to their focus on custom code and integration support.

The only stakeholder who doesn't want you to consider third-party support is SAP. That's worth remembering as you evaluate your options.

Start evaluating third-party support now. Contact us to discuss your migration timeline and third-party support options.