SAP S/4HANA introduces new user types, new metric models, new deployment options, and a 2027 ECC maintenance deadline that SAP is using to accelerate signings. Understanding S/4HANA licensing before you commit — whether to RISE or perpetual licences — is the difference between a right-sized S/4HANA estate and one that costs 30–50% more than it should. This guide gives you the independent analysis SAP's sales team won't.
SAP S/4HANA is not just a technology upgrade from ECC. It represents a fundamental change in how SAP licenses its core ERP. The licence model, user types, deployment options, and commercial structures are all different — in ways that consistently result in higher licence costs for enterprises that migrate without independent analysis.
The core change is this: SAP moved from a broadly defined user type model in ECC (where Professional, Limited Professional, and Employee covered most scenarios) to a more granular, role-based approach in S/4HANA, while simultaneously changing how certain third-party and automated access is charged via the Digital Access model. The result is that many ECC users who were legitimately classified as Limited Professional or Employee get re-evaluated at Professional rates during migration — unless you push back with evidence.
S/4HANA licences are available under two commercial models. Perpetual licences are purchased outright and supported via the annual 22% Enterprise Support fee. RISE with SAP subscriptions wrap S/4HANA licences, infrastructure, and support into a single annual fee. Both models use the same underlying user type framework — understanding that framework is the foundation of any S/4HANA licensing analysis.
S/4HANA user classification determines the per-user licence cost. Getting users into the right category is the single most impactful cost lever available during and after migration. SAP's USMM tool and commercial team will default to the highest applicable category unless you actively challenge and document each user's actual usage pattern.
| User Type | Cost Level | Typical Use Cases | Key Characteristics |
|---|---|---|---|
| Professional | Highest | Power users, finance controllers, advanced procurement, complex reporting authors | Unrestricted access to all S/4HANA functionality. SAP defaults users here if any Professional-level transaction has been executed — even infrequently. |
| Functional | High | Warehouse managers, plant maintenance leads, advanced production users | Access to a defined set of functional areas. Less than Professional but restricted to specific module domains. Available in specific modules only. |
| Limited Professional | Medium | General business users, order processors, goods receivers, standard reporting users | Restricted access to core S/4HANA functionality within defined limits. 3–5× cheaper than Professional. Most SAP landscapes have more Limited Professional users than their current ECC classification suggests. |
| Employee | Low | ESS/MSS users, time entry, expense submission, basic self-service portal users | Restricted to Employee Self-Service and Manager Self-Service functionality only. Cannot access any transactional SAP processes. Often overlooked — many portal users qualify but are not classified here. |
| Developer | High | ABAP developers, technical configuration specialists, BTP developers | Authorised for technical development activities. Should be limited strictly to individuals who actively develop in the system — not all IT staff. |
| Productivity | Low | Read-only reporting consumers, dashboard viewers, data extraction users | Read-only access to defined data sets. Enterprises with large reporting populations — particularly in manufacturing and supply chain — often have significant Productivity reclassification opportunities. |
The most important insight from this table: the cost difference between Professional and Limited Professional is 3–5×. In a landscape of 5,000 users, reclassifying 1,000 from Professional to Limited Professional can reduce annual licence maintenance by millions. This reclassification work should happen before migration, not after — because your post-migration user population becomes the baseline for all future measurements.
Our SAP licence optimisation team performs forensic user classification analysis across your ECC landscape, identifying which users genuinely require Professional licences and which can be legitimately moved to lower-cost categories before your S/4HANA migration baseline is set.
Book a User Classification Review →Migrating from ECC to S/4HANA is not a one-to-one licence transfer. SAP's migration tools and commercial team will produce a mapping that appears technically justified — but which almost always results in an inflated S/4HANA licence baseline. Understanding where this inflation occurs is critical.
SAP's ECC-to-S/4HANA mapping tool defaults users who have executed any Professional-level transaction to Professional in S/4HANA. This includes users who ran one report per quarter. Without a detailed activity review, these users all come across at Professional pricing — often increasing your licence bill by 40–60% before any new functionality is added.
Some ECC landscapes used FUE (Full Use Equivalent) licences that entitled unlimited user count within a defined usage band. The FUE model does not exist in S/4HANA. Enterprises migrating from FUE must restructure to Named User pricing — a migration that, without careful planning, results in a significant step-up in annual licence cost.
ECC sold many licences on a module basis (e.g., SAP ERP HCM, SAP ERP Financials). S/4HANA pricing is primarily user-based, not module-based. Users who accessed module-specific functionality in ECC must be re-evaluated against the S/4HANA user type model — sometimes resulting in a lower cost, sometimes higher, depending on the breadth of their actual access.
Third-party integrations that created SAP documents in ECC (orders, deliveries, invoices) may trigger Digital Access charges in S/4HANA if not properly scoped before migration. Your pre-migration interface inventory must explicitly map every integration against the Digital Access document type list before you sign an S/4HANA agreement.
The ECC-to-S/4HANA licence mapping exercise should be completed independently, before engaging SAP's commercial team in pricing discussions. The output of this analysis is your negotiating baseline — and it almost always shows a materially lower user count and lower licence cost than SAP's own mapping tool produces. Our S/4HANA migration licensing service delivers this analysis as a structured, evidence-based report that you can take directly into contract negotiations.
S/4HANA is available in several deployment configurations, each with distinct licensing implications. Choosing the wrong deployment model — or failing to understand the licensing differences — is a common and costly mistake.
Perpetual licences, customer-managed infrastructure, full customisation capability. You own the software and pay 22% Enterprise Support annually. This model offers the most flexibility and, over a 7–10 year horizon, typically the lowest total cost of ownership — but requires significant internal infrastructure capability.
Best for: Organisations with strong internal IT, high customisation needs, or specific data sovereignty requirements.
Subscription-based, SAP-managed infrastructure on hyperscaler of your choice. Identical S/4HANA functionality to on-premise, but operational responsibility transferred to SAP. Same user type model applies. Annual subscription replaces perpetual + maintenance. Full details in our RISE with SAP guide.
Best for: Organisations seeking managed infrastructure without full cloud-SaaS constraints.
Multi-tenant SaaS. Restricted customisation. Mandatory twice-yearly updates. Role-based user types may differ from Named User model. Typically lower per-user cost than Private Edition, but significant process standardisation required. Best for greenfield deployments or subsidiaries.
Best for: New deployments, subsidiaries, organisations adopting SAP standard processes.
Many enterprises will run multiple S/4HANA deployment types simultaneously — on-premise for core operations, RISE Private Edition for subsidiaries, and Cloud Public Edition for greenfield entities. Each deployment type may have different user type definitions, and SAP's measurement tools will consolidate all of these into a single ELP. Understanding how your hybrid landscape is measured across deployment boundaries is essential to avoiding unexpected compliance exposure.
SAP announced that mainstream maintenance for SAP ECC will end in 2027, with extended maintenance (at a premium) available to 2030 for eligible customers. This is a real deadline with real implications. It is also being used by SAP's commercial team as the primary driver to accelerate RISE and S/4HANA signings — often without the buyer fully understanding their options.
No new SAP Notes, no legal/regulatory updates, no new functionality. Customers remaining on ECC after this date have no supported path to patches for legal changes, tax code updates, or security vulnerabilities under the standard maintenance contract.
SAP offers extended maintenance beyond 2027 for qualifying customers, at a premium above the standard 22% fee. Third-party maintenance providers (Rimini Street, Spinnaker Support) also offer alternatives that can reduce costs while extending the operational life of your ECC landscape.
Third-party maintenance is a legitimate option for organisations that need to extend their ECC runway while planning an S/4HANA migration on their terms, not SAP's accelerated timeline. Our support cost reduction advisory covers the full range of options available.
SAP's sales team will use the 2027 deadline to create urgency and reduce your negotiating timeline. A decision made under deadline pressure — without proper licence mapping, TCO analysis, and negotiation preparation — will almost always cost more than one made with adequate preparation time. The 2027 deadline is real, but a 2025 or 2026 signing is not necessary to meet it. Plan strategically, not reactively.
The most significant and frequently underestimated cost in any S/4HANA migration is the dual-running cost: the period during which you are paying both your existing ECC maintenance fees and your new S/4HANA licence or RISE subscription. For complex landscapes, this period typically runs from 18 months to 3 years.
If your annual ECC maintenance cost is £3M and your new S/4HANA subscription is £4M, your dual-run period costs £7M per year. Over 24 months, that is £14M in licence costs before you go live on S/4HANA. This parallel running cost is almost never modelled accurately in the initial S/4HANA business case and consistently creates budget overruns at the programme level.
SAP offers "migration credits" — a percentage of your existing ECC licence investment applied against your S/4HANA commitment. The credit percentage, applicability, and terms are all negotiable. Enterprises that accept SAP's standard credit terms leave money on the table. Independent analysis of your entitlement under SAP's credit programme consistently produces better outcomes than accepting SAP's initial offer.
Beyond the dual-run cost, the S/4HANA migration programme itself requires significant investment in custom code remediation, interface rebuilding, data migration, and end-user training. None of these costs appear in SAP's licence proposal — but they all affect the total cost of your S/4HANA transition. See our S/4HANA migration licensing service for a comprehensive approach to modelling all of these costs before you commit.
Our S/4HANA migration licensing team builds an end-to-end model of your S/4HANA programme costs — user type mapping, dual-run cost, migration credits, Digital Access exposure, and RISE vs perpetual comparison — giving you the facts you need to negotiate from strength.
Get Your S/4HANA Cost Model →Licence optimisation for S/4HANA is not a one-time exercise at migration. It is an ongoing programme of user classification review, access rights management, and contract position maintenance that should run throughout the lifecycle of your S/4HANA deployment. The enterprises that manage SAP licence costs most effectively are those that treat their licence position as a live asset — not a static number agreed at contract inception and forgotten until the next audit.
Before defining your S/4HANA user baseline, perform a forensic cleanse of your ECC user population. Remove users who have been inactive for 12+ months, reclassify users whose actual usage pattern does not justify Professional, and identify portal and self-service users who should be classified at Employee level. This single exercise typically reduces S/4HANA licence cost by 20–40%.
S/4HANA's Fiori-based interface and simplified data model offer an opportunity to redesign user roles from scratch — restricting access more precisely to what each job function actually requires. Narrowing the transaction footprint of users who currently have broad access reduces their classification tier and your licence cost.
Establish a formal user provisioning process that maps each new SAP user to a specific licence type at the point of onboarding. Without governance, licence types drift upward over time — access is granted for one-off needs and never revoked, accumulating as Professional user counts that inflate your next USMM measurement.
Build a full inventory of every third-party integration that touches S/4HANA and map each against SAP's Digital Access document type list. Interfaces that create chargeable documents should be contractually covered before go-live. Interfaces that do not create chargeable documents should be documented as explicitly excluded from Digital Access charges.
Maintain your own Effective License Position on at least a quarterly basis — do not wait for SAP's audit notification to understand your compliance position. Enterprises that run internal ELP reviews proactively consistently perform better in formal SAP audits. See our SAP licence compliance service for a managed approach to ongoing ELP maintenance.
Every S/4HANA contract renewal is an opportunity to right-size your licence position. If your actual user population has decreased since the last contract, negotiate downward. If you have built a cleaner licence position through user classification work, use this as evidence in renewal negotiations to push back on SAP's escalation proposals.
No — and this is the most important licence cost lever in any S/4HANA migration. Many users classified as Professional in ECC were assigned that type because they had access to Professional-level transactions, not because they used them regularly or at all. A forensic review of actual transaction usage in ECC typically reveals that 30–50% of Professional users can be legitimately reclassified to Limited Professional in S/4HANA, producing a material reduction in annual licence cost.
S/4HANA's Limited Professional user type is broadly equivalent to the ECC Limited Professional, but with differences in which specific transactions and Fiori apps are accessible. The exact scope of each user type is defined in SAP's Price List and the supplementary licence metrics document attached to your contract. These definitions change with each SAP pricing update — reviewing them against your actual user population at each contract renewal is important.
If you are still running ECC after 31 December 2027 without an extended maintenance arrangement, you will be out of mainstream support. Your system will continue to operate technically, but you will receive no new SAP Notes, no legal/regulatory updates (critical for payroll, tax, and compliance-sensitive processes), and no security patches. Most enterprises cannot accept these risks for their core ERP platform, which is why planning your S/4HANA migration — or an extended maintenance strategy — needs to begin immediately if it hasn't already.
Yes. Third-party maintenance providers like Rimini Street and Spinnaker Support offer ECC maintenance contracts that cover security patches, regulatory updates, and break-fix support at fees typically 50% below SAP's 22% Enterprise Support rate. Third-party maintenance is a legitimate strategy for extending your ECC runway while completing a properly planned S/4HANA migration. However, it does affect your relationship with SAP and should be considered as part of a comprehensive commercial strategy rather than a purely cost-driven decision.
Not necessarily. Over a 5–7 year horizon, perpetual licences plus infrastructure costs typically produce a lower TCO than RISE — but the comparison depends heavily on your infrastructure capability, your existing cloud strategy, and the specific terms you negotiate. RISE's value is in operational simplification and vendor consolidation, not primarily in cost reduction. Independent TCO modelling — covering both options with your actual licence requirements — is essential before making this decision. Our RISE advisory team builds this model for enterprises at the proposal stage.
The audit mechanics are similar — SAP uses USMM to measure named user consumption, and LAW to consolidate across your landscape. However, S/4HANA audits also increasingly include Digital Access document counting and BTP consumption analysis. The range of potentially chargeable activities is wider in S/4HANA than in ECC, which makes pre-audit independent analysis even more important. For a full guide to the SAP audit process, see our SAP audit guide.
Before you sign an S/4HANA contract — perpetual or RISE — get an independent analysis of your user types, migration costs, and negotiation position. Our S/4HANA migration licensing team works exclusively for buyers. No SAP affiliation. No reseller agenda.