A comprehensive analysis of SAP's ECC-to-2033 transition option — how the private cloud subscription bridge works, what it costs, who qualifies, how it compares to staying on-premises or migrating to S/4HANA via RISE, and the contractual, licensing, and strategic implications that CIOs must address before the 2030 deadline.
SAP's new ERP Private Edition Transition Option allows select ECC customers to continue running SAP ECC (ERP Central Component) with full support until year-end 2033 — three years beyond the 2030 extended maintenance deadline and six years beyond the 2027 mainstream support end date.
This isn't a simple support extension for on-premises ECC. It's a new subscription service — ECC running as a managed private cloud service under RISE with SAP. Customers must migrate their ECC environments to the HANA database and into SAP's private cloud infrastructure by end of 2030 to qualify. From 2031–2033, SAP provides continued security patches, legal updates, and stability fixes — at a premium subscription price.
For the thousands of enterprises that cannot complete their S/4HANA migration by 2030, this transition option is a potential lifeline. But it comes with conditions, costs, and strategic consequences that demand immediate attention — even though the deadline is years away.
| Timeline | Event | Implication |
|---|---|---|
| End of 2027 | ECC mainstream support ends | No new functionality; security-only patches. Standard maintenance continues at current rates. |
| 2028–2030 | ECC extended maintenance period | Security and legal patches only. ~2% uplift on maintenance fees. Must be on latest EHP. |
| End of 2030 | ECC extended maintenance ends; on-premises ECC goes unsupported | No patches, no support. Running unsupported ECC creates security, regulatory, and operational risk. |
| By end of 2030 | Transition option deadline — ECC must be on HANA in SAP private cloud | Requires RISE contract, HANA migration, and cloud lift-and-shift before this date. |
| 2031–2033 | ECC supported under transition option (private cloud) | Security, legal, and stability patches. Premium subscription pricing. SAP manages infrastructure. |
| End of 2033 | Transition option ends — must be on S/4HANA | No further ECC extensions planned. S/4HANA migration is mandatory by this date. |
Key takeaway: The transition option is a strategic last resort for large, complex SAP environments that genuinely cannot migrate to S/4HANA by 2030. It buys time but doesn't avoid the migration — it postpones the deadline to 2033 while adding cloud subscription costs and requiring significant infrastructure changes (HANA migration + cloud move) by 2030. CIOs must decide now: accelerate S/4HANA, plan for the transition option, or evaluate third-party alternatives.
The transition option is not universally available to all ECC customers. Understanding what it is — and what it isn't — is essential for strategic planning.
What it is: A managed cloud subscription service that runs your existing ECC environment in SAP's private cloud (typically on a hyperscaler like Azure, AWS, or GCP under SAP's RISE framework). SAP manages the infrastructure, database, and application layer. You continue running ECC — not S/4HANA — with SAP providing security patches, legal updates, and stability fixes through 2033.
What it is NOT: It is not a simple extension of on-premises ECC support. You cannot stay on your own servers and hardware running ECC and receive SAP support after 2030. The transition option requires moving to SAP's managed cloud. It is also not a blanket offer — SAP has indicated that only core ECC components are covered. The full SAP Business Suite 7 (including some industry solutions and add-ons) may not all qualify after 2030.
| Requirement | Detail | Implication |
|---|---|---|
| RISE with SAP contract | Must sign RISE agreement (or equivalent private edition contract) by 2028 | Commits you to SAP's cloud subscription model and terms |
| HANA database migration | ECC must run on SAP HANA (not Oracle DB, DB2, SQL Server, etc.) by 2030 | Database migration project required if not already on HANA |
| Cloud lift-and-shift | ECC must be running in SAP's managed private cloud by end of 2030 | Infrastructure migration; data centre exit for ECC workloads |
| Core ECC only | Only core ECC components are confirmed eligible; some Business Suite 7 add-ons may not qualify | Industry solutions, bolt-ons, and legacy modules need separate assessment |
| Premium pricing | 2031–2033 subscription at higher rate than standard RISE pricing | Significant cost increase over current maintenance fees |
| S/4HANA migration obligation | Must migrate to S/4HANA by end of 2033 — no further ECC extensions planned | The migration is postponed, not avoided |
Who should consider this option:
The transition option is designed for large, complex enterprises with heavily customised ECC environments — organisations running dozens of ECC instances across multiple countries with deep integrations, custom ABAP code, industry-specific processes, and regulatory requirements that make S/4HANA migration a multi-year programme. For these organisations, even with aggressive migration planning, not all ECC systems will be on S/4HANA by 2030.
The transition option is not designed for organisations that are simply procrastinating on S/4HANA. SAP has made clear that this is a premium offering for specific circumstances — not a convenient alternative to migration planning.
What IT Leaders Should Do Now — Transition Option Assessment
Assess your S/4HANA migration timeline honestly: Will all ECC systems be migrated by 2030? If the answer is "no" or "uncertain," the transition option must be part of your planning.
Inventory your ECC landscape: Which ECC components, industry solutions, and add-ons are in scope? Not everything qualifies for the transition option.
Understand the HANA prerequisite: If your ECC runs on Oracle, DB2, or SQL Server, a HANA database migration is required before 2030 — a significant project in itself.
Engage SAP early: The RISE contract negotiation for the transition option is complex. Starting in 2025–2026 gives you maximum negotiating leverage and preparation time.
Every ECC customer now faces three strategic paths. The right choice depends on your migration readiness, budget, customisation complexity, and risk tolerance.
| Factor | Stay on ECC (On-Prem) | Transition Option (ECC in Cloud) | RISE with SAP (S/4HANA) |
|---|---|---|---|
| Support horizon | Ends 2030 (extended maintenance) | Extended to 2033 in SAP private cloud | S/4HANA supported to 2040+ |
| Pricing model | Perpetual licences + annual maintenance (~22%) | Cloud subscription (premium rate 2031–33) | Cloud subscription (RISE) |
| Infrastructure | Customer-managed (full control) | SAP-managed private cloud (hyperscaler) | SAP-managed cloud |
| Migration required | None — continue as-is | HANA migration + cloud lift-and-shift by 2030 | Full S/4HANA migration (brownfield or greenfield) |
| Customisation preserved | All existing customisations retained | ECC customisations preserved (same codebase) | Customisations must be re-evaluated / re-built for S/4HANA |
| Post-2030 risk | No patches; security/regulatory exposure | Patches and support through 2033 | Full support on current platform |
| Vendor lock-in | Low — own licences; can use third-party support | High — committed to RISE subscription and SAP cloud | High — cloud subscription dependency |
| Cost trajectory | Stable (maintenance fees + own infrastructure) | Increasing (subscription + premium + HANA migration) | Variable (subscription replaces maintenance + licence) |
| Best for | Orgs migrating to S/4HANA by 2030 or using third-party support | Large complex orgs that cannot migrate by 2030 | Orgs ready to migrate to S/4HANA |
The Hidden Fourth Path — Third-Party Support:
Beyond SAP's three options, some organisations are evaluating third-party ECC support (e.g., Rimini Street, Spinnaker Support) as an alternative to extended maintenance or the transition option. Third-party providers offer continued support for ECC at typically 50% of SAP's maintenance cost — without requiring HANA migration or cloud subscription. However, third-party support means no SAP patches (the provider creates custom fixes), no access to SAP enhancements, and potential complications if you later want to return to SAP's ecosystem. For organisations committed to S/4HANA eventually but needing bridge support beyond 2030, third-party support is a viable financial alternative — but with strategic trade-offs.
The financial implications of each path are complex and vary significantly based on your current SAP estate size, licensing metrics, and infrastructure costs.
1. Current State — On-Premises ECC Maintenance:
Most ECC customers pay annual maintenance at approximately 22% of their perpetual licence value. For a mid-to-large enterprise with $10M in SAP perpetual licences, that's approximately $2.2M/year in maintenance fees. Extended maintenance (2028–2030) adds approximately 2% — bringing the rate to ~24%, or $2.4M/year. Infrastructure costs (data centres, hardware, DBA, basis team) are additional — typically $1–3M/year depending on scale.
2. Transition Option — Cloud Subscription Pricing:
The transition option converts your ECC environment from on-premises maintenance to a RISE cloud subscription. SAP's standard approach is to convert existing perpetual licence value into a subscription credit — but the conversion ratio is a key negotiation point. Typical RISE conversions value perpetual licences at 80–100% of their net book value as a credit toward annual subscription fees. However, the transition option's premium pricing for 2031–2033 means the annual subscription cost will significantly exceed current maintenance.
| Cost Component | On-Prem ECC (Current) | Transition Option (2028–2033) | RISE S/4HANA |
|---|---|---|---|
| Software/licence | Perpetual — already paid | Subscription — recurring annual cost | Subscription — recurring |
| Annual maintenance/support | ~$2.2–2.4M (22–24% of $10M) | Included in subscription — but higher total | Included in subscription |
| Infrastructure | ~$1–3M (own data centre + staff) | Included — SAP manages in cloud | Included in RISE |
| Migration cost | None (status quo) | HANA migration + cloud lift-and-shift: $2–10M+ (one-time) | Full S/4HANA migration: $5–50M+ (varies enormously) |
| 2031–2033 premium | N/A — no support available | Premium uplift over standard RISE rates | N/A — standard subscription |
| Annual run cost (est.) | ~$3.2–5.4M (maintenance + infra) | ~$4–8M (subscription including infra) | ~$3.5–7M (subscription) |
3. The Double Migration Problem:
The transition option requires two migrations: first, a HANA database migration and cloud lift-and-shift of ECC by 2030; then, a full S/4HANA migration by 2033. Each migration has its own costs, risks, and organisational disruption. Organisations choosing the transition option should budget for the combined cost of both migrations — not just the first. The total cost of the transition path (HANA migration + cloud move + 3 years premium subscription + S/4HANA migration) may exceed the cost of an accelerated S/4HANA migration that avoids the intermediate step entirely.
What IT Leaders Should Do Now — Cost Modelling
Build a 10-year TCO model (2025–2035): Model all three paths — on-prem through 2030 then unsupported, transition option through 2033, and accelerated S/4HANA — with realistic migration costs, subscription pricing, and infrastructure savings.
Quantify the double migration cost: If you take the transition option, you'll migrate twice. What does the HANA + cloud move cost? What does the subsequent S/4HANA migration cost? How does this compare to doing S/4HANA once?
Negotiate licence conversion credits aggressively: The conversion ratio from perpetual licences to subscription credits is the single most important financial variable in RISE negotiations. Independent benchmarking reveals significant variation in what SAP offers — and what's achievable.
A related but distinct issue is SAP's S/4HANA Compatibility Packs — a mechanism that allows customers migrating to S/4HANA to continue using certain ECC transaction codes and business processes that haven't yet been fully replicated in the S/4HANA architecture.
What are Compatibility Packs?
When SAP redesigned ERP as S/4HANA, some ECC functionality was re-engineered (simplified data model, new UX, etc.) while other ECC features were carried forward through "compatibility" layers. Compatibility Packs preserve specific ECC transaction codes and processes within S/4HANA — allowing organisations to migrate without immediately re-engineering every business process. They're particularly important for organisations with heavy customisation that depends on specific ECC tables, transaction codes, or data structures.
The 2025 Deadline:
SAP has set deadlines for Compatibility Pack availability. Some packs have already been deprecated; others have end dates in 2025–2027. This means that organisations planning S/4HANA migrations must check whether the Compatibility Packs they depend on will still be available when they migrate — or whether they need to re-engineer those processes for native S/4HANA before migration.
| Compatibility Pack Area | Status | Implication |
|---|---|---|
| Finance (FI/CO) — Asset Accounting | Migration to New Asset Accounting required | Must migrate to New Asset Accounting before or during S/4HANA move |
| Materials Management (MM) | Some transaction codes preserved; others deprecated | Validate each MM transaction code against S/4HANA compatibility list |
| Sales & Distribution (SD) | Largely compatible; some billing changes | Review custom pricing procedures and output management |
| Warehouse Management (WM) | WM deprecated; replaced by Extended Warehouse Management (EWM) | Major re-implementation required if using classic WM |
| Credit Management | Classic Credit Management deprecated; SAP Credit Management replaces | Re-configuration required |
| Custom ABAP code | Must be checked against S/4HANA Simplification List | Custom code remediation project required |
Impact on the Transition Option:
Organisations taking the transition option (staying on ECC through 2033) avoid Compatibility Pack deadlines in the short term — because they're not migrating to S/4HANA yet. However, when they do migrate (by 2033), the Compatibility Packs that existed in earlier S/4HANA versions may no longer be available. This means the transition option could increase the complexity of the eventual S/4HANA migration — because the compatibility bridges that would have simplified the move may be gone by 2033.
Any discussion of SAP licensing transitions must address digital access (indirect/digital access pricing, or DAAP) — one of the most financially significant and misunderstood aspects of SAP licensing.
What is Digital Access?
Digital access refers to scenarios where non-SAP systems (CRM, e-commerce, customer portals, IoT devices, APIs) create, update, or read SAP data without a human SAP user logging in. Under traditional SAP licensing, only named human users required licences. SAP's introduction of digital access pricing in 2018 created a new licensing requirement for these machine-to-machine and system-to-system interactions — measured by the number of documents created in SAP by external systems.
Why Digital Access Matters for the Transition Option:
If you're negotiating a RISE contract for the transition option, your digital access position must be resolved as part of the deal. SAP will audit your digital access usage as part of the RISE conversion — and any unresolved indirect usage creates a compliance liability that SAP can use as negotiating leverage.
| Digital Access Scenario | Pre-DAAP Risk | RISE Conversion Impact |
|---|---|---|
| E-commerce orders creating SAP sales orders | Potentially unlicensed under old model | Must be licensed under DAAP or negotiated as part of RISE |
| CRM system creating service tickets in SAP | Indirect access — licensing status uncertain | Clarify during RISE negotiation; may need document packages |
| IoT sensors creating maintenance orders | Growing volume — potentially unlicensed | High-volume document creation; significant cost if priced per-document |
| API integrations reading SAP data | Read-only — lower risk under most interpretations | Generally lower cost; confirm during RISE terms |
| EDI/B2B document exchange | Depends on contract version and interpretation | Must be explicitly addressed in RISE agreement |
Practical Guidance: Resolve your digital access position before RISE contract negotiation — not during it. If SAP discovers unresolved indirect usage during the RISE conversion process, they will use it as leverage to extract higher subscription pricing or additional document licence purchases. An independent digital access assessment before engaging SAP for RISE ensures you understand your exposure and can negotiate from an informed position.
SAP's Global License Audit & Compliance (GLAC) team has become increasingly active — and the transition to RISE creates new audit dynamics that CIOs must understand.
1. Pre-RISE Audit Risk:
SAP commonly conducts licence audits before major commercial events — including RISE contract negotiations. The audit serves two purposes: it establishes the customer's current compliance position (creating leverage for SAP if gaps exist) and it quantifies the existing licence estate for conversion credit calculations. If your ECC environment has compliance gaps — unlicensed users, digital access exposure, engine licence shortfalls — SAP will discover them during the pre-RISE assessment process.
2. RISE Contract Compliance:
Moving to RISE changes the compliance model. Under on-premises perpetual licensing, SAP audited licence usage (named users, engines, digital access). Under RISE subscription, compliance shifts to: subscription scope (are you using only the components and user types included in your subscription?); fair use policies (RISE contracts include acceptable use terms); and digital access document volumes (if DAAP is included in the RISE terms).
3. Preparing for Audit-Ready RISE Negotiations:
| Preparation Step | Purpose | Timing |
|---|---|---|
| Internal licence compliance review | Identify and resolve compliance gaps before SAP does | 12–18 months before RISE negotiation |
| Digital access assessment | Quantify indirect usage; determine DAAP exposure | 12 months before RISE negotiation |
| User type optimisation | Right-size named user licences (Professional → Limited → Employee Self-Service) | 6–12 months before RISE |
| Engine licence reconciliation | Verify SAP package/engine licences match actual usage | 6–12 months before RISE |
| Custom code analysis | Identify custom ABAP code creating unlicensed access patterns | As part of S/4HANA readiness assessment |
The principle is simple: know your compliance position before SAP does. Every unresolved compliance issue is leverage that SAP will use in RISE negotiations — either explicitly (demanding remediation purchases) or implicitly (building non-compliance risk into subscription pricing). Independent pre-negotiation assessment eliminates this leverage.
Whether you're pursuing the transition option, standard RISE, or optimising your current ECC position, several negotiation levers can significantly reduce cost and improve terms.
1. Licence Conversion Credits:
When converting perpetual licences to RISE subscription, SAP offers a credit for existing licence value. The conversion ratio varies — typically 80–100% of net book value — but is negotiable. Every percentage point matters: on a $10M licence estate, the difference between 80% and 95% conversion is $1.5M in credit value. Independent benchmarking of conversion ratios achieved by comparable organisations is the most effective negotiating tool.
2. Subscription Pricing Benchmarks:
RISE subscription pricing varies significantly between customers — based on deal size, timing, competitive pressure, and negotiating skill. SAP's initial subscription proposals are typically 20–40% above what well-negotiated customers achieve. Independent pricing benchmarks — comparing your proposed rates against comparable RISE deals — consistently reveal significant negotiation room.
3. Transition Option Premium Negotiation:
The 2031–2033 premium pricing for the transition option is a new commercial construct — there is limited market data on what SAP is charging. Early adopters of the transition option have an opportunity to set the pricing benchmark. Key negotiation points include: the premium uplift percentage above standard RISE rates; whether the premium applies to the full subscription or only the ECC-specific component; term flexibility (can you exit the transition option early if S/4HANA migration completes before 2033?); and SLA guarantees for the ECC cloud environment during the transition period.
| Negotiation Lever | Impact Area | Typical Savings |
|---|---|---|
| Licence conversion ratio | Credit value applied to subscription | $500K–$3M+ depending on licence estate size |
| Subscription rate benchmarking | Annual subscription cost | 20–40% below SAP's initial proposal |
| Transition premium negotiation | 2031–2033 premium uplift | Varies — limited market data; early movers set precedent |
| Term flexibility | Ability to exit early or adjust scope | Reduced lock-in risk; option value |
| Digital access resolution | DAAP pricing within RISE | Negotiating DAAP as part of RISE vs separate reduces total cost |
| User type optimisation pre-RISE | Subscription baseline (fewer users = lower subscription) | 10–30% reduction in user-based subscription metrics |
4. Timing and Competitive Pressure:
SAP's negotiating flexibility increases when: you're approaching a fiscal quarter or year-end for SAP's sales team; you can credibly demonstrate alternative paths (third-party support, non-SAP ERP); and you're engaging early (2025–2026) rather than late (2029–2030) when SAP knows you have fewer options. Starting RISE negotiations 3–4 years before the 2030 deadline provides maximum leverage.
The right path depends on your specific circumstances. Here are recommendations segmented by organisation type.
| Organisation Profile | Recommended Path | Key Actions |
|---|---|---|
| Large enterprise, complex ECC, cannot migrate by 2030 | Transition option + parallel S/4HANA programme | Start RISE negotiation now; plan HANA migration by 2028; begin S/4HANA for new processes while ECC runs through 2033. |
| Mid-size enterprise, moderate customisation, migration feasible by 2030 | Accelerated S/4HANA migration via RISE | Begin S/4HANA project in 2025–2026; negotiate RISE with strong conversion credits; avoid the transition option's double migration cost. |
| Organisation with limited SAP dependency | Evaluate alternatives | Assess whether S/4HANA is the right platform long-term. Consider Oracle, Microsoft, or other ERP alternatives if SAP dependency is low. |
| Organisation seeking cost containment | Third-party support bridge | Move to third-party ECC support post-2030 at ~50% of SAP maintenance; use savings to fund S/4HANA migration at your own pace. |
| Organisation already on HANA | Strong transition option candidate | Already past the HANA prerequisite. Cloud lift-and-shift of ECC is the only migration needed. Lower barrier to transition option. |
| Organisation with major S/4 readiness gaps (WM, Asset Accounting, custom code) | Transition option for extra time | Use 2031–2033 to complete S/4HANA readiness work (Compatibility Pack alternatives, custom code remediation, process redesign). |
Key principle: The transition option is a bridge, not a destination. Every organisation choosing the transition option must have a parallel S/4HANA migration programme — the 2033 deadline is firm, and SAP has indicated no further extensions. Use the extra time strategically: migrate the most complex ECC components during 2031–2033 while the simpler ones move first. Don't use 2031–2033 to delay — use it to complete what 2025–2030 wasn't enough time for.
Regardless of which path you choose, here are the actions that every ECC customer should take now.
| # | Action | Timing | Expected Impact |
|---|---|---|---|
| 1 | Assess your S/4HANA migration timeline honestly. Will all ECC systems be on S/4HANA by 2030? By 2033? Identify which systems are at risk and why. This assessment determines whether the transition option is necessary. | Immediate | Informs strategic path selection; prevents last-minute decisions |
| 2 | Conduct an independent SAP licence compliance review. Identify and resolve all compliance gaps — user types, digital access, engine licences — before engaging SAP for RISE. Every unresolved issue is SAP negotiating leverage. | Within 6 months | Eliminates compliance leverage; reduces RISE negotiation risk |
| 3 | Model 10-year TCO for all paths. On-prem through 2030, transition option through 2033, accelerated S/4HANA, and third-party support. Include migration costs, subscription pricing, infrastructure savings, and the double migration cost of the transition option. | Within 6 months | Data-driven path selection; identifies most cost-effective route |
| 4 | Optimise your SAP licence position before RISE negotiation. Right-size user types, resolve digital access, eliminate shelfware, and consolidate entitlements. Your current licence position is the baseline for RISE conversion credits — a cleaner position means better economics. | 12 months before RISE | Lower subscription baseline; higher conversion credit value |
| 5 | Engage SAP for RISE negotiation in 2025–2026. Early engagement gives maximum negotiating leverage. SAP's flexibility decreases as 2030 approaches and your options narrow. Start now while you have alternatives. | 2025–2026 | Best pricing and terms achievable; SAP still competing for your commitment |
| 6 | Assess Compatibility Pack dependencies for S/4HANA. Which ECC transaction codes and processes depend on Compatibility Packs? Are those packs still available in current S/4HANA versions? This determines your S/4HANA readiness and migration scope. | Within 12 months | Identifies S/4HANA migration blockers; informs timeline and complexity |
| 7 | Engage independent SAP licensing expertise. SAP negotiations — particularly RISE conversions and transition option terms — are complex, high-stakes commercial events. Independent advisory with SAP licensing expertise and benchmarking data ensures you're not leaving value on the table. | Before RISE negotiation | Optimised terms; 10–20× ROI on advisory fee |
Key point: The ECC-to-2033 transition option is a premium bridge for complex enterprises that need more time — not an alternative to S/4HANA migration. It requires HANA migration and cloud subscription by 2030, premium pricing for 2031–2033, and full S/4HANA migration by 2033. The total cost of the transition path (double migration + premium subscription) may exceed accelerated S/4HANA. Every ECC customer must model all paths, optimise their current position, and engage SAP from a position of informed strength — starting now, not in 2029.
A managed cloud subscription service that allows ECC customers to run SAP ECC with full support until year-end 2033 — three years beyond the 2030 extended maintenance deadline. It requires migrating ECC to the HANA database in SAP's private cloud (under RISE with SAP) by 2030. It's not a simple on-premises support extension — it's a cloud subscription with premium pricing.
Large, complex enterprises with heavily customised ECC environments that genuinely cannot complete S/4HANA migration by 2030. Requirements include a RISE with SAP contract signed by 2028, ECC running on HANA database, and ECC migrated to SAP's managed private cloud by end of 2030. Only core ECC components are confirmed eligible — some Business Suite 7 add-ons may not qualify.
The transition option converts on-premises maintenance to a RISE cloud subscription with premium pricing for 2031–2033. Annual costs will significantly exceed current maintenance fees. Additionally, the HANA database migration and cloud lift-and-shift have one-time costs of $2–10M+ depending on environment complexity. The total cost includes both the intermediate migration and the eventual S/4HANA migration.
Usually not. The transition option involves two migrations (HANA + cloud by 2030, then S/4HANA by 2033) plus premium subscription pricing. An accelerated S/4HANA migration does one migration at potentially lower total cost. However, for organisations where S/4HANA migration by 2030 is genuinely impossible due to complexity, the transition option provides supported ECC during the gap — which has operational and regulatory value.
SAP has indicated no further ECC extensions are planned beyond 2033. Organisations must be on S/4HANA by year-end 2033 or run ECC unsupported. The 2033 deadline should be treated as firm for planning purposes.
Compatibility Packs preserve specific ECC transaction codes and business processes within S/4HANA — allowing migration without immediately re-engineering everything. Some packs have end dates in 2025–2027. Organisations delaying S/4HANA migration (via the transition option) may find that Compatibility Packs available today are deprecated by the time they migrate in 2031–2033 — potentially increasing migration complexity.
Digital access (indirect usage) must be resolved as part of RISE contract negotiation. Unresolved indirect usage creates compliance liability that SAP uses as negotiating leverage. An independent digital access assessment before engaging SAP for RISE ensures you understand your exposure and can negotiate from an informed position.
Third-party ECC support (e.g., Rimini Street) provides continued ECC support at ~50% of SAP maintenance cost without requiring HANA migration or cloud subscription. Trade-offs include no SAP patches (provider creates custom fixes), no access to SAP enhancements, and potential complications returning to SAP's ecosystem. It's viable for cost containment while funding S/4HANA migration at your own pace.
Now — 2025–2026. Early engagement gives maximum negotiating leverage because SAP is still competing for your commitment. As 2030 approaches, your options narrow and SAP's flexibility decreases. Starting 3–4 years before the deadline also gives time for pre-negotiation optimisation (user right-sizing, digital access resolution, compliance cleanup).
Redress provides independent SAP advisory: licence compliance review, digital access assessment, user optimisation, RISE negotiation support with pricing benchmarks, transition option evaluation, and ongoing licence governance. All fixed-fee, 100% vendor-independent — no commercial relationships with SAP or any SAP partner.
This article is part of our SAP Licensing Overview pillar. Explore related guides:
Redress Compliance has helped hundreds of Fortune 500 enterprises — typically saving 15–35% on renewals and new deals.
100% vendor-independent · No commercial relationships with any software vendor