
Meet the Authors
Kellton's recent analysis identifies seven strategic decisions that determine whether an SAP S/4HANA transformation delivers business value or just a technical upgrade.
SAPinsider's 2026 ERP Migration and Transformation research shows only 34% of organizations have completed their SAP S/4HANA transition as the 2027 deadline nears.
Kellton argues that fragmented master data and inconsistent processes now cap enterprise AI ambitions, making ERP foundation quality an AI readiness issue.
Why do SAP S/4HANA programs that go live on time and on budget still have business leaders asking why planners export data to spreadsheets and finance still reconciles manually? In a recent article, Dr. Srinivas Bandi, Senior Vice President for SAP at Kellton, argued that ERP transformations rarely fail because of technology. They underperform because critical strategic decisions were delayed, underestimated, or never made at all.
The article lays out seven decisions that separate high-performing transformations from expensive upgrades. The first is the business case itself: programs built on ECC support is ending, frameworks deliver a modern ERP and little else, while the strongest cases start from a measurable operational constraint, such as missing real-time inventory visibility or a data model that forces manual reconciliation at every close. The second and third decisions address process and technical debt. Mature ECC environments carry hundreds of process variations and thousands of custom objects, and SAP’s Clean Core strategy exists precisely to force the question of which ones deserve to survive.
The remaining decisions cover data architecture readiness for the Universal Journal (ACDOCA), integration architecture that scales beyond the ERP through API-led connectivity and SAP Business Technology Platform (BTP), whether SAP becomes the foundation for enterprise AI, and how transformation value is measured after go-live. The AI point is notable. The article argues the quality of the SAP foundation is increasingly the ceiling on AI ambition, because fragmented master data and inconsistent processes do not stop reporting. However, they do stop organizations from trusting AI outputs enough to act on them.
The article builds on Kellton’s earlier 2026 guidance, including its comparison of greenfield, brownfield, and bluefield migration approaches, which notes that brownfield conversions typically complete in six to eighteen months while greenfield programs can run from eighteen months to three years, and its 2026 guide to SAP BTP side-by-side extensions, which positions Clean Core as a matter of business survival rather than best practice.
Research Backs It Up
SAPinsider’s Benchmark Research on ERP Migration and Transformation 2026 underscores the urgency of these decisions. While 55% of surveyed organizations report having deployed SAP S/4HANA or SAP S/4HANA Cloud, only 34% indicate a completed transition, and 36% are still implementing, evaluating, or building a business case. The research also found that nearly three times as many respondents as last year cite SAP’s AI announcements as the biggest external factor shaping their migration plans, confirming Kellton’s argument that AI readiness now sits inside the ERP business case rather than beside it.
Meanwhile, SAPinsider’s Technology Leader’s Strategic Agenda for 2026 reports that 70% of technology leaders name increasing operational efficiency and reducing costs as their top priority. Kellton’s framing of the migration as a systematic elimination of process, technical, data, and integration debt speaks directly to that agenda.
What This Means for SAPinsiders
A weak business case guarantees a weak outcome, even with a flawless go-live. With the end of mainstream maintenance in 2027 approaching and 36% of organizations still in evaluation or implementation, ERP program managers should anchor their SAP S/4HANA business case to a specific operational constraint with a measurable cost, and then evaluate every scope decision against that outcome.
Clean Core is a classification exercise, not a slogan. CIOs and enterprise architects should run SAP’s custom code analysis before finalizing a migration approach and sort every process and custom object into three buckets: competitive differentiation, regulatory necessity, or historical inertia. Kellton’s analysis suggests that the third bucket is consistently the largest and represents the transformation opportunity.
AI ambition now depends on the quality of the ERP foundation. SAPinsider’s 2026 research shows that AI access has become a major driver of migration, but AI also exposes weaknesses that dashboards absorb. Data and analytics leaders should invest in master data remediation and integration architecture on SAP BTP before go-live, treating the Universal Journal and governed data as prerequisites for any credible SAP Business AI roadmap.



