SAP Maintenance Cost Reduction:
Breaking Free from the 22% Trap

SAP maintenance fees represent one of the largest and most persistent cost items in enterprise IT budgets. For organisations running traditional SAP ECC (ERP Central Component) or Business Suite, SAP Enterprise Support costs 22% of net licence value annually — a fee that has remained essentially unchanged for over a decade despite repeated pushback from large enterprise customers. For a company with $5M in SAP licence value, that means $1.1M per year in maintenance before any software is actually used. This guide is part of our SAP license negotiation series and provides a complete framework for reducing this cost through negotiation, third-party support, or hybrid approaches.

The maintenance cost conversation is one of the most sensitive in any SAP relationship. SAP actively discourages customers from exploring alternatives and uses support continuity as a barrier to negotiation. But the market for SAP support optimisation has matured significantly: third-party support vendors now serve thousands of large SAP customers, SAP has introduced some support tier flexibility in response to market pressure, and the link between maintenance payments and the right to access future S/4HANA migration is far more nuanced than SAP typically represents.

The 22% Problem: What You're Actually Paying For

SAP Enterprise Support at 22% is not inherently unreasonable for a software platform that delivers critical business process infrastructure. The problem is the combination of: (1) the base against which 22% is calculated often includes software licences purchased years or decades ago that are no longer in active use; (2) the support services actually consumed by most enterprises represent a fraction of what 22% funds; and (3) the fee increases annually through escalation provisions tied to CPI or fixed percentages, compounding the overpayment over time.

The 22% rate applies to net licence value (NLV) — the total value of SAP licences your organisation holds on record with SAP. This includes licences for modules and products that may be uninstalled, unmaintained, or superseded by cloud replacements. SAP's Licence Audit services can and do identify the full scope of licensed products and apply maintenance accordingly. Organisations that have partially migrated to SAP cloud products (SuccessFactors, Ariba, Concur) often continue paying on-premise maintenance for the ECC versions of those modules even after decommissioning them.

The Perpetual Licence Paradox

SAP perpetual licences are exactly that — perpetual. Once paid for, the licence is yours indefinitely. But the maintenance fee is also effectively perpetual, with no natural sunset unless you negotiate a reduction. This creates a paradox: organisations that have fully amortised their SAP licence investment continue paying a significant recurring fee that is nominally for access to new features and fixes — but in practice, most mature SAP ECC installations have been stable for years with minimal new functionality requirements. The maintenance fee becomes a relationship-maintenance fee rather than a product-maintenance fee.

Calculating Your True Maintenance Overpayment

To assess your maintenance overpayment, start by pulling your SAP Licence Usage Agreement (LUA) and identifying your current NLV basis. Then audit whether the licences in your NLV basis are still active — decommissioned products, retired modules, and superseded cloud replacements should not be in the maintenance basis. Calculate the percentage of your maintenance fee consumed by licences you actively use versus licences that are historical artefacts of past procurement. In our engagements, the average enterprise has 15–25% of their NLV basis in products that are no longer actively deployed.

SAP Enterprise Support: What You Actually Get

SAP Enterprise Support provides several categories of value: access to support notes and patches (bug fixes and security updates), access to new software releases and enhancement packs, SAP's Mission Control Centre for critical issues, access to the SAP Support Portal and knowledge base, and various proactive support services. For organisations actively developing on SAP or making heavy use of enhancement pack content, Enterprise Support delivers genuine value. For organisations in maintenance-mode running stable SAP environments with minimal change, the value equation is less compelling.

Support Utilisation Analysis

Before making any support strategy decisions, conduct a support utilisation analysis. Over the past 24 months, measure: how many SAP Notes your team applied, how many critical OSS messages you raised and the resolution time, which enhancement pack content was deployed, and whether any SAP Mission Control Centre engagements occurred. Organisations that apply fewer than 20 SAP Notes per year, raise fewer than 5 critical support messages, and have not deployed new enhancement pack content in 24 months are paying for support services they are not consuming.

Third-Party Support Options

Third-party SAP support providers — primarily Rimini Street, Spinnaker Support, and a smaller number of regional providers — offer support for SAP ECC and related products at rates of 50–60% below SAP's Enterprise Support pricing. Instead of 22% of NLV, third-party support typically costs 10–14% of NLV, with service levels that match or exceed SAP's standard response time commitments.

What Third-Party Support Provides

