SAP Cloud Hybrid Licensing: Navigating On-Prem and Cloud in One Environment

The Hybrid Reality Most SAP Customers Are Living

The idea that SAP customers migrate cleanly from on-premise ECC to a fully cloud-native S/4HANA environment in a single, well-scoped project is marketing copy, not operational reality. In practice, the path is years long, involves parallel running, and produces a period — often lasting three to five years — where the same employees access both on-premise and cloud SAP systems simultaneously.

Gartner data from end-2024 shows that only 39% of SAP's 35,000 ECC customers have licensed S/4HANA. The other 61% remain on ECC, most of them running at least some cloud modules — SuccessFactors for HR, Ariba for procurement, Concur for T&E, or BTP for integration. That is a hybrid estate by any measure, and it creates licensing complexity that SAP's standard commercial model was not designed to simplify.

The deadline that forces decisions is now less than two years away. EHP 6, 7, and 8 mainstream maintenance ends 31 December 2027. EHP 0–5 already ended on 31 December 2025. For customers on those older releases, the choice is now binary: pay significantly more for Extended Maintenance (at an uplift of approximately 2% of licence value above the standard 22% maintenance rate, reaching roughly 24%), or commit to a migration timeline.

Dual-Use Rights: The Contract Clause That Prevents Double-Billing

The most immediate commercial risk in hybrid SAP environments is double-counting of user licences. When your finance team accesses on-premise S/4HANA in the morning and SuccessFactors in the afternoon, SAP's standard position is that both accesses require separate licence entitlements — one from the perpetual on-premise agreement, one from the cloud subscription.

The protection against this is dual-use rights — a contractual provision that allows a user counted under an on-premise named user licence to also access defined cloud products without triggering a separate subscription seat. SAP does offer dual-use provisions, but they are not automatically included in either the on-premise licence agreement or the cloud subscription. They must be negotiated explicitly, documented in writing, and applied at the specific product level.

In practice, we regularly find clients running hybrid environments for two to four years before discovering their current contracts do not provide dual-use coverage for all the cloud modules their users are accessing. At that point, the back-dating exposure can be substantial. The correct time to negotiate dual-use rights is before the first cloud module goes live — not when the audit notice arrives.

Migration Parallel Running: Managing the Transition Window

Every SAP migration project includes a period of parallel operation — the legacy system runs alongside the new cloud environment for testing, parallel validation, or staged cutover. During this window, SAP's licence model, absent protective contract language, treats both systems as active and billable.

Negotiating a migration parallel-running allowance — typically defined as a fixed period (six to eighteen months) during which the legacy system's licence costs are not additive to the new cloud subscription — is essential for controlling total cost of ownership during transition. The longer your migration project, the more valuable this provision becomes. SAP Q4 deals (July–September, aligned to SAP's fiscal year end on 30 September) are the best time to negotiate this clause, as account executives have maximum discount authority and deal closure pressure in that window.

Important: the allowance must specify which systems are covered, which user populations benefit, and what happens if the migration runs past the defined window. Vague language — "reasonable transition support" — is not enforceable. Dates, product names, and user counts must appear in the signed amendment.

Integration Licensing: The BTP Boundary Problem

In hybrid SAP environments, BTP is the integration layer between on-premise and cloud. When an on-premise S/4HANA process creates a document that triggers a SuccessFactors workflow through an Integration Suite flow, multiple licence domains intersect at that transaction. The question of which licence covers the integration — and whether the data flow constitutes "indirect access" — is one of the most commercially significant in SAP licensing today.

SAP's Digital Access model, introduced from 2018–2019 as a settlement mechanism following the indirect access disputes that cost several large enterprises tens of millions of dollars, shifted the framework from named-user counting to document-based pricing. Under Digital Access, certain document types (purchase orders, sales orders, production orders) are licensed per-document rather than per-user, which can be significantly cheaper — or significantly more expensive — depending on your transaction volumes and existing licence position.

For hybrid environments, the critical governance question is: which integration patterns trigger Digital Access document counts, and are those counts covered by your existing subscription or on-premise entitlements? Most organisations do not have a complete answer to this question without a deliberate inventory exercise. The inventory should cover every integration flow between on-premise and cloud systems, map each to the relevant licence metric, and identify any gaps against current entitlements.

Co-Termination Strategy: One Renewal, Maximum Leverage

