In my conversations with SAP leaders since Sapphire 2026, one thing has become increasingly clear: Clean Core has graduated from technical best practice to strategic mandate. SAP is positioning it as the foundation upon which modernization, cloud transformation, and AI-enabled speed will be built. 

For years, customization was viewed as an unavoidable part of running SAP. After all, it was part of the appeal that brought businesses to SAP in the first place. Organizations developed bespoke processes, custom code, specialized reports, and local variations to meet business requirements that standard functionality could not address. The resulting complexity was accepted as the price of flexibility, but what was often overlooked was the cumulative impact of those decisions. Technical debt built up gradually, hidden inside development backlogs, upgrade projects, and support models. It was expensive and occasionally frustrating, yes – but rarely viewed as a strategic concern. 

Today, that perspective has changed. The conversations taking place across the SAP ecosystem increasingly reflect a different reality. What was once considered technical debt is now a business constraint. As organizations seek to accelerate S/4HANA adoption, move to the cloud, and prepare for AI-driven operations, this complexity has become an enterprise-wide barrier to agility. 

That evolution is reflected in the conversations I’m having every week with SAP leaders in complex enterprises. Regardless of industry or geography, the same takeaways keep surfacing when we talk about Clean Core. Based on what I’m hearing, and what I’ve seen organizations deal with in practice, five observations stand out.

1. Clean Core Has Become Measurable 

One of the most significant developments in recent years has been SAP’s decision to reposition Clean Core from a principle into a measurable framework.  

Historically, technical debt was difficult to quantify. Most organizations knew it existed, but few could accurately assess its scale or understand its impact on future innovation. Now, they can evaluate their Clean Core maturity across areas such as Processes, Data, Integrations, Operations, and Extensibility (along with SAP’s latest Clean Core A-to-D framework). 

Technical debt is no longer completely hidden; it is measurable and increasingly tied to an organization’s ability to adopt new capabilities. The importance of this evolution lies not in the score itself, but in what it reveals. Organizations now have a clearer understanding of how complexity and customization may be affecting upgrade readiness, innovation velocity, and long-term operational costs — the same move toward economic measurement that’s reshaping how SAP change gets reported at board level.

2. The Biggest Challenge Is Visibility

Many organizations assume remediation is the most difficult aspect of a Clean Core strategy. In practice, visibility is often the greater challenge. 

Few organizations can confidently answer fundamental questions about their SAP landscape: Which customizations continue to deliver business value? Which duplicate standard functionality? Which have become obsolete? What alternatives are there? 

Without those answers, remediation efforts often become reactive and inefficient. Before complexity can be reduced, it must first be understood. 

3. Governance Matters More Than Remediation 

Removing existing technical debt is important, but the priority should be to prevent new technical debt from making its way into production. 

Complexity rarely enters an SAP landscape through major transformation programs. More often, it accumulates through hundreds of smaller decisions: a local business exception, a custom enhancement, a project shortcut, or a governance process bypassed to meet a deadline. Each decision may appear justified in isolation, but collectively, they create the very complexity organizations later spend years trying to remove. 

This is why getting clean and staying clean are fundamentally different challenges. Remediation addresses historical debt, whereas governance determines whether new debt will emerge. 

4. Artificial Intelligence Has Changed the Conversation

One of the dominant themes at this year’s Sapphire was the growing focus on autonomous operations and agentic AI. Organizations are exploring how AI can automate increasingly sophisticated business processes. These systems depend upon consistent data structures, standardized business rules, and predictable process models.

Customization introduces uncertainty into each of those areas. An AI agent may be capable of processing information at extraordinary speed, but it cannot reliably navigate years of undocumented exceptions, overlapping customizations, and inconsistent business logic. 

The risk extends beyond inefficiency. Poorly governed AI systems have the potential to amplify inconsistencies, execute flawed business logic at scale, and undermine the very efficiencies they are intended to create. For many organizations, Clean Core has evolved from something that makes upgrades easier to a business imperative linked to AI readiness. 

5. Clean Core Must Be Built into Everyday Change

The organizations making the greatest progress are approaching Clean Core differently. They are not treating it as a one-time remediation effort, nor are they viewing it as a compliance exercise. Instead, they are building the capabilities required to continuously understand, govern, and enforce Clean Core standards throughout the lifecycle of their SAP environment. 

They are identifying technical debt earlier, making better design decisions, preventing non-compliant changes from entering production, and maintaining visibility as their landscapes evolve. 

From Remediation to Discipline 

Treating Clean Core as a strategic prerequisite represents a fundamentally different mindset: one focused on operational discipline before remediation. The question is no longer whether organizations should pursue Clean Core, but how they build the visibility, governance, and discipline required to sustain it. 

That discipline has to live somewhere other than a policy document or in someone’s head. It should be built into your release model itself, at the point where a change either moves toward standard or drifts away from it.  

This is where Intelligent Change Management becomes the operating model for Clean Core. 

Klario helps organizations make better decisions before work begins. Using agentic AI, it evaluates requirements, explores potential solution approaches, and assesses them against SAP best practices and Clean Core principles. Rather than defaulting to customization, teams gain a clearer understanding of the trade-offs involved and can identify opportunities to adopt standard functionality, key-user extensibility, or compliant side-by-side extensions before development starts. 

ActiveControl then governs execution. Compliance checks, code analysis, transport governance, and release controls ensure those decisions are implemented consistently and that non-compliant changes are identified before they reach production. As delivery continues across complex SAP landscapes, dependency mapping and change controls help prevent the reintroduction of the very complexity organizations are trying to remove. 

Together, Klario and ActiveControl connect design intelligence with governed execution. This is what Intelligent Change Management looks like in practice: an operating model that combines AI-guided decision-making with enterprise-grade change orchestration, enabling organizations to maintain a Clean Core while continuing to deliver change at the speed of business. 

The Question is No Longer Whether, But How

Throughout this article, I’ve shared the Clean Core takeaways I keep hearing from SAP leaders and the patterns we’re seeing across organizations. The most successful enterprises are now building Clean Core into the way change is designed, governed, and delivered rather than treating it as a one-time initiative. 

If you’re thinking about how to turn Clean Core from a project into an operating model in your own SAP environment, let one of our experts guide you through what’s worked for similar organizations. Book a 30-minute conversation to get started.