A twenty thousand employee logistics firm stopped renewing SAP support by habit. License optimization shrank the maintenance base, and third party maintenance took over the stable ECC core. Eight million dollars stayed in the business.
A North American logistics firm with roughly twenty thousand employees paid SAP maintenance on a license base that had grown for fifteen years and shrunk in usage for five. The ECC core was stable and going nowhere soon.
License optimization plus a third party maintenance move on the stable core saved eight million dollars across the engagement horizon.
The firm saved eight million dollars by shrinking the maintenance base through license optimization, then moving the stable ECC core to third party maintenance at roughly half the SAP Enterprise Support rate.
The trigger was a renewal notice that assumed the full historical base would renew as always. Finance asked what the maintenance actually bought on systems frozen by design.
The estate split into a stable ECC core with no planned upgrades, satellite systems with active roadmaps, and a future S/4HANA decision deliberately not yet made.
The license measurement showed named users without humans attached, engine metrics sized for a bigger business, and shelfware from projects that never shipped. All of it billed maintenance every year.
Maintenance percentage points are negotiated rarely and grudgingly. The base is arithmetic: every license removed cuts its maintenance forever. The base moved first, then the model.
Two levers produced the saving: a smaller maintenance base after optimization, and third party maintenance on the stable core at roughly half the SAP rate, with SAP support retained where the roadmap justified it.
Support models by system segment
| Segment | Roadmap | Support model | Cost effect |
|---|---|---|---|
| Stable ECC core | Frozen, run for years | Third party maintenance | Near 50 percent reduction |
| Active satellites | Enhancements planned | SAP support retained | Smaller base after cleanup |
| Shelfware | None | Removed from renewal | Maintenance eliminated |
| S/4HANA decision | Deferred by choice | License position preserved | Option kept open |
Third party maintenance delivers break fix, regulatory updates, and customization support, but none of the version upgrades listed in the SAP support offerings. For systems with no upgrade path planned, that trade is the point, not the problem. The RISE with SAP path was evaluated and consciously deferred.
The closing sequence was license measurement, base cleanup, system segmentation by roadmap, then the support model decision per segment, all documented before the renewal deadline.
The standard SAP account team position is that leaving Enterprise Support forfeits the future, because rejoining costs back maintenance and the S/4HANA path closes. We disagree. In roughly 20 to 30 SAP support engagements we advised across 2024 and 2025, the firms that segmented their estates kept every strategic option open while cutting support cost by 45 to 55 percent on frozen systems, and the license positions preserved in the exercise priced the eventual S/4HANA conversation better, not worse. The buyer side move is to let each system earn its support model from its own roadmap, document the license baseline, and treat back maintenance math as a negotiation input rather than a deterrent.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The maintenance invoice was a history lesson. We paid for the business we used to be, on systems we had ordered not to change.
More SAP cost analysis lives in the SAP knowledge hub and the related SAP BTP rationalization case study.
White Paper · SAP
SAP support and maintenance. The buyer side negotiation
SAP support runs 22 percent of license value a year. Read it free.
The saving combined two levers: license optimization that shrank the maintenance base, and third party maintenance on the stable ECC core at roughly half the SAP Enterprise Support rate, while SAP support stayed on systems with active roadmaps.
For stable systems with no planned upgrades it is a mature, widely used model covering break fix, regulatory updates, and customizations. What it does not provide is new SAP versions, which frozen systems do not consume anyway.
No, if license positions are preserved. The firm kept its entitlements documented and intact, so a future S/4HANA or RISE move remains a commercial negotiation, with back maintenance treated as a negotiable input rather than a lock.
In our 2024 to 2025 engagements, 10 to 25 percent of the maintenance base on mature ECC estates traced to licenses with no assigned users or measurable usage. That share bills every year until the base is cleaned.
The base first, always. Rates move by points after hard negotiation; the base moves by removing licenses that should never have renewed. Every license removed cuts its maintenance permanently.
Half our maintenance bought upgrades we had decided never to install. Naming that out loud was the whole business case.
Confidential consultation. No follow up sales call unless you ask for one.
SAP support benchmarks, RISE pricing signals, license optimization patterns, and the buyer side moves across the SAP estate.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