Third-party SAP support typically includes: dedicated support engineers (often former SAP employees) familiar with your specific installation, support for the SAP code base you are running — including customisations that SAP's standard support does not cover, tax, legal, and regulatory updates for supported jurisdictions, and response time SLAs that are typically faster than SAP's standard Enterprise Support commitments. What third-party support does not provide: access to new SAP product releases or versions, SAP enhancement pack content, or the right to upgrade to S/4HANA (which requires re-licensing under SAP's current commercial model regardless of support provider).

The S/4HANA Migration Question

SAP's standard narrative is that moving to third-party support forecloses your S/4HANA migration path. This is SAP's commercial position, not a technical reality. Migrating to SAP S/4HANA is a re-licensing event that requires new S/4HANA licence purchases regardless of your current support status. The right to migrate does not depend on having paid Enterprise Support to SAP continuously — SAP will sell you new S/4HANA licences whether or not you have been using third-party support. What third-party support does affect is your access to certain migration tools and services that SAP bundles with Enterprise Support (DMLT, SAP Activate methodology content). These tools can be purchased separately or replaced with third-party equivalents.

Risk Considerations

Third-party support carries real risks that must be evaluated honestly. The primary risk is access to SAP's security patch stream — critical security vulnerabilities discovered in SAP software are addressed through official SAP Notes, which third-party providers cannot access from SAP and must reverse-engineer or address independently. For organisations in highly regulated industries (financial services, healthcare, defence) where security patch compliance is audited, this is a significant consideration. The secondary risk is future SAP support for complex issues that involve interaction between standard SAP code and customisations — SAP's support for these scenarios depends on the customer being on standard support.

The Hybrid Support Model

A growing number of enterprises are adopting hybrid support models that balance the cost savings of third-party support against the risk mitigation of maintaining some SAP support coverage. The most common hybrid approach involves moving most of the SAP estate to third-party support while maintaining SAP Standard Support (not Enterprise Support) on the most business-critical systems or on systems where active development and enhancement pack access are genuinely needed.

SAP does offer a lower-cost support tier — SAP Standard Support at 18% of NLV — that is often overlooked in maintenance cost discussions. While SAP's default position is that Enterprise Support (22%) is required for all large enterprises, many organisations have successfully negotiated downgrade rights to Standard Support for portions of their SAP estate. Standard Support versus Enterprise Support: you lose access to certain proactive support services, Mission Control Centre, and some advanced monitoring tools, but retain patch access, support portal access, and the right to new releases.

Negotiating SAP Support Directly

Even without moving to third-party support, significant maintenance savings are achievable through direct negotiation with SAP. SAP has more flexibility on maintenance pricing than it typically acknowledges, particularly for large customers, long-term relationship commitments, and organisations that can credibly demonstrate a third-party support evaluation.

NLV Basis Reduction

The most straightforward maintenance savings come from reducing the NLV basis on which 22% is calculated. This requires a formal SAP licence audit to identify inactive or unused licence positions, formal requests to SAP to retire licences for decommissioned products, and negotiation of the NLV reduction. SAP will resist NLV reductions aggressively — maintenance revenue is highly predictable and valuable to SAP's financial model. However, with documented evidence of licence inactivity and the explicit alternative of third-party support, NLV reductions of 10–20% are achievable in approximately 40% of the engagements we manage.

Maintenance Fee Caps

Even if the NLV basis is not reducible, negotiating a cap on annual maintenance fee escalation provides long-term savings. Standard SAP Enterprise Support contracts contain escalation provisions of 2–5% annually. Negotiating a flat-fee maintenance arrangement — fixed at current levels for 3–5 years — eliminates escalation risk entirely. This is most achievable when combined with a commitment to S/4HANA migration within the defined period, as SAP values the migration revenue commitment.

Support Credit Packages

As an alternative to fee reductions, SAP sometimes offers "support credit" packages — additional services, implementation support, or cloud service credits in exchange for maintaining or expanding the maintenance commitment. These can represent genuine value if the services are services you would otherwise purchase. They can also be largely valueless if the credits expire unused or apply to services you would never need. Evaluate any support credit package on the basis of its actual usable value, not its notional list value (which SAP will quote at list prices).

Maintenance vs. Migration: The S/4HANA Lever

SAP's long-stated end-of-mainstream-maintenance date for SAP ECC 6.0 has been extended multiple times, most recently to 2030 with extended maintenance to 2033. These extensions reflect SAP's commercial reality: too many customers are not yet ready for S/4HANA migration, and cutting off maintenance would accelerate defections to third-party support or competitive platforms. The extension is good news for organisations seeking to extend the value of their ECC investments, but it also reduces the urgency that SAP uses to drive maintenance negotiations.

If your organisation has a credible S/4HANA migration roadmap, use it as a negotiation lever in maintenance discussions. A commitment to a defined S/4HANA migration timeline — even a broad one — gives SAP a commercial reason to offer concessions on ECC maintenance fees in exchange for securing the future S/4HANA licence and RISE revenue. The key is ensuring any maintenance concessions are contractually locked in and not dependent on the migration proceeding on SAP's preferred timeline or commercial terms. See our guide on SAP S/4HANA migration negotiation for detailed tactics.

Risks of Leaving SAP Support

A balanced maintenance optimisation analysis must acknowledge the genuine risks of third-party support or significant maintenance reduction. These are not hypothetical — they have materialised for organisations that moved too aggressively without adequate risk mitigation.

Security vulnerability coverage is the most significant risk. SAP routinely releases security patches through the SAP Note mechanism. In 2025, SAP issued over 300 security corrections including several rated "Hot News" (the highest severity level). Third-party support providers must reverse-engineer security fixes or provide workarounds, which takes time and may not achieve the same level of remediation as SAP's official patches. For regulated industries with mandatory patching timelines, this gap is a compliance risk.

The second risk is support for complex, customisation-related issues. SAP's standard support covers the base SAP code; third-party providers extend this to cover customisations. But the most complex SAP issues — particularly those arising from interactions between customisations and base SAP code — require deep access to SAP's internal knowledge base and development resources that third-party providers cannot replicate. For organisations with heavily customised SAP environments, the risk of unresolvable issues is higher than for organisations running close to standard.

Decision Framework

The following framework helps organisations assess which maintenance optimisation approach makes most sense given their specific circumstances.

Profile	Recommended Approach	Expected Savings
S/4HANA migration <24 months	Negotiate SAP maintenance discount tied to migration commitment	10–20%
Stable ECC, no migration planned <5 years	Hybrid: third-party for non-critical systems, SAP Standard for critical	30–45%
Stable ECC, heavily customised	Negotiate NLV reduction + escalation cap; third-party for non-critical only	15–30%
Regulated industry (FS, healthcare)	SAP Standard Support (downgrade from Enterprise) + NLV cleanup	10–25%
Mixed landscape (ECC + cloud products)	Remove cloud product licences from NLV basis; negotiate blended rate	15–25%