Introduction – Why Shelfware Grows During Migration
Most SAP software isn’t caused by buying the wrong product — it’s caused by buying too early. Many companies moving to S/4HANA overestimate user demand or include every possible module “just in case,” only to see a chunk of those licenses sit idle for years.
This often happens when SAP ECC and S/4HANA run in parallel during a phased rollout, or when project teams purchase future functionality long before it’s needed. The result? Unused licenses (“shelfware”) that drain budgets through maintenance fees and tie up capital.
License timing should be treated as a negotiation lever, not a mere procurement checkbox. In practice, you have more control than you think: you can start with what you truly need for the initial go-live and scale up later as usage grows.
SAP’s sales teams might push for a big upfront purchase, but you don’t have to bite. Read our ultimate guide to SAP S/4HANA Licensing Migration Cost Traps: Don’t Let Licensing Surprise You.
By aligning license purchases with actual deployment phases and promptly retiring legacy ECC licenses, you avoid paying for two systems at once or buying software years before it delivers value.
- Review actual vs. projected S/4HANA usage: Base your S/4 license counts on real data and realistic adoption rates, not optimistic guesses.
- Align licenses with rollout phases: Purchase licenses in tranches tied to each go-live wave or region, rather than all at once on day one.
- Plan to retire or convert ECC licenses: As you migrate, have a strategy to terminate maintenance on old ECC users/modules or convert them into S/4 credits.
The “Just in Case” Trap — Overbuying for Future Needs
One common pitfall is buying more S/4HANA licenses than you need upfront “just in case.” It’s an understandable impulse: CIOs fear running short during a critical go-live, and SAP’s sales reps often warn about audit exposure or promise better discounts if you buy big now. However, overbuying as insurance can backfire.
Those extra licenses meant for future users or modules might sit unused for years, all while you’re paying 22% annual maintenance on them. We’ve seen companies pre-purchase modules that the project was later postponed or canceled, resulting in shelfware and sunk costs.
Moreover, loading up on licenses upfront locks you into a higher support cost baseline—SAP calculates your support fees on the total license value, including any unused parts. That means higher ongoing costs with nothing to show for it.
Why the “just in case” approach is risky:
- You end up paying maintenance on unused S/4HANA licenses for years before they deliver any value.
- You might buy costly add-on modules that never get implemented if the project scope changes.
- Your support costs are inflated from day one, since they’re based on a larger license pool than you actually use.
How to avoid overbuying: License in phases aligned to your project timeline. If only Finance and Logistics go live in year one, don’t buy licenses for HR and CRM users until those rollouts are on the horizon. Negotiate add-on flexibility instead of a bloated upfront quantity.
For example, secure contractual rights to purchase additional users later at the same discount or price you get now, so you’re protected from future price hikes without having to over-purchase. Document these future purchase rights in the agreement – this gives you peace of mind that you can scale when needed, without penalty, but you’re not paying today for hypothetical users of tomorrow.
Sample Clause: “Customer may procure up to 25% additional user licenses at the same unit rate within 18 months of initial go-live.”
Finally, maintain a healthy skepticism in negotiations. Conversational Tip: SAP will always tell you to buy early — but they’ll never refund what you don’t use. Stand your ground on buying only what’s necessary and let usage (not fear) dictate follow-on purchases.
What are the hidden costs? – Hidden Licensing Costs in S/4HANA: What Most Customers Don’t See Coming.
Avoiding Double Maintenance on Legacy ECC Licenses
Another costly trap during S/4HANA migrations is paying double maintenance – one stream for S/4 and another for legacy ECC licenses you no longer truly need.
Many customers keep their old ECC systems running in read-only mode or for backup during the transition, but forget (or don’t realize they’re allowed) to terminate maintenance on those obsolete licenses.
SAP isn’t going to voluntarily stop billing you; if you don’t formally notify and terminate, SAP assumes all ECC licenses are still in use and keeps charging full support. The result is effectively paying maintenance twice: once for your new S/4 licenses and again for the legacy ECC ones sitting idle.
To avoid this double-pay scenario, take action proactively. First, identify which ECC licenses and users will be completely retired or migrated off as you go live on S/4HANA. This might include old engines or modules you won’t use in S/4, as well as a chunk of user licenses whose roles have moved to the new system.
Next, notify SAP in writing before your support renewal date that you intend to terminate support on those specific ECC licenses. (Check your contract for the notice period, usually 3-6 months before renewal.) This formal termination is critical – it’s the only way to stop the maintenance meter from running. In parallel, discuss with SAP the possibility of a conversion or credit for those retired licenses.
In many S/4 migration agreements, you can negotiate to apply the value of the maintenance you were paying on ECC toward new S/4 licenses or subscriptions. Essentially, instead of wasting that money, use it to offset your new costs.
- ECC license inventory reviewed: Catalogue all your existing ECC licenses and determine which ones are truly not needed post-migration.
- Unused entitlements flagged for termination: List out the specific user types or modules to drop, and send SAP a formal termination notice for their maintenance.
- Conversion or credit negotiated: Secure a written agreement (or contract clause) that the maintenance value from the terminated ECC licenses will be credited against your new S/4HANA license fees or subscription costs.
Example Clause: “Maintenance value of retired ECC licenses shall be applied as credit against S/4HANA subscription costs.”
Following these steps ensures you’re not throwing money away on a shelf full of legacy licenses. Conversational Tip: If you don’t formally terminate maintenance, SAP assumes you’re still using it — and keeps charging. Don’t pay for two ERPs when you only need one.
Read how to license the database, HANA Database License Considerations: What to Know Before You Migrate to S/4HANA.
Using Conversion Credits to Reclaim Value
When moving from ECC to S/4HANA, you’ve likely invested millions in your ECC licenses over the years. The good news is you can often reclaim some of that value through SAP’s conversion programs – but SAP won’t hand those credits over unless you ask and negotiate firmly.
Conversion credits allow you to trade in or convert your old licenses into new S/4 licenses or cloud subscriptions, thereby reducing the net cost of the migration.
Think of it as a recycling program for your software investment: it won’t give you full value back, but it can significantly offset the price of S/4 if handled smartly.
There are a few conversion options to be aware of:
- Product Conversion: In certain cases, you can swap specific ECC product licenses for equivalent S/4HANA product licenses. For example, you might exchange ECC Financials module licenses for S/4HANA Finance licenses. This is a one-to-one replacement of similar functionality. (Note: SAP had formal product conversion programs in the past; today, these swaps may be case-by-case, so negotiate if you have comparable S/4 products for your ECC modules.)
- Contract Conversion: This is the most common path. You essentially tear up your old ECC contract and sign a new S/4HANA licensing contract, with SAP giving you credit for the net value of the licenses you’re giving up. For instance, if you have $5M worth of ECC licenses on the books, SAP might provide a credit (not necessarily dollar-for-dollar) that reduces the price of your S/4HANA deal. The exact credit is negotiable – SAP will consider which old licenses map to S/4 and which were shelfware. Make sure you highlight the value of what you actually used; unused ECC shelfware might be valued low by SAP in this exchange, so it’s in your interest to terminate truly unused licenses beforehand, as noted.
- Maintenance Credit (Cloud Extension): If you’re moving to a subscription model (like S/4HANA cloud or RISE), SAP has programs where you can apply the maintenance fees you would have paid on ECC toward your new subscription bill. Essentially, for a period of time, your ECC support payments become credits against the cloud subscription cost instead. This can ease the financial double burden during the overlap, but it must be set up in the contract. It usually requires committing to the new cloud licenses and possibly expanding the scope to qualify.
Checklist for securing conversion credits:
- Identify eligible licenses for conversion: Pin down which parts of your ECC portfolio are being replaced by S/4HANA. These are your bargaining chips for credit – know their original cost and current maintenance spend.
- Confirm credit value and terms: Push SAP to spell out how much credit you’ll get and for what. Is it 100% credit on paper licenses? A certain percentage of net value? Also, clarify if the credit has an expiration (e.g., must be used by a certain date or only valid toward specific S/4 products).
- Get it in writing: Do not rely on verbal promises. Ensure the conversion credits or trade-in deal is documented in the license agreement or an amendment. For example, include a clause detailing the credit applied for each retired product or the total contract value credit. This prevents any “memory loss” after you’ve signed on the dotted line.
Migrating to S/4HANA is the perfect time to reclaim value from shelfware, but only if you negotiate it. Pro Tip: SAP doesn’t volunteer conversion credits — you have to ask, calculate, and lock them in writing.
Come prepared with your own numbers on what you’ve invested and what you’re replacing, and use that to maximize the credit SAP gives you toward S/4.
Start with What You Need – The Right-Sizing Approach
One of the smartest ways to avoid shelfware is simple in concept but often ignored: right-size your S/4HANA licenses to actual needs. Rather than buying based on rosy projections or a future state headcount, start with licenses for what you know you’ll use in the initial phase of the migration.
Right-sizing involves aligning license volume and types with real usage and near-term requirements, then gradually scaling up. It requires a bit of analysis, but it’s well worth it – you’ll avoid paying for thousands of ghost users or rarely-used modules.
How do you right-size effectively? Begin by using your existing ECC system usage data as a baseline. Analyze your ECC user logs and transaction stats to see how many people are actively using each module or functionality that you plan to migrate first.
For example, suppose only 500 users regularly use the SAP finance module today, and you’re rolling out S/4 Finance in phase one.
In that case, it might make sense to license, say, 600 users (to allow a small growth buffer) for that phase – not the full 1,000 users in the company who might eventually use it years later.
Build a license forecast for each rollout wave (e.g., Wave 1: Finance & Logistics in Europe – X licenses; Wave 2: Add North America – Y more licenses; Wave 3: HR module next year – Z licenses later). By tying license purchases to module or regional go-lives, you ensure you’re paying for software in sync with value realization.
Importantly, include a modest buffer for growth or unexpected use, but keep it reasonable.
A 10–15% buffer on user count or transactions can cover normal growth without significant waste. There’s no need to double your licenses “just in case” when you can always procure a bit more later with the proper pricing protections in place.
- Usage-based sizing model complete: Use real ECC usage metrics to calculate how many S/4HANA users and engine licenses you actually need for each phase.
- License quantities tied to rollout phases: Split your S/4 license procurement into multiple tranches aligned with deployment milestones, instead of one mega-purchase.
- Growth buffer defined (but not overblown): Add a small extra margin to each phase’s license count (e.g., +10%) for safety, and justify why that buffer is enough based on historical growth.
This disciplined approach can yield substantial savings. For example, a company migrating its finance and logistics operations first decided to initially license only about 60% of its eventual total users. They then added the remaining users in later phases once those divisions were ready. By not buying 100% upfront, they saved approximately €1.4M in initial license and maintenance costs.
Right-sizing takes a bit more effort upfront in analyzing needs, but it’s the antidote to shelfware. Better to adjust your license count upward later due to real demand than to sit on excess licenses and regret it.
Managing Unused S/4HANA Licenses Post-Go-Live
Shelfware isn’t just a pre-migration or mid-migration issue; it can sneak back in even after you’ve gone live on S/4HANA. Organizations change – projects get delayed, business units are sold, user counts fluctuate – and suddenly you might have more S/4 licenses than you actually use.
Without ongoing oversight, today’s right-sized environment can become tomorrow’s shelfware scenario. The key is to treat license management as an ongoing practice post go-live, not a one-time true-up.
First, implement regular license utilization reviews. In an on-prem S/4HANA environment, use SAP’s measurement tools like USMM or License Administration Workbench (LAW) quarterly to see how many users are actually logging in and what roles they have.
For S/4HANA cloud subscriptions, review the usage reports or dashboards to check consumption versus your contracted amounts. These periodic check-ups will highlight if, for example, you purchased 1,000 Professional User licenses but only 800 are assigned and active. That’s a 20% shelfware you can address.
Second, optimize what you have. If certain users are inactive or have left, reassign those licenses to new employees instead of buying more.
If some users have a high-level license but only use basic functions, consider downgrading them to a cheaper license type (and use the expensive licenses for those who truly need them). For engine or package licenses, verify if you’re using as much as you thought – maybe that extra SAP SRM engine isn’t being used at all and could be dropped at renewal.
Finally, when it comes time for renewals (especially for cloud subscriptions, which might be annual or multi-year contracts), negotiate adjustments based on actual usage.
Don’t blindly renew the same quantities if your utilization reports show 15% of the licenses are unassigned. Approach SAP with data to either reduce the count or get some credit for under-use.
Some SAP contracts may allow reductions only at renewal without penalty – make sure to exercise that right if you have it. And if you don’t, it’s something to negotiate for next time (more on that in the next section).
- Governance team in place: Assign responsibility (to a SAM manager or a licensing team) to track S/4HANA license usage continuously.
- Quarterly utilization reports run: Use SAP’s tools or your own monitoring to get a clear picture of license consumption every quarter; identify any growing pile of unused licenses.
- Renewal optimization planned: Before each support renewal or subscription anniversary, analyze usage and decide where to trim or adjust license counts; engage SAP early to discuss credits or reductions so you’re not stuck paying for stale licenses.
By actively managing licenses post-migration, you ensure you’re only paying for what you actually need year after year.
Conversational Tip: Licenses age like milk — the longer they sit unused, the worse they smell at renewal time. In other words, letting shelfware fester will only lead to painful conversations later; it’s better to clean it up regularly.
Negotiation Levers to Avoid Future Shelfware
The best time to prevent shelfware is when you’re negotiating your S/4HANA license contract. You have the most leverage right before you sign, so use it to bake in flexibility that will save you from shelfware down the road.
Here are a few negotiation levers and clauses that can help keep your license footprint optimized throughout the S/4HANA lifecycle:
- Flexible consumption or pay-as-you-grow: If you’re moving to S/4HANA under a subscription model, ask for flexible consumption terms. Instead of a rigid fixed number of user subscriptions, see if SAP will agree to an annual true-up or pay-per-use model. For example, you commit to a baseline and then can add users as needed each year at the same rate. This way, you’re not forced to oversubscribe on day one. In on-premise deals, negotiate price protections on future license purchases (so adding licenses later won’t cost more per unit) rather than buying all upfront.
- Annual true-up vs. upfront commit: Push for a contract structure that allows you to adjust license counts periodically (say yearly) rather than locking into a huge number upfront that might overshoot your needs. An annual true-up means you reconcile and purchase any additional usage once per year, encouraging you to pay only for what was actually used. It’s a safety net if your actual user count is lower than expected – you won’t be stuck with prepaid shelfware because you only commit what you truly need incrementally.
- Reduction rights for lower usage: Negotiate the right to reduce your license or subscription quantities if your usage or business circumstances change. Vendors often hate giving this, but it’s worth asking for, especially for multi-year cloud deals. For instance, include a clause that allows you to decrease the number of users or modules by a certain percentage at each renewal period without penalty. This protects you if, say, automation reduces your need for some user licenses or a division using S/4 is spun off.
Sample Clause: “Customer may reduce S/4HANA subscription quantities by up to 10% annually without penalty or fees, adjusting the contract value accordingly at renewal.”
These kinds of terms act as insurance against shelfware. They ensure that if reality doesn’t match your initial plans, you have room to maneuver rather than being over-committed.
Be prepared to justify these requests by explaining your rollout strategy and uncertainty in forecasts – SAP might be more amenable if they understand you’re not trying to buy less, but to buy smarter.
And remember, if you don’t ask, you don’t get. It’s far better to negotiate flexibility up front than to beg for it after you’ve signed.
- Flexibility clauses included: Your S/4 contract should have provisions for adding licenses at locked-in prices or scaling subscriptions up and down, to avoid one-way door commitments.
- True-up structure confirmed: If possible, structure the deal to true-up annually for actual growth, rather than front-loading all licenses. Make sure the contract language is clear on how additional licenses will be priced.
- Reduction rights documented: Secure written rights to reduce license counts or switch to smaller license types at certain intervals if usage drops. This gives you an exit ramp for any shelfware that does appear.
By using these levers, you maintain commercial control and can adapt your license footprint as your business evolves, ensuring shelfware doesn’t creep in over time.
5 Steps to Avoid Shelfware in Your S/4HANA Migration
- License in phases – not all at once. Start with what you need for each go-live, and expand later instead of overbuying upfront.
- Terminate ECC maintenance on unused licenses. Don’t keep paying support for old ECC users or modules you’ve retired – formally shut them off or convert them.
- Convert legacy licenses into credits early. Negotiate trade-in credits for your ECC investments as part of the S/4 deal, so you recoup value rather than paying twice.
- Add flexibility clauses for growth and reduction. Build terms into your contract that let you adjust license counts upward or downward, preventing long-term shelfware.
- Review utilization quarterly and adjust proactively. After go-live, continually monitor license usage and adjust at renewals so you only pay for what you use.
By following these steps, CIOs and CFOs can keep a tight rein on SAP licensing costs during an S/4HANA migration. The goal is to ensure every euro or dollar spent on licenses is justified by actual business use – and to avoid the expensive trap of shelfware lurking in your SAP environment.
Read about our SAP Services.
