RISE with SAP vs On-Premise: The Complete Enterprise Guide for 2026

The RISE with SAP vs On-Premise Decision: What SAP Doesn't Tell You

For twenty years, SAP built its commercial power on expensive, mission-critical on-premise installations. Large enterprises paid premium pricing for the privilege of running SAP in their own data centres—and SAP maintained that revenue model through aggressive auditing and contract complexity.

Then cloud economics changed. AWS, Azure, and Google Cloud proved that infrastructure costs collapse at scale. SAP watched this shift and made a strategic choice: if enterprises were going to move workloads to the cloud anyway, SAP would own that transition. The result is RISE with SAP—a bundled offering designed to lock customers into SAP's infrastructure, SAP's pricing, and SAP's support model for years.

This matters enormously. We've reviewed over 50 RISE proposals across financial services, manufacturing, and retail—and in nearly every case, the enterprise was making the decision based on incomplete information. SAP's sales motion emphasises simplicity and bundling, but obscures the true TCO calculation, contract lock-in mechanisms, and alternative paths.

What RISE with SAP Actually Includes

RISE bundles five components into a single contract, and understanding each is critical:

• S/4HANA Private Cloud: SAP's hosted, managed instance of S/4HANA. SAP owns the infrastructure, applies patches, manages backups. Your data is in SAP's controlled environment.
• Business Technology Platform (BTP) credits: A dollar value allocation of cloud services (analytics, integration, app development, AI). Sounds valuable until you realise 70% of allocated credits go unconsumed.
• Enterprise Support: SAP's premium support offering, non-negotiable in RISE contracts, priced at 22% of licence value annually. Includes SAP Response Time (not fix time).
• Infrastructure and hosting: SAP-managed data centre capacity, replication, and infrastructure resilience. You don't choose your cloud provider—SAP chooses for you.
• Implementation and migration: Typically billed separately, but migration costs routinely exceed licence costs by 2-3x, with SAP-preferred partners capturing most delivery.

Sounds comprehensive. And it is—until you realise SAP has bundled components that were previously separable into forced items, locked you into pricing escalators, and created switching costs so high that renegotiation becomes nearly impossible after Year 1 of a three-year contract.

The ECC End-of-Maintenance Deadline Is Real—But It's a Lever, Not a Trap

SAP will retire ECC (Enterprise Resource Planning Central Component) in December 2027. Support ends. Security patches stop. This is real.

But SAP uses this deadline aggressively in sales conversations. "Your ECC instances are ending. You must migrate to S/4HANA. RISE is the fastest path." Technically true. Strategically incomplete.

Alternative paths exist:

• Extended Maintenance: SAP offers extended maintenance beyond 2027, priced at 100% of licence value annually (versus 22% for RISE Enterprise Support). Expensive, yes—but you maintain flexibility.
• Third-party Maintenance: Rimini Street, Spinnaker, and others offer S/4HANA and ECC support at 30-50% of SAP's pricing. We've successfully negotiated third-party support into on-premise licensing models for clients saving 50-70% on annual support spend.
• Managed S/4HANA On-Premise: Some enterprises migrate to S/4HANA on their own infrastructure (AWS, Azure, or private cloud) and stack third-party support. Full control, lower costs, but more operational responsibility.

The 2027 deadline is real. The urgency SAP creates around it is sales strategy.

What RISE with SAP Actually Costs

Let's be concrete. SAP typically prices RISE offerings starting at $3-5M annually for a mid-market enterprise (500+ named users, multi-module implementation). Here's what that actually includes and what it doesn't:

Why BTP Credits Are a Red Herring

SAP markets BTP credits as "free" cloud capabilities bundled with RISE. Enterprises receive an allocation—often $500K-$1M depending on their licence size—and can theoretically access advanced analytics, low-code development, AI services, and integrations on the BTP platform.

Here's the reality: 70% of customers never fully consume their BTP credits. They're allocated but underutilised. Why?