SAP customers running hybrid estates typically accumulated their contracts over many years — an on-premise agreement from 2012, a SuccessFactors subscription from 2016, an Ariba contract from 2018, a BTP agreement from 2022. These contracts have different renewal dates, different account teams, and different commercial terms. Each renewal is treated as a standalone event, which means SAP negotiates each in isolation with maximum advantage on its side.

Co-termination — aligning all major contract end dates to a single renewal window — reverses that dynamic. When your on-premise maintenance, S/4HANA cloud subscription, SuccessFactors, BTP, and Ariba agreements all renew in the same cycle, you are negotiating your total SAP relationship, not a series of individual line items. The leverage is substantially larger, the account team's discount authority is more likely to be exercised, and the commercial protections (price caps, dual-use rights, rollover provisions) are easier to embed consistently across all agreements.

The practical challenge is getting there. Contract end dates are rarely aligned by accident, and deliberately mis-aligning them is a known SAP commercial tactic — it ensures no single renewal window is large enough to justify customer-side advisory resources. Moving contracts onto a common cycle typically requires paying some short-term premium to extend shorter-term agreements. That premium is almost always recovered in the first co-term renewal through improved deal economics.

Maintenance Rates in Hybrid Environments

On-premise SAP contracts carry a standard maintenance rate of 22% of net licence value annually. For customers whose EHP releases fell under EHP 0–5, that mainstream maintenance already ended on 31 December 2025 — meaning any customer on those releases who has not migrated is now paying without the standard maintenance entitlement, or has entered Extended Maintenance at the elevated 24% rate.

For EHP 6, 7, and 8 customers, the December 2027 deadline is the relevant pressure point. SAP's Extended Maintenance option for 2028–2030 adds approximately 2% to the standard rate — a meaningful ongoing cost increase. Third-party maintenance providers such as Rimini Street offer support for ECC systems at rates up to 50% below SAP's standard maintenance, covering tax, legal, and regulatory updates. For organisations that have committed to a cloud migration but need to maintain ECC for three to five more years, third-party maintenance is a commercially rational bridge — and it removes SAP's maintenance revenue argument for withholding migration credits.

The fact SAP would prefer you not consider: migration credits decrease by approximately 10% per year of delay. A customer who migrates to S/4HANA in 2025 receives materially more credit against their new subscription than the same customer who waits until 2027. The financial case for moving faster is real — but SAP rarely leads with it in renewal conversations, because the credit also reduces the new subscription's first-year invoice.

Client Pattern: The Undocumented Hybrid

A European professional services firm we advised had been running an SAP hybrid estate for six years — on-premise S/4HANA for finance and logistics, SuccessFactors for HR, BTP for API management. No one had reviewed the combined contract position since the initial cloud modules were onboarded. When we mapped their entitlements against actual usage, we identified three categories of exposure: 847 SuccessFactors users who were double-counted in both the on-premise and cloud agreements, without dual-use rights; fourteen integration flows in BTP that generated Digital Access document counts not covered by the existing DAAP (Digital Access Adoption Programme) agreement; and an ECC legacy system running in parallel for one subsidiary that had never been formally decommissioned.

Total uncontracted exposure before our intervention: €2.1 million on a conservative basis. Resolution through negotiation — including retroactive dual-use rights, a DAAP right-sizing, and formal decommissioning of the legacy ECC instance — reduced the exposure to zero with no additional spend required. The firm had been at audit risk for years without knowing it.

What to Do Before Your Next SAP Renewal

The preparation steps for a hybrid SAP renewal are more extensive than for a single-product agreement. Before entering any commercial conversation with SAP, you should have completed: a full inventory of all on-premise and cloud SAP entitlements across every active contract, a user access mapping that identifies which employees access which systems and which licence type covers each access, an integration flow inventory that maps every BTP and third-party integration to the relevant licence metric, and a contract alignment review that identifies co-termination opportunities and dual-use gaps.

This preparation typically takes four to eight weeks for a mid-size enterprise. It is the difference between a negotiation where SAP controls the information and one where you do. Every engagement we conduct starts here. The findings consistently reveal exposures the client did not know existed and leverage the client did not know they had.

Redress Compliance provides SAP commercial advisory exclusively for buyers. We do not resell licences or take SAP referral fees. If your hybrid SAP estate has not had an independent commercial review in the last two years, it almost certainly contains avoidable cost.