Mapping Legacy SAP ERP Licenses to S/4HANA User Roles
Converting legacy SAP ERP users to S/4HANA licenses is a critical step in any migration plan. CIOs and CTOs must reclassify existing ECC user licenses (Professional, Limited, Employee, etc.) into the new S/4HANA roles (Professional, Functional, Productivity) to optimize costs and ensure compliance.
The goal is to align each user’s license with their functional role in the business, so you pay only for what’s needed while avoiding any audit risk from under-licensing.
Legacy vs. S/4HANA License Types
SAP’s legacy ECC system offered a sprawling list of named user types (e.g., Professional User, Limited Professional, Employee Self-Service, Warehouse User, Developer, etc.).
This often caused confusion and inflexibility. SAP S/4HANA simplifies user licensing into a few broad categories that cover the “digital core” ERP usage:
- Professional Use – Full unrestricted access across all modules and processes. Equivalent to the classic “Professional User” – meant for power users who perform complex, cross-functional tasks (e.g., a finance manager or supply chain planner). It’s the highest-cost license tier.
- Functional Use – Access to a defined set of functional areas or modules related to a user’s job role, but not enterprise-wide access. This is essentially the S/4HANA replacement for the old “Limited Professional” user. For example, a procurement officer or sales representative can handle their specific transactions (such as sales orders and purchase orders) but wouldn’t have permissions beyond their domain. Priced lower than Professional.
- Productivity Use – A lighter user with self-service or limited tasks, analogous to the old “Employee” or casual user licenses. These users might enter timesheets, create expense reports, or view payslips. It’s the lowest tier and has the lowest cost, covering what ECC refers to as Employee Self-Service and similar low-intensity roles.
- Developer Use – A technical user license for developers and system administrators. This allows deep technical access (coding, configuration) but not business transactions. In ECC, this was referred to as “Developer User”; it carries over to S/4HANA (often priced at a premium due to its powerful access).
S/4HANA’s user categories are hierarchical – a Professional user can do everything Functional and Productivity users can, etc. This means you should always assign the minimum license type required for each person’s role to control costs.
Unlike ECC, where dozens of niche user types existed, S/4HANA’s streamlined model forces organizations to rethink how users are classified.
Read Contractual Differences Between RISE with SAP and BYOL Models.
Mapping Legacy Users to S/4HANA Roles
Mapping legacy SAP license types to S/4HANA roles is not a one-to-one conversion. You can’t simply swap an “ECC Limited Professional” for an identical S/4 license, because the categories have changed.
The key is to map based on each user’s functional role and actual system usage:
- Professional Users: In ECC, many users were forced into the high-cost Professional tier because their work required them to touch multiple areas. In S/4HANA, some of those users might be downgraded. Example: Under ECC, a sales manager had to have a Professional User license. In S/4HANA, if the sales manager only handles sales and CRM processes, a Functional Use license will cover their needs at a lower cost. Only truly cross-functional power users (or administrators) remain Professional.
- Limited Professional/Operational Users: ECC’s “Limited Professional” (and various operational roles, such as Warehouse or Shop Floor users) generally map to Functional Use in S/4HANA. However, it depends on their activity scope. A warehouse supervisor who performs goods movements and inventory checks could be a Functional User (since S/4HANA Functional covers many supply chain transactions). If a legacy role is extremely limited in scope (for example, a production worker who only records time on a machine), that user might even qualify as a Productivity User.
- Employee and ESS Users: Basic self-service users in ECC (entering time, viewing HR info) become Productivity Users in S/4HANA. The good news is that S/4HANA Productivity Use is inexpensive and covers a broad range of simple tasks across HR, basic procurement, and other areas. You no longer need separate license types for every lightweight scenario – one Productivity license type covers most of them.
- Developers and Technical Users: Your ECC developers would still need Developer Use licenses in S/4HANA (one per named developer). There’s typically no change here, though note that developer licenses are often high-cost. Additionally, system technical users (such as batch jobs and integrations) may not require a license if they fall under engine metrics or are covered by the S/4HANA foundation license, but this involves technical details. Ensure you review how background users or bots are handled under S/4 contracts to avoid surprises.
Tip: Start by conducting a license mapping workshop with both your SAP licensing specialists and business process owners. List out each legacy user type you have and decide which new S/4HANA category fits based on the person’s job functions.
This often reveals opportunities to downgrade some users to a lower-cost category because the S/4HANA Functional licenses are more capable than ECC’s mid-tier licenses were.
Optimizing and Rightsizing Licenses Before Migration
Converting licenses is an opportunity to streamline operations and save money.
Before you sign any S/4HANA contract, take these steps:
- Audit Current Usage: Analyze who is using the SAP system and the manner in which they are utilizing it. You may discover, for example, that 10–20% of your named users haven’t logged in for months. Inactive or dormant users should be removed or at least excluded from your future license counts. There’s no point paying maintenance on licenses not in use.
- Reclaim and Reassign: Identify users who were over-provisioned in ECC. Perhaps a user was given a Professional license years ago but now only performs a narrow role, such as basic data entry – that user could be assigned a Functional or Productivity license in S/4. By right-sizing roles now, companies often save 10–30% on S/4HANA license costs versus a one-to-one carryover.
- Match License to Actual Role: Ensure each user’s license type aligns with their current job responsibilities (not just their job title). This may mean downgrading some and, in a few cases, upgrading others who were under-licensed. It’s critical to get this mapping right before migration; whatever mix of licenses you contract for S/4HANA will lock in your costs and compliance obligations going forward.
- Clean Up User Accounts: Remove users who no longer need any access. Also, double-check user records for accuracy (e.g., no generic accounts masquerading as individuals, which is not allowed under named-user licensing). SAP auditors scrutinize user lists closely – an account that remains enabled with no activity can still be considered a licensable user if not handled properly. It is better to purge or archive these before moving to S/4.
- Consider Engine and Add-On Licenses: While mapping users, review which SAP modules or engines you’re using. S/4HANA’s core includes some functionality that was previously separate in ECC, which may allow you to drop certain engine licenses. On the other hand, if you plan to add new modules (e.g., advanced analytics or SCM add-ons), factor this into your license plan. The goal is to enter S/4HANA with a lean, accurate license footprint – just the users and modules you need.
By optimizing upfront, one company found that it could reduce its total named users by 15% (eliminating contractors and former employees) and shift nearly half of the remaining users from Professional to Functional licenses.
This type of adjustment translates to millions of dollars in savings over the life of the S/4HANA contract, and it positions the company well for future compliance.
SAP License Conversion Programs and Pricing
Moving to S/4HANA isn’t just a technical upgrade – it’s effectively signing a new contract. SAP does not automatically “carry over” your old ECC licenses.
Instead, you have two main options to acquire S/4HANA licenses:
- Contract Conversion (License Exchange): This is the primary route for existing customers. You essentially retire your ECC contract and negotiate a new S/4HANA license contract. SAP will typically offer credit for the investment value of your existing licenses, which can offset the cost of the new licenses. For example, if you have $5 $5M worth of ECC licenses on the books, SAP might credit a portion of that toward your S/4HANA purchase. The credit is negotiable – it’s not a 1:1 dollar swap, especially if some of your old licenses are shelfware you never used. Be prepared to demonstrate to SAP which licenses are truly necessary in the future. Unused licenses are unlikely to earn credit (SAP knows they were idle), so clean them out beforehand. The upside of contract conversion is that you can simplify your agreement and potentially eliminate unused products. The downside is it’s a one-shot, all-or-nothing deal – you’ll be committing to an entirely new license model in one go.
- RISE with SAP (Subscription Conversion): RISE is SAP’s cloud subscription offering for S/4HANA (typically hosted in SAP’s cloud or hyperscalers). This also involves terminating your old licenses and moving to a subscription model based on Full User Equivalents (FUE) or similar metrics. In a RISE deal, your ECC licenses essentially become obsolete (they’re “converted” into a subscription service). SAP often bundles infrastructure, support, and even some transformation services into its RISE offering. They may offer incentives like reduced subscription fees or cloud credits if you choose RISE, but be cautious: you should still negotiate recognition of your past investments (for instance, a discount off the standard RISE pricing). RISE can be attractive if you want an OPEX model and SAP-managed infrastructure, but it means you no longer own licenses – you’re renting the software.
- Product Conversion (Legacy program): SAP had an older program to swap specific licenses product-for-product (e.g., converting an ECC Financials module license into an equivalent S/4 module). This was limited and is now largely retired. Most customers today will either be undergoing a full contract conversion or transitioning to RISE.
Pricing Considerations:
S/4HANA licenses have a published price list, but most enterprise deals are heavily discounted. As a rough reference, the list price of an S/4HANA Professional User license might be in the ballpark of $3,000–$4,000 (perpetual, one-time, plus annual support of ~20%). At the same time, a Functional User could be around half of that, and Productivity Users a fraction (a few hundred dollars list price).
In subscription terms, we see quotes like $100–$200 per user per month for core S/4HANA access (exact pricing varies by user type and volume). Always get a detailed breakdown from SAP and use your existing spend as leverage.
If you’ve paid maintenance on a large ECC estate for years, remind SAP’s sales team of that investment – they have some latitude to offer credits or discounts, especially if you migrate sooner rather than later.
Negotiation Tip:
Aim to time your conversion negotiations with SAP’s quarter or year-end for maximum leverage, and get quotes for both the on-premise license route and RISE. Even if you prefer one, comparing both gives you bargaining power.
Also, ask SAP about any ongoing promotions (for example, SAP has offered extended support on ECC or discount tiers for S/4HANA if you sign up before certain dates in the past). The impending 2027 ECC support deadline means SAP is keen to move customers now – use that to your advantage.
Ensuring Compliance and Avoiding Audit Pitfalls
One of the worst outcomes of a license migration is ending up out of compliance and exposed to audits.
To avoid any audit risk, focus on aligning licenses to actual usage from day one:
- Accurate Role Mapping = Compliance: If a user is assigned a Functional Use license, ensure their SAP roles and authorizations in S/4HANA restrict them to activities allowed for that license. For instance, a Functional User shouldn’t be executing transactions that are reserved for Professional users (like certain cross-module configurations or high-level postings). Collaborate with your SAP security team to ensure that each user’s system role is aligned with their license type. This way, even if an auditor checks, the user’s activity will be within the bounds of their license.
- Don’t Under-License “Just to Save Money”: It might be tempting to classify everyone as a cheaper user type, but if a power user is misclassified as Functional and they perform broader tasks, you will get flagged in an audit. The cost of true-up and back maintenance fees could far outweigh the savings. It’s safer to slightly over-provision in ambiguous cases (or split duties) than to under-license. That said, avoid blanket over-licensing too – find the balance by thoroughly reviewing user needs.
- Monitor Usage Continuously: Post-migration, institute a periodic review of user activity. S/4HANA provides usage reports (and tools like SAP License Administration Workbench). Monitor if any Functional users start using transactions beyond their scope or if new integrations are creating indirect use. Catch it early and adjust licenses or access. A continuous compliance program will prevent nasty surprises when SAP audits (typically, SAP has the right to audit you annually or with notice).
- Indirect Access & Digital Access: S/4HANA introduced the Digital Access model to license indirect use through documents (such as sales orders). Make sure you understand how external systems interacting with S/4HANA are licensed. If you have a large number of interfaces (e.g., Salesforce creating quotes in SAP), consider SAP’s Digital Access Adoption Program or alternative licensing options to cover these. Indirect usage is a common audit pain point – address it in your S/4HANA licensing plan (either through document licensing or by ensuring external users and devices have the appropriate licenses).
- Document Everything: Maintain documentation of your license mapping decisions and the assumptions behind them. In a compliance audit, having a clear rationale (“User X is a Functional User license because they perform only sales module tasks – see attached role description”) can make a big difference in demonstrating your good-faith compliance. It also helps internally to educate managers why certain people have (or don’t have) certain access.
Remember, SAP audits aren’t going away with S/4HANA – if anything, SAP has become more vigilant. However, if you’ve done the homework, matched licenses to functional roles, and kept the house clean, an audit should be uneventful.
Many CIOs also engage a third-party licensing advisor to perform a mock audit after migration, ensuring a thorough review of all aspects. It’s an extra layer of assurance that your new S/4HANA environment is both cost-effective and compliant.
Recommendations
- Map Roles to Licenses Early: Before purchasing S/4HANA licenses, map every user’s functional role to the appropriate S/4HANA license type. Use actual usage data to guide decisions, ensuring heavy users get Professional licenses and lighter users are downgraded to Functional or Productivity.
- Eliminate Shelfware: Clean up inactive users and terminate unused SAP licenses before negotiating your S/4 deal. This maximizes credit for what you truly need and cuts maintenance waste.
- Negotiate Conversion Credits: Don’t Accept SAP’s First Offer. Push for credits recognizing your ECC investment. Leverage any upcoming SAP deadlines (like quarter-end or the 2027 support cutoff) to get better terms.
- Right-Size to Save Costs: Resist the urge to copy your old license count to S/4HANA. Take the opportunity to right-size. For example, if 200 users were Limited Professionals in ECC, perhaps only 100 need to be full Professionals in S/4, with the remaining 100 serving as Functional users. This can slash costs dramatically.
- Align Security with Licensing: Collaborate with your security and BASIS teams to ensure that user permissions in S/4HANA do not exceed the capabilities allowed by their licenses. This alignment is designed to prevent compliance issues.
- Monitor and Adjust: Treat license management as an ongoing process. Post-migration, regularly review user activity and licenses. Adjust license assignments if people’s roles change or if you spot misclassification.
- Consider Future Growth: When planning your S/4 licenses, factor in future projects and anticipated user needs. It’s often more cost-effective to negotiate extra licenses or FUEs upfront than to do so later. However, avoid over-buying far beyond needs – find a balance with some buffer for growth.
- Compare RISE vs. Perpetual: Determine if a RISE with SAP subscription is a better fit for your strategy than a traditional license conversion. Even if you stick to on-premise, understanding the subscription model helps in negotiations and long-term planning.
- Educate Your Team: Ensure that your IT and procurement teams understand the nuances of S/4HANA’s licensing. Internal stakeholders should be aware, for example, of what a “Functional User” can do, to avoid requests for unnecessary Professional licenses due to misunderstandings.
- Engage Experts if Needed: If you have a large and complex SAP footprint, consider engaging an SAP licensing expert or a third-party advisor. They can identify hidden risks and opportunities (like indirect usage or contract loopholes) that you might miss.
FAQ
Q1: What are the main differences between ECC and S/4HANA user license types?
A: SAP ECC had a wide array of user license types (Professional, Limited Professional, Employee, etc.), whereas S/4HANA consolidates these into just a few: Professional (full access), Functional (limited to certain business areas), Productivity (self-service/light use), plus Developer and a couple of technical categories. S/4HANA’s model is simpler – essentially a high, medium, and low tier for users, which makes it easier to manage but requires re-mapping your users into those buckets.
Q2: How do we determine which S/4HANA license a particular user needs?
A: The best approach is to analyze the user’s actual job role and the SAP transactions they perform. Map their role to one of the S/4 license categories. If they work across multiple modules or perform complex tasks (such as finance postings or configuring system settings), they likely need a Professional license. If they stick to one domain (like only sales orders or only warehouse tasks), a Functional license usually suffices. If they perform only self-service tasks or occasional data entry, they are a candidate for the Productivity user role. Conducting a usage analysis (using SAP’s logs or an optimization tool) for each user is ideal before making a decision.
Q3: Can we get credit for our existing SAP ERP licenses when moving to S/4HANA?
A: Yes – if you go through SAP’s contract conversion program, you negotiate a credit for the net value of your ECC licenses. In practice, SAP will assess what you own and how it maps to S/4. They might, for example, credit a portion of what you originally paid for 500 Professional and 100 Limited licenses towards the cost of, say, 400 Professional and 200 Functional S/4 licenses. The credit is not automatic; you must take the initiative to obtain it. Be aware that completely unused licenses (shelfware) will carry little to no credit. Essentially, SAP offers trade-in value for the equipment you were actively using to encourage you to migrate. Always get the proposed credit in writing and ensure it’s reflected as a discount or line item in the S/4HANA contract.
Q4: What if we end up under-licensing some users by mistake?
A: If you misclassify users (e.g. give someone a Functional license but they perform tasks requiring Professional), you are technically out of compliance, in an SAP audit, that could result in a demand that you purchase the proper licenses for those users (often at full list price, potentially with back maintenance fees). To avoid this, double-check roles and perhaps err on the side of caution for borderline cases. It’s also wise to run a test audit or use SAP’s License Audit Workbench in your S/4 system after a few months to see if any users appear misclassified. If you catch it early, you can adjust licenses (or adjust their access) before an official audit. The goal is zero surprises. Proper planning and ongoing monitoring are your safety net here.
Q5: How does the SAP S/4HANA “Digital Access” (indirect licensing) affect user licenses?
A: Digital Access is SAP’s model for licensing indirect usage of S/4HANA (e.g., when external systems create documents in SAP). It’s separate from named user licenses. In ECC, some customers had to license numerous “proxy” named users or risk compliance issues with interfaces. With S/4HANA, you can opt to license these indirect interactions by the documents they generate (e.g., 1,000 sales orders via an API). This means your human-named user licenses don’t have to cover those external systems. However, you need to either purchase a Digital Access document pack or ensure your contract conversion includes some allowance for this. It’s essential to analyze the number of documents your interfaces create (SAP’s Digital Access Estimation tool can help) and then determine whether to stick with classic user licensing for those interactions or opt for document-based licensing. Many companies negotiating S/4 deals in 2025 are bringing up Digital Access and securing better terms for it as part of the conversion.
Q6: What is Full User Equivalent (FUE), and do we need to worry about it?
A: FUE stands for Full User Equivalent, and it’s essentially a metric SAP uses for subscription licensing (like RISE or S/4HANA Cloud). Instead of buying 100 Professional and 500 Functional licenses, for example, you might buy a pool of FUEs. Different user types consume different fractions of an FUE (e.g., a Professional might be 1.0 FUE, a Functional 0.2 FUE, a Productivity 0.03 FUE – note these ratios are examples). The idea is to give flexibility in a cloud subscription: you just have X FUEs, and you allocate them among user types as needed. If you’re going the on-premise route with perpetual licenses, FUE doesn’t apply. But if you consider RISE or any subscription model, you’ll encounter FUEs. The key is to size it right – too few FUEs and you can’t cover all users, too many and you overpay. SAP will help calculate this, but it’s wise to verify their calculations and ensure they align with your usage projections.
Q7: Are there any deadlines or incentives associated with moving to S/4HANA that we should be aware of?
A: SAP has publicly stated that support for ECC will end in 2027 (with optional extended support for a fee beyond that). As that date approaches, SAP tends to reduce incentives for late movers. Currently (2024–2025), many customers can still receive decent incentives – for instance, credits on conversion, discounts on S/4 licenses, or favorable terms on extended ECC support – if they commit to S/4HANA now. After 2027, you lose leverage because staying on ECC is no longer an option (without incurring heavy support fees). So, there is an implied “soft deadline” to get a good deal. It’s not a single public offer, but your SAP account team will be more generous if you’re an early adopter. Also note that SAP has recently removed some legacy conversion SKUs from their price list, which effectively forces any ECC holdouts to adopt the newer licensing approach. In short, it’s better to act sooner rather than later from a commercial standpoint.
Q8: Can we phase our user license conversion, or do we have to do it all at once?
A: Technically, the contract conversion is usually a one-time event – you sign a new S/4 contract covering all users in scope. However, you can structure your migration in phases (e.g., finance may go live first with some users, followed by manufacturing later). During an interim period, you might run ECC and S/4 in parallel. SAP typically requires that once you convert the contract, any production use going forward is under the new licenses. However, they do allow some flexibility: for example, you might negotiate provisions to continue using ECC for a subset of users for a limited time (dual-use rights) during a phased go-live. You will be paying for S/4 licenses during that time, but SAP’s conversion policy often allows for the concurrent use of the old system. Ensure that this dual-usage right is included in your contract if you require a phased deployment. It ensures you won’t be out of compliance running ECC and S/4 side by side for migration.
Q9: How should we approach negotiating the S/4HANA contract to get the best deal?
A: Treat it like any major enterprise software negotiation – come prepared with data and options. Know your current license inventory and usage (so SAP can’t oversell you). Solicit an initial proposal from SAP, but also consider getting an independent pricing benchmark or a third-party expert’s input – this gives you a sense of the discount range to aim for. Don’t be afraid to push back on items that don’t make sense; for example, if SAP’s quote assumes 300 Professional users but your analysis says you need only 150, provide that rationale and ask for a revised quote. Use the competitive angle of RISE vs on-premise: even if you prefer one, getting quotes for both creates leverage (“We are evaluating a switch to RISE with subscription vs. keeping perpetual – how can you make the on-prem deal more attractive?”). Also, obtain commitments on things beyond just price – ask for training credits, extended support for ECC during the transition, or flexibility to adjust the license mix after a year if needed. These can often be negotiated in, especially if the deal helps SAP hit its targets.
Q10: What are the common pitfalls in license mapping and conversion that we should avoid?
A: A few pitfalls to watch for: (1) Assuming automatic conversion – thinking SAP will just swap your licenses evenly. In reality, you must proactively negotiate and choose what you need; nothing is automatic. (2) Overlooking indirect use – forgetting about non-human system access, which can bite you later if not licensed properly. (3) Stale user list – if you carry over a bunch of unused accounts into S/4, you’ll overpay and possibly invite compliance issues (an auditor sees 1000 licensed users but only 800 active – they’ll question the gap). Clean the list first. (4) One-size-fits-all licensing – giving everyone the same license type “for simplicity” is costly; you lose the benefit of the tiered model. (5) Ignoring future needs – maybe today you need no Professional users in a certain area, but next year you plan to roll out a new module – factor that future state in so you aren’t caught short. Avoiding these pitfalls comes down to thorough analysis and not rushing the licensing workstream. It’s as important as the technical migration, if not more, for your ERP program’s long-term success.
Read more about our SAP Advisory Services.
