SAP S/4HANA Licensing Pitfalls – The Hidden Cost of a Phased Migration
Migrating to SAP S/4HANA isn’t usually a flip-the-switch moment. Most organizations take a phased approach – running the old SAP ECC system alongside the new S/4HANA for months or even years. It feels safer to move in stages, but this overlap can carry hidden costs.
If you’re not careful, you might see both ECC and S/4HANA showing up on your support invoice at full price. In other words, without the right terms in place, a phased migration can lead to double-paying for SAP licenses and maintenance during the transition.
Why does this happen? SAP’s standard policies assume you’ll pay for each live product environment. So if your ECC system is still technically “in use” while S/4 is rolling out, SAP expects support and license fees for both.
Read our ultimate guide to SAP S/4HANA Licensing Migration Cost Traps: Don’t Let Licensing Surprise You.
This is not something SAP will automatically warn you about – it’s on you to treat licensing as a critical workstream in your migration project, not an afterthought. Before your finance team gets an unwelcome surprise, make sure you have a plan to handle parallel systems.
Migration Licensing Preparation Checklist:
- Confirm your overlap timeline: How long will ECC and S/4HANA coexist? Nail down the expected duration and phases of the parallel run.
- Identify duplication risk points: Pinpoint where users, modules, or processes might run in both systems at once – those are potential double-pay scenarios.
- Review conversion terms: Understand how your current license entitlements convert to S/4HANA. Clarify what you’re entitled to carry over and what new licenses you need, in writing.
Paying Twice – The “Dual System” Trap
One of the biggest pitfalls in a staged migration is the “dual system” trap – paying for two systems simultaneously. When you keep ECC running while S/4HANA is coming online, SAP doesn’t give you a free pass by default.
They will happily bill you for ECC maintenance and charge for S/4 licensing unless you negotiate otherwise. We’ve seen companies assume the old system would be free during the changeover, only to be billed for both environments.
Here’s how the trap works and how to avoid it:
- Risks of Dual Operation:
- Double maintenance costs: You continue paying annual maintenance on ECC, and at the same time, you’re paying subscription fees or maintenance for S/4HANA. The overlap period effectively doubles your SAP costs.
- No automatic pause: SAP won’t automatically pause or prorate ECC support just because you’re going live on S/4. Unless you explicitly arrange it, both bills keep coming.
- Deactivated users still count: Even if you’ve turned off some ECC user accounts, they may still count toward your license total on ECC. If those licenses remain on contract, SAP will charge maintenance for them until you formally remove or terminate them.
- How to Fix It (Avoiding Dual Pay):
- Negotiate dual-use rights: Before starting the migration, negotiate a dual-use clause in your SAP agreement. This clause should allow you to run ECC and S/4HANA concurrently for a defined period without incurring additional costs. For example, secure a 12-month window post-S/4 go-live during which ECC can remain operational (for read-only access, historical data, etc.) without incurring additional license fees.
- Get a grace period in writing: Ask SAP for a grace period during which you can safely operate both systems. Make it part of your contract that for X months of overlap, you won’t incur duplicate maintenance charges on the old system.
- Include clear transition triggers: Build transition clauses into the contract that specify when ECC charges should stop. For instance, tie the end of ECC maintenance payments to a milestone (like completion of data migration or a set cut-off date).
For example, you might add language in your contract such as:
“Customer may operate ECC and S/4HANA environments concurrently for 12 months post go-live without incurring duplicate maintenance fees.”
Such a clause ensures you’re not on the hook for full support costs on two systems at once. It forces SAP to acknowledge the overlap in writing.
Conversational Tip: If you don’t take control of defining the overlap period, SAP will – and they’ll bill you for both environments as long as they can.
Misunderstanding License Conversion Ratios
SAP encourages customers to transition their existing licenses to S/4HANA with conversion programs. The idea is that you won’t have to buy everything from scratch – in theory, your ECC licenses convert to S/4 licenses on some ratio or credit basis.
The pitfall is in the fine print: those conversion ratios are not always 1:1, and unwary customers can lose value during the swap.
Common Conversion Pitfalls:
- The 1:1 myth: You might assume 100 ECC user licenses equal 100 S/4HANA user licenses. In reality, SAP might not honor a one-for-one conversion. They could introduce new license metrics or definitions, which might mean you get fewer S/4 licenses for your ECC investment. (For example, a company with 100 ECC Professional users could find that only translates into 60 S/4 user licenses if SAP reclassifies user types or usage criteria in the new system.)
- Partial module conversion: Some ECC modules don’t have a straightforward S/4 successor. An ECC component might split into multiple S/4HANA modules, each requiring its own license. If you’re not careful, you may end up needing additional licenses to cover what one ECC module did.
- Expiring credits: SAP often gives a credit value for your existing licenses to apply toward S/4 – but these credits can diminish or expire. There’s usually a window of time to use the credit. If you wait too long to migrate, the credit might shrink (or vanish), meaning you effectively lose the value of what you already paid for.
How to Get a Fair Conversion:
- Validate every ratio: Insist on a detailed conversion mapping from SAP for each product and user type. Go line by line to see what each of your ECC licenses will convert into. Don’t assume anything – get it in writing that, say, your 500 Professional Users convert to 500 S/4HANA Professional Users (or whatever the equivalent is). If SAP proposes a different ratio, understand why and challenge it.
- Retain entitlements until cutover: Ensure your contract specifies that your old ECC entitlements remain valid until you switch off ECC. You don’t want SAP de-authorizing your ECC licenses prematurely. During the migration, you might need to fall back on ECC, so you must legally be allowed to use it fully until cutover.
- Secure conversion credits and timelines: If SAP is giving you credit for your existing licenses, clarify how much and how long it’s valid. For instance, if they offer a 100% license credit toward S/4HANA if you migrate by the end of the year, that should be documented. Ask what happens if your project slips – does the credit drop to 50% next year? Lock in the best terms possible and calendar any deadlines so you don’t miss them.
Pro Tip: SAP’s conversion math tends to favor SAP. Always double-check the conversion ratios and credit conditions, and don’t sign off until every conversion detail is crystal clear to you. If something looks off (like losing 40% of your users in the conversion), raise it with SAP and negotiate an adjustment.
Read how to license the database, HANA Database License Considerations: What to Know Before You Migrate to S/4HANA.
The Hidden Support Clock
Another costly trap is assuming that moving to S/4HANA automatically stops the support fees for ECC. It doesn’t. SAP’s support contracts have their own lifecycle, and they auto-renew if you don’t actively terminate them. This is the “hidden clock” ticking in the background of your migration.
When you bought SAP ECC, you committed to annual maintenance (typically 20-22% of license value), which renews every year unless canceled with advance notice. If you migrate to S/4 but don’t tell SAP to stop ECC maintenance, they will keep charging you. We’ve seen companies complete their migration and months later realize they’re still paying for support on the old system sitting idle.
Avoiding Surprise Maintenance Bills:
- Know your notice period: Check your ECC maintenance contract for the required termination notice period (often 3 to 6 months before the annual renewal date). Mark that date on your calendar now. If you miss it, SAP will renew your support for another year by default.
- Give formal notice in time: Plan the timing of your migration alongside your support schedule. As soon as you’re confident about retiring ECC (or significantly reducing its use), send SAP a formal written notice to terminate or reduce ECC maintenance effective on the appropriate date. Simply migrating systems doesn’t trigger any automatic stop; it’s up to you to officially request the termination per the contract terms.
- Document end of support in your migration plan: Ideally, include the end date for ECC support fees in your S/4HANA migration agreement. For example, if you know you’ll be off ECC by next June, have the contract specify that ECC maintenance charges will cease on that date. This puts SAP on notice and gives you legal backup to stop paying for ECC when you’re done.
- Watch out for co-terminus contracts: Sometimes SAP ties multiple products into one support agreement with a common end date. If your ECC support is co-terminated with other software, you might need to negotiate a decoupling or partial termination. Ensure that killing ECC support doesn’t inadvertently affect other licenses you’re keeping. Review your contract or ask SAP if any “bundled” maintenance clauses will complicate dropping ECC.
In short, don’t assume SAP knows you’ve moved on. Until you explicitly prove to SAP that you don’t need ECC support and have followed their rules to terminate it, they will keep the meter running. A proactive letter to SAP (and a confirmation from them) can save you a significant amount of money post-migration.
Overlooking Transitional Licensing Options
SAP rarely advertises it, but there are transitional licensing arrangements that can smooth out a migration. These options can save you money or at least avoid some licensing pain during the switch. The catch: you usually only get them if you ask and negotiate.
Many customers simply aren’t aware of these possibilities, so they miss out and end up paying more than necessary.
Some transitional options to explore with SAP:
- Temporary dual-use licenses: In some cases, SAP can provide a special temporary license or allowance for you to run both ECC and S/4HANA concurrently. This might be a specific licensing construct for the migration period that legally permits dual use (beyond the normal 30-day test periods) without extra cost. Always inquire if such a program is available for your situation.
- Conversion credits for unused licenses: If you are not using portions of your ECC system or have shelfware (unused licenses), ask about getting license value credit. SAP might grant you credits for the maintenance value of retired ECC components or users, which you can apply toward your new S/4HANA licenses or subscriptions. Essentially, this offsets costs so you’re not paying for old and new at the same time.
- Contract conversion programs: SAP offers programs to convert your entire contract, such as merging your old perpetual licenses with new cloud subscriptions under one agreement. This can sometimes simplify things and provide financial incentives, like reduced subscription fees or one-time credits. Be cautious, though: a full contract conversion means you terminate the old contract and start fresh on SAP’s latest terms. Make sure any special discounts or usage rights you had carry over, or negotiate equivalent benefits in the new contract.
Transition Planning Checklist:
- Ask for all options in writing: Don’t rely on verbal assurances. If an SAP rep mentions a migration promotion or dual-use provision, have them send the official policy or include it in your contract. Get the details on duration, scope, and any conditions (like needing to be on a certain software release).
- Verify eligibility: Some programs have prerequisites (e.g., you must be on a certain ECC version or have active maintenance). Confirm you qualify for any transition program before assuming it’s available.
- Capture credit value upfront: If SAP offers you credits for your existing licenses, lock in that value before you sign the S/4 deal or renew anything. For instance, ensure the contract states: “maintenance value of discontinued ECC licenses will offset S/4HANA subscription costs during the transition.” That way, if you drop a $500k/year ECC support bill, you should see an equivalent $500k reduction or credit in your S/4 costs for that overlap period.
- Time-bound your transition: Transitional arrangements typically have an expiration. Know exactly how long you have dual-use rights or credits. If you need longer, negotiate it upfront or have an option to extend. Avoid finding out later that your courtesy period ended three months before you finished migrating a region.
In essence, don’t be shy about leveraging your status as a migrating customer. SAP wants you on S/4HANA, so use that as leverage to get flexible terms that ease the switch. If you don’t ask for these transitional perks, SAP is certainly not going to insist you take them – they’d rather collect full price.
Data and Module Mismatch During Migration
A phased migration often happens module by module or business unit by business unit. Maybe Finance moves to S/4HANA this year, while Supply Chain and HR are still on ECC until next year. This staggered approach can create a licensing minefield if not managed closely.
The core issue is that the same people and data can exist in two systems, and SAP’s license counting might see that as two separate usages.
Risks in a partial migration:
- Double-counted users: If John Doe is using the new S/4HANA Finance module but still needs to use ECC for, say, Procurement (which hasn’t migrated yet), John is active in both systems. SAP’s auditor could count John as two users (one in ECC, one in S/4) unless you reconcile that. Without controls, you might pay for John twice because he shows up in two user lists.
- Different metrics for old vs new: License metrics can change between ECC and S/4HANA. For instance, ECC might count a “Professional User” one way, while S/4HANA might categorize that user differently or have new user types. If only part of someone’s role moved to S/4, you might have trouble classifying their usage correctly. This mismatch can lead to over-licensing or compliance issues – either you overspend by erring on the safe side, or you under-license and risk an audit finding.
- Indirect access exposures: During the transition, some data might flow between ECC and S/4. If external systems are integrated with ECC that now feed into S/4 (or vice versa), you could inadvertently trigger indirect usage concerns. For example, if ECC is still handling orders from a web store and pushing them to S/4, are those documents properly licensed under SAP’s digital access rules? It’s a headache tracking what’s hitting which system.
Steps to avoid user and data overlap issues:
- Track and reconcile user IDs: Maintain a master list of users who have access to either system. Flag anyone who has accounts in both ECC and S/4HANA. You may decide to restrict dual access where possible (e.g., once Finance folks move to S/4, cut off their ECC access except for read-only access). At a minimum, you need transparency on who is in both systems to manage their licensing.
- Use SAP’s LAW tool before an audit does: SAP provides the License Administration Workbench (LAW) to help consolidate license data from multiple systems. Run LAW reports during your migration to see if the same person is counted twice and to simulate what an official audit would find. If LAW shows 1,000 users when you only have 600 employees, you know you have a duplication problem to fix.
- Define system ownership per function: Try to assign clear “home” systems for each user or group. For example, if Finance is on S/4 and Logistics is on ECC, then financial users should primarily use S/4, and logistics users should stick to ECC until cutover. Minimize cross-over usage unless necessary. This way, each user is truly active in only one environment, simplifying compliance.
- Document your module migration plan: Keep an updated plan of which modules have moved and which remain on ECC, and who is using them. This will help you justify to SAP (or to yourself) why certain users still need ECC access. It’s also useful for determining when you can drop ECC licenses – e.g., “once Logistics goes live in Q4, we can deactivate those ECC users and remove that license segment.”
- Audit after each phase: After each migration phase (say, after Finance go-live), do a mini-audit internally. Check that you reduced ECC user counts appropriately and that new S/4 users match expected numbers. By cleaning up as you go, you prevent a pile-up of dual users or forgotten accounts.
Phased projects are complex, but the goal is to avoid a scenario where SAP can claim you exceeded licenses because of parallel usage. Stay on top of the moving pieces, and you won’t end up paying for the same person or data twice.
Negotiation Levers to Avoid Cost Overlap
Lastly, let’s talk strategy. The best way to avoid extra licensing costs during your migration is to negotiate favorable terms before and during the project. If you’re already in a multi-year SAP agreement or facing a renewal, use that timing to your advantage.
SAP account executives are often willing to bend (or at least cushion the blow) if it means securing your long-term S/4HANA business.
Here are some negotiation tactics to keep costs in check:
- Bundle your migration with renewals: If your ECC support renewal is coming up, use that as leverage. For example, agree to renew or extend maintenance only if SAP grants you the necessary migration concessions (dual-use rights, credits, discounts on S/4 licenses, etc.). SAP is keen to keep you as a customer, especially during the ECC-to-S/4 transition period when some consider third-party support or alternate solutions. Bring that to the table.
- Ask for multi-phase credits upfront: Explain your phased migration plan to SAP and request licensing flexibility for those phases. This could be credit for modules you will retire later, or a pricing structure that steps up as you move more users to S/4 rather than charging all at once. By signaling your full roadmap, you might negotiate a deal that anticipates phase 1, 2, 3, etc., with costs aligned to each wave instead of double-paying throughout.
- Set end-dates for ECC costs: Ensure the agreement has a written timeline for when ECC fees stop. Don’t leave it open-ended. For instance, if you plan a complete cutover in 18 months, negotiate a clause stating that ECC maintenance is waived or terminated after 18 months. This puts a fixed horizon on overlap costs.
- Escalate if needed: Sometimes your immediate sales rep might resist giving concessions (they worry about their quota). If you’re not getting traction, don’t be afraid to go above their head. Engage SAP global account management or even higher executives by emphasizing the strategic nature of your project. Let them know you’re considering all options to control costs. Often, senior SAP reps can approve special terms (like extended dual-use or extra credits) that field salespeople cannot or will not offer initially.
You might propose contract language such as:
“To support a phased S/4HANA migration, the customer retains full rights to operate the ECC system in parallel without duplicate maintenance charges during the transition period.”
This kind of clause explicitly frees you from double payments while you migrate in stages. It’s essentially telling SAP: we’ll move to S/4, but you must cooperate on the financial side.
Negotiation Checklist:
- Identify your leverage points: Know when your current SAP contracts renew and what other deals (cloud products, additional licenses) SAP wants to sell you. Use those as bargaining chips to secure migration-friendly terms.
- Get migration incentives in the proposal: Push SAP to include any promised discounts or credits for migrating directly in the offer/quote. For example, if they say you’ll get 12 months of dual usage, make sure the quote or contract explicitly reflects that (e.g., a line item showing ECC support waived for a year).
- Document everything in the master agreement, as verbal promises or side emails won’t help later. All the special conditions – from dual-use periods and conversion credits to support end-dates – should be codified in your SAP contract or an addendum. If it’s not written, assume it doesn’t exist.
Conversational Tip: If you’re already halfway through your migration and haven’t revisited your SAP contract, you’re playing catch-up. The best time to negotiate cost overlaps is before they happen. Proactivity is key – once you’re in the thick of migration, your leverage diminishes, and SAP knows it.
5 Migration Pitfalls to Watch (and How to Fix Them)
- Running ECC and S/4 simultaneously without dual-use rights – Fix: Negotiate an overlap clause upfront so you’re not paying maintenance on ECC and subscriptions for S/4 at the same time.
- Assuming a 1:1 license conversion, fix: scrutinize SAP’s conversion offers. Double-check how each ECC license converts to S/4 and get those terms in writing to avoid a reduction in entitlements.
- Not formally terminating ECC maintenance – Fix: Don’t assume SAP will stop billing. Send a written termination notice for ECC support according to your contract’s notice period, and confirm the end date of charges.
- Counting the same users in both systems – Fix: Monitor user access across ECC and S/4. Use tools (like SAP LAW) and internal audits to identify duplicate user IDs and adjust licensing so each human is only counted once.
- Ignoring transitional credits and programs – Fix: Proactively ask SAP about the available migration incentives. Negotiate for dual-use licenses, conversion credits, or flexible contract terms – and capture all these concessions in your agreement.
By keeping these pitfalls in mind and taking action to address them, you can navigate your S/4HANA migration without falling into the common licensing traps that cause costs to balloon. A little extra diligence and tough negotiating now will save your organization from paying double for the same ride. Good luck with your SAP move – and remember, when it comes to SAP contracts, the details today determine the invoices tomorrow.
Read about our SAP Services.
