SAP maintenance is charged at 22 percent of the net license value every year, so a $40M perpetual estate carries roughly $8.8M in annual support before the contractual uplift is applied. Unlike a license fee, maintenance never stops. It compounds with annual increases and it is owed on every license you hold, including the ones nobody uses. That makes maintenance the most reliable cost-reduction target in an SAP estate, because the levers do not require SAP's permission and several can be executed unilaterally. This guide sets out the five that work.
The reason maintenance is overpaid is structural. Perpetual licenses were bought in waves over fifteen years, business needs changed, modules were abandoned, but the support bill was never re-based. SAP has no incentive to remind a customer that they are paying 22 percent annually on a module switched off in 2019. Finding and retiring that spend is the buyer's job, and it is worth a great deal.
The five maintenance levers
Five distinct levers reduce an SAP support bill, and they differ sharply in difficulty, savings, and risk. The table ranks them so the high-return, low-risk moves are addressed first.
| Lever | Typical saving | Difficulty | Needs SAP agreement |
|---|---|---|---|
| Retire shelfware before renewal | 10 to 25 percent | Medium | Partial |
| Cap or remove annual uplift | 3 to 7 percent per year | Medium | Yes |
| Convert to S/4HANA subscription | Re-bases support entirely | High | Yes |
| Third-party support | 50 to 60 percent | Medium | No |
| Re-tier from Enterprise to Standard | Up to a third of support delta | Low | Yes |
The sequence matters. Retiring shelfware before a renewal locks the saving into the new baseline, while doing it after renewal leaves you paying for another full term. The mechanics of how renewal timing controls every other lever are covered in our SAP renewal strategy guide, and the cross-vendor view of the same problem is in reducing software maintenance fees.
Shelfware retirement
Shelfware is license you own, pay maintenance on, and do not use, and in a mature SAP estate it commonly runs at 15 to 30 percent of the perpetual portfolio. Retiring it is the cleanest saving because it removes a real cost for capability nobody wants. The obstacle is SAP's bundling rules, which often prevent dropping a single product line without affecting the support discount on the rest.
The workable path is to identify unused licenses through an internal measurement, confirm they are genuinely abandoned and not seasonally dormant, then negotiate their removal at a contract renewal or conversion event when the whole agreement is open. Trying to drop them mid-term usually triggers a repricing clause that erases the saving. The measurement that finds shelfware is the same USMM and LAW process described in our SAP license audit guide.
The repricing trap: Many SAP agreements contain a clause that recalculates the support discount on remaining licenses if any are removed, so dropping shelfware mid-term can raise the unit support cost on everything else and wipe out the saving. Shelfware retirement belongs at a renewal or S/4HANA conversion, when the full contract is reopened and the discount structure can be reset together.
Third-party support
Third-party maintenance providers such as Rimini Street and Spinnaker Support service SAP systems for roughly half of SAP's fee, typically a 50 to 60 percent reduction. The trade is real. You keep your perpetual licenses and get support for tax, legal, and break-fix issues, but you forgo new SAP releases, enhancement packages, and direct access to SAP's patch stream. For a stable ECC estate that the business does not intend to upgrade, the economics are compelling.
The decision turns on roadmap. If you are heading to S/4HANA inside three years, the disruption of leaving and re-joining SAP support usually outweighs the saving. If you intend to run ECC to the 2027 mainstream maintenance horizon and beyond on extended terms, third-party support can fund much of the eventual migration. The 2027 timeline that frames this choice is covered in our SAP ECC 2027 end-of-life strategy guide.
Conversion and re-tiering
Converting perpetual licenses to an S/4HANA subscription re-bases support entirely, because the new subscription folds maintenance into a single recurring fee rather than charging 22 percent on legacy net value. Whether this saves money depends on the conversion credits applied to the deal, which can offset a large part of the new subscription. Those credits are the subject of our S/4HANA conversion credits guide, and the full RISE economics sit on the SAP RISE advisory page.
Re-tiering is the quiet lever. SAP Enterprise Support costs the same headline 22 percent as Standard Support but bundles services many customers never use. Where the additional Enterprise services are not consumed, moving to Standard Support reduces the effective rate. This is a negotiation, not a unilateral move, and SAP resists it, but for customers who run their own support operation it is worth pursuing at renewal.
Why maintenance compounds against you
The reason maintenance deserves its own program is the mathematics of compounding. A support line that rises 4 percent a year does not stay flat in real terms; it grows relentlessly while the underlying licenses age and lose relevance. Over a ten-year horizon, the cumulative effect is that a buyer can pay more in support than the original licenses cost, for software that has not changed. The table shows how a $5M annual support line behaves under a typical uplift.
| Year | Support at 4% uplift | Cumulative paid |
|---|---|---|
| Year 1 | $5,000,000 | $5,000,000 |
| Year 3 | $5,408,000 | $15,608,000 |
| Year 5 | $5,849,000 | $27,000,000 |
| Year 10 | $7,116,000 | $60,000,000 |
Sixty million dollars over a decade for a static perpetual estate is the real cost of accepting the uplift without challenge. The single most valuable contract term a buyer can win is a multi-year cap or freeze on the uplift, because it bends the entire curve down. Securing it is a renewal-timing exercise, covered in our SAP renewal strategy guide, and it belongs alongside the cross-vendor view in reducing software maintenance fees.
Enterprise Support versus Standard Support
SAP sells two support tiers, and the difference between them is services, not the headline rate. Enterprise Support bundles mission-critical response times, an engagement framework, and proactive services such as quality checks, while Standard Support provides the core break-fix and update entitlement. Many customers pay the Enterprise premium and consume only the Standard substance, which makes the tier choice a genuine lever for organizations that run their own mature support operation.
| Tier | Includes | Best fit |
|---|---|---|
| Enterprise Support | Faster SLAs, engagement framework, proactive checks | Lean internal teams, mission-critical estates |
| Standard Support | Break-fix, legal and tax updates, patches | Mature internal support, stable estates |
| Third-party support | Break-fix and updates from a non-SAP provider | Stable ECC, no near-term upgrade |
The re-tier decision is not automatic. Enterprise Support earns its premium where internal teams are thin and downtime is costly. Where the organization already operates a strong run function, the proactive Enterprise services duplicate internal capability, and moving to Standard reclaims the premium. SAP resists the downgrade, so it is a negotiation best run at renewal with the rest of the support agenda.
Build the third-party support business case on the roadmap, not the rate: The 50 to 60 percent saving from third-party support is real, but the decision should turn on whether you intend to upgrade. For a stable ECC estate that will run to and beyond the 2027 maintenance horizon, third-party support can fund the eventual S/4HANA migration. For an estate converting inside three years, the cost of leaving and re-joining SAP support usually outweighs the saving. The 2027 timeline is in our SAP ECC 2027 end-of-life strategy guide.
Maintenance on engines and indirect licenses
Maintenance is owed on every license type, not only named users, and the engine and indirect portions of the estate are frequently overlooked in a reduction program. An engine license that was bought for a peak workload years ago still carries 22 percent annual support even if current consumption is a fraction of the licensed capacity. Re-sizing engine licenses to actual consumption at renewal removes maintenance on capacity that will never be used, and the consumption data comes from the same measurement described in our SAP license audit guide.
Indirect and digital access licenses carry maintenance too, and a buyer who over-bought document capacity in a panic settlement is paying support on that surplus every year. Right-sizing the digital access entitlement to genuine document volume, covered in our SAP digital access guide, removes both the license surplus and the recurring maintenance on it. A complete maintenance program looks at the whole estate, not just the named user line.
Partial cancellation and license drops
The cleanest maintenance saving is to stop paying support on licenses you will never use again, but SAP contracts make this deliberately hard. Most agreements prohibit dropping a subset of licenses without consequence, and many contain an all-or-nothing clause that forces a customer to either keep support on the entire bundle or surrender the whole product line. Understanding exactly what your contract permits is the first step, because the answer varies by agreement and by what was negotiated originally.
Where partial cancellation is permitted, it must clear the repricing arithmetic to be worthwhile: the support saved on the dropped licenses has to exceed any loss of volume discount on what remains. Where it is prohibited, the drop becomes a renewal or conversion item, folded into the larger negotiation when the whole agreement is open. Either way, identifying the unused licenses through measurement, as described in our SAP license audit guide, is the prerequisite. The cross-vendor framework for these decisions is in our reducing software maintenance fees guide.
A further lever is the conversion of unused on-premise licenses into cloud credit at an S/4HANA move, which can rescue value from shelfware that would otherwise simply be surrendered. The credit mechanics are in our S/4HANA conversion credits guide, and the full RISE economics are on the SAP RISE advisory page.
Benchmarking the support rate
The 22 percent headline support rate is widely treated as fixed, but the effective rate a buyer pays varies once discounts, uplifts, and bundling are accounted for, and benchmarking it against the market is a legitimate negotiation step. Large strategic customers sometimes secure capped or reduced effective rates that smaller customers never see, and a buyer who knows where their effective rate sits relative to comparable estates can argue from evidence rather than hope. The benchmark data sits alongside the discount evidence in our SAP discount benchmarks guide.
Benchmarking also exposes the compounding uplift as a negotiable item rather than a fact of nature. When a buyer can show that comparable customers have secured multi-year uplift caps, the request stops being unusual and becomes a market-standard term SAP is harder to refuse. The renewal event where this is won is covered in our SAP renewal strategy guide, and the buyer-side advisory that runs the benchmark is the SAP optimization practice.
Building the maintenance reduction case
The strongest program runs the levers in combination and times them to a single contract event. Baseline the estate to find shelfware, model the third-party versus SAP-support roadmap decision, quantify the conversion credit offset, and bring all of it to one renewal so the discount structure is reset once rather than nibbled at. Done this way, a maintenance reduction program reaches the upper end of the 20 to 60 percent range rather than the lower. For the full picture, see the complete SAP licensing guide, the SAP optimization practice, and our software licensing advisory service.