• BTP requires upskilling. Your development team is trained on SAP legacy tooling, not modern cloud development frameworks.
• Integration into your existing SAP landscape requires specialised expertise. Off-the-shelf BTP solutions don't exist for most enterprise problems.
• The SAP ecosystem doesn't incentivise BTP consumption. SAP wins if you renew the RISE contract. Whether you use those credits is immaterial to their revenue.
• Unused credits don't roll over. Annual allocations reset. You're essentially paying for cloud services you'll never use.

From a negotiation standpoint, this is your leverage. When SAP quotes $800K in annual BTP credits, you can accurately counter that your enterprise will realistically consume 25-30% of that allocation. The surplus is vapour. It should either be removed from pricing or converted to a cash rebate.

The Pricing Escalator Trap

SAP's standard RISE contract terms include annual escalators. These are subtle, often buried in the Order Form's T&Cs:

• Licence escalation: 3-4% annually, compounding. On a $2M base, this is $60-80K added cost Year 2, $120-160K by Year 3.
• Infrastructure escalation: 4-7% annually, sometimes higher. SAP claims this reflects underlying cloud cost inflation (partially true) but also captures margin expansion as your use grows.
• Support escalation: Typically tied to licence escalation but can be negotiated separately. We've achieved flat-fee Enterprise Support over 3-year terms by bundling longer commitments.

The cumulative effect is insidious. Year 1 pricing looks reasonable. By Year 3, your annual bill has grown 12-20% compounded—and you're contractually locked. Renegotiation requires proving changed circumstances, which SAP rarely accepts.

Comparison Framework: RISE TCO vs On-Premise + Hyperscaler + Third-Party Support

Let's model a realistic enterprise scenario: 1000 named users, 5-module S/4HANA instance, Fortune 500 company.

The difference: $6.2M over three years. On a $14M total investment in on-premise, that's a 43% cost advantage.

This calculation assumes:

• You negotiate on-premise licensing at 20-22% discount (achievable for enterprises of this scale)
• You achieve a flat-fee licence agreement (no escalators) over the 3-year term
• You migrate to AWS (public cloud) and maintain your own operational responsibility
• You contract with Rimini Street for support (established provider, predictable SLAs)

Not every enterprise can execute this model. Some require SAP-managed infrastructure for compliance reasons. Others lack the operational maturity for independent cloud management. But for many Fortune 500 companies with internal cloud capabilities, this path is both viable and significantly cheaper.

On-Premise Isn't Dead — But It's Under Attack

SAP's commercial strategy depends on making on-premise SAP feel expensive, unsupported, and obsolete. The marketing message is clear: ECC is dying, on-premise is legacy, cloud is the future, RISE is inevitable.

This framing is commercially motivated and strategically misleading.

The Case for Staying On-Premise (With Guardrails)

On-premise SAP remains viable if you:

• Have the operational capability to manage infrastructure: Whether on-premise data centres or public cloud (AWS, Azure), you need teams capable of managing S/4HANA deployments, patching, capacity planning, and disaster recovery.
• Have contractual stability on licensing: SAP's list prices for on-premise are 5-10% lower than RISE bundled pricing, but escalators still apply. You need multi-year licensing agreements with negotiated, capped escalation (ideally flat fees for 3 years).
• Embrace third-party support: Rimini Street has supported S/4HANA since its 2015 release. Spinnaker specialises in hyperscaler S/4HANA deployments. Both are mature alternatives to SAP's Enterprise Support. The trade-off is different SLAs (they won't commit to SAP's official response times) but at 40-60% of SAP's cost.
• Invest in your cloud layer: AWS S/4HANA licensing is AWS-provided, highly flexible, and lower cost than SAP infrastructure. Azure hybrid benefit programs exist. GCP has SAP certification. The public cloud does infrastructure better than SAP's proprietary hosting.

ECC Extended Maintenance Options Beyond 2027

SAP's official messaging is that ECC support ends December 2027. Period. But nuance exists:

