The decision rule: the metric follows the contract — classic named-user categories live on perpetual on-premise paper, the Full User Equivalent is the unit of SAP’s cloud subscriptions, so you choose a metric by choosing a deployment, not from a menu. The lever you actually control is classification: an advanced-use user draws thirty times the FUE pool of a self-service user, so how your real population maps into categories moves the bill more than any discount you will negotiate.
Published 8 January 2026 · Last reviewed 3 March 2026
The classic named-user model is the one ECC estates and perpetual on-premise S/4HANA contracts run on: every person who touches the system needs a named-user license in a fixed category — Professional for full operational use, Limited Professional (re-cut as Functional Use in S/4HANA paper) for narrower operational roles, Employee or Productivity Use for self-service tasks, Developer for workbench access — each with its own price point and rights, bought perpetually and carried with annual support of roughly a fifth of license value on the whole estate. The categories are silos. A surplus of Employee licenses cannot cover a shortfall of Professionals; reshaping the estate means a purchase, not a reshuffle. Alongside the users sit the engines — packages metered on orders, revenue, cores, payslips and a hundred other metrics — licensed separately, plus digital access for indirect use.
The Full User Equivalent is the metric SAP’s cloud subscriptions replaced all of that with. You subscribe to one pool of FUEs; user categories convert into the pool at fixed ratios — one advanced-use user consumes a whole FUE, core-use users convert at five to one, self-service users at thirty to one, and a developer weighs in at two FUEs each. The pool is fungible: if a hundred advanced users become eighty advanced and a hundred core, the same FUE count absorbs the change without re-papering. The unit travels across RISE and GROW alike, though what a FUE buys differs between the private and public editions — that comparison has its own guide.
This guide is general information about SAP user metrics as they stand in 2026, not licensing or legal advice for your situation; ratios and program terms are set by your contract, which governs. It names no firms; the firm directory lists SAP-capable advisors with balanced pros and cons, listed, not ranked.
The FUE conversion table is short enough to memorise and consequential enough to audit. One advanced-use subscription equals one FUE; five core-use subscriptions equal one FUE (0.2 each); thirty self-service subscriptions equal one FUE (a thirtieth each); one developer equals two FUEs. Run the spread: moving a single user from the advanced box to the self-service box changes that user’s draw on the pool by a factor of thirty, and moving a thousand users does it a thousand times. No negotiated discount approaches the leverage of the classification exercise itself — which is why the sizing stage of any cloud deal, not the discount stage, is where SAP licensing advisory work earns its keep.
Classification cuts the other way under classic paper. There the categories are priced rather than ratioed — a Professional license costs multiples of an Employee license, with support compounding the difference annually — and the historic failure mode is well documented: organisations bought Professional licenses defensively, because the category definitions are usage-based and ambiguity felt dangerous in audit season. Decades of that habit left estates where the Professional count reflects fear rather than work actually performed. That inheritance matters enormously at conversion time, because a 1:1 mapping of Professional into advanced-use FUE imports the over-classification into the subscription — permanently, at subscription rates.
Note also what neither metric covers. Engines under classic contracts keep their own metrics, and cloud bundles have their own add-on catalogue; digital access for machine-created documents is a live line item in both worlds. A user-metric comparison that ignores the non-user line items is half a comparison.
| MECHANIC | CLASSIC NAMED USERS | FUE |
|---|---|---|
| License shape | Perpetual purchase plus annual support on the estate | Term subscription; no perpetual fallback |
| Unit | One license per person, per fixed category | One blended pool; categories draw it down at ratios |
| Categories | Professional, Limited Professional / Functional, Employee / Productivity, Developer | Advanced (1), core (0.2), self-service (1/30), developer (2 FUE) |
| Fungibility | None — categories are silos; reshaping means buying | Pool is fungible across the mix within the subscribed total |
| Engines & add-ons | Separate packages on their own metrics | Much sits in the bundle; add-on catalogue priced separately |
| Compliance mechanism | Measurement and audit against entitlements | Consumption governance; gaps surface at true-up and renewal |
| Price protection | License is sunk; support rises slowly on a large base | Whatever renewal caps were drafted at signature |
| Exit position | Perpetual rights persist if support lapses (with consequences) | Subscription lapses; converted licenses were retired |
The rows that decide real outcomes are the last two. Classic paper’s price protection is structural — the license is bought, and only support moves — while a subscription’s only protection is the renewal cap somebody remembered to negotiate. And the exit row is asymmetric in a way buyers consistently underweight: a classic estate that drops support still owns its licenses, whereas a converted estate handed its perpetual rights in as credit. The fallback is not suspended; it is gone.
Classic named users remain rational for estates staying on-premise on purpose: ECC systems riding mainstream maintenance to end-2027 (with extended maintenance to 2030 at a premium, and a private-edition transition option that can carry ECC commitments further), and perpetual on-premise S/4HANA where the organisation wants asset ownership, depreciation treatment, or independence from subscription renewal cycles. A well-run perpetual estate with disciplined user classification is often the cheaper position over a five-to-seven-year model — a factual modelling outcome, not a recommendation — and the RISE vs on-premise guide works through that arithmetic.
FUE is not optional once the destination is cloud: every RISE / SAP Cloud ERP Private and GROW / public-edition contract is FUE-metered, so the real question is never “which metric do I prefer” but “on what classification mapping, at what credit, with what flexibility do I enter the pool.” The pool’s fungibility is a genuine operational advantage for organisations whose user mix shifts — seasonal workforces, M&A activity, shared-services consolidation — because re-profiling inside the pool needs no commercial event. SAP, for its part, has been explicit with investors that the perpetual business is being wound down over time; that is the vendor’s strategic direction stated factually, and it belongs in any plan with a ten-year horizon.
The mixed estate is the common reality: classic ECC paper in the core, a FUE subscription somewhere in the group, engines and digital access on both sides. Keeping one coherent picture of entitlements across the two metrics is unglamorous effective-license-position work, and it is what makes the eventual conversion negotiable rather than forensic.
Most organisations meet this comparison at a contract conversion, and the mechanics deserve plain statement. Your perpetual licenses are retired into the subscription in exchange for a negotiated credit — they do not wait in escrow for your return. The credit policy has stepped down over the years since conversions began, so the percentage on offer is a point-in-time commercial fact to verify in your own paper, not a published entitlement. And the classification mapping is negotiated, not mechanical: ECC Professional maps naturally toward advanced use, Limited Professional toward core use, Employee toward self-service — but “naturally” is doing silent work in that sentence, because the historic Professional over-count makes the natural mapping an expensive one.
The negotiation sequence that protects the buyer runs classification first, commercials second: re-profile the user population against real usage data before SAP’s sizing exercise does it on defaults, contest the mapping while it is still a draft, then negotiate ramp, credit, renewal caps and add-on scope on the resulting FUE count. Run it in the other order and every discount is computed on an inflated base. Renewal protections matter doubly here because the conversion burned the fallback: caps, term length and exit assistance drafted at signature are the only ones that will exist. This is the core territory of SAP license negotiation engagements, and on the compliance side the discipline shifts from audit-season measurement to continuous consumption governance — classification drift, not license counts, is what surfaces at true-up with money attached.
Mapping Professional to advanced 1:1. The single most expensive default in SAP cloud sizing. Historic Professional counts encode defensive buying; profile actual usage and let the data assign the category.
Importing shelfware into the pool. Named users who left the company, duplicated accounts, dormant IDs — a classic estate carries them harmlessly as sunk cost; a FUE baseline carries them as recurring subscription. Clean the population before it is counted.
Forgetting developers weigh double. At two FUEs each, a development bench converts at sixty times the rate of self-service users. Check who genuinely needs workbench access before the count freezes.
Assuming the bundle absorbed the engines. Some classic engines map into cloud-bundle scope; others persist as add-ons, and digital access remains its own conversation. Reconcile line by line rather than assuming the FUE figure is the whole bill.
Treating the vendor’s sizing output as a finding of fact. It is an opening position produced on defaults that are rational for its author. Audit the mapping with your own usage data — or have someone independent do it, which is its own selection decision.
Negotiating the discount before the denominator. A generous percentage off an over-classified FUE count is a poor trade against an honest count at standard terms. Sequence matters more than headline generosity.
The two FUE-metered programs compared →
The migration both metrics sit inside →
The non-user line item on both sides →
How to pick the firm for this work →
Firms that do classification and sizing work →
Every field guide on the site →
A Full User Equivalent is the blended user metric of SAP’s cloud ERP subscriptions (RISE, GROW and S/4HANA Cloud generally). Different user categories convert into the FUE pool at fixed ratios: one advanced-use user consumes a full FUE, five core-use users share one FUE, thirty self-service users share one FUE, and a developer consumes two FUEs. You subscribe to one pool of FUEs and your user mix draws it down at those rates.
Classic named users are perpetual licenses bought per person in fixed categories — Professional, Limited Professional (Functional in S/4HANA terms), Employee or Productivity use, Developer — each with its own price and rights, plus annual support on the whole estate. The categories are not fungible: surplus Employee licenses cannot cover a shortfall of Professionals. FUE replaces those fixed boxes with a single pool that any user mix can draw against at the conversion ratios.
On-premise S/4HANA remains available as perpetual licensing with named-user categories and annual support, and large installed bases still run ECC on classic paper while mainstream maintenance runs to end-2027 (extended options to 2030, and the private-edition transition option can carry ECC further). SAP’s commercial energy, however, is behind the FUE-metered cloud subscriptions, and SAP has told investors it intends to wind down the perpetual business over time — a strategic direction worth factoring into any long-horizon plan.
In a RISE-style contract conversion your perpetual licenses are retired in exchange for a negotiated credit against the subscription. The rights do not sit in escrow: if you later exit the subscription, the perpetual fallback is gone. The credit policy has also stepped down over the years, so the terms on offer are a point-in-time fact to verify, not an entitlement. Both the credit and the user-classification mapping are negotiated, and both deserve independent scrutiny before signature.
Neither metric is inherently cheaper; the outcome depends on your user mix and how honestly it is classified. A population mapped 1:1 from Professional licenses into advanced-use FUE will usually look expensive, because many historic Professional assignments were defensive over-licensing rather than a reflection of real usage. Re-profiling users into core-use and self-service categories before sizing — not after — is where FUE economics are made or lost.
Digital access — licensing for documents created by non-SAP systems — exists in both worlds. Under classic paper it is a separate line item alongside named users and engines; under cloud subscriptions a document allotment is typically part of the negotiated bundle. Conversion does not make the question disappear: the allotment in a FUE contract is a negotiated number that should be checked against your actual integration landscape.
Deciding how a real user population should map between fixed named-user categories and a blended FUE pool is exactly what an SAP licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.