SAP S/4HANA License Models – Perpetual vs Subscription (CapEx vs OpEx)

SAP S/4HANA License Models

Introduction: A Strategic Choice

Choosing how to license SAP S/4HANA is a strategic decision that will influence your IT budget and flexibility for years. CIOs and CFOs need to align on whether a capital expenditure (CapEx) approach or an operating expenditure (OpEx) approach fits the company’s goals.

SAP offers multiple licensing options – from traditional on-premise perpetual licenses to cloud-based subscriptions (and even hybrid combinations) – each with different cost profiles, risks, and benefits.

This choice has taken on urgency as SAP’s legacy ERP (ECC) nears end-of-support in 2027 and the push to S/4HANA accelerates.

The model you select will shape your total cost of ownership (TCO) and your ability to adapt to change. It’s not just about cost – it affects who manages the infrastructure, how upgrades occur, and how much control you retain versus outsourcing to SAP.

In this post, we’ll compare perpetual vs. subscription vs. hybrid licensing models for S/4HANA. We’ll examine the mechanics (CapEx vs OpEx impact), pros and cons of each model, cost considerations over a 5-year horizon, and common pitfalls to watch out for (like lock-in or paying twice). Read our ultimate guide to S/4 Hana Licensing.

We also provide an FAQ and some expert recommendations at the end. By understanding these trade-offs, you can choose the model that best aligns with your company’s financial strategy and IT roadmap.

Perpetual Licensing (CapEx Model)

Perpetual licensing means you buy the S/4HANA software outright as a capital asset.

You pay a large one-time license fee and then an annual maintenance fee (typically ~20% of the license price) for support. You run the system on your own infrastructure (on-premise or hosted), and you have indefinite usage rights.

This model has a high upfront cost, but ongoing yearly costs (maintenance and IT operations) are relatively fixed. Over a long period, owning the license outright can be more cost-effective than paying annual subscriptions.

• Pros:
  • Ownership & control: Full control over the system and upgrade schedule. Licenses never expire (even if you stop maintenance, you can keep using the last version).
  • Long-term savings: If used for many years, the total cost can be lower than subscriptions. After the upfront investment, annual costs (support) are predictable.
• Risks:
  • High upfront cost: Large CapEx outlay on day one. Requires confidence in long-term use and executive buy-in.
  • Infrastructure burden: You manage servers, storage, backups, and upgrades. This adds internal cost and effort, and delaying upgrades to save money can leave you on outdated software.
  • Shelfware: Overbuying licenses leads to unused (sunk-cost) licenses you can’t easily resell. Excess capacity = wasted money.
• Negotiation Tips:
  • Price and support: Push for a steep license discount (SAP often gives 50%+ on big deals) and lock in the maintenance rate (around 20% with no increases). If you’re upgrading from ECC, negotiate credit for your existing licenses to offset the S/4HANA cost.
  • Use cloud as leverage: Even if you plan to stay on-prem, getting a quote for SAP’s cloud option can give you bargaining power. Show SAP you have alternatives – it often leads to a better deal on the perpetual license.

Subscription Licensing (OpEx Model)

Subscription licensing means you rent the software and pay as you go. Instead of a big upfront spend, you pay a recurring subscription fee (OpEx) – usually annually – that covers the software, infrastructure (cloud hosting), and support. SAP (or a cloud provider) manages the system for you.

This model has a very low startup cost and offers agility (you can get up and running quickly, and scale usage up or down as needed). However, you never own the license – if you stop subscribing, you lose access.

Over many years, the total cost can end up higher than a one-time purchase, since the payments are continuous.

• Pros:
  • Lower upfront: Minimal CapEx. Easier to start without a large purchase; costs are spread over time.
  • All-in-one service: Cloud subscription includes infrastructure and updates. SAP handles maintenance and keeps the system up-to-date.
  • Scalable: Easier to increase capacity or users as needed (within contract terms) without new hardware investments.
