A 23% Support Hike on Already Inflated Fees
The CFO's reaction when the SAP renewal landed was unprintable. After years of steady 3–5% annual increases, their largest ERP vendor had included a clause in the renewal contract that would raise standard support fees by 23% — citing "enhanced cloud support infrastructure." The retailer had no intention of moving to SAP's cloud. Yet they were being asked to fund it anyway.
This is a pattern we see constantly. SAP uses its annual maintenance contract — typically 22% of original licence value — as a cash engine that operates independently of whether the customer gets any value. For a company running SAP ECC 6.0 across its entire retail operation, the numbers had become untenable.
The retailer's SAP landscape was mature: ECC 6.0 with modules spanning MM (Materials Management), SD (Sales & Distribution), FI/CO (Finance & Controlling), WM (Warehouse Management), and HR. The system had been stable and customised over 14 years. There was no business case for S/4HANA migration — at least not on SAP's timeline. But SAP had a different view. Their account team had made it very clear: stay on standard support, or pay a premium for extended maintenance.
"SAP told us that standard support for ECC would move to 'limited maintenance' by 2027. When we asked what that actually meant in practice, they couldn't define it clearly — but they could tell us the price of extended maintenance. That told us everything we needed to know about who this policy was designed for."
Facing a Similar SAP Renewal?
Get a no-obligation assessment of your support options before you sign anything.
What Made This Transition Complex
Retail ERP environments are not simple landscapes to work with. The retailer had four primary concerns that made them hesitant about third-party support:
Hundreds of custom ABAP developments, BADIs, and user exits embedded throughout the core ERP. Any new support provider would need deep expertise to service these.
SAP instances spanning Germany, Netherlands, France, Spain, Poland, Czech Republic, and Austria — with multi-currency, multi-language requirements.
Retail does not get planned downtime. Any support transition needed to complete without disrupting point-of-sale, stock replenishment, or financial close cycles.
The company hadn't ruled out S/4HANA migration — they just needed 3–5 more years to build the business case properly, without being held hostage to SAP's fee schedule.
SAP's account team had framed the situation deliberately: any move away from standard support would "jeopardise" access to regulatory updates — particularly around German GoBD compliance and country-specific payroll changes. This is a common scare tactic. The reality, as the retailer would discover, is quite different.
Our ApproachHow We Structured the Transition
Our engagement began 14 months before the SAP renewal date — early enough to have genuine leverage, late enough that the urgency was real. We ran the transition in five phases:
Documented every custom object, identified all regulatory tax and payroll modules, catalogued open SAP support tickets, and assessed the quality of existing documentation. Produced a risk-ranked transition readiness report.
Ran a structured RFP across qualified third-party support providers. Evaluated on regulatory coverage (GoBD, French FEC, Spanish SII), ABAP customisation depth, SLA guarantees, and EU data residency. Selected and negotiated final contract terms.
Facilitated structured knowledge transfer sessions between the retailer's internal SAP team and the new support provider. Handed over all custom ABAP documentation, transport logs, and existing incident histories.
Managed the SAP notice period and contract exit. Coordinated download of all applicable regulatory update packages before the SAP support end date. Ensured all IP rights and licence terms were correctly transferred.
30-day parallel monitoring period with daily check-ins. Full financial close cycle completed under new support arrangement. Verified all country-specific payroll runs completed correctly.
Before and After: The Numbers
| Cost Component | SAP Standard Support | Third-Party Support | Annual Saving |
|---|---|---|---|
| Core ERP Maintenance (ECC 6.0) | €2,850,000 | €1,120,000 | €1,730,000 |
| HR / Payroll Module Support | €480,000 | €195,000 | €285,000 |
| Regulatory Update Management | Included (theoretical) | €85,000 | Cost absorbed, net positive |
| Escalation / Premium Support Add-ons | €870,000 | Included in base | €870,000 |
| Total Annual Support Spend | €4,200,000 | €1,800,000 | €2,400,000 (57%) |
The figures above exclude one-time transition costs (project management, knowledge transfer, legal review) which totalled approximately €180,000 — meaning full payback was achieved in under five weeks of the first year.
The ResultsEighteen Months On
Eighteen months after the transition, the retailer's Head of Technology reviewed what had actually happened versus what SAP's account team had warned about.
German GoBD, French FEC, Spanish SII, and Polish SAF-T requirements all met on schedule. The "regulatory risk" narrative was exactly that — a narrative.
Down from 11.3 hours under SAP standard support. The third-party provider assigns dedicated engineers with retailer-specific ECC knowledge, not generalists working from a ticket queue.
Year 1 savings funded: new e-commerce platform integration, AI-driven demand forecasting pilot, and a logistics optimisation project that had been blocked for three years.
The S/4HANA migration decision is now genuinely optional, not forced. The company can choose the right moment — on their terms, not SAP's pricing calendar.
See the SAP Audit Defence Playbook
15 pages of tactics used in 200+ SAP contract negotiations. Free download.
"GoVendorFree told us the compliance risk was overstated. We were sceptical — SAP had made it sound existential. Eighteen months later, not a single compliance issue. What we do have is €2.4 million a year that used to go to SAP now going into projects that actually matter to our customers."
Is Your SAP Estate in the Same Position?
The indicators that make a company a strong candidate for third-party SAP support are consistent across the cases we see:
- ✓ Running SAP ECC 6.x or earlier, with no firm migration date within 18 months
- ✓ Standard support fees exceeding €400K annually
- ✓ System is stable and customised — you're not consuming SAP innovation credits
- ✓ The SAP renewal conversation is creating tension at board or CFO level
- ✓ Digital transformation budget is constrained by the vendor maintenance burden
If three or more of those apply, a 15-minute conversation is worth your time. We'll tell you honestly whether third-party support makes sense for your environment — or whether there's a different lever to pull in your negotiation with SAP.
Discuss Your SAP Situation
Confidential. No obligation. We'll respond within 15 minutes during business hours.
Read More SAP Case Studies
See how manufacturers, banks, and logistics companies have cut SAP costs by 50–75%.