Most enterprise SAP portfolios accumulate over a decade or more as a sequence of point purchases. A business case in 2014 added an engine for plant maintenance. A regional rollout in 2016 added a country pack. A 2018 deal added an analytics edition. Each acquisition was reasonable in isolation. The combined portfolio is rarely reviewed against the contemporary bundle alternatives, and the dead-weight share of the portfolio — entitlements paid for but no longer used — quietly accumulates. Converting the legacy portfolio into a current SAP bundle (RISE, GROW, or a structured combination) is the single largest optimization most estates have available, and the conversion math is generally more favourable than the SAP team’s opening proposal suggests.
What the dead weight looks like
Dead weight in a legacy SAP portfolio shows up as engine entitlements with no corresponding usage data, country packs for jurisdictions the buyer has exited, Named-User packages for headcount the business no longer carries, BusinessObjects editions whose user populations have migrated to other analytics tools, and add-on products whose business sponsor left the company three reorganisations ago. Each item carried support and maintenance through every contract renewal, frequently for years past its operational utility. The cumulative dead-weight share in a portfolio that has not been reviewed in five years typically sits between fifteen and thirty per cent.
The first piece of work in any conversion conversation is the dead-weight inventory. The inventory pulls every contractual entitlement, every active engine, every Named-User package, and every add-on; cross-references each against actual usage data (transaction history, engine metric data, named-user activity); and produces a per-entitlement classification: in use, partially in use, or dormant. The dormant items are the conversion baseline reduction. See the licence compliance assessment service brief for the inventory methodology.
The conversion arithmetic
SAP’s standard conversion offer prices the current bundle (typically RISE or GROW) against the existing contracted licence position. The conversion ratio is documented in the contract addenda and is generally favourable for buyers with substantial Named-User counts and meaningful Digital Access volume. The arithmetic is straightforward in form but consequential in detail: the buyer’s contractual licence position converts to a Full Use Equivalent (FUE) value using the published ratio, and the FUE value drives the bundle pricing.
Where the buyer-side opportunity sits is in the input to the conversion: the contractual licence position itself. If the contractual position has been reduced before the conversion (through dead-weight retirement, through Named-User reclassification, through engine right-sizing), the FUE conversion baseline is correspondingly lower. If the contractual position is taken as-is, the FUE baseline is constructed from the dead weight. The pre-conversion optimization work is therefore not an alternative to the conversion — it is the input that determines what the conversion produces.
The four pre-conversion moves
Four optimization moves should precede any bundle conversion conversation. First, dead-weight retirement: formally surrender unused entitlements via SAP’s shelfware programme or via contract amendment. Second, Named-User reclassification using transaction-history evidence to move users from Professional to Limited Professional or Employee where the actual usage supports it (see the reclassification playbook). Third, engine right-sizing on metric-based engines where the contracted metric exceeds actual consumption. Fourth, indirect-access mapping to support the Digital Access component of the conversion (see the indirect users in USMM piece).
The buyer who arrives at the conversion conversation with the optimized baseline negotiates from the optimized position. The buyer who arrives with the as-is portfolio negotiates from the as-is portfolio. The difference is a year of background work and frequently a seven-figure swing on the conversion outcome.
The shelfware programme
SAP’s shelfware retirement programme allows buyers to surrender unused entitlements in exchange for a reduction in the maintenance base. The programme is administered case by case rather than as a published policy, and the terms vary. The standard pattern is a reduction in the support and maintenance bill corresponding to the surrendered entitlement, with the underlying licence struck from the contract. The programme is more responsive when the surrender is paired with new bundle commitment than when it is requested in isolation; this is one of the reasons to align the dead-weight retirement with the conversion conversation rather than to pursue it independently.
The engine question
Engine metrics — the metric-based components of the SAP portfolio such as Quality, Process Mining, Master Data Governance, and the various industry solutions — meter on factors other than user count: order line items, master data records, transaction volumes. The metered baseline at last contract negotiation may no longer reflect the actual consumption, in either direction. Estates that have grown their use of the engine carry latent compliance exposure; estates that have reduced their use carry latent overpayment. The conversion conversation is the moment to true up both directions, and the SAP team is generally willing to entertain step-down where the optimization evidence is presented. See the engine consumption review piece for the methodology.
Where S/4HANA changes the picture
The S/4HANA migration is typically the trigger event for a bundle conversion conversation; the two events are frequently aligned by SAP’s account team. The alignment is convenient but creates a sequencing trap: the migration deadline pressures the conversion conversation, and the conversion conversation accelerates the bundle commitment. The buyer-side discipline is to begin the pre-conversion optimization work twelve to eighteen months before the migration milestone, so that the optimized baseline is available when the conversion conversation opens and the buyer is not constructing the position under deadline pressure. See the RISE conversion economics piece for the migration-conversion sequencing.
What the research supports
The licence optimization handbook sets out the full pre-conversion sequence with the inventory templates, the reclassification methodology, and the engine right-sizing approach. The handbook also covers the conversion-negotiation lever set: the FUE ratio negotiation, the maintenance-base treatment, the Digital Access component, the BTP credit allocation, and the term-and-exit provisions. See also the SAP RISE topic page for the conversion product context and the manufacturer bundle conversion case file for an end-to-end example.
The negotiation sequence
The recommended negotiation sequence runs in four stages. Stage one: assemble the optimized baseline through the four pre-conversion moves. Stage two: model the conversion outcomes at multiple FUE ratios and bundle structures, so that the negotiation has a defended buyer-side target. Stage three: open the conversion conversation with SAP, presenting the optimized baseline and the modelled target. Stage four: structure the contract with the lever set defined — right to step down, BTP credit treatment, Digital Access provisions, exit terms. The four stages take six to twelve months for a mid-market estate and twelve to twenty-four months for a large enterprise. See the contract negotiation service brief for the engagement model.
What goes wrong
The recurring failure mode in bundle conversions is treating them as a procurement event rather than as a sustained optimization programme. The conversion conversation runs in three months under deadline pressure, the optimized baseline is constructed from whatever is available rather than from a full inventory, and the conversion outcome reflects the rushed baseline rather than the optimized one. The mitigation is calendar discipline: begin the optimization work twelve to eighteen months before the conversion conversation opens, so the optimized baseline is the starting point rather than a half-finished project.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
Pull the contractual licence position from the last renewal addendum. Pair it with the most recent USMM submission. The gaps between contracted and actual are the conversion-savings opportunity. The licence optimization service brief covers the full sequence.