
Meet the Authors
SAPinsider's SAP S/4HANA Migration Benchmark Report 2025 found 62% of organizations cite high project cost and 55% cite duration as migration barriers, with 43% saying their landscapes are too complex to migrate.
AI can accelerate discovery by flagging redundant Z-programs, retirement-ready custom tables, and shadow processes, but enterprise architects, process owners, and compliance teams still own the design decisions.
Custom-code remediation and data harmonization, each cited by about 41% as the hardest parts of moving to SAP Cloud ERP Private, are the same prerequisites that make enterprise AI trustworthy.
Artificial intelligence (AI) can help SAP teams see migration complexity earlier, but it does not decide what to keep. The more useful way to think about AI in ERP migration is as an agent-led toolchain that exposes how custom-code debt, process variation, data quality, and integration risk are all part of the same readiness problem.
For many SAP customers, the migration discussion still starts with cost and time. SAPinsiders SAP S/4HANA Migration Benchmark Report 2025 found that 62% of organizations cite high project cost as a key barrier to moving to SAP Cloud ERP, while 55% cite project duration. Complexity sits underneath both concerns. That is especially true when 43% say their SAP landscapes are too complex to move to SAP Cloud ERP Private, often because older environments carry years of custom code, undocumented exceptions, bespoke integrations, and data workarounds.
That is where AI enters the conversation. But the useful version of the AI co-pilot claim is narrower than the marketing suggests. AI can help teams identify patterns, exceptions, dependencies, and risks faster. It can make hidden issues visible earlier in the program. What it cannot do is remove accountability for design decisions. Those choices still belong to the enterprise architects, process owners, security leaders, and compliance stakeholders who must live with the operating model after go-live.
Discovery Shapes the Migration
One of the clearest messages in the benchmark data is that many organizations still do not have a complete evidence base for migration design. SAP Readiness Check is used by roughly 51% of organizations, and ETL tools by 45%. By contrast, Process Discovery for SAP S/4HANA Transformation is used by only 25% to 26% of organizations, and Custom Code Lifecycle Management by just 14%.
That gap matters because 62% say reducing custom code to create a clean and agile core is an important ERP requirement. Clean-core intent is running ahead of clean-core evidence. Without better analysis, migration planning turns into a reactive archaeology project. AI-assisted discovery can improve that situation by helping teams triage what they actually have before they commit to what comes next.
In practical terms, AI can identify Z-programs in FI/CO that may duplicate standard functionality, posting variants tied to outdated intercompany rules, custom tables for retirement, and extensions better redesigned on SAP BTP. That output is the start of a structured review process, not the end of one.
Process mining adds another layer of evidence. AI can help teams compare how work moves through finance or procurement against SAPs intended process models and best practices. That can expose approval detours, manual rekeying, and shadow processes. For migration teams, the question is not simply which code objects survive, but which process variants deserve to exist in the future-state model. AI accelerates that comparison, but process owners still decide whether a variation reflects a legitimate business requirement.
The AI Dividend Depends on Data
SAP customers clearly have interest in AI. At the end of 2025, 54% of organizations surveyed by SAPinsider were considering AI in their SAP Cloud ERP deployment. Planned usage included Joule at 38% and SAP BTP AI Foundation at 34%. But AI plans depend on prerequisites many organizations are still struggling to address.
SAPinsiders RISE with SAP research identifies remediating custom code and data cleansing as the two most challenging parts of moving to SAP Cloud ERP Private, each cited by about 41%. The same research makes clear that removing unused customizations and harmonizing data are also crucial for using AI effectively. The work required to make migration possible is increasingly the same work required to make AI trustworthy.
The connection is straightforward. The effort to retire a custom material master extension overlaps with ensuring an AI prompt returns a reliable inventory answer. The process standardization required to consolidate order-to-cash variants overlaps with making AI-suggested actions coherent across regions. AI readiness and cloud ERP readiness should not be treated as separate tracks. They are becoming the same discipline. The RISE with SAP Methodology shows how clean core and clean data sit at the center of this shared work, alongside the other agent-led areas that accelerate the transformation.
Data migration is another area where AI sharpens judgment. Organizations deal with duplicate records, inconsistent naming conventions, incomplete master data, and historical information better archived than migrated. AI-assisted analysis can score master data quality, flag anomalies, identify duplicates, and surface records that no longer support active processes. This intelligence makes data scope more realistic early on and reduces the risk of carrying low-value data into a new environment.
SAP Customer Evolution prepares an operating model where clean data, standardized processes, cloud ERP, and modular extensions work together. In that model, AI is not bolted on after the migration. It becomes trustworthy because the underlying ERP landscape is more disciplined.
Testing Still Matters
Testing deserves a clear place in the migration conversation. Once teams decide which processes and extensions remain, they need confidence that redesigned workflows will perform under real business conditions. AI can generate regression test scenarios for high-risk processes by analyzing transaction history, integration dependencies, and prior defect patterns. That is especially useful in financial close or procurement approvals, where a missed edge case causes disruption.
Still, AI is an accelerator for test design and coverage, not a substitute for business validation or final signoff. The value is improving risk visibility, not removing human accountability.
Recommendations Still Pass Through Governance
The post-migration record shows why governance remains essential. Improved process efficiency outcomes fell from 63% to 28% year over year. End-user and business satisfaction declined from 44% to 39%. Successful preservation of necessary custom code declined from 37% to 31%. Technical cutover alone does not guarantee process discipline.
An AI-assisted recommendation may identify a customization as redundant against standard functionality, but a process owner may know it supports a regulatory obligation. Security and compliance teams must validate authorizations, roles, and separation-of-duties impacts. As one SAP COE lead noted in SAPinsiders RISE research, security teams are involved from day one in cloud transitions because cybersecurity controls are essential to avoiding breach risk.
Migration priorities reinforce that point. 84% of organizations cite minimal disruption to operations as a top requirement, 80% cite compliance with global and local regulations, 78% cite integration between core ERP and business applications, and 76% cite cleansed and harmonized operational data. These governance priorities tie directly to business continuity. AI organizes evidence, but decisions sit with the leaders responsible for the operating model.
What This Means for SAPinsiders
For enterprise architects, the clean-core story is no longer just intent. The gap between the 62% who say clean core matters and the lower use of Process Discovery suggests teams lack evidence for confident design. AIs value is helping teams see custom code, process variation, and integration risk as one connected problem, making it easier to decide what to keep, redesign, or move to SAP BTP.
The investment case is converging for CIOs. Custom-code remediation and data harmonization are hard migration tasks and prerequisites for enterprise AI. Spending on cloud ERP readiness increasingly supports AI readiness.
AI-assisted recommendations are inputs to governance, not final deliverables. For system integrators, human review remains non-negotiable. The technology surfaces risks faster, but people still own the design decisions and the business outcome. For teams that want to see how an agent-led approach accelerates the move to SAP Cloud ERP Private, this SAP online learning session offers a practical walkthrough.




