Why Companies Consider Rejoining SAP Support
Many SAP customers turn to third-party support providers — firms like Rimini Street, Spinnaker Support, or Origina — to reduce costs. Third-party maintenance typically runs at approximately 50% of SAP's standard support fees, delivering substantial savings that can total millions over several years. After enjoying those savings, however, strategic circumstances can arise that make returning to SAP maintenance appealing or necessary.
Preparing for an S/4HANA migration is the most common driver. To transition from SAP ECC to S/4HANA, companies need SAP's official conversion tools, migration guides, and access to new software releases. Being on SAP support eases access to these resources and upgrade paths. Without SAP maintenance, the company cannot download S/4HANA or apply the conversion. If your roadmap includes S/4HANA within the next two to three years, returning to SAP support becomes a practical prerequisite.
Needing official patches or version upgrades is a second driver. Third-party support keeps existing systems running — providing bug fixes, tax and regulatory updates, and interoperability patches — but it cannot provide new SAP software versions or enhancement packs. If the business requires a major version upgrade, new functionality that only SAP provides, or integration with SAP's newer cloud services, rejoining SAP maintenance is the straightforward path to obtaining it.
Executive pressure for vendor-backed support is a third, often underappreciated driver. Leadership changes, board-level risk concerns, or audit committee questions can create internal pressure to return to SAP's official maintenance umbrella. Executives may feel more secure with SAP itself backing mission-critical ERP systems, even if third-party support was performing adequately. Rejoining SAP maintenance can be a politically safe decision that reassures stakeholders the company has the vendor's full backing — particularly valuable in regulated industries or ahead of major business events like IPOs, mergers, or divestitures.
In short, the cost-saving phase with third-party support typically comes to an end when strategic needs arise that only SAP can address. Access to SAP's latest technology, official support infrastructure, and the reassurance of vendor-backed maintenance pull organisations back — but the terms of that return require careful navigation.
SAP's Reinstatement Policy Explained
SAP's maintenance return policy is notoriously strict and deliberately punitive. It is designed as a deterrent — to make leaving SAP support financially painful enough that customers think twice before switching to third-party providers, and to recover revenue from those who did.
⚠️ Key Elements of SAP's Reinstatement Policy
- Full back-maintenance fees: SAP typically requires payment of all the maintenance fees for the entire period you were off support — as if you had never left. If you were away for three years at 20%+ of licence value per year, SAP will present a bill for those three years of "skipped" support fees.
- Reinstatement penalty surcharge: On top of the back fees, SAP commonly adds a surcharge of 10–20% of the total back-maintenance amount. This penalty is SAP's explicit fee for "allowing" you to return, making the total reinstatement cost equal to or even exceeding the cost of purchasing new licences outright.
- Compliance review before reinstatement: SAP may conduct a licence compliance review before welcoming you back. If your usage grew while off support — additional users, expanded modules, indirect access via third-party systems — SAP could demand you purchase those licences and pay maintenance on them retroactively. Rejoining SAP maintenance may effectively come with an audit attached.
- No advertised amnesty: SAP does not offer a public "welcome back" programme or standard discount for returning customers. Any fee waiver or reduction must be negotiated case-by-case, typically by tying the return to a larger investment commitment (new licences, RISE subscription, S/4HANA migration).
The financial arithmetic can be severe. Consider a company with $10 million in SAP licence value paying standard 22% maintenance ($2.2 million per year). After three years on third-party support, SAP's reinstatement demand would be approximately $6.6 million in back fees plus $660K–$1.32 million in penalty surcharge — a total of $7.26–$7.92 million. At that level, the reinstatement cost approaches the original licence investment itself. This often negates the savings enjoyed during the third-party period and can make the entire third-party detour a net negative financially, unless the company negotiated the return strategically.
From SAP's perspective, the policy is logical: you benefited from the software while paying a third party, and SAP wants to recover the maintenance revenue as if you had stayed. But from the customer's perspective, it creates a formidable financial barrier to returning — which is precisely why negotiation is essential.
Strategies for Rejoining SAP Without Paying Full Back Fees
Facing a reinstatement invoice that can run into millions, organisations must approach the return to SAP support as a negotiation rather than a formality. There are three primary strategies for reducing or eliminating back-maintenance fees.
Purchase New Licences or Subscriptions (Clean Slate)
Instead of reinstating maintenance on your existing legacy licences, consider purchasing fresh licences — for example, licensing S/4HANA as a new contract — or moving to a subscription service like RISE with SAP. Under a new contract, you avoid paying back-maintenance on the old licences entirely, since you are technically starting a new commercial relationship. The downside is that you are paying for software licences again, but this route can be financially attractive if SAP's reinstatement quote equals or exceeds the cost of new licences. For organisations already planning an S/4HANA migration or cloud transition, buying new licences or subscriptions as part of that project may cost less than reinstating legacy support and then migrating later. Always model both scenarios side by side: the total cost of reinstatement (back fees + ongoing maintenance) versus the total cost of a new purchase or subscription (licence/subscription fees + implementation + ongoing support). In many cases, the clean-slate approach is the better financial outcome.
Negotiate an Amnesty Tied to New Investment
SAP does not advertise "welcome back" discounts, but everything is negotiable when you are bringing future revenue. Approach SAP as a customer who wants to return and invest in new SAP products — S/4HANA, RISE, Business Technology Platform, or cloud services. Emphasise your planned spend and present a credible multi-year roadmap. With that commitment on the table, push for a back-fee amnesty — a waiver or reduction of the back-maintenance fees as a condition of signing the new deal. For example: "If we commit to a $5 million RISE subscription over five years, we expect SAP to waive the $7 million in back support fees." The key is positioning your return as a win for SAP's future revenue pipeline, not just a request for forgiveness. SAP's sales team is measured on new bookings — a large cloud or S/4HANA deal is far more valuable to their targets than collecting back fees on legacy ECC licences. Use that dynamic to your advantage. Success is not guaranteed, but organisations that tie reinstatement to substantial new investment commitments have the strongest negotiating position.
Bundle Reinstatement Into a Broader Migration Deal
A variation of the amnesty approach is to fold the maintenance reinstatement into a larger commercial package. For instance, negotiate a deal where you return to SAP support as part of signing an S/4HANA licence contract or a RISE with SAP cloud subscription. In a bundle deal, SAP can apply special discounts, credits for your previous licence investment, or a discounted first-year maintenance rate on the new contract — structured so that the back fees are effectively absorbed into the broader deal economics. From SAP's side, the total deal value justifies the concession; from your side, the reinstatement cost becomes part of a value-adding project budget rather than a standalone penalty payment. Always get any such concession documented explicitly in the contract — verbal commitments during sales negotiations do not survive account team changes. Bundling is complex, but if you are genuinely planning an SAP migration, this approach can transform a punishing reinstatement fee into a line item within a strategic investment.
In all cases, do not accept SAP's first reinstatement quote. Whether through new purchases, amnesty negotiations, or bundle deals, there are always avenues to avoid writing a blank cheque for years of lapsed maintenance. Use your leverage as a potential new revenue source for SAP to secure a better outcome.
Licence Considerations When Returning
A critical point that is often misunderstood: when you left SAP support, you did not lose your SAP licences. SAP licences are perpetual — you retain the legal right to use the software you paid for, regardless of whether you are on SAP maintenance or third-party support. Your existing licences are the foundation for any return. You are not a new customer; you already own the software. Rejoining support is about reinstating maintenance on those licences (or swapping them for new ones), not repurchasing the software itself.
Perpetual Rights Remain
Your SAP licence entitlements survive the third-party support period. There is no "expiry" for having been off SAP maintenance. Any suggestion that your licences are invalid without SAP support is incorrect — perpetual means perpetual.
Maintenance vs. Subscription
Decide whether to reinstate traditional maintenance on your existing licences or transition to a subscription model (RISE, S/4HANA Cloud). If going cloud, negotiate credit for your existing licence investment in the new subscription pricing.
Usage Growth During the Gap
If you added users, expanded modules, or grew indirect access while off support, SAP will require you to licence those expansions upon return — potentially with retroactive maintenance. Conduct a self-audit before approaching SAP.
Compliance Self-Audit First
Before contacting SAP, verify user counts, module usage, and indirect access scenarios against your entitlements. Proactive awareness of any compliance gaps lets you control the conversation rather than letting SAP discover issues and charge list price.
If your usage grew during the gap — additional users deployed, new modules activated, third-party systems accessing SAP data (indirect/digital access) — you must address this before or during the reinstatement negotiation. SAP will almost certainly review your deployment as part of the return process. If they discover unlicensed usage, the consequences compound: you will be asked to purchase those licences and pay back-maintenance on them for the entire gap period, potentially at list price with no discount. The strategic approach is to conduct a thorough internal compliance review first, identify any gaps, and either true-up proactively (at negotiated rates you control) or include the true-up as part of the broader reinstatement deal where you have leverage to negotiate pricing.
Also consider whether any licences you hold are no longer needed. If you have shelfware — licensed modules or user types that you are no longer using — you may choose not to reinstate maintenance on those components, thereby reducing your ongoing support cost. This is a legitimate optimisation: you are under no obligation to put every historical licence back under maintenance. Only reinstate what you actually use and need.
System Currency and Upgrade Requirements
A practical challenge when returning to SAP maintenance is ensuring your systems are "current" enough for SAP to support. If you have been on third-party support for several years, your SAP software release may now be outdated or past its supported lifecycle. SAP will typically not provide full support for very old versions, so rejoining may require a software upgrade as part of the process.
Check your software versions: Review the version and patch level of your SAP ERP, database, and other components. If you left at ECC 6.0 on an older Enhancement Pack, that version may now be out of mainstream SAP support. SAP may mandate that you apply the latest support packs or upgrade to a minimum release before officially taking you back. Essentially, SAP does not want to support a system that is years out of date — the support overhead is too high, and the codebase may have known issues that only newer patches address.
Factor in upgrade project costs and timing: A version upgrade can be a significant project — potentially requiring several months, a dedicated team, and consulting assistance. During third-party support, you likely did not receive new SAP releases, so there could be a substantial leap between your current version and the minimum supported release. Include these project costs in your cost-benefit analysis. If you must spend heavily on a technical upgrade and pay reinstatement fees, the financial justification for returning needs to be commensurately strong.
Negotiate a grace period: In some cases, companies negotiate a short interim arrangement: they rejoin SAP support and immediately undertake the required upgrade, with SAP providing limited assistance during the transition window. SAP may agree to this if you present a credible upgrade plan with defined milestones. Clarify these expectations in the contract — you do not want to pay reinstatement fees and then discover SAP will not help you until you complete the upgrade independently. Plan the sequence so there is no gap in support coverage.
Cost-Benefit Analysis of Rejoining SAP
Before signing any agreement to return to SAP maintenance, step back and perform a rigorous cost-benefit analysis. Rejoining SAP support is a significant financial decision — sometimes running into millions — and a clear-eyed evaluation will determine whether the return is genuinely worth it or whether staying with third-party support longer is the smarter path.
| Cost Factor | Details | Example (3-Year Gap, $10M Licence Value) |
|---|---|---|
| Back-maintenance fees | Annual rate × years off support (typically 22% × 3) | $6.6 million |
| Reinstatement penalty | Surcharge of 10–20% on back fees | $660K–$1.32M |
| Total reinstatement cost | Back fees + penalty | $7.26–$7.92M |
| Upgrade project costs | If system version requires upgrade | $500K–$2M+ (varies) |
| Third-party savings realised | ~50% of SAP fees × years off support | $3.3M saved over 3 years |
| Net cost of the detour | Reinstatement + upgrade – savings | $4.46–$6.62M net additional cost |
Against these costs, weigh the benefits: access to S/4HANA conversion tools and new releases (essential if you are planning a migration), SAP's development-level support for critical issues (something third-party providers cannot escalate to SAP engineering), risk reduction and compliance assurance (particularly valuable in regulated industries), and the strategic positioning of your ERP platform for future innovation. If rejoining SAP support is enabling a larger initiative — an S/4HANA migration, a cloud transformation, a merger that requires SAP standardisation — the reinstatement cost becomes part of a project with its own ROI that may well justify the expense.
However, if you are returning simply to resume steady-state support for an ageing ECC system with no near-term migration plans, the cost-benefit case is much weaker. In many such scenarios, companies conclude that staying with third-party support until a defined migration point is more cost-effective — the savings continue to accumulate, and the reinstatement cost is deferred or eliminated entirely if the eventual migration uses new licences rather than reinstating old ones.
Negotiation Checklist for Returning to SAP
🎯 Pre-Negotiation Preparation
- Audit your licences and usage: Inventory all SAP licences, modules in use, current user counts, and indirect access scenarios. Identify any areas where usage exceeds entitlements and any licences that are no longer needed (shelfware). Present a clean, updated licence position to SAP — this accelerates negotiations and avoids drawn-out compliance disputes.
- Model multiple scenarios: Calculate costs for paying full reinstatement, buying new licences instead, staying with third-party support longer, or migrating to a cloud subscription. Having these comparisons allows you to counter SAP's proposals with data and demonstrate that you will not accept an unreasonable deal.
- Define your SAP roadmap: Clarify internally whether you plan to migrate to S/4HANA, adopt RISE, or remain on ECC. Your roadmap determines your leverage — a customer planning a multi-million cloud investment has far more negotiating power than one simply seeking to reinstate legacy support.
🎯 Negotiation Execution
- Propose a back-fee amnesty tied to new investment: Clearly communicate your planned SAP spend and use it as leverage to request a waiver or reduction of back-maintenance fees. Make the ask explicitly — SAP will not offer amnesty unprompted, but a significant deal on the table creates flexibility.
- Get everything in writing: Document every element — reinstatement fee waivers, credits for old licences, specific software versions you are entitled to, compliance settlements, and any promises about support for current systems. Verbal assurances from SAP sales teams do not survive account team rotations.
- Secure future cost protections: Negotiate price caps on ongoing maintenance fees (maximum annual increase percentages), or locked rates for a defined period. One reason you may have left SAP support was escalating costs — do not rejoin without addressing the structural issue that drove you to third-party support in the first place.
- Address system currency requirements upfront: Confirm which software versions SAP will support, what upgrades are required, and whether SAP will provide interim support during the upgrade window. Include the upgrade timeline and any SAP assistance in the contract.
- Engage independent advisers: SAP's reinstatement process is complex, and the financial stakes are high. Independent licensing advisers who understand SAP's internal pricing models, approval processes, and standard concession patterns can negotiate outcomes that internal procurement teams — who may face this situation once in a decade — cannot achieve alone.
Five Recommendations for CIOs Considering Rejoining SAP Support
Treat Rejoining as a Negotiation, Not a Default
Do not assume you must accept SAP's reinstatement terms. Approach the return like a new deal — because it is one. You are a customer bringing future revenue, and SAP's sales team has targets to meet. Use that dynamic to negotiate back-fee amnesty, reduced reinstatement penalties, and favourable ongoing terms. The worst outcome is accepting SAP's first quote without pushback.
Time the Return to Maximise Leverage
Your leverage is highest when you are committing to a significant new investment — an S/4HANA licence purchase, a RISE subscription, or a major cloud migration. If you can time your return to coincide with one of these events, SAP has every incentive to accommodate your reinstatement terms to win the larger deal. Returning purely to resume legacy support, with no new spend commitment, gives SAP little reason to offer concessions.
Get Your Compliance House in Order Before Approaching SAP
Conduct a thorough internal licence audit before initiating any conversation with SAP. Identify compliance gaps, unused licences, and indirect access exposures. Knowing your position — and proactively addressing gaps on your terms — prevents SAP from using the reinstatement process as a de facto audit where they control the pricing. Self-awareness is the best defence against compliance surprises at the negotiation table.
Compare All Paths: Reinstate, Repurchase, Stay, or Migrate
Model the financial scenarios rigorously. Reinstating legacy maintenance may not be the cheapest route — purchasing new S/4HANA licences, subscribing to RISE, or simply staying with third-party support until a natural migration point may all deliver better outcomes. Present these comparisons to SAP during negotiations: if repurchasing is cheaper than reinstating, SAP has a powerful incentive to improve the reinstatement terms to prevent you from choosing the clean-slate option (which resets their revenue baseline).
Lock in Sustainable Cost Terms to Avoid Repeating the Cycle
One reason you left SAP support in the first place may have been escalating, unsustainable maintenance costs. Do not rejoin without addressing this structural issue. Negotiate price caps on annual maintenance increases, fixed fees for a defined term, or a subscription model with predictable pricing. The goal is to avoid the same cost trajectory that pushed you toward third-party support — otherwise you risk repeating the entire cycle in a few years, with the same reinstatement penalties awaiting you again.