• SAP Extended Maintenance: SAP offers two years of extended ECC support (through 2029) at 100% of licence value annually. Expensive but buys time for S/4HANA migration if you're not ready in 2027.
• Third-party extended support: Rimini Street commits to supporting ECC beyond 2030 for customers who migrate off SAP support before official end-of-life. This is contractually binding in their agreements. The value is obvious: you migrate to ECC third-party support, get 5-10 year runways, and negotiate from strength.
• Hybrid migration approach: Some enterprises are running ECC in parallel with a phased S/4HANA implementation. ECC remains on extended maintenance or third-party support (cheap), while new modules and processes migrate to S/4HANA on independent infrastructure. This reduces migration risk and capital intensity.

How Enterprises Save 50-70% on Support Costs With Third-Party Maintenance

Here's the concrete math:

• SAP Enterprise Support: 22% of licence value. On a $2M licence, that's $440K annually. For 10 years, it's $4.4M.
• Rimini Street support: Typically 40-50% of SAP's pricing. On the same $2M licence, that's $176-220K annually. For 10 years: $1.76-2.2M.
• Savings over the lifecycle: $2.2-2.64M saved by switching to third-party support.

The catch: third-party support doesn't include SAP's official certified patches and response SLAs. Your team needs to validate patches before deployment. Response times are measured in business days, not SAP's official "severity 1 within 4 hours" model. Your operational risk profile changes.

For most Fortune 500 companies with internal SAP expertise, this trade-off is acceptable. You lose SAP's brand-name insurance; you gain financial leverage and operational independence.

RISE with SAP Contract Anatomy — What to Negotiate

RISE contracts follow a standard structure that's designed to be non-negotiable. The approach is: "This is the RISE product. You can negotiate price and some terms, but the framework is fixed." This is false. We've successfully renegotiated dozens of RISE Orders of Formation (Order Forms are the binding documents—the Master Agreement is boilerplate).

The Order Form and Its Hidden T&Cs

SAP's RISE Order Form is typically 40-60 pages of tables, schedules, and cross-referenced T&Cs. The key sections are:

• Section A: Licence: Named Users, usage metrics, any special use-rights. This is where FUE (Fully Utilized Equivalent) calculations appear. Negotiation point: Challenge the initial FUE assumption. SAP often over-estimates. Demand annual true-up mechanics that protect you from overages if actual FUE is lower.
• Section B: Services: Enterprise Support level, response times, and escalation procedures. Negotiation point: Negotiate lower support tiers for non-critical modules. Not every module needs SAP's highest SLA.
• Section C: Infrastructure: Data centre location, backup/disaster recovery SLAs, uptime guarantees, and escalation procedures. Negotiation point: This is where SAP's infrastructure SLAs are vague. Push for specific, measurable commitments: "99.95% uptime, measured monthly, with credits if missed." Standard RISE contracts often say "best efforts," which is unenforceable.
• Section D: Pricing: Licence fees, infrastructure fees, support fees, and escalation rates. Listed separately, which is good—it allows negotiation of each component independently.
• Section E: Term and Renewal: Initial term (typically 3 years), renewal options, and early termination provisions. Negotiation point: This is critical. Most RISE contracts auto-renew at escalated pricing unless you give 120 days' notice. Negotiate to push that to 180-360 days. Build in renewal price caps (e.g., "renewal pricing cannot exceed current pricing plus 5% annually"). Negotiate exit fees if you want to terminate early—they're often 50-100% of remaining contract value, which is economically punitive.

Negotiating BTP Credits vs Cash Value

SAP bundles BTP credits into RISE pricing at a stated "value," but that value is fictional because the credits are non-transferable, non-tradeable, and typically under-consumed.

Negotiation strategy:

• Request conversion of 30-50% of BTP credits to cash rebates. SAP will resist, but this is standard negotiation territory.
• Demand annual rollover of unused credits (most contracts forfeit unused credits annually). Even partial carryover reduces waste.
• If SAP won't budge on credit terms, demand credit value to be excluded from any price escalation calculations. If they escalate pricing 3% annually, that escalation should apply only to non-BTP components.
• Specifically exclude BTP credits from the FUE calculation. If your named users change, your BTP allocation should remain fixed.

