Clean core, explained on one page
What SAP means by clean core, why it matters for upgrades and AI, and the practical steps to get there.
Ostrell Consulting ·

“Clean core” is one of SAP’s most-used phrases, and one of the least explained. Here it is on one page.
What it means
A clean core is an SAP system kept close to standard. Changes and extensions are made in ways SAP supports and upgrades don’t break: through configuration, released APIs, and extensions built side-by-side on SAP Business Technology Platform (BTP) rather than modifications inside the core.
Why it matters
- Upgrades get smaller. Fewer modifications mean less to retest and fix every time SAP releases an update.
- New features arrive faster. Including SAP’s AI capabilities, which work best on standard processes and clean data.
- Lower running costs. Less custom code to support, document and explain to new team members.
The five areas to look at
- Custom code. Find what is used, what is duplicated and what is dead. Retire what you can.
- Extensions. Move suitable extensions out of the core onto BTP.
- Integrations. Rebuild point-to-point interfaces on SAP Integration Suite using released APIs.
- Data. Clean master data and keep it clean with ownership and rules.
- Processes. Adopt standard processes where they are good enough, which is more often than people expect.
Where to start
A clean core assessment gives you a list of what to keep, rework or retire, and a plan to get there without stopping the business. It pairs naturally with an S/4HANA move, but you can start on ECC today.