• Risks:
  • Higher long-term TCO: Over many years, subscription fees can add up to more than a one-time purchase + maintenance would have. You’re essentially renting indefinitely.
  • Vendor lock-in: If you stop paying, you lose the software. You depend on SAP’s cloud to run your business, which can be a risk if you ever want to change.
  • Renewal surprise: After the initial term, subscription costs can rise. Auto-renewals or growth in usage (e.g., more users, increased data) may increase fees if not capped.
• Negotiation Tips:
  • Right-size & flexibility: Only pay for what you need. Negotiate the contract to match your actual user counts and usage, with the ability to adjust if your needs change. Avoid over-committing up front.
  • Price protection: Set caps on price increases and define renewal terms now (no big surprises after the initial term). Also, if you’re moving from on-prem, use your existing investment as leverage – ask for credits for the licenses/maintenance you will drop.
  • Exit provisions: Make sure you understand the exit process. Negotiate data export support and a clear wind-down plan so that if you ever need to leave the service, you can do so without crippling your business.

Hybrid Licensing (Mix of CapEx and OpEx)

Hybrid licensing refers to the use of a combination of perpetual and subscription models. For example, a company might keep its core S/4HANA system on-premise with perpetual licenses, but use a cloud subscription (e.g., RISE with SAP) for certain extensions or regional deployments.

This approach lets you balance CapEx and OpEx – continuing to leverage owned licenses where it makes sense, while taking advantage of cloud flexibility in other areas.

It’s often used for phased migrations (gradually moving to S/4HANA) or to handle diverse business unit needs.

The trade-off is increased complexity: you must manage both types of contracts and be careful to avoid duplicative licensing (paying twice for the same users or functionality).

• Pros:
  • Flexible deployment: Use on-premise for some systems and cloud for others, depending on what’s most cost-effective or strategic for each case.
  • Phased migration: You can migrate in stages. Legacy systems can run in parallel with new cloud systems during rollout, reducing risk.
  • Optimize costs: Match workloads to the best model (e.g., keep stable, high-use processes on owned licenses, use subscriptions for variable or new needs) to minimize total costs.
• Risks:
  • Complex management: Two models mean two sets of contracts and metrics to track. License compliance and administration become increasingly complex.
  • Overlap/double cost: If you’re not careful, you might pay for the same thing twice (e.g., user licenses on-prem and again in the cloud). Without negotiated dual-use rights during transition, costs can overlap.
• Negotiation Tips:
  • Dual-use period: During migration, negotiate a period where you can run both the old (on-prem) system and the new (cloud) system without extra charges. This prevents paying double while you transition.
  • Selective conversion: Don’t convert more licenses to subscription than necessary. Get credit for any on-prem licenses you give up, and consider keeping some licenses out of the cloud deal as a safety net. This way, if plans change, you still hold some perpetual rights.

5-Year Cost Comparison

For example, imagine a deployment that costs about the same under either model over five years.

If an on-premises S/4HANA with perpetual licenses costs, say, $25 million (including a $10M license plus five years of support and infrastructure), a cloud subscription for five years might also total around $25 million (spread evenly as $5M per year).

The difference is timing and what happens after Year 5.

The perpetual approach front-loads a lot of cost but then tapers off (you own the asset and just pay maintenance), whereas the subscription keeps going at the full rate. By Year 6 and beyond, the owned license scenario would likely become cheaper than continuing to subscribe.

The takeaway: evaluate costs over the long run, not just the first year.

Depending on your assumptions, the breakeven point for subscription vs. perpetual is often around 4–6 years.

Always project the Total Cost of Ownership over a multi-year period (and include things like infrastructure, support, and potential price increases) to make an informed decision.

Common Pitfalls to Avoid