Infrastructure SLAs and What's Actually Enforceable

This is where most enterprises get hurt. SAP's standard RISE infrastructure terms promise availability but define it vaguely. Typical language: "SAP will use commercially reasonable efforts to maintain 99.9% availability."

"Commercially reasonable efforts" is not enforceable. It's undefined. When SAP's infrastructure fails—and it will fail—you have no contractual recourse.

Negotiation approach:

• Define uptime precisely: "Uptime means S/4HANA instance is accessible from your primary access point. Measurement window is 0000-2359 UTC daily. Reported monthly. Excludes planned maintenance windows."
• Demand service credits: "If monthly uptime falls below 99.9%, you receive 5% of monthly infrastructure fees as credit. Below 99.5%, 10% credit. Below 99%, 15% credit."
• Protect against vendor-defined maintenance windows: SAP claims the right to patch, update, and maintain their infrastructure. In RISE contracts, they reserve maintenance windows but they're vague. Push for "planned maintenance windows cannot exceed 4 hours monthly, scheduled with 72 hours' notice, during agreed-upon low-activity windows."
• Demand disaster recovery SLAs: "In the event of data loss, SAP will restore from backups within 4 hours. Restore Point Objective (RPO) is 1 hour. Recovery Time Objective (RTO) is 4 hours." These should be specific, not "best efforts."

Exit Provisions and What Happens If You Want to Move Off RISE

SAP's lock-in mechanisms centre on exit costs. Here's how they work:

• Data export limitation: RISE contracts can limit how SAP exports your data when you exit. Standard terms might promise "reasonable cooperation" but don't specify timelines, formats, or SLAs. You could wait months for data export.
• Early termination fees: If you terminate early, SAP invoices for remaining contract value minus a small credit (typically 5-10%). On a $4M/year RISE contract, Year 2 early termination could cost $7-8M in exit fees.
• Infrastructure portability: RISE instances are on SAP's infrastructure. If you want to exit before your contract ends, you need SAP to export your database, license files, and configuration. This is deliberately slow in standard contracts.
• On-premise S/4HANA re-licensing: If you migrate from RISE to on-premise S/4HANA, you need to license on-premise S/4HANA separately. SAP doesn't credit your RISE licence payments toward that purchase. You're essentially paying twice.

Negotiation approach:

• Push for lower early termination fees (20-30% of remaining contract value is more reasonable than 50-100%)
• Demand data export SLAs: "SAP will export all customer data, licenses, and configuration within 30 days of termination notice, in mutually agreed-upon formats."
• Negotiate credit mechanics for migration: "If customer migrates to on-premise S/4HANA within 90 days of RISE contract end, SAP will credit 25% of Year 1 RISE licence cost toward on-premise licensing fees."
• Require API and integration stability: "SAP will maintain API stability for 12 months post-contract termination to allow customer data extraction and third-party tool integration."

Typical Discount Ranges Achievable (20-35% on List Price)

SAP publishes RISE list pricing, but it's not binding. Enterprise customers almost always negotiate:

• 20% discount: Standard for mid-market (500-1500 named users), achievable without external advisors.
• 25-30% discount: Typical for large enterprise (2000+ users) with competitive tension (considering on-premise, multiple cloud providers).
• 30-35% discount: Possible for Fortune 500 scale with multi-year commitment and strategic bundling across multiple SAP services.
• 35%+ discount: Rare, requires significant business leverage (e.g., major partner status, multi-entity global rollout, or genuine walk-away power).

Beyond pricing, these elements are also negotiable and often more valuable than discount percentage:

• Flat infrastructure fees over the 3-year term (vs. annual escalators)
• Reduced support tier for non-critical modules
• Capped FUE (named user count) for the term
• Lower early termination penalties
• Longer renewal price notification windows

The 10 Questions Every Enterprise Must Answer Before Choosing RISE

Before you sign a RISE contract, you must answer these questions decisively. If you can't answer clearly, you're not ready. We've published a full guide on this topic (key questions to ask SAP before choosing RISE), but here's the summary:

