SAP Cloud Is Quietly Becoming an AI-Readiness Program

SAP Cloud ERP and SAP Cloud ERP Private (formerly RISE with SAP) projects are moving beyond mere cloud migration exercises. It is now a mandatory AI-readiness operating model in the form of Joule and the embedded SAP Business AI capabilities showcased at SAP Sapphire 2026.

After Sapphire, the key visible changes include the targeted future, the Autonomous Enterprise, and the help customers get to transform into the future state: the Agent-led transformation or migration and modernization. That is because SAP teams understand that evolving customers has always been a “move to” initiative, helping customers recognize the benefits of the targeted future, highlighting SAP support (Tools, Methodology, Services) for the transformation, and working out any “bridges” that help customers through the transition.

AI Is Driving the Migration Conversation

The market narrative has also shifted abruptly. According to SAPinsider’s SAP S/4HANA Migration Research, 54% of respondents now plan to use AI or generative AI in their SAP ERP Cloud deployment. Across the respondent base, 38% plan to use Joule and 34% plan to use SAP BTP AI Foundation.

This is a stark contrast to just a year ago, when generative AI had minimal impact on SAP Cloud ERP adoption and sat at the bottom of ERP planning priorities. Today, organizations are actively reevaluating SAP Cloud ERP Private, specifically in light of access to generative AI.

SAPinsider’s SAP Business Data Cloud Research captures this from another angle: 26% of organizations cite enabling AI and agent-based use cases as a primary investment driver, matching the exact percentage of those driving SAP Cloud ERP transformations. As a result, AI enablement is the rationale for digital transformation today.

The AI Question Is an ERP Hygiene Question

Joule and embedded SAP Business AI are not generic, standalone chatbots. They are engineered to deeply understand the relationships among transactions, master data, and workflows embedded within SAP’s enterprise architecture. When a user queries Joule, it does not just scrape a knowledge base. It reads real-time tables, verifies authorization roles, and attempts to execute actions based on the system’s underlying business logic. Because Joule is completely tethered to this process context, AI readiness inevitably becomes an ERP hygiene issue.

A finance reconciliation use case perfectly illustrates both the technical problem and the human cost of using AI with inconsistent data. Imagine a customer master containing multiple, conflicting versions of the same vendor across different regional business units. When an end-user asks Joule to identify an invoice discrepancy or suggest a posting variant, the AI pulls from those inconsistent records. Instead of streamlining the workflow, it generates conflicting matches and hallucinated suggestions.

The human user, who was supposed to be aided by an intelligent copilot, is forced to abandon the tool and perform manual forensics across multiple screens just to determine which vendor record is accurate. When AI delivers a poor answer due to poor data, it destroys user trust and turns an expensive innovation into a frustrating obstacle.

SAPinsider’s SAP Business AI Research proves why this data dependency cannot be ignored:

• 79% say access to high-quality, trusted data is required for AI adoption.
• 70% require integration with SAP and other enterprise systems.
• 69% require strong AI governance, risk, and compliance management.

Additionally, 76% of SAP Cloud ERP migration planners require cleansed and harmonized operational data across systems.

Clean Core Is Where AI Ambition Meets Reality

The clean core is where the AI discussion gets real. SAPinsider’s migration research shows that 43% of organizations know they need to modernize or eliminate custom processes, and 36% want to adopt best-practice business process models. Yet only 17% report using clean-core setup and analysis, and a mere 14% use custom code lifecycle management.

This execution gap is exactly what SAP’s RISE with SAP Methodology is engineered to close: an AI-enabled, best-practice framework built on a standardized roadmap, expert guidance from SAP and validated partners, and an agent-led toolchain that automates the resource-intensive work of custom code modernization and data migration in line with clean core principles. Structured across six phases (Discover, Prepare, Explore, Realize, Deploy, and Run) and reinforced by quality gates, it operationalizes the clean-core discipline on which AI readiness depends, turning “we know we should” into a governed path organizations can follow.

Organizations that have already moved to SAP Cloud ERP or SAP Cloud ERP Private consistently identify adapting custom code, integrating third-party applications, and cleansing data as their steepest challenges. While current research does not quantify the exact cost of custom code on Joule’s time-to-value, the conclusion is undeniable: customization increases migration complexity, and complexity directly delays AI readiness.

SAP BTP as the Extension Surface

A second major shift in the Cloud migration and Clean Core conversation is the reliance on SAP BTP as the designated surface for extensions that would otherwise become toxic in-core modifications. Currently, 38% of SAPinsider migration respondents report using SAP BTP for migration or innovation, while 36% of technology leaders list SAP BTP expansion as a planned initiative.

The argument here is architectural, not statistical. While it is not proven that side-by-side SAP BTP extensions deploy AI faster than in-core modifications, the architectural logic holds up: side-by-side extensions preserve the ERP core, reduce upgrade friction, and support modular innovation without hardcoding more technical debt into the system of record.

For enterprise architects, the question is no longer just whether to move to SAP Cloud ERP, but exactly which custom processes should be retired, redesigned around standard best practices, or moved to a side-by-side extension.

What This Means for SAPinsiders

Enterprise Architects must embed AI readiness into migration governance. SAP BTP and a clean-core philosophy are not just about system flexibility—they are the architectural foundation of AI readiness. Do not treat AI as a feature toggle to be flipped on after a cloud migration. The business transformation towards an autonomous enterprise demands that AI readiness be governed by strict data quality metrics, process standardization, and a clear extension strategy from day one. A clean core builds the mandatory operating model for scaling AI securely.

Reconcile board-level AI ambitions with data reality. CIOs face immense pressure to deliver immediate AI outcomes, but these expectations must be aggressively reality-checked against the actual state of your landscape. Trusted, harmonized operational data is the ultimate gating factor for confident AI adoption. Before committing to transformative timelines, audit your existing custom-code debt and the adoption of clean-core tooling. If your master data is fragmented and your core is heavily modified, your enterprise AI initiatives will fail to generate accurate business insights.

SI/GSI Leaders should explicitly scope remediation to prevent downstream paralysis.
Custom code remediation and master data harmonization must be explicitly ring-fenced within your initial project scope. Treating these elements as secondary tasks guarantees they will resurface later as paralyzing complexities of transformation. If SI/GSI teams fail to account for the heavy lifting required to cleanse data and retire legacy code upfront, they risk delivering a modernized ERP environment that is fundamentally unprepared for SAP’s next-generation capabilities.