Retiring Old SAP Components During S/4HANA

Every S/4HANA migration retires a slice of the prior SAP estate. ECC core modules, business suite add ons, industry solutions, and named user licenses all sit on the cut list at various stages of the program.

The buyer side risk is twofold. SAP wants the retired licenses to disappear quietly. The customer wants either a credit or a maintenance reduction. Without contract discipline, neither happens.

Read this alongside the SAP knowledge hub, the SAP services page, the S/4HANA migration page, and the Vendor Shield subscription.

Key Takeaways

What an SAP CIO and procurement leader need to know in 90 seconds

Most S/4HANA programmes carry shelf. Thirty to fifty percent of legacy SAP licenses retire during cutover.
SAP wants the shelf to disappear. Without credit, the customer keeps paying maintenance on retired components.
The credit conversation is contractual. Shelf credit is negotiated at the S/4HANA contract signing, not at cutover.
Maintenance reduction is the second lever. Drop the maintenance line on retired components inside the same year.
Named user retirement matters. Old named user types convert to FUE at controlled rates.
Industry solutions need attention. Retail, utilities, banking, public sector add ons retire on different paths.
Document the retired list. A signed retirement schedule protects the customer at the next audit.

Five legacy SAP categories to retire

Different SAP component classes retire on different commercial paths. The buyer side discipline starts with categorizing the legacy estate.

Category list

ECC core modules. FI, CO, MM, SD, PP. Retire as S/4HANA Core lands.
Business Suite add ons. CRM, SRM, SCM, PLM. Retire on staggered timelines.
Industry solutions. IS Retail, IS Utilities, IS Oil and Gas, IS Banking. Different retirement paths each.
Named user licenses. Professional, Limited Professional, Employee Self Service.
Database and tooling. SAP MaxDB, Sybase ASE, Solution Manager add ons.

Retirement path per category

Category	Replaced by	Credit available	Maintenance drop
ECC core	S/4HANA Core	Yes, partial	Yes, at cutover
SAP CRM	SAP CX or third party	Limited	Yes, at cutover
SAP SRM	SAP Ariba or third party	Limited	Yes, at cutover
SAP PLM	Stays in S/4HANA	None	None
IS Retail	S/4HANA Retail	Yes, partial	Yes, at cutover
Named user	FUE	Conversion rate	Reduces with FUE move
MaxDB	HANA	Yes	Yes

Shelf license credit

SAP runs a structured credit program for legacy components that retire into S/4HANA. The credit name and rules change every two to three years.

Three credit rules to negotiate

Credit cap. SAP typically caps shelf credit at thirty to fifty percent of legacy book value.
Credit application window. Credit must apply to the S/4HANA purchase, not to a future spend.
Credit recognition timing. Credit lands on the contract date, not on the cutover date.

Typical credit ranges

Legacy component class	Book value	Credit range	Effective net
ECC core modules	EUR 2M	40 to 60 percent	EUR 800K to 1.2M
Business Suite CRM	EUR 1.5M	20 to 40 percent	EUR 300K to 600K
Industry solution	EUR 1M	30 to 50 percent	EUR 300K to 500K
Named user pool	EUR 5M	FUE conversion	Varies by mix

Shelf credit is negotiated once, at contract signature

The single most common buyer side mistake is to leave the shelf credit conversation for after the S/4HANA contract is signed. After signature, SAP carries no commercial incentive to credit retired components. The leverage window closes on the day the S/4HANA order form is signed.

Maintenance reduction trap

SAP support runs on the deployed estate plus the unused shelf. Customers who retire components without dropping the maintenance line continue paying twenty two percent of book value on shelved licenses.

Three maintenance traps

The annual escalator continues. Maintenance on retired components rises with the contract escalator each year.
The base is sticky. SAP defends the maintenance base as a contractual minimum.
The drop window is narrow. Maintenance drops require notice on the contract anniversary.

Maintenance drop process

Identify retired components. Match to the S/4HANA cutover schedule.
Calculate the maintenance line. Twenty two percent of book value per component.
Issue formal notice. Six months before the contract anniversary in writing.
Reconcile with SAP. SAP confirms the retired list and adjusts the renewal invoice.
Track the savings. Year on year support spend reduction reported to the CFO.

Contract clauses that protect the customer

The S/4HANA contract is the only place the retirement schedule has legal force. Customers who land the right clauses at signature carry the leverage through cutover.

Five clauses to negotiate

Shelf retirement schedule. Named legacy components with target retirement dates.
Shelf credit recognition. Credit amount and application against the S/4HANA purchase.
Maintenance drop right. Contractual right to drop maintenance on retired components.
Named user conversion rate. Old user types to FUE at a defined rate.
Audit protection during cutover. No license audits during the S/4HANA cutover window.

The single most expensive S/4HANA migration mistake is leaving the shelf credit and the maintenance drop for after signature. The leverage window closes on the contract date. Negotiate retirement at the same table as the S/4HANA purchase.

What to do next

The seven step checklist below sets up any S/4HANA contract that involves retired SAP components.

Inventory the legacy SAP estate. Modules, add ons, industry solutions, named users.
Map the cutover schedule. Which components retire in which release wave.
Calculate the shelf credit ask. Book value times negotiated credit percentage.
Quantify the maintenance line. Twenty two percent of retired book value per year.
Negotiate the retirement schedule into the S/4HANA contract. Five core clauses listed above.
Issue maintenance drop notices on time. Six month anniversary cadence.
Track the SAP support spend reduction. Reported to the CFO each year.

Frequently asked questions

Can shelf credit move from S/4HANA to other SAP products?

Shelf credit is usually scoped to the S/4HANA purchase by default. SAP will offer wider application across SAP Cloud, BTP, or Signavio at the customer request, but the credit cap drops on wider application. Most customers concentrate the credit on the S/4HANA Core SKU to maximize the effective discount.

What happens to named users on the FUE move?

Named user licenses convert to Full Use Equivalents at a defined conversion rate per user type. SAP Professional users land at the highest FUE consumption, Limited Professional at a middle band, and ESS or developer types at a fractional rate. The buyer side play is to map the actual usage pattern against the FUE band before signing the conversion clause.

Does maintenance drop apply to all SAP components?

Maintenance drop applies to components that retire from production use under the SAP support model. Components that stay in production at reduced capacity continue carrying maintenance. The contractual drop right needs explicit language naming the retired component list. Without that language, SAP defends the maintenance base as a contractual minimum.

How do industry solutions retire into S/4HANA?

SAP industry solutions retire on different paths depending on the S/4HANA target. IS Retail moves cleanly into S/4HANA Retail. IS Utilities and IS Oil and Gas often need partner extensions. IS Banking carries the most fragmented retirement path with several customer specific carveouts. Customers should map the industry solution to the S/4HANA target before signing.

Is there an audit protection clause during cutover?

Yes, SAP will agree to an audit protection clause covering the cutover window in most enterprise S/4HANA contracts. The clause typically runs eighteen to thirty months from cutover start and protects the customer against a license audit of components in flight. The clause must be drafted into the order form at signature.

How does Redress engage on S/4HANA migrations?

Redress runs S/4HANA contract advisory inside the Vendor Shield subscription and the Renewal Program. Engagements include shelf credit modeling, maintenance drop planning, named user to FUE conversion review, and side letter drafting. Every engagement is led by a former SAP commercial executive now on the buyer side.

How Redress engages on SAP migrations

Redress runs SAP advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every SAP engagement is led by a former SAP commercial executive on the buyer side.

Read the related benchmarking, about us, locations, and contact pages.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

Retiring old SAP components during S/4HANA migration. The buyer side playbook.