Introduction: Why ECC-to-S/4HANA License Mapping Is Complex and Risky
SAP's migration from ERP Central Component (ECC) to S/4HANA is not merely a system upgrade—it is a complete restructuring of how users are licensed and costs are calculated. Many organizations assume their legacy Professional User licenses will map directly to S/4HANA Professional Use, or that their Limited Professional User pool will remain the same size and cost. This assumption is dangerous and costly. In my experience defending over 80 indirect access disputes, I have seen SAP use the migration moment as a reset button, reclassifying users into higher tiers, applying new measurement methodologies, and presenting organizations with 30–50% cost increases as simply "the cost of modernization." This guide walks you through the precise mapping rules, the FUE (Full User Equivalent) calculation methodology, and the negotiation strategies that protect your budget during this transition.
The Legacy ECC License Landscape: What You Have Now
SAP's legacy ERP licensing model centered on discrete user types, each tied to specific functional roles and access rights. Understanding your current footprint is the first step toward a defensible migration plan. The primary ECC user types are Professional User, Limited Professional User, Employee Self-Service (ESS) User, Warehouse User, Developer, and Portal User, each carrying different price points and access profiles.
Professional User (PU) is the most expensive tier in ECC and grants full access to all SAP modules and transactions. A Professional User can navigate any business process—finance, procurement, supply chain, production—without restriction. This tier carries the full license cost and is typically reserved for core business users who require broad system access. Organizations often oversize this category because the user types were historically assigned by department rather than by actual transactional need.
Limited Professional User (LPU) represents an intermediate tier designed to reduce costs. LPU licenses restrict access to a defined subset of transactions and modules. For example, a Limited Professional User might have access to procurement and supplier management but not to production planning or financial consolidation. In my audit experience, many organizations allocated LPU licenses to regional procurement teams, finance business partners, and demand planners. The cost of an LPU is typically 50–60% of a Professional User, making it attractive for cost optimization—if you can actually enforce the role restrictions.
Employee Self-Service (ESS) User is the lowest-cost tier and is restricted to HR and payroll transactions. ESS users typically submit leave requests, view payslips, and update personal information but cannot access transactional business processes. This user type is heavily used in large organizations with thousands of employees and is the most cost-efficient tier in the ECC model. ESS licenses cost roughly 20–30% of a Professional User.
Warehouse User (WU) and Developer licenses are specialized roles. Warehouse Users access only the warehouse management and inventory movement transactions, making them cost-effective for supply chain teams in logistics-heavy organizations. Developer licenses grant access to development and testing systems and are not counted against production license costs (though they still require explicit naming and audit trails).
The critical point: in ECC, user types are defined by access restrictions built into the system's authorization matrix. A user is classified as Limited Professional if and only if their authorization profile blocks them from certain transactions. If a user can access every transaction—because someone granted broad access "just in case"—that user becomes a Professional User, regardless of job title or stated intent.
S/4HANA's Simplified (But Costlier) Tier Structure
S/4HANA consolidates the legacy user types into a three-tier model: Professional Use, Functional Use, and Productivity Use. On the surface, this looks like simplification. In practice, it is a reset that often drives users into higher tiers.
Professional Use in S/4HANA is the equivalent of ECC's Professional User—unrestricted access across all modules and processes. However, the licensing rules have tightened. Professional Use is now more strictly enforced through role-based access control (RBAC) and cannot be granted to users who access only a subset of the system. If you have 100 users who technically access "professional" functions but could be restricted to narrower roles, S/4HANA's licensing audit will flag them as needing Professional Use licenses unless you have a formal role definition, access control list, and audit trail proving the restriction.
Functional Use is S/4HANA's new intermediate tier, designed to replace Limited Professional. Functional Use grants access to a defined set of processes—procurement, payroll, asset management—but not the full suite. The cost is nominally 40–50% of Professional Use, making it attractive. However, SAP's definition of Functional Use is stricter than ECC's Limited Professional. Functional Use is tied to specific predefined roles and processes; if a user's access profile crosses multiple process domains, SAP will argue that the user needs Professional Use instead.
Productivity Use is the lowest-cost S/4HANA tier and is roughly equivalent to ECC's ESS User. Productivity Use is restricted to light transactions like leave requests, expense reporting, and read-only business intelligence access. ESS users in ECC typically map cleanly to Productivity Use, but only if their access truly is limited to self-service. If an ESS user has been granted any transactional modification rights, they may be reclassified to Functional or Professional Use.
The critical difference: S/4HANA licensing is measured by actual user transactions and role assignments at migration time, not by the license category you purchased in ECC. SAP will reclassify based on what users actually access, not on your historical license structure.
How SAP Maps ECC to S/4HANA: The Reclassification Process and Its Traps
The migration process begins with a user access review—SAP calls this the "License Reconciliation Report" or similar. SAP's tools scan your ECC system, extract user authorization profiles, and analyze which transactions and modules each user accessed in the past 12 months. This analysis is then mapped to S/4HANA's three-tier model. This is where the trap springs.
SAP's measurement is conservative and vendor-favorable. The company errs on the side of categorizing ambiguous users into higher tiers. Here's why: if a user in ECC had access to 15 transactions across finance, procurement, and supply chain (even if they only regularly used 3 of them), SAP's tool will recommend Professional Use in S/4HANA unless you can prove that access is unnecessary. The burden of proof shifts to you. In ECC, you were licensed for what you purchased. In S/4HANA, you must prove you don't need each access right.
One common trap: Limited Professional Users in ECC often become Professional Use in S/4HANA. Why? Because many organizations used LPU loosely. An LPU license was purchased, the user had access to, say, procurement and inventory, but was also granted "read-only" access to financial reports or supply chain analytics. In S/4HANA's stricter model, that read-only access counts as crossing into the financial domain, disqualifying the user from Functional Use and pushing them into Professional Use. Organizations discover this during the reclassification process and face sudden cost increases.
Another trap: Role-based access control (RBAC) is now mandatory. In ECC, you could manage user access via a mix of individual role assignments and custom authorizations. S/4HANA demands that every user be mapped to a predefined role or role combination. SAP has published hundreds of predefined roles, but these roles are "as is"—you cannot modify them without losing support. If a user's needs don't fit neatly into a predefined role, SAP will assign them to the next-higher tier role, which is often Professional Use. You then face a choice: accept the higher cost or redesign your business process to fit the role.
The legal language matters. SAP's licensing terms state that users are licensed based on "the maximum access rights granted or available to the user," not based on their stated job title or their actual daily transaction volume. SAP auditors measure this by running a Transaction-Code Analysis (t-code scan): which transaction codes can user X access? If user X can access 150 t-codes, they get Professional Use in S/4HANA. If they can access 35 t-codes but those 35 span multiple domains, they likely require Professional Use. Only if their t-codes are confined to a narrow, predefined functional domain do they qualify for Functional Use.
I have seen organizations lose 20–30% of their Limited Professional User population to this reclassification. An organization with 500 LPU licenses discovers that 120 of them must be converted to Professional Use, adding $150,000–$200,000+ to annual license costs (depending on list price and discount). And this happens after you have already committed to the migration and invested in S/4HANA implementation.
Full User Equivalents (FUE) Explained: How S/4HANA Cloud and RISE Measure Users
If you are deploying S/4HANA on-premises, you license by user tier: you pay for X number of Professional Use licenses, Y number of Functional Use, and so on. If you are moving to S/4HANA Cloud or RISE with SAP, the licensing model shifts to Full User Equivalents (FUE). Understanding FUE is critical because it is where many organizations discover their true cost.
The FUE model converts all users into a single metric. Each user type is assigned a weight, and the total FUE count determines your license cost. The standard FUE formula is approximately:
Total FUE = (# Professional Users × 1.0) + (# Functional Users × 0.5) + (# Productivity Users × 0.3)
For example, if you migrate with 200 Professional Use, 300 Functional Use, and 1,000 Productivity Use users, your FUE count is: (200 × 1.0) + (300 × 0.5) + (1,000 × 0.3) = 200 + 150 + 300 = 650 FUE. RISE with SAP or S/4HANA Cloud pricing is then applied per FUE per month, meaning a higher FUE count directly increases your cloud subscription cost.
The trap: when SAP reclassifies your users during migration, your FUE count almost always increases. If SAP reclassifies 100 Limited Professional users as Professional Use instead of Functional Use, you lose the 0.5 multiplier benefit and instead pay at the 1.0 multiplier. This adds 50 FUE to your count. At $100–$150 per FUE per month (typical RISE pricing), that is $60,000–$90,000 per year in additional cloud costs.
Furthermore, the FUE formula is not publicly disclosed in full detail. SAP publishes the rough weights, but the actual calculation may include adjustments for concurrent users, floating licenses, and application-specific access. Always request SAP to provide your detailed FUE calculation in writing before signing a RISE agreement.
S/4HANA Changes the License Baseline: The Critical Reset
This is the most important section of this article. When you migrate to S/4HANA, SAP resets your license baseline. Your ECC license mix does not carry forward as-is.
In ECC, your baseline is defined by what you purchased: 250 Professional Users, 300 Limited Professional Users, and 2,000 ESS Users. When you renew ECC, SAP audits you against that baseline. If you are 5% over, you pay for the overage; if you are under, SAP may not aggressively push you to increase. The baseline is fixed.
In S/4HANA, SAP recalculates the baseline based on measured user access at the time of migration. SAP's tools scan your ECC system, categorize every named user by their actual access rights, and create a new baseline in S/4HANA that reflects that measured state. This measured baseline then becomes your new license baseline. If SAP's tools determine that you have 450 Professional Use equivalents (after reclassification), that becomes your new baseline—even if you previously licensed for 250 Professional Users.
SAP uses sophisticated measurement: DDLC analysis (Digital Direct License Check), which captures every access event. SAP's DDLC metric measures the number of digitally distinct users accessing the system within a month, not the number of named licenses purchased. This is critical. If you have 250 named Professional User licenses but your actual DDLC shows 280 distinct users accessing with professional privileges, you have a 30-user shortfall. SAP will demand payment for those 30 users when you migrate, or offer a grace period followed by enforcement.
Many organizations do not discover the true impact of the baseline reset until they receive SAP's migration proposal. A common scenario: organization purchased 200 Professional User licenses in ECC (to save cost, thinking they would enforce limited access), but in reality, 280 users have been granted professional-level access over the years. When migrating to S/4HANA, SAP's DDLC measurement reveals the true count of 280, and the organization is presented with a baseline of 280 Professional Use users in S/4HANA. The organization then faces a choice: pay for 80 additional licenses immediately, or renegotiate.
The message is stark: conduct a user access review before you begin S/4HANA migration negotiations. Know your true user count and access distribution. If you do not right-size your footprint before SAP's measurement tool is activated, you will be measured against a higher baseline and will pay for that excess throughout your S/4HANA contract.
How to Conduct a Pre-Migration User Access Review
A User Access Review (UAR), also called a License Access Report or LAW report in SAP context, is your most powerful tool for controlling costs during migration. The goal is to align your actual user access with your licensed positions before SAP's reclassification tool measures you against a new baseline.
Begin by extracting user master data from your ECC system. Run SAP reports SUIM (User Information System) to capture all named users, their assigned roles, and the transactions they have accessed in the past 12 months. This report shows not just who is licensed, but who is active and what they actually do. You will often discover dormant accounts, shared logins, and users with access far beyond their job requirements.
Next, map each active user to the correct S/4HANA tier. Create a spreadsheet with columns for user name, current ECC license type, recommended S/4HANA tier, justification, and business owner sign-off. For each user, ask: does this user truly need access to their current transaction set? If a user needs only procurement and vendor management, can they be restricted to a Functional Use role? If a user is in HR and only uses ESS features, should they be a Productivity Use user?
The critical step: document and enforce the access restrictions within ECC before migrating. Remove unnecessary transactions from user roles. Delete dormant accounts. Consolidate duplicate user IDs. Separate shared login accounts into individual named accounts. Each of these actions reduces your user count and pushes borderline users into lower tiers. SAP's measurement tool will then measure the cleaned-up state, resulting in a lower baseline in S/4HANA.
Organizations that perform a thorough UAR before migration typically achieve a 10–20% reduction in their measured user count. This translates to $100,000–$300,000+ in savings over a 3–5 year S/4HANA contract, depending on user count and SAP pricing.
Negotiation Strategies for the Conversion
When SAP presents its migration proposal, the negotiation window is typically 4–8 weeks. The proposal will include a conversion credit—usually 70–80% of your current ECC license value, applied as a discount on your first-year S/4HANA fees. Conversion credits are designed to sweeten the deal and offset part of the baseline-reset shock. However, these credits are time-limited and decreasing.
As of April 2026, SAP is offering 70–80% conversion credits to organizations migrating within this calendar year and next. By 2027, as ECC reaches mainstream end-of-support, these credits will drop to 50–60%. By 2028, they may be lower still or disappear entirely. The first negotiation point: maximize your conversion credit by accelerating your migration timeline if you are on the fence about go-live date.
The second negotiation point: dispute SAP's reclassification of borderline users. If SAP has classified 50 users as Professional Use when your business case supports Functional Use, push back. Request that SAP provide a detailed list of the t-codes that drove the Professional Use classification. Often, the list includes read-only reports or rarely-used administrative transactions that can be removed from the user role without impacting their ability to do their job. By removing 5–10 transactions per user, you can move users down tiers and reduce your FUE count.
The third negotiation point: split your migration into tranches. Instead of moving all users to S/4HANA on day one, propose a phased migration. Migrate your core 200 "essential" professional users in phase 1, while the remaining users stay on ECC maintenance mode (which is less expensive than an active ECC deployment). In phase 2, 6–12 months later, migrate the remaining users. This approach spreads the reclassification and baseline-reset pain across two cycles and gives you time to optimize access in phase 1 before phase 2 is measured. SAP may resist a long phased approach, but a 6–12 month phase 2 is usually negotiable.
The fourth negotiation point: lock in pricing for the credit period. SAP will offer a conversion credit for, say, 24–36 months. Ensure that this credit is locked in at a fixed discount percentage and not eroded by list price increases. A 75% conversion credit means you pay 25% of list price for year one. If SAP's list prices increase by 5% per year (typical), a fixed credit locks that discount in. Without a fixed credit, the discount may be applied to a rising list price, reducing its real value.
The fifth negotiation point: negotiated pricing for your measured baseline. If SAP's reclassification increases your baseline from 250 to 320 Professional Use equivalent users, ask SAP to apply a one-time "baseline reconciliation discount" on the excess 70 users for years one and two of your S/4HANA contract. SAP sometimes agrees to this to smooth the migration shock. The discount might be 30–40% off list price for those 70 users for 24 months, giving you time to optimize headcount or redeploy those users to lower-cost tiers.
Key Mistakes to Avoid
Based on my experience defending licensing disputes, here are the mistakes I see most often during SAP migrations:
Mistake 1: Skipping the User Access Review. Organizations eager to migrate immediately deploy S/4HANA without conducting a UAR first. SAP then runs its measurement tool against the "as-is" state—bloated with excess access, dormant accounts, and uncontrolled permissions—and calculates a high baseline. The organization then discovers that their new S/4HANA license cost is 40–50% higher than expected. A UAR takes 4–8 weeks but saves hundreds of thousands of dollars.
Mistake 2: Accepting SAP's first reclassification without challenge. SAP's measurement tools are sophisticated but not perfect. The tool errs on the side of conservatism (high tiers) to protect SAP's revenue. If you receive a reclassification report showing 400 Professional Use users, and your business case supports 320, request that SAP break down the classification by user and transaction set. Often, you can justify moving 30–50 users to lower tiers through business process adjustments or access restrictions.
Mistake 3: Conflating on-premises S/4HANA with RISE with SAP pricing. On-premises S/4HANA is licensed per user tier (you buy 200 Professional Use licenses). RISE with SAP is licensed per FUE. These are different measurement models with different cost implications. A 30% reduction in user count might save you $100,000/year in on-premises licensing but only $50,000/year in RISE (because Functional and Productivity users are weighted at 0.5 and 0.3 FUE). Understand which model applies to your deployment before negotiating.
Mistake 4: Forgetting about support costs. SAP support is typically 22% of your net license value annually. If your S/4HANA license baseline is $1 million, support is an additional $220,000/year. When calculating your conversion credit and the value of migrating, include support costs in your total cost of ownership. A 75% conversion credit on licenses looks attractive until you realize that support fees are not discounted and will grow with your license count.
Mistake 5: Not locking in conversion credit terms in writing. Conversion credits are verbal offers until they are written into your contract. Ensure that your conversion credit percentage, the term of the credit (is it 24 months or 36 months?), and how it is applied (lump sum discount or per-license reduction?) are all spelled out in the master agreement. I have seen organizations negotiate a 75% conversion credit only to discover in the signed contract that it applies only to year one, not years two and three.
Conclusion: Protect Your Baseline Before Migration Begins
The S/4HANA migration is an opportunity to right-size your user base and align licensing with business reality. It is also a moment of vulnerability: SAP's measurement tools are precise, the baseline reset is real, and the cost impact can be severe. Organizations that conduct a thorough user access review, understand the FUE metric, and negotiate conversion credits aggressively emerge with sustainable licensing costs. Organizations that rush into migration without preparation often pay 30–50% more than necessary.
The path forward is straightforward: (1) conduct a user access review in your current ECC system to understand your true user count and access distribution; (2) clean up excess access and dormant accounts before SAP's measurement tool is activated; (3) request that SAP provide a detailed reclassification report and challenge borderline user assignments; (4) negotiate a substantial conversion credit with a long term window; and (5) lock in these terms in your master agreement before signing.
Ready to navigate your SAP migration with confidence?
Redress Compliance's SAP licensing experts have defended 80+ indirect access disputes and guided hundreds of migrations.