1. Do you have the operational capability to run on-premise or public cloud SAP? If yes, RISE is optional, not mandatory. If no, factor in the operational maturity building cost—it's significant.
2. What's your current SAP licence position? If you have perpetual on-premise licenses that don't expire until 2027-2028, compare the economics of staying on-premise vs. RISE migration carefully. Your sunk cost in those licenses is leverage.
3. What's your actual S/4HANA module footprint? Some modules require SAP's tightest support SLAs (Finance, Supply Chain). Others don't. This affects your Enterprise Support negotiation.
4. How much indirect access risk does your implementation carry? If you have complex, non-standard integrations to SAP, indirect access auditing in RISE is possible. This is a contract provision that requires careful review.
5. What's your realistic BTP consumption? Get external counsel to assess this—not SAP's. Most enterprises over-estimate. This drops the effective RISE value significantly.
6. Do you have genuine integration requirements that require SAP's proprietary cloud tooling? If your integrations are REST APIs, webhooks, or standard protocols, public cloud options are often better. BTP lock-in is overstated if you're not using it.
7. How much migration cost are you actually facing? Get a detailed migration assessment from someone other than SAP's SI partners. Migration often exceeds licence cost. This is the largest variable in the TCO equation.
8. What's your contract renegotiation timeline and leverage? Are you in an immediate crisis (2027 ECC deadline urgent) or do you have flexibility? Flexibility is negotiation leverage. Don't negotiate from desperation.
9. What are your compliance and data residency requirements? If you need data in specific geographies, RISE's infrastructure model matters. SAP's private cloud options are limited compared to public cloud.
10. What's your real 3-year financial capacity for this investment? RISE creates fixed, non-negotiable annual cost commitments. If your budget is variable or under pressure, on-premise + hyperscaler provides more cost control.

If you're unable to answer these ten questions with conviction, bring in external advisors. SAP's sales team will not challenge their own commercial proposition.

How Independent Advisors Evaluate RISE vs On-Premise

Our methodology for RISE advisory differs fundamentally from SAP's approach. We don't optimise for SAP migration. We optimise for enterprise economics. Here's our framework:

Step 1: Baseline Your Current Licence Position

Before evaluating RISE, you need to understand what you own today:

• Total perpetual licences (product, named user, FUE equivalents)
• Maintenance contracts (end dates, annual cost, escalators)
• Extended maintenance commitments (especially post-2027 for ECC)
• Any non-standard licensing agreements (loyalty discounts, volume pricing, renewal commitments)

This baseline is your economic anchor. SAP won't credit this value if you migrate to RISE—another reason not to migrate hastily.

Step 2: Model True TCO Across Scenarios

We typically model three scenarios:

• RISE with SAP: 3-year cost including list price, negotiated discount, BTP allocation (adjusted for realistic consumption), infrastructure, support, and escalators.
• On-Premise + Hyperscaler + Third-Party Support: Licence (perpetual purchase or multi-year subscription), cloud infrastructure (AWS/Azure/GCP), support (third-party or tiered SAP), and operational overhead.
• Hybrid: Partial migration (some modules RISE, others on-premise), staggered timeline, with extended maintenance for non-migrated components.

We model each scenario across 3, 5, and 10-year horizons. Short-term looks often favour RISE (bundled simplicity). Long-term usually favours on-premise/hyperscaler (lower escalation, operational control).

Step 3: Forensic Contract Benchmarking

We review anonymized RISE contract terms from similar enterprises and assess:

• Achievable discount ranges (what are comparable enterprises negotiating?)
• Escalator benchmarks (what are reasonable annual price increases?)
• Support tier patterns (which modules require which SLAs?)
• Exit provision precedents (what have other enterprises achieved?)

This benchmarking tells you if SAP's initial offer is genuinely competitive or if further negotiation is realistic.

Step 4: Operational Risk Assessment

We assess your ability to execute each scenario:

