The boardroom felt quieter after the ink dried.
The CIO had just signed the RISE with SAP contract. Legal had reviewed it. Finance had modeled the OpEx shift. The 2027 deadline was no longer a threat - it was a line item on the project plan. The organization was, officially, on the path to S/4HANA.
Then the calls with the implementation team started.
Who was migrating the data? SAP. No - the SI. Actually, the customer's internal team, with support. Who was remediating 2,400 custom ABAP objects? That would be the SI, in a separate statement of work. Who was redesigning the core procure-to-pay process? That was a business transformation engagement - also separate.
The realization hit hard: RISE with SAP is the road. But no one in that contract was going to build the car or drive it.
This post is the briefing that should have happened before the contract was signed. It covers what RISE actually covers, what it doesn't, and what a CIO in 2026 must plan for - before the 2027 deadline forecloses the options.
What RISE with SAP Actually Is: The Commercial Reality
Bottom line: RISE with SAP is a commercial subscription model - not a migration service, not a transformation program. It bundles S/4HANA Cloud, SAP Business Technology Platform (BTP), and managed infrastructure into a single contract. The migration work happens on top of it, not inside it.
SAP launched RISE with SAP in 2021 as a vehicle to accelerate the cloud conversion of its ECC customer base. In 2025, SAP rebranded the private edition as "SAP Cloud ERP Private," but the commercial structure remains: one subscription agreement, one point of accountability for infrastructure and licensing, one path to cloud ERP.
That clarity has real value. RISE consolidates what was previously a patchwork of separate licenses, hyperscaler agreements, and BTP contracts. For a CFO trying to forecast multi-year IT spend, the shift from perpetual license + on-premise infrastructure costs to a predictable subscription model is meaningful.
But "predictable" is doing a lot of work in that sentence.
The Bundle Breakdown: S/4HANA Cloud, BTP, and Infrastructure
At its core, RISE with SAP (Cloud ERP Private) bundles:
- SAP S/4HANA Cloud, Private Edition - the ERP platform itself, running in SAP's data center or on a hyperscaler of your choosing (AWS, Azure, or Google Cloud)
- SAP Business Technology Platform (BTP) - the integration and extensibility layer, including integration suite, low-code tools, and analytics capabilities
- SAP Business Network - access to SAP's supplier collaboration network
- SAP Joule - SAP's generative AI assistant, now included at no additional license cost as of 2025
- Clean Core monitoring tooling - the dashboard and guided remediation paths that show which customizations comply with SAP's extensibility model
What RISE is not is a hyperscaler contract. You still negotiate separately with AWS, Azure, or Google Cloud for compute and storage if you choose to host on one of them rather than in SAP's own data center. RISE does not absorb hyperscaler costs.
The Shift from CapEx to OpEx: Financial Implications for the CFO
The financial model underlying RISE is an OpEx conversion. Organizations surrender perpetual S/4HANA licenses and shift to a recurring subscription. Infrastructure moves off the balance sheet. The annual RISE subscription becomes a fully operational expense.
For CFOs this is not automatically a win. The subscription economics require scrutiny. SAP BTP usage above bundled thresholds is metered and billed on consumption - overages can be significant without a hard ceiling in the contract. The actual migration services - the implementation consulting - are not included in the RISE subscription and are typically invoiced at 1.5 to 3 times the first-year license cost, according to market research on RISE implementation economics.
The move from CapEx to OpEx changes how IT spend appears on financial statements, but it does not reduce the total investment required to reach go-live.
The RISE Reality Gap: What RISE Isn't
Bottom line: Buying RISE does not migrate your data. It does not fix your custom code. It does not redesign your business processes. These three items - data migration, custom code remediation, and business process reengineering - are the primary cost drivers of any ECC-to-S/4HANA project. None of them are in the RISE subscription.
This is the gap that takes most CIOs by surprise.
It's Not a Migration Engine: Who Actually Moves the Data
RISE with SAP gives you SAP's migration tooling - the Software Update Manager, SAP Data Migration Cockpit, and SAP Readiness Check. These tools identify what needs to move. They do not move it.
Data extraction, cleansing, transformation, loading, and validation is a project in itself. For a complex ECC landscape, it can consume 20-30% of total project effort. Historically, 58% of ECC-to-S/4HANA migrations face data quality issues that cause go-live delays. Poor master data, duplicate records, and inconsistent organizational structures in the source system become problems in the target system - and they surface during migration, not before, unless a dedicated data readiness program precedes the project.
The CIO who assumes the RISE subscription addresses data migration will discover this gap late, and the cost of addressing it late is significantly higher than addressing it early.
It's Not a Custom Code Remediator: The Clean Core Burden
The average enterprise running SAP ECC has accumulated thousands of custom ABAP objects over years of business-specific development. These modifications - known as the custom code footprint - represent competitive differentiation in some cases and accumulated technical debt in most.
S/4HANA's architecture is fundamentally different from ECC. The underlying data model changed. Many ECC function modules and table structures no longer exist in the same form. Custom code that works today will break in S/4HANA unless it is remediated, replaced with standard SAP functionality, or moved to BTP extensions.
RISE includes tooling - the Clean Core Compliance Dashboard and guided remediation paths - that tells you which of your customizations are non-compliant with SAP's extensibility model. It categorizes them on an A-through-D scale. What RISE does not do is fix the non-compliant code. That work falls entirely to the SI partner and the customer's internal ABAP development team.
For organizations with large customization footprints, this is where project timelines and budgets expand unpredictably. The ASUG 2024 S/4HANA Journeys research found that nearly half (49%) of organizations that completed their S/4HANA migration saw costs exceed their original budgets - with consulting fees as the primary source of overrun, up 20% since 2023. Custom code remediation is a significant driver of those consulting hours.
It's Not Business Process Reengineering
S/4HANA's value does not come from running old ECC processes on new infrastructure. It comes from standardizing processes to match SAP best practices, reducing the custom code footprint that prevents clean upgrades, and positioning the organization to consume SAP's AI capabilities through Joule and BTP.
That transformation - moving from how the business operated in ECC to how it should operate in S/4HANA - is business process reengineering. It requires process owners, functional leads, change management, and executive sponsorship. It is the most politically complex part of any SAP transformation.
RISE does not fund it, staff it, or manage it. It is entirely the customer's responsibility, typically with an SI partner facilitating the workshops, decisions, and documentation.
RISE in 2026: The Clean Core and AI Imperative
Bottom line: In 2026, RISE is no longer just a cloud hosting decision. It is the prerequisite for SAP's AI roadmap. Organizations that adopt RISE without a Clean Core strategy will have cloud infrastructure - and no ability to benefit from the AI capabilities SAP is building on top of it.
<figure>Clean Core Maturity → AI Readiness → Business Value</figure>
The SAPinsider benchmark research published in early 2026 found that generative AI is now influencing ERP decisions for 43% of SAP professionals - up sharply from 14% in 2023. SAP's Joule assistant is embedded throughout S/4HANA Cloud, finance workflows, procurement, and HR. But Joule operates on standardized, clean data. It cannot extract intelligence from a custom-coded, heavily modified ECC landscape that has been lifted and shifted into a cloud environment without process redesign.
This is the AI readiness trap: organizations that migrate to RISE without achieving Clean Core arrive in the cloud with the same data complexity and process variation they had on-premise. They pay subscription costs. They do not get AI value.
Why Clean Core is Non-Negotiable in a RISE Contract
SAP's Clean Core strategy mandates that all customizations be moved out of the S/4HANA core and into the BTP extension layer, using approved extensibility APIs. This is not a recommendation. For organizations on RISE, it is a condition of receiving continuous cloud updates. SAP's cloud release cycle delivers two major updates per year. A non-compliant customization that modifies the SAP core will break with every update.
The Clean Core compliance dashboard that now ships with RISE gives organizations visibility into their compliance posture. Acting on that visibility - remediating non-compliant code, rebuilding extensions on BTP, retiring obsolete customizations - requires a structured program that most organizations have not fully scoped.
Organizations implementing Clean Core principles migrate more efficiently, adopt future releases faster, and require less post-go-live remediation. The inverse is also true: organizations that carry customization debt forward into RISE create a technical mortgage that compounds with every release.
Unlocking AI Readiness via BTP and Standardized Processes
SAP BTP is the technical foundation for everything SAP is building with AI. Joule runs on it. Custom AI extensions are built on it. Business process integrations with third-party systems run through it. The 2025 SAPinsider migration benchmark found that 61% of organizations plan to use BTP as part of their S/4HANA investment, up from 57% in 2024.
But BTP's value is conditional on the cleanliness of the underlying S/4HANA data model. An organization running standardized, fit-to-standard S/4HANA processes has clean master data, consistent organizational structures, and predictable transaction flows. That is the environment in which Joule's anomaly detection, cash flow forecasting, and procurement exception handling deliver measurable value.
The sequence matters: Clean Core first, then BTP integration, then AI activation. Organizations that skip step one and attempt to activate step three will spend their BTP budget on integration remediation rather than innovation.
Is RISE with SAP Right for You? A Decision Matrix
Bottom line: RISE is the right commercial model for most SAP ECC customers heading toward 2027 - but only if entered with clear eyes about what it does and does not include. The organizations most at risk are those with large customization footprints who treat RISE as a migration solution rather than an infrastructure and licensing vehicle.
The table below is not exhaustive, but it captures the primary variables CIOs should evaluate before committing.
When RISE Makes Strategic Sense
RISE is well-suited for organizations that:
- Have a manageable customization footprint. If the ECC landscape is relatively standard, with fewer than 500 custom ABAP objects and no mission-critical custom processes, the path to Clean Core is tractable within a 12-18 month migration program.
- Are ready to invest in the full transformation, not just the license. Organizations that budget separately for SI engagement, data migration, custom code remediation, and change management - and treat RISE as the infrastructure layer of a broader program - position themselves for a successful go-live.
- Want to eliminate ECC maintenance risk before 2027. ECC mainstream maintenance ends in 2027. Extended maintenance is available through 2030 at a premium, but the pressure to exit ECC is real. For organizations with a clear migration timeline, RISE consolidates the infrastructure and licensing decisions into a single contract, reducing vendor management complexity.
- Are making AI a strategic priority. If the board has committed to SAP AI adoption as a business priority, RISE with a Clean Core strategy is the required technical path. There is no Joule on ECC.
When Your Customization Footprint Rules It Out
RISE requires careful reconsideration for organizations that:
- Have deeply customized ECC landscapes with custom processes that have no SAP standard equivalent. If the business has built significant competitive differentiation on top of ECC through custom code, the effort to migrate that differentiation to BTP extensions is substantial. The economics of RISE may not pencil out against the total cost of that remediation.
- Cannot absorb the dual-run period. RISE migrations require running ECC and S/4HANA in parallel during testing and cutover - typically 3-12 months. This doubles infrastructure costs for that period and is rarely included in initial RISE estimates. Organizations with constrained capital budgets need to model this explicitly.
- Are not yet operationally ready for a Clean Core mandate. Moving to RISE without Clean Core readiness creates a situation where the organization pays cloud subscription costs while still operating with the technical debt of an on-premise ECC architecture. The financial case for RISE is substantially weakened in this scenario.
In every case, the decision should be preceded by a rigorous readiness assessment that quantifies the customization footprint, data migration complexity, and total cost of transformation - not just the RISE subscription cost.
Bridging the Gap: How ITChamps Drives the RISE Vehicle
Bottom line: RISE with SAP provides the road. ITChamps provides the vehicle and the driver. Through the 3PS Advisory framework and S/4HANA Migration practice, ITChamps bridges the gap between the RISE subscription and a successful, Clean Core-compliant go-live.
The gap between signing a RISE contract and achieving a production-ready S/4HANA system is where most migrations encounter difficulty. The SAPinsider 2025 RISE benchmark identified remediating custom code, cleaning data, and securing business-unit support as the top three obstacles organizations face in the transition. These are precisely the workstreams that RISE does not address - and that ITChamps is built to execute.
ITChamps 3PS Advisory: Navigating the RISE Contract
The ITChamps 3PS Advisory framework addresses the three critical gaps in a RISE deployment: process readiness, platform readiness, and people readiness.
Before a RISE contract is finalized, ITChamps conducts a structured S/4HANA Readiness Assessment that quantifies:
- The organization's custom code footprint, categorized by SAP's A-D extensibility compliance model
- Data quality and migration complexity across all relevant data domains
- Business process alignment with SAP fit-to-standard, identifying where standard functionality meets business needs and where BTP extensions will be required
- The true total cost of the transformation, inclusive of SI services, data migration, custom code remediation, and change management - not just the RISE subscription
This assessment changes the commercial conversation. Rather than discovering the RISE Reality Gap after the contract is signed, organizations enter the RISE engagement with a complete picture of what it will take to reach go-live. ITChamps accelerates S/4HANA adoption via its proprietary 3PS Advisory framework, ensuring the RISE subscription is paired with an executable transformation roadmap from day one.
Accelerating Clean Core and Custom Code Remediation
ITChamps delivers up to 30% faster migration via its proprietary framework, applied directly to the two workstreams that most frequently cause overruns: custom code remediation and data migration.
On custom code, ITChamps' approach begins with the rationalization question: which customizations genuinely differentiate the business, and which represent accumulated technical debt that should be retired? In most ECC landscapes, a significant share of custom objects are unused or redundant. Retiring them before migration reduces the remediation scope and accelerates the timeline.
Remaining custom functionality is evaluated against SAP's extensibility model. Where standard S/4HANA functionality covers the business need, ITChamps guides the process redesign to adopt the standard. Where differentiation is genuine, ITChamps builds the BTP extension to the correct architectural specification - ensuring Clean Core compliance and upgrade safety from the first release.
On data migration, ITChamps applies structured data readiness methodology before any technical migration begins. Master data governance, deduplication, and cleansing are addressed in the source system. Data migration objects are mapped, validated, and tested iteratively - not in a single cutover sprint.
The result is a RISE deployment that achieves Clean Core compliance at go-live, not as a post-go-live remediation project. That distinction determines whether the organization unlocks AI value in year one or continues paying subscription costs while deferring the transformation it thought it had already funded.
Frequently Asked Questions
What does RISE with SAP actually include?
RISE with SAP (now also referred to as SAP Cloud ERP Private for the private edition) bundles SAP S/4HANA Cloud, SAP Business Technology Platform, SAP Business Network access, managed infrastructure (hosted by SAP or a hyperscaler), and - as of 2025 - SAP Joule AI and Clean Core monitoring tooling. It is a commercial subscription model that consolidates licensing and infrastructure under one contract. It does not include migration services, custom code remediation, data migration, or business process redesign. Those workstreams are the responsibility of the customer and their SI partner.
How is RISE with SAP different from simply buying S/4HANA?
Before RISE, organizations purchased S/4HANA perpetual licenses, managed their own infrastructure or contracted separately with hyperscalers, and procured BTP independently. RISE bundles these into one subscription with SAP as the single commercial counterpart. The shift is from CapEx (perpetual licenses, owned infrastructure) to OpEx (subscription). RISE also includes access to SAP's Business Network and, in 2025, added Joule AI and Clean Core tooling to the standard bundle. The core distinction remains: RISE is a commercial structure, not a migration program.
What is the RISE Reality Gap?
The RISE Reality Gap is the distance between what the RISE subscription covers - infrastructure, licensing, platform access, and tooling - and what is required to actually go live on a clean, operational S/4HANA system. The gap includes data migration, custom code remediation to Clean Core compliance, business process redesign, change management, and organizational readiness. These workstreams are not funded or staffed by SAP through the RISE contract. They require a qualified SI partner and represent the majority of total transformation cost. ASUG's 2024 research found consulting fees and SI services to be the primary source of cost overruns in S/4HANA migrations - 49% of organizations reported exceeding their original budgets.
What is Clean Core and why does it matter for RISE?
Clean Core is SAP's architectural standard for S/4HANA Cloud. It requires that all custom code and business logic be moved out of the S/4HANA core and into the BTP extension layer, using SAP's approved extensibility APIs. Organizations that do not achieve Clean Core compliance cannot safely receive SAP's continuous cloud updates - and they cannot activate SAP's AI capabilities, including Joule. In practical terms, Clean Core is what converts a RISE subscription from a hosting migration into an AI-ready, future-proof ERP platform. Without it, the organization pays cloud costs while retaining the technical debt of an on-premise architecture.
Is RISE with SAP mandatory before the 2027 SAP ECC deadline?
No. The 2027 date marks the end of SAP's mainstream maintenance for ECC and older S/4HANA versions - after which no standard support packages or functional updates will be issued. Extended maintenance is available through 2030 at a premium. RISE is SAP's preferred commercial model for the cloud transition, but organizations can also adopt S/4HANA on-premise or through other licensed arrangements. The 2027 deadline is a commercial lever and a risk management trigger; it is not a RISE mandate. However, for organizations intending to move to S/4HANA Cloud and unlock SAP's AI roadmap, RISE or the equivalent SAP Cloud ERP Private subscription is the required commercial path.