Migrating to S/4HANA is the single best opportunity to shed years of accumulated SAP shelfware. This guide explains how to identify unused components, execute licence retirement, navigate conversion credit mechanics, and ensure every dollar in your new contract delivers genuine business value.
This guide is part of our SAP S/4HANA Licensing Complete Guide. See also: Mapping Legacy Licences to S/4HANA Roles | Budgeting for S/4HANA Transition | S/4HANA Pricing and Cost Optimisation.
SAP shelfware means licences and modules you have paid for but are not actively using. These idle user licences, unused engines, and never-deployed add-on modules quietly consume budget through annual maintenance fees of approximately 20-22% of the original licence price, every single year, regardless of whether anyone logs in.
The accumulation is gradual and predictable. Organisations over-purchase during initial deployments to accommodate optimistic growth projections. Mergers bring duplicate SAP estates that are never consolidated. Projects are cancelled after licences have been procured. Employees leave but their named user allocations persist. Over a decade of SAP ownership, these small oversights compound into substantial financial exposure.
| Shelfware Category | How It Accumulates | Typical Scale |
|---|---|---|
| Dormant named users | Employees who have left, changed roles, or stopped using SAP but still have assigned licences. Common to find 15-25% of named users with zero logins over a trailing 12-month period | 15-25% of named user base |
| Unused modules and engines | Legacy components purchased as part of bundles or for projects that stalled. SAP CRM, SRM, PLM, APO, or industry solutions never fully implemented or replaced by third-party tools | 2-5 modules per enterprise |
| Redundant legacy systems | Older SAP components superseded by newer S/4HANA capabilities or third-party alternatives but retained on contract "just in case," generating ongoing support costs for outdated functionality | Varies by estate complexity |
| Financial scale | For an enterprise with $10 million in SAP licences, even a 15-20% shelfware ratio means $1.5-2 million of the investment delivers no value, while costing $300-400K per year in wasted maintenance | $300-500K annual waste typical |
Beyond direct costs, shelfware obscures visibility into actual requirements and weakens your negotiating position with SAP. You cannot optimise what you have not measured. Every unused component on your contract inflates your maintenance base and gives SAP a larger number to anchor renewal discussions around. Eliminating shelfware before negotiation changes the dynamics entirely.
The impending end of SAP ECC mainstream support in 2027 forces every SAP customer to confront their licensing estate. This transition is not an automatic carry-over of existing licences. It requires either a product conversion or a contract conversion, both of which present a strategic opportunity to restructure your SAP agreement from the ground up.
| Approach | What It Means | Shelfware Outcome |
|---|---|---|
| Carry everything forward (waste) | Convert all existing licences 1:1 into S/4HANA equivalents without analysis | Perpetuates shelfware, inflates the new contract, and locks in maintenance payments on unused software for another cycle |
| Selective conversion (partial) | Convert core licences and drop obviously unused modules, but without comprehensive usage analysis | Captures easy savings but misses dormant users, under-utilised engines, and redundant add-ons |
| Strategic estate reset (optimal) | Full usage audit, business owner validation, and roadmap alignment before any conversion. Every component justified by current or planned usage | Maximum cost reduction and contractual clarity. No shelfware carried forward |
| Strategic Action | Detail |
|---|---|
| Drop unneeded components | S/4HANA's core includes functionality that previously required separate engines in ECC. Legacy modules like SAP BW Accelerator, classic APO, or industry solutions rendered obsolete by S/4 innovations should be retired rather than carried forward. Each retired component eliminates both licence and maintenance costs |
| Eliminate idle users | Right-size user counts before conversion. Most enterprises discover 15-20% of named users are effectively dormant. Decommissioning 500 dormant users out of 3,000 before converting immediately reduces the new contract's scope and cost |
| Consolidate and simplify | If consolidating a separate SAP CRM instance into S/4HANA's customer management, or replacing SAP HR with SuccessFactors, consolidate the corresponding licences. Overlapping capabilities in the new environment mean overlapping licences are pure waste |
Retiring old components requires a combination of data-driven analysis and stakeholder engagement. The assessment should begin well before you enter S/4HANA contract negotiations. Ideally 6-12 months in advance.
| Assessment Step | Detail | Timing |
|---|---|---|
| Inventory all licences and modules | Create a comprehensive register of every SAP product, engine, and user licence. Include core ERP modules, additional components (HCM, CRM, industry solutions, third-party add-ons sold through SAP), and all user licence types with quantities | T-minus 12 months |
| Assess business relevance | For each component, determine whether it is actively used, planned for S/4HANA, or genuinely obsolete. Challenge assumptions. Modules purchased for cancelled projects or abandoned processes are prime retirement candidates | T-minus 10 months |
| Engage functional owners | Confirm with business and IT owners whether processes supported by each module will continue in S/4HANA. Legacy components like SAP APO, classic SAP HR on ECC, or SAP SRM may be replaced by new S/4HANA modules or third-party systems | T-minus 8 months |
| Analyse usage logs | Use SAP's Licence Administration Workbench (LAW) or SAM tools to examine actual usage patterns. Identify named users with zero activity, engine metrics well below licensed levels, and modules with no transaction volume | T-minus 10 months |
| Quantify financial impact | Calculate the maintenance cost of each identified shelfware component. This creates a compelling business case for retirement and provides specific targets for contract negotiation | T-minus 8 months |
Begin your licence utilisation assessment immediately, regardless of your planned migration date. The earlier you identify shelfware, the more options you have for maximising value during conversion. Delayed assessment compresses negotiation timelines and reduces flexibility.
The conversion path you choose fundamentally determines how effectively you can eliminate shelfware. Each approach offers different levels of flexibility for restructuring your licence estate.
| Dimension | Product Conversion | Contract Conversion |
|---|---|---|
| Mechanism | Swap specific ECC products for S/4HANA equivalents | Negotiate entirely new S/4HANA agreement with credit for legacy licences |
| Contract terms | Existing contract preserved | New contract from scratch |
| Dual-use rights | Included. Run ECC and S/4 in parallel | Must be negotiated explicitly |
| Shelfware handling | Limited. Unused licences sit on contract unless separately terminated | Full flexibility. Trade in legacy value, reallocate to needed products |
| Credit mechanism | No credit. 1:1 swap only | SAP calculates credit based on legacy licence value |
| Best for | Minimal shelfware, conservative migration | Significant shelfware, strategic portfolio reset |
Contract conversion is effectively a wholesale licence overhaul. SAP calculates a credit based on the current net value of the licences you surrender. This credit can be applied to any new S/4HANA product. A $500,000 SAP CRM engine that was never fully utilised can be redirected as credit toward S/4HANA users, Analytics Cloud, or BTP credits. The idle licence transforms from a recurring maintenance liability into funding for productive software.
| Case Study: European Manufacturer | Detail |
|---|---|
| Situation | Manufacturing enterprise with $12.9 million in perpetual SAP licences identified approximately 20% shelfware ($2.6 million) through a comprehensive usage audit. Annual maintenance on unused components totalled $572,000 |
| Approach | Pursued contract conversion, presenting SAP with detailed usage data and a clear future-state architecture. Independent advisory helped negotiate maximum credit value for surrendered licences |
| Result | $2.6 million in shelfware value applied as credit toward new S/4HANA licences. Annual maintenance on unused components eliminated entirely, saving $572,000 per year. Every licence in the new contract tied to active, planned functionality |
| Takeaway | Contract conversion enables organisations to convert historical over-purchasing into funding for S/4HANA migration while simultaneously eliminating the ongoing maintenance burden of unused software |
| Credit Negotiation Factor | What to Know |
|---|---|
| Credit valuation | SAP may assign reduced or zero credit to licences that are not deployed. Prepare detailed usage documentation showing historical deployment even for components being retired. This supports higher credit assignment |
| Incremental spend requirements | SAP frequently requires that a portion of the new contract represent incremental spend (e.g., minimum maintenance increase). Understand these thresholds before negotiation to structure the deal favourably |
| Timing impact | SAP's conversion credit percentages typically decline as 2027 approaches. Converting earlier locks in higher credit values. Some enterprises secure S/4HANA licences ahead of actual go-live to maximise credit position |
| Termination vs credit trade-off | Terminating licences before conversion saves maintenance immediately but removes them from the credit pool. Assess which licences SAP will credit generously versus those they will not, and optimise the sequence accordingly |
The financial case for retiring unused components is compelling and straightforward to calculate. Every terminated licence generates immediate, recurring savings through eliminated maintenance payments, plus potential one-time credit value during conversion.
| Metric | Legacy ECC Environment | Optimised S/4HANA Migration |
|---|---|---|
| Total licence value | $12.9 million | $12.9 million (reinvested via credit) |
| Unused shelfware | Approximately 20% ($2.6M idle) | 0% carried forward |
| Annual maintenance on shelfware | $572,000 per year wasted | $0. Eliminated |
| 5-year maintenance saving | N/A | $2.86 million cumulative |
Terminating a single unused SAP engine module with $100,000 in annual maintenance generates an immediate $100,000 annual return. Reducing named user counts by 500 can save six figures annually. These savings compound over the life of the S/4HANA agreement (typically 3-5 years), creating substantial budget that can fund implementation services, training, innovation, or simply improve the bottom line. An optimised licence footprint also reduces compliance risk, simplifies audit responses, and provides genuine visibility into what your organisation actually uses.
While the benefits are clear, CIOs must approach shelfware retirement strategically to avoid common mistakes that can undermine savings or create new problems.
| Pitfall | Risk | Prevention |
|---|---|---|
| Cutting without validation | Terminating a licence before confirming with business owners that the functionality is not needed. An idle module today may have a planned deployment tomorrow | Always cross-reference retirement decisions against the IT roadmap. Get written confirmation from functional owners before terminating any component |
| Creating new shelfware | Over-provisioning the S/4HANA environment "just in case" by converting all existing users 1:1 or purchasing excess capacity | Right-size from day one based on verified usage. Add licences later under pre-negotiated pricing. Do not convert shelfware into new-generation shelfware |
| Overlooking indirect access | S/4HANA introduces new licensing metrics including Digital Access (document-based) and FUEs. Retiring a module because a third-party replacement handles that function does not eliminate all licensing requirements | Ensure proper indirect access licences exist for any third-party integration with S/4HANA. Assess integration points before assuming a module retirement eliminates all costs |
| Ignoring termination clauses | Most SAP contracts permit licence drops only at specific times (contract anniversary or renewal) with required notice periods | Review your SAP contract for when and how you can terminate. Align termination timing with your migration schedule |
| Missing dual-use rights | Retiring a component before confirming it is no longer needed in the legacy ECC environment that may run in parallel during migration | Secure dual-use rights in your S/4HANA agreement allowing ECC and S/4 to run in parallel. Verify no critical functionality was retired before decommissioning legacy |
The termination-versus-credit trade-off is the most consequential financial decision in shelfware retirement. Terminating saves maintenance immediately but reduces the credit pool. Including shelfware in a contract conversion captures credit value but means continued maintenance payments until execution. Model both scenarios financially for each component, and optimise the sequence accordingly. For licences SAP is unlikely to credit generously, early termination typically delivers better net value.
Executing a shelfware retirement programme requires a structured timeline that begins 12 months before your target S/4HANA contract negotiation date.
| Step | Activity | Timing | Detail |
|---|---|---|---|
| 1 | Conduct full licence inventory | T-minus 12 months | Create a comprehensive register of every SAP product, engine, user licence, and add-on. Include licence type, quantity, annual maintenance cost, and contract expiry dates. Use SAP's LAW tool supplemented by SAM platforms |
| 2 | Execute usage analysis | T-minus 10 months | Pull 12 months of usage data for every component and user. Flag modules with zero or minimal transaction activity, named users with no logins, and engines operating well below licensed capacity. Quantify maintenance cost of each shelfware item |
| 3 | Validate with business owners | T-minus 8 months | Present findings to functional owners. Obtain written confirmation of retirement decisions. Challenge "we might need it someday" responses with cost data. Ongoing maintenance of an unused module typically exceeds re-procurement cost if genuinely needed later |
| 4 | Model conversion scenarios | T-minus 6 months | Compare product conversion vs contract conversion financial outcomes including credit values, maintenance savings, incremental spend requirements, and total cost of ownership. Select the approach that maximises net value for your shelfware profile |
| 5 | Negotiate with SAP | T-minus 4 months | Present SAP with your optimised licence requirement supported by comprehensive usage data. Negotiate maximum credit for surrendered licences. Demand line-item pricing transparency. Secure dual-use rights, renewal caps, and flexibility clauses |
| 6 | Execute and monitor | Ongoing | Decommission retired components on schedule. Verify maintenance charges cease on terminated licences. Establish ongoing usage monitoring to prevent new shelfware accumulation in the S/4HANA environment |
| Case Study: Financial Services Firm | Detail |
|---|---|
| Situation | North American financial institution preparing to convert 3,200 SAP named users to S/4HANA. Internal IT proposed a straightforward 1:1 conversion to minimise risk and project complexity |
| Analysis | Independent licence review revealed 640 users (20%) had not logged into SAP in over 12 months. An additional 380 users (12%) had fewer than 5 transactions per quarter and could be downgraded to limited-access types. Three legacy modules (SAP SRM, classic BW Accelerator, industry solution) had zero active users |
| Result | Optimised S/4HANA contract covered 2,560 full users (vs 3,200), 380 limited-access users, and excluded all three legacy modules. Total annual licence and maintenance savings exceeded $680,000. Credit from retired modules funded SAP Analytics Cloud deployment |
| Takeaway | A 1:1 conversion is the path of least resistance but also the path of maximum waste. Every migration should be preceded by rigorous usage analysis and business owner validation |
| Recommendation | Detail | Priority |
|---|---|---|
| Start the audit now | Begin licence utilisation assessment immediately regardless of migration date. The earlier you identify shelfware, the more options you have for maximising value during conversion | Critical |
| Engage SAP early on conversion options | Initiate discussions about product vs contract conversion well in advance. Understand how SAP will treat your shelfware and signal clearly that you intend to optimise | Critical |
| Terminate unused licences proactively | Where contract terms permit, halt maintenance payments on clearly unused components before migration. Immediate savings strengthen your financial position for negotiation | High |
| Negotiate aggressively for credits | Present comprehensive usage data to support maximum credit assignment. Do not accept SAP's first credit offer. Advisory support typically secures 15-25% higher credit values | High |
| Right-size from day one | Base S/4HANA user counts and module selections on verified current usage and approved roadmap items, not historical licence quantities. Add capacity later under pre-negotiated pricing | Critical |
| Align licensing with architecture | Ensure every component in the new contract has a justified place in your future-state IT architecture. If third-party solutions replace SAP functions, do not licence equivalent SAP modules | High |
| Secure contractual protections | Include dual-use rights, renewal price caps, flexibility to add or remove components, and maintenance base calculations on discounted prices. These terms determine whether initial savings are sustained | Critical |
| Consider independent advisory | For estates exceeding $5 million, expert support typically delivers 15-20% deeper optimisation than internal procurement alone through benchmark data, credit negotiation expertise, and contractual safeguards | Recommended |
Shelfware means SAP software licences you have paid for but are not using. CIOs should care because it wastes budget through ongoing support fees on idle software (typically 22% of licence cost annually), adds compliance complexity, and obscures visibility into actual requirements. Eliminating shelfware immediately cuts costs and simplifies your licence estate.
Start by analysing system usage data and user logs over a 12-month period. Look for modules with zero or minimal transaction activity and user IDs with no logins. Cross-check findings with business unit owners to confirm whether components are still needed. SAP's Licence Administration Workbench (LAW) and software asset management tools provide the raw data. Common culprits include modules purchased as part of bundles for projects that never launched and accounts belonging to former employees.
Modules replaced by S/4HANA functionality or third-party solutions are the primary candidates. Common examples include legacy SAP SRM (supplier management), SCM/APO (supply chain planning), classic SAP CRM, older BW Accelerator, and industry solutions not part of the future-state architecture. Also targeted are named user licences for dormant accounts and engine licences operating well below capacity.
Yes, through SAP's contract conversion programme. SAP evaluates the licences you own and provides credit toward new S/4HANA purchases. The credit can cover a substantial portion of new licence cost. However, SAP may assign reduced or zero credit to licences never deployed, and they may require some incremental spend in the new contract. Negotiation with supporting usage data is essential to maximise credit value.
This depends on your situation. Terminating before conversion saves maintenance immediately but reduces the pool available for credit. Including shelfware in a contract conversion captures credit value but means continued maintenance payments until execution. Model both scenarios financially. For licences SAP is unlikely to credit generously, early termination typically delivers better net value.
Product conversion swaps specific ECC products for S/4HANA equivalents within your existing contract. It is simpler but offers limited flexibility for eliminating shelfware. Contract conversion negotiates an entirely new S/4HANA agreement with credit for legacy licences. It is more complex but provides full flexibility to restructure your estate, monetise shelfware, and reallocate value to products you genuinely need. Contract conversion is the better path when significant shelfware exists.
Right-size from day one by basing S/4HANA user counts on verified current usage rather than historical quantities. Avoid 1:1 conversions that perpetuate over-provisioning. Negotiate pre-agreed pricing for future additions so you can expand as needed without pressure to over-purchase upfront. After migration, institute quarterly or semi-annual usage reviews to catch emerging shelfware before it accumulates.
SAP's conversion credit percentages typically decline as the 2027 ECC end-of-support deadline approaches. Converting earlier generally locks in higher credit values. Some enterprises secure S/4HANA licences ahead of actual go-live to maximise their credit position. Delaying conversion until the last moment reduces both credit values and negotiation leverage as SAP has less incentive to offer favourable terms.
S/4HANA introduces Digital Access (document-based) licensing alongside traditional named user metrics. If you retire an SAP module because a third-party system handles that function, the integration between the third-party system and S/4HANA may still require indirect access licences. Assess all integration points carefully before assuming a module retirement eliminates all associated licensing requirements.
For an enterprise with $10 million+ in SAP licences, typical shelfware ratios of 15-20% translate to $1.5-2 million in idle licence value and $300-500K in annual wasted maintenance. Over a 5-year S/4HANA agreement, cumulative maintenance savings alone can exceed $2 million. Additional value comes from conversion credits that fund new S/4HANA capabilities. Independent advisory typically identifies 15-20% deeper optimisation than internal procurement alone.
Our SAP advisory team brings benchmark data from 500+ enterprise deals and deep expertise in shelfware identification, conversion credit negotiation, and licence estate optimisation. Vendor-independent. Fixed-fee engagements.
SAP Advisory ServicesIndependent SAP licensing advisory. Shelfware identification. Conversion credit negotiation. Estate optimisation. 100% vendor-independent, fixed-fee engagement.