The Third-Party Maintenance Calculation That Most Companies Get Wrong
Between 2020 and 2024, the SAP alternative maintenance market grew at 9.9% compound annual growth rate. By 2033, the market is projected to reach $10.2 billion, up from approximately $4.5 billion today. That growth isn't accidental. It's driven by a simple, irrefutable fact: SAP's standard maintenance costs 22% of your license base annually, while providers like Rimini Street and Spinnaker Support charge approximately 11%—half the price.
On a $10 million SAP license base, this looks straightforward. SAP charges $2.2 million per year. Third-party providers charge $1.1 million per year. You save $1.1 million annually. Over three years, that's $3.3 million in pure cash back in your operating budget. For CFOs managing tight IT budgets, this is the math that wins boardroom approval.
But this calculation ignores one critical variable: the exit cost. And for companies planning to return to SAP support—whether to migrate to S/4HANA, regain access to the SAP portal, or achieve SAP-certified compliance—that exit cost rewrites the entire financial narrative.
What You Give Up When You Leave SAP Support
Understanding the reinstatement cost first requires understanding what third-party maintenance actually doesn't include. This isn't small print. This is foundational architecture.
When you move to third-party maintenance, you lose:
- SAP Portal Access: You cannot log into SAP's support portal. All incident management, knowledge articles, and technical resources flow through your third-party provider only.
- New Software Releases and Upgrades: SAP publishes new enhancement packs, kernel updates, and patches. Third-party providers maintain existing versions but do not deliver new functionality or major releases.
- Future HANA Certification: If you're running on traditional databases and third-party support extends that infrastructure to 2040 (as Rimini Street does), you cannot certify new HANA deployments under that support contract.
- SAP-Certified Regulatory Updates: SAP publishes regulatory and compliance updates—tax law changes, GDPR implementations, financial reporting standards. Rimini Street provides its own regulatory updates, but SAP does not accept these as equivalent for re-certification purposes when you return.
The last point is subtle but critical. Rimini Street extends support for SAP ECC through 2040. SAP's standard support for EHP 6-8 ends December 31, 2027. This sounds like Rimini Street gives you 13 years of additional runway. Mathematically true. Operationally misleading.
When you exit third-party maintenance and attempt to reinstate with SAP, SAP requires remediation work to bring your system into SAP-certified compliance. The regulatory updates from third-party providers are not automatically accepted. You may need to retroactively implement SAP-certified patches, tax updates, and compliance changes. This is paid professional services work. It can cost hundreds of thousands of dollars.
The Reinstatement Penalty: The Numbers SAP Won't Volunteer
Here's where the financial model breaks down for most third-party users: SAP's reinstatement policy.
When you return to SAP support after using a third-party provider, you must pay:
- Back Maintenance Fees for the Entire Third-Party Period: If you used third-party maintenance for three years, you owe SAP the difference between what you paid third-party and what you would have paid SAP. On a $10 million license base: three years at 22% = $6.6 million. You paid third-party $3.3 million. You owe SAP $3.3 million in back fees.
- Reinstatement Surcharge: On top of back maintenance, SAP applies a reinstatement surcharge of 10-20%, typically calculated around 15%.
Let's run the complete math for a realistic scenario:
A company switching third-party support in 2022 stayed with their provider for three years. Their license base: $10 million. Their annual third-party cost: $1.1 million. Total third-party spend 2022-2025: $3.3 million. When they decided to migrate to S/4HANA in 2025 and contacted SAP about reinstatement:
- Back maintenance fees: $3.3 million
- Reinstatement surcharge (15%): $495,000
- Regulatory compliance remediation: $850,000
- Total reinstatement cost: $4.645 million
Over three years, they saved $3.3 million. To return to SAP, they must pay $4.645 million. Their net position: negative $1.345 million. And this is before S/4HANA migration costs, which run separately at $5-15 million depending on complexity.
In the actual case study we've analyzed: A UK utilities company switched to third-party maintenance in 2022 on an ECC EHP 7 system, saving £880,000 per year. Over three years, that's £2.64 million saved. In 2025, they decided to migrate to S/4HANA. Their reinstatement cost (back fees + surcharge + compliance remediation): £4.8 million. Their total three-year cost to return: negative £2.16 million in net cash flow.
The Regulatory Update Problem
The compliance issue deserves separate treatment because it's where third-party support creates hidden organizational risk.
SAP publishes regulatory updates continuously. In 2023, for example, SAP released critical updates related to UK tax reporting, GDPR data retention, and financial reporting standards. These updates are delivered to SAP support customers as part of standard maintenance. They're also delivered to Rimini Street customers, but through Rimini Street's own delivery pipeline, using Rimini Street's own quality and testing standards.
When you maintain your ECC system on third-party support, your regulatory compliance is technically current—you have the patches Rimini Street is delivering. But you don't have SAP's sign-off on those patches. You don't have SAP certification.
This matters when:
- You face a regulatory audit and regulators ask for proof of SAP-certified compliance.
- You need to integrate with a new SAP module or system that requires certified baseline compliance.
- Your organization is acquired or merges, and the buyer's compliance team requires SAP-certified systems.
- You attempt to migrate to S/4HANA and SAP's migration tools require pre-migration compliance certification.
In these scenarios, you may need to retroactively patch your ECC system with SAP-certified regulatory updates. This is not a simple process. This is technical remediation work. Depending on your system complexity, this can cost $500,000 to $2 million in professional services.
Who Should Use Third-Party Maintenance (and Who Shouldn't)
Third-party SAP support is not universally wrong. But it is situationally specific, and the exit cost calculation changes the decision matrix fundamentally.
You should consider third-party maintenance if:
- You are committed to your ECC system for the next 5-10 years and have no active S/4HANA migration roadmap.
- Your business processes are stable, and you don't require frequent new SAP functionality or releases.
- You don't need SAP portal access or SAP-certified compliance for regulatory or contractual reasons.
- Your industry doesn't have heavy SAP-specific compliance certification requirements (finance, healthcare, utilities with SAP-certified audit trails).
- You have sufficient internal technical resources to manage risk independently if your third-party provider has coverage gaps.
You should NOT use third-party maintenance if:
- You're actively evaluating S/4HANA migration or cloud strategies within the next 3-5 years. The reinstatement cost is almost certainly higher than the support savings.
- Your industry has SAP-certified compliance requirements (financial services, healthcare, heavily regulated utilities).
- Your organization regularly integrates new SAP modules or upgrades existing modules. You'll need SAP portal access and SAP-certified paths forward.
- You're planning mergers, acquisitions, or significant organizational integrations where compliance certification becomes a liability.
- You can't quantify the exit cost in advance—and most companies can't, which is why they get surprised.
Not sure if third-party maintenance makes financial sense for your organization?
Get a license and maintenance cost analysis from our SAP commercial advisory specialists.The RISE with SAP Escape Route
There's a negotiation lever that third-party support customers rarely use: RISE with SAP.
SAP's cloud transformation strategy centers on RISE with SAP, which bundles ERP (S/4HANA), analytics (Analytics Cloud), and managed infrastructure services into a single contract. For companies using third-party support, RISE presents an opportunity to exit third-party agreements with reduced reinstatement penalties.
Here's why: SAP is aggressively incentivizing cloud adoption. When a third-party customer approaches SAP with serious intent to migrate to RISE with SAP (not just return to SAP support), SAP has authority to waive reinstatement fees or offer significant discounts. This isn't documented in SAP's published maintenance policy. This is a commercial negotiation point, and SAP applies it selectively to accelerate cloud transitions.
The UK utilities company we mentioned earlier didn't just pay the £4.8 million reinstatement cost. They engaged SAP directly about converting to RISE with SAP instead of returning to traditional support, then migrating to S/4HANA. SAP offered to waive 60% of the back maintenance fees (£1.98 million) as an incentive to commit to RISE with SAP. Their effective reinstatement cost dropped from £4.8 million to £2.82 million—still significant, but a £2 million difference.
This negotiation is most effective when:
- You approach SAP in Q4 of their fiscal year (December 31 year-end). SAP has maximum discount authority at fiscal year-end.
- You commit to RISE with SAP simultaneously with exiting third-party maintenance. One exit + one commitment = leverage.
- Your organization has a defined S/4HANA migration roadmap. "We're thinking about it" doesn't move the needle. "We're migrating January 2027" does.
- You have a large license base. SAP's discount authority scales with contract value. A $10 million license base gets better negotiating terms than a $1 million license base.
Building a Third-Party Exit Strategy Before You Need One
Most companies don't make a third-party exit plan when they enter third-party support. They should. The difference between planned exit and reactive exit is frequently millions of dollars.
A planned exit strategy answers these questions before you commit to third-party maintenance:
- What is our S/4HANA migration roadmap? If migration is likely within 5 years, third-party maintenance is almost certainly a financial negative when you include exit costs. If migration is 10+ years away or not planned at all, third-party maintenance may pencil out.
- What are our regulatory compliance requirements? If your industry requires SAP-certified compliance (regulated utilities, financial services, healthcare), what is the cost to achieve compliance certification when you return to SAP? Build this into the third-party calculation.
- What triggers a mandatory exit? An acquisition? An ECC end-of-life date? A merger? A cloud transformation initiative? Map these scenarios and model the reinstatement cost for each.
- When should we approach SAP for reinstatement negotiation? SAP's discount authority is highest in Q4 (fiscal year-end). If you know you're exiting in year 3 of third-party support, negotiate exit terms in Q4 of year 2. Don't wait until you need to exit.
- Should we commit to RISE with SAP instead of traditional support? Run the RISE math alongside traditional SAP support math. For many mid-market companies, RISE is becoming cost-competitive with traditional SAP support + third-party + exit costs combined.
Build these decisions into your third-party support contract negotiation. Spend time on exit terms. SAP's reinstatement policy is policy, but reinstatement fees are negotiable, particularly if you're planning to stay in the SAP ecosystem (cloud or on-premise) after exiting third-party.
Six Decisions to Make Before Switching to Third-Party Support
If you're evaluating third-party support now, use this decision framework to validate whether the 50% maintenance savings actually translate to bottom-line value for your organization.
1. Calculate Your Honest Exit Cost
Ask SAP directly: what is the reinstatement cost if we return to SAP support after three years of third-party maintenance? Get it in writing. Don't estimate. SAP will provide this number upon request. If SAP won't give you a number, you don't have enough information to approve third-party maintenance.
2. Model S/4HANA Migration Timing
Does your organization have a documented S/4HANA roadmap? If yes, when? If migration is within 4-5 years, third-party maintenance almost always creates a financial loss when you factor in reinstatement costs. If migration is 8+ years out or not planned, the math changes.
3. Assess Regulatory Compliance Exposure
Do you operate in an industry (financial services, healthcare, utilities, energy) where SAP-certified compliance is contractually or legally required? If yes, what is the remediation cost to achieve SAP-certified compliance when you return? This can be $500,000 to $2 million. Add this to your exit cost calculation.
4. Evaluate Your Risk Tolerance for Self-Service Support
Third-party support has limited escalation paths for critical issues. SAP's support organization is significantly larger. If you have a critical issue with third-party maintenance—a production outage, a compliance gap—your escalation options are constrained. Are your technical and operational teams prepared to handle higher-risk scenarios with third-party support?
5. Document Mandatory Exit Triggers
What events would force you to return to SAP support immediately? An acquisition? An ECC system migration? A regulatory audit? Map these scenarios. For each, calculate the reinstatement cost. Use the worst-case scenario as your financial reserve for third-party maintenance.
6. Negotiate RISE with SAP Alternative Pricing
SAP RISE includes infrastructure, analytics, and S/4HANA in a single contract. For some organizations, RISE is becoming cost-competitive with traditional SAP support. Get a RISE quote for your organization before committing to third-party support. Sometimes the "savings" from third-party support are smaller than moving to RISE with SAP and eliminating exit cost risk entirely.
Need help modeling the true cost of third-party SAP support for your organization?
Our SAP commercial advisory specialists have navigated 80+ third-party exit negotiations and SAP audit defence engagements.Third-party SAP support saves 50% on annual maintenance costs. That's mathematically true and strategically incomplete. The real question is not whether third-party support reduces your current-year SAP spending. The real question is what your total cost of ownership will be when you factor in reinstatement penalties, compliance remediation, and exit triggers.
For companies on stable ECC systems with no migration plans and no compliance certification requirements, third-party support can make financial sense. For everyone else—and that's most organizations—the exit cost calculation should be your primary decision driver. Run the numbers before you sign the contract. SAP's reinstatement policy isn't negotiable, but SAP's willingness to waive portions of that policy absolutely is, particularly if you approach SAP with a clear timeline and credible cloud migration commitment.
The companies that make this work are the ones that plan the exit before they execute the entrance.