What You Are Actually Paying For
Annual maintenance for SAP ECC is calculated as a percentage of the net licence value. Enterprise Support runs at approximately 22%. Standard Support runs at approximately 17%. This percentage is applied to the original discounted licence value, not list price, meaning that the actual maintenance rate as a percentage of what you paid depends heavily on the discounts negotiated at the time of purchase. For customers who secured deep discounts of 60 to 70% off list, the maintenance-to-paid-licence ratio can exceed 100% within five years. That means you have paid more in cumulative maintenance than you ever paid for the licences themselves.
SAP Enterprise Support provides access to SAP's support portal, software updates and patches including Enhancement Packages, legal and regulatory updates, and 24/7 access to SAP's technical support team for Priority 1 issues. In theory, this is a comprehensive package. In practice, many organisations use only a fraction of these services, particularly if their ECC systems are stable and not undergoing active development.
SAP has historically applied annual increases of 3 to 4% to maintenance fees. In 2024, this jumped to approximately 5%, with some customers reporting increases as high as 8% when factoring in inflation adjustments and contractual price escalation clauses. These increases are typically applied automatically at renewal and, unless actively challenged, compound year after year. Over a five-year period, an unchallenged 5% annual increase turns a $4 million annual bill into $5.1 million.
Shelfware, licences that are purchased but not actively deployed or used, is endemic. It arises from over-purchasing during initial rollouts, from business units that decommissioned SAP-dependent processes, from merger-related licence accumulation, and from SAP's bundling practices. Across client engagements, shelfware typically accounts for 15 to 30% of the total SAP maintenance bill.
Before doing anything else, request a complete licence extract from SAP's licence portal showing every product, metric, quantity, and associated maintenance cost. Map licences to active usage through SAP Solution Manager's LAW (Licence Administration Workbench) to compare entitlements against actual system consumption. Identify every licence with zero or minimal usage. These are your immediate cost reduction targets.
European retail chain avoids €10M penalty and cuts SAP renewal costs by 20%
The 2027 Support Deadline: Threat or Opportunity
SAP's mainstream support for ECC 6.0 is scheduled to end on 31 December 2027. After that date, SAP will no longer provide standard support for ECC under existing maintenance agreements. SAP offers extended maintenance through 2030 at an additional premium, typically a 2% uplift on top of existing maintenance fees, with no functional enhancements and a progressively diminishing support investment.
Most organisations view the 2027 deadline as a threat. It is also significant negotiation leverage.
SAP's revenue model depends on retaining its installed base. Every customer that exits SAP maintenance represents a permanent revenue loss. Between now and 2027, SAP's account teams are under intense pressure to secure long-term commitments, whether through RISE with SAP conversions, S/4HANA licence sales, or extended support agreements. This pressure means SAP is more flexible on pricing, terms, and concessions than at almost any other time in the past decade.
The Three Strategic Paths
Path A: Migrate to S/4HANA. Full conversion by 2027. Requires significant investment, typically 1.5 to 3x annual SAP spend. SAP offers migration credits and conversion discounts, but these must be negotiated aggressively.
Path B: Extended Maintenance. Stay on ECC through 2030. Buys time but at escalating cost (22% plus 2% premium plus annual increases). No new functionality. Increasingly limited support responsiveness.
Path C: Third-Party Support plus Optimisation. Transition to independent support. 50%+ cost reduction. Indefinite support timeline. Preserves migration flexibility. Requires careful planning but delivers immediate savings.
These paths are not mutually exclusive. The most effective strategy often combines elements: negotiate an improved SAP maintenance deal short-term, eliminate shelfware immediately, transition non-critical modules to third-party support, and preserve the option to migrate selected workloads to S/4HANA on your own timeline. The 2027 deadline is not a trap. It is the best negotiation leverage SAP customers have had in a decade.
Optimising Your SAP Support Renewal
Before the next SAP maintenance renewal, a structured review of the contract and usage can unlock substantial savings, even without moving to third-party support. These tactics are applicable regardless of the long-term ERP strategy.
Eliminate Shelfware Licences
Identify every SAP module, user type, and engine licence that is not actively deployed in production. Common culprits include unused SAP BusinessObjects licences, over-provisioned Professional user types when Limited Professional or Employee Self-Service would suffice, and modules purchased as part of bundle deals but never implemented. For every licence removed from maintenance, you recover 22% of its value annually — a permanent reduction. Approaching this with detailed usage data and a firm position typically yields results even when SAP pushes back.
Downgrade Your Support Tier
If the organisation does not require SAP's full Enterprise Support, evaluate lower-cost alternatives. Product Support for Large Enterprises (PSLE) offers reduced fees for customers who do not need the full Enterprise Support scope. The difference between Enterprise Support at 22% and Standard Support at approximately 17% on a $20 million licence base is $1 million annually. For organisations with stable ECC systems that rarely engage SAP support, a lower tier is often more than sufficient.
Lock In Multi-Year Pricing
Use the 2027 deadline as leverage to negotiate a multi-year maintenance agreement with fixed pricing. SAP may be willing to cap annual increases at 0 to 3% rather than 5 to 8% in exchange for a commitment through 2027 or beyond. A three-year deal at 0% increase versus a 5% annual increase saves approximately 15% in cumulative maintenance costs over the term.
Leverage Future S/4HANA Plans
If evaluating or planning an S/4HANA migration, use that intent as negotiation currency. SAP's account teams are heavily incentivised to secure S/4HANA commitments, and they will often offer short-term maintenance discounts, migration credits, or deferred payments to customers who signal genuine migration interest. Extract concrete concessions before signing anything. For advisory support, see SAP Contract Negotiation Service.
Challenge Annual Price Increases
Many SAP customers accept annual price escalations as non-negotiable. They are not. Push back every year, formally, in writing, before the renewal date. Over a five-year period, the difference between a 2% and an 8% annual increase on a $4 million base is $1.3 million.
Download the SAP Contract Negotiation Playbook
Third-Party Support: A Strategic Alternative
Third-party SAP support has matured significantly and now represents a credible, proven alternative for organisations seeking to dramatically reduce ECC maintenance costs. Leading providers such as Rimini Street and Spinnaker Support typically charge approximately 50% of SAP's maintenance fee, delivering immediate annual savings while offering service levels that often exceed SAP's own support in responsiveness and scope.
Extended System Life with No Artificial End Date
Unlike SAP's 2027 deadline, third-party support providers commit to supporting the current ECC system for 15+ years from the date of engagement. There is no forced migration timeline, no end-of-support cliff, and no escalating "extended maintenance" premium. You decide when to move, based on business readiness, not vendor pressure.
Custom Code and Interface Support Is Included
SAP's standard support explicitly excludes assistance with custom ABAP code, bespoke interfaces, and third-party integrations. Third-party providers typically include custom code support covering ABAP programmes, user exits, enhancements, and custom reports. For heavily customised ECC environments, this alone can justify the transition: broader support scope at half the cost.
Tax, Legal, and Regulatory Updates Are Delivered Independently
Reputable third-party providers address tax and regulatory updates through their own in-house development teams, which produce and deliver these updates for all supported SAP versions. The updates are delivered as ready-to-apply packages, often with implementation guidance tailored to the customer's specific configuration.
Comparison: SAP Enterprise Support vs Third-Party Support
| Dimension | SAP Enterprise Support | Third-Party Support |
|---|---|---|
| Annual fees | ~22% of licence value, rising annually | ~50% of SAP fee (typically fixed) |
| Support timeline | 2027 mainstream; 2030 extended (+2%) | Indefinite, 15+ years |
| Patches / updates | Full patches, Enhancement Packages, security fixes | Critical bug fixes, tax/regulatory updates, security advisories |
| Custom code | Not covered | Fully covered (ABAP, interfaces, custom reports) |
| Annual escalation | 3 to 8% recently trending higher | Typically 0% or capped at 2 to 3% |
| Migration incentives | Credits and conversion discounts available | No migration credits; cumulative savings fund migration |
Evaluate third-party support even if you do not intend to switch. Request proposals from at least two providers — Rimini Street and Spinnaker Support are the market leaders — to obtain detailed scoping and pricing. Having a credible third-party proposal strengthens your negotiation position with SAP immeasurably, regardless of outcome.
Cost Modelling: Quantifying the Savings Opportunity
The following illustrative model uses a mid-to-large enterprise with $5 million in annual SAP ECC maintenance, comparing four strategic paths over five years from 2025 to 2030.
| Scenario | Year 1 | Year 5 | Five-Year Total | Saving vs Baseline |
|---|---|---|---|---|
| A: Status quo (5% annual increase) | $5.00M | $6.08M | $27.6M | Baseline |
| B: Negotiate 0% increase | $5.00M | $5.00M | $25.0M | $2.6M (9%) |
| C: Shelfware removal + fixed pricing | $3.75M | $3.75M | $18.8M | $8.8M (32%) |
| D: Third-party + shelfware removal | $1.88M | $1.88M | $9.4M | $18.2M (66%) |
The difference between Scenario A (passive renewal) and Scenario D (full optimisation) is $18.2 million over five years. Even the moderate Scenario C delivers $8.8 million in savings with minimal operational change. Capital that can be redirected to S/4HANA migration, cloud modernisation, or other strategic IT investments.
Key Risks and How to Mitigate Them
Loss of Access to SAP Patches and Enhancement Packages
Once you leave SAP Enterprise Support, you no longer receive SAP-delivered patches, security notes, or Enhancement Packages. For organisations running stable ECC deployments with no plans to implement new SAP functionality, this is often acceptable. Third-party providers deliver critical bug fixes and security advisories through their own engineering teams. However, if the ECC system is still undergoing active development or requires new SAP features, remaining on SAP support for those modules is advisable.
Future S/4HANA Migration Implications
SAP offers migration credits and conversion discounts to customers who remain on SAP Enterprise Support. Customers who leave SAP support may lose access to these incentives. However, the financial analysis often reveals that the cumulative savings from third-party support more than offset the lost migration credits. If the S/4HANA migration is three or more years away, the savings generated in the interim can directly fund the migration, often with money to spare.
SAP Audit Exposure
SAP retains the right to audit licence compliance regardless of whether you are on SAP support. The mitigation is straightforward: ensure licence compliance is watertight before making any changes. Conduct an internal licence reconciliation to verify that deployed user counts, digital access usage, and engine metrics align with contractual entitlements. A clean compliance position eliminates SAP's most potent leverage. See also: SAP Licence Management Services.
Reinstatement Costs
If you leave SAP support and later wish to return, SAP charges a reinstatement fee, typically the full back-maintenance for all years during which support was not paid, plus a penalty premium. The financial model should include a reinstatement scenario for risk quantification.
Enterprise Case Examples
Global Manufacturer: $8M Saved Through Licence Optimisation and Third-Party Maintenance
A US-based manufacturing company with a $6.5 million annual SAP maintenance bill across ECC 6.0, BW, and BusinessObjects. Redress Compliance conducted a full licence usage audit, identified 22% shelfware (primarily unused BusinessObjects and over-provisioned Professional User licences), and managed the transition of stable ECC modules to third-party support while retaining SAP Enterprise Support for BW which was still under active development. Annual SAP maintenance was reduced from $6.5 million to $3.2 million, saving $8 million over the first three years with zero operational disruption.
European Retail Chain: Avoids €10M Penalty and Cuts Renewal Costs by 20%
A large European retail chain faced both a SAP audit claim and an upcoming ECC maintenance renewal. SAP's audit findings alleged significant under-licensing of digital access (indirect use), creating a potential penalty of €10 million+ that was being linked to the renewal conversation. Redress Compliance separated the audit defence from the renewal negotiation, challenged SAP's digital access calculation methodology, and negotiated a RISE with SAP renewal package that addressed both the compliance position and the ongoing maintenance costs. The audit penalty was eliminated through technical rebuttal, and renewal costs were reduced by 20%. Read full case study →
Your 8-Step Action Plan
Assemble a Cross-Functional Task Force
Form a team spanning IT, procurement, finance, and legal to drive SAP maintenance cost reduction. Assign clear ownership: one person accountable for licence data, one for vendor negotiation, one for third-party evaluation.
Baseline Your Current SAP Spend
Document every SAP licence, module, and associated maintenance charge. Calculate total ECC maintenance spend, identify the effective maintenance rate, and flag every licence with zero or minimal usage.
Identify and Quantify Shelfware
Using LAW and USMM data and stakeholder interviews, identify every unused or under-utilised SAP licence. Quantify the annual maintenance cost attributable to each. Prioritise the largest cost items for immediate termination or renegotiation.
Obtain Third-Party Support Proposals
Request scoping and pricing from at least two independent support providers. Compare their service scope, SLA terms, and pricing against SAP Enterprise Support. Even if you do not switch, having a credible third-party proposal strengthens your negotiation position with SAP immeasurably.
Model Multiple Scenarios
Build three-year and five-year cost models covering: status quo, negotiated renewal, shelfware elimination, partial third-party transition, and full third-party transition. Include SAP's annual escalation assumptions and reinstatement costs.
Negotiate with SAP from a Position of Strength
Approach SAP with data: your shelfware analysis, your third-party proposals, and your scenario models. Make clear that you are evaluating alternatives and that the renewal terms must reflect the value SAP delivers, not simply continue historical pricing.
Execute and Document Every Change
Whether you negotiate a better SAP deal, terminate shelfware, or transition to third-party support, execute meticulously. Submit termination notices within contractual windows, obtain written confirmation of all concessions, and verify that invoices reflect agreed changes.
Establish Ongoing Governance
Implement quarterly SAP licence and support reviews to prevent shelfware re-accumulation, track escalation rates, and maintain compliance readiness. Build a renewal calendar with 90-day advance alerts. SAP cost optimisation is not a one-time project — it is a permanent organisational capability.
SAP Licensing Intelligence — Delivered Monthly
Join CIOs and IT procurement leaders receiving our monthly advisory on SAP ECC maintenance strategy, RISE negotiations, and cost optimisation tactics.
Facing an SAP ECC Renewal Before 2027?
Related SAP Articles
European Retail Chain Avoids €10M Penalty and Cuts RISE Renewal Costs by 20%
Audit defence separated from renewal negotiation. Penalty eliminated. Renewal restructured on client's terms.
Read Case Study →SAP Licensing Knowledge Hub
55+ expert guides covering Named User licensing, Digital Access, RISE, S/4HANA, audits, and negotiation strategy.
Explore Hub →SAP Contract Negotiation Service
Independent SAP contract, RISE, and renewal negotiation with benchmarking intelligence. Fixed-fee, no vendor affiliations.
Learn More →