• If you choose RISE, can you effectively adopt it operationally? Do you have cloud-native SAP expertise?
• If you choose on-premise/hyperscaler, do you have internal cloud infrastructure expertise? Are you comfortable self-managing patches and upgrades?
• What's your disaster recovery readiness? RISE transfers DR responsibility to SAP (check the SLAs). On-premise requires you to own it.

TCO is only part of the equation. Operational feasibility matters equally.

What We've Seen in 50+ RISE Proposals: Patterns and Risks

Patterns we've consistently observed:

• Infrastructure over-sizing: SAP's initial RISE infrastructure recommendations are 120-150% of first-year needs. They justify this as "future-proofing," but it means you're paying for capacity you won't use for years. Demand right-sizing and reserve scaling for growth.
• BTP allocation as padding: SAP typically allocates BTP credits at 25-40% of anticipated licence value. This sounds generous until you realise 70% goes unconsumed. The allocation is inflated to improve the stated price-to-value ratio.
• Vague infrastructure SLAs: Nearly every RISE contract we review lacks specific, measurable uptime commitments. "Best efforts" language is standard. We always negotiate this to specific percentages with service credits.
• Auto-renewal surprises: Most enterprises don't realise their RISE contract auto-renews unless they give 120 days' notice. By the time they discover this, the renewal window has passed and they're locked in at escalated pricing. We push this to 180-360 days' notice minimum.
• FUE creep: Enterprises often commit to higher named user counts than they actually deploy. By Year 2, they're paying for 30-40% unused capacity. Demand annual FUE true-ups and protection against overage charges.

Average Savings From Proper Negotiation: 25-35%

Our clients typically achieve:

• Pricing discount: 20-30% off initial SAP quote (sometimes higher)
• Infrastructure cost reduction: 15-25% through right-sizing and SLA negotiation
• Support cost reduction: 10-20% through tiered support and module-specific SLAs
• Overall TCO impact: 25-35% reduction from SAP's initial proposal

This assumes you engage advisors early (pre-contract, not post-signature). Post-signature negotiation is harder and sometimes impossible.

Making the Right Decision for Your Enterprise

RISE with SAP is a legitimate strategic path for some enterprises. But it's not the only path, and it's not always the best path. Here's our decision framework:

Choose RISE If:

• You genuinely lack internal operational expertise for independent cloud infrastructure management and don't want to build it.
• You need SAP's BTP cloud capabilities as a core part of your strategic roadmap (not just allocated but actively consumed).
• You have specific regulatory or compliance requirements that SAP's private cloud uniquely satisfies (rare, but it happens).
• You can negotiate economics within 25-30% of the on-premise/hyperscaler model (making bundled simplicity genuinely cost-effective).
• You prefer fixed, predictable annual costs over variable operational overhead.

Choose On-Premise + Hyperscaler + Third-Party Support If:

• You have or can build internal cloud infrastructure expertise.
• You want to avoid multi-year contract lock-in and maintain negotiation flexibility.
• You're comfortable with third-party support trade-offs (good SLAs but different from SAP's official certifications).
• You want to reduce total cost of ownership significantly (30-50% savings are achievable).
• You need data residency flexibility or multi-cloud capability.

Consider a Hybrid Approach If:

• You're mid-migration from ECC to S/4HANA and can't accelerate the timeline.
• Some of your business units are genuinely cloud-ready while others require extended on-premise runway.
• You want to stagger investment across multiple years instead of a large upfront migration.
• Your business is volatile and you want cost optionality (hybrid lets you adjust which workloads are on RISE vs on-premise).

The 5 Factors That Determine the Right Path

Ultimately, the decision rests on five factors:

1. Operational capability: Can you manage cloud infrastructure? Be honest about your internal expertise gap.
2. Financial flexibility: Do you have budget flexibility (on-premise) or do you need fixed costs (RISE)?
3. Timing pressure: Is the 2027 ECC deadline genuine urgency or sales pressure? This drives your negotiation leverage.
4. Strategic technology needs: Do you genuinely need BTP cloud services? If not, RISE's cloud components are wasted.
5. Total cost of ownership: Model all scenarios. Let the math inform the decision, not SAP's pitch.

Frequently Asked Questions