• Lock-in: Once you commit to a subscription or cloud bundle, it can be difficult and expensive to switch providers or revert to on-premises later. This heavy vendor dependency means you must negotiate flexibility upfront and have a contingency plan in place.
• Double payment: During a transition, some companies mistakenly pay twice for the same software – for example, continuing maintenance on old licenses while also paying for a new S/4HANA subscription. Avoid overlapping costs by carefully timing your move and utilizing conversion credits or dual-use agreements.
• Auto-renewal: Cloud subscriptions (and even annual maintenance) can auto-renew under existing terms if you don’t actively renegotiate or cancel in advance. Mark your calendar for renewal dates – otherwise, you might get stuck with an unwanted renewal or a price increase you could have contested.

Understand what drives costs, SAP License Cost Drivers – Named Users vs. Engines in S/4HANA.

Perpetual vs. Subscription vs. Hybrid

FAQ

Q: We have SAP ECC licenses. Do we need to pay all over again for S/4HANA?
A: Not necessarily. SAP offers a conversion program for existing customers. You can get credit for your ECC licenses when moving to S/4HANA (whether you choose new on-prem licenses or a subscription like RISE). In short, you trade in your old licenses for a discounted price on the new ones, so you’re not paying twice. Be sure to negotiate that credit and time the switch so you don’t overlap paying for maintenance and subscription.

Q: Is SAP going to stop offering perpetual licenses?
A: SAP is heavily pushing cloud subscriptions, but S/4HANA on-premise (perpetual licensing) is still available as of 2025. There’s no official plan to eliminate on-prem licenses yet. However, SAP’s focus (and most new features and incentives) is on the cloud side, so we may see the balance continue to shift toward subscription models in the coming years. Right now, you have a choice, but the trend is cloud-first.

Q: Which model costs less over time, perpetual or subscription?
A: It depends on the time frame. A perpetual license can be cheaper over a long period (for example, beyond 5 years) because after the upfront investment, you only pay maintenance. A subscription is usually cheaper in the short term (no big upfront cost, and it includes infrastructure). Many organizations find that around the 4-6 year mark, the cumulative costs start to favor the perpetual model. It’s crucial to run the numbers for your situation to find the break-even point.

Q: What if we decide to leave the cloud and go back on-prem later?
A: Switching back can be difficult. If you converted your licenses to move to the cloud, you likely surrendered those perpetual rights. That means to go back on-prem, you’d have to purchase new licenses or negotiate some return of rights, which can be costly. Additionally, migrating from a cloud environment is a major project. In practice, very few companies revert once they’ve moved to S/4HANA cloud, so try to make the right choice upfront. If you are concerned, consider maintaining a minimal on-premises system as a backup or obtain contractual clarity on exit options.

Expert Recommendations

1. Perform a multi-year TCO analysis: Before committing, model out 5, 10 years of costs for each option (licenses, maintenance, subscriptions, infrastructure). This reveals the true long-term cost difference and break-even point of CapEx vs. OpEx for your scenario.
2. Match the model to your financial strategy: Decide based on your company’s approach to spending. If you prefer capital investment and full control (and can support the necessary infrastructure), perpetual may be a suitable option for you. If you want to preserve cash upfront, treat ERP as a service, and stay agile, a subscription might align better. The licensing model should support your broader IT and business objectives.
3. Use SAP incentives and avoid double-paying: If you’re an existing customer, leverage SAP’s conversion credits and promotions. Plan your migration timing so you’re not paying for old and new systems at the same time. A carefully managed transition (for example, discontinuing maintenance as the subscription begins) can result in significant cost savings.
4. Negotiate flexibility in the contract: Whichever model, build in protections. For perpetual deals, negotiate maintenance terms (caps, the right to drop unused licenses, etc.). For subscriptions, negotiate the ability to adjust usage, cap price increases at renewal, and define exit options (so you’re not trapped). In a hybrid scenario, insist on agreed dual-use periods and credit for any licenses you trade in.
5. Keep leverage by exploring alternatives: Don’t go into negotiations with only one scenario. Get quotes for both on-prem and cloud versions (and even consider third-party support or delaying purchase). When SAP knows you have options, you’ll have a stronger negotiating position and likely better terms. Be willing to walk away or change course – it will help you secure a more favorable deal.

Read about our SAP Advisory Services.

Do you want to know more about our SAP Services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit