Skip to main content

Clean Core

Get your SAP core standard, governed, and upgrade-safe, so the AI era can actually be trusted to run on it.

Clean core is the unglamorous work that decides whether your next S/4HANA upgrade is a weekend or a nightmare, and whether SAP's agents can act on your system without breaking it. We analyze your custom code, move what belongs off-core onto BTP as side-by-side extensions, and rebuild your upgrade path so releases stop being a project. The goal is a core that stays standard while your differentiation lives where it can be changed safely.

Start a conversation See related case studies
Clean Core sketch
“Clean Core,” by Gemini 3 Pro ImageJun 20262,002 tokensthe story →
Why now

A messy core makes AI agents unsafe. A clean one makes them trustworthy.

The reality

  • Years of modifications, enhancements, and BAdIs sit inside the digital core, so every S/4HANA upgrade turns into a regression-testing slog and custom code keeps breaking on release.
  • At Sapphire 2026 SAP put agent-led migration tooling front and center, promising 35 percent-plus effort reduction. That tooling assumes a standard, well-governed core. It cannot reason about spaghetti you bolted on a decade ago.
  • Autonomous Enterprise and Joule agents act on your live system. Point an agent at undocumented custom logic and an over-customized core and you have automated a mistake at machine speed.
  • Clean core got framed as fit-to-standard purism, which made teams either ignore it or panic. Neither move gets you to a system that upgrades cleanly or runs AI safely.

What changes

  • A core you can trust an agent to touch

    Standard, documented, decoupled from custom code. That is the actual entry requirement for SAP Business AI and Joule to act on your data without supervision, not a nice-to-have you add later.

  • Custom code judged honestly, not dogmatically

    We classify against SAP's Clean Core levels (A best, D dirtiest, per SAP Note 3578329). Some traditionally criticized techniques are Level B and fine to keep. We triage by real risk, not LinkedIn hot takes.

  • Differentiation moved off-core

    The logic that makes you you moves to BTP as side-by-side extensions, where it can change on its own clock without blocking a core upgrade. The core stays standard underneath it.

  • Upgrades that stop being projects

    Once the core is clean and extensions are decoupled, releases become side-effect-free. You take SAP innovations as they ship instead of running an upgrade program every couple of years.

  • A roadmap matched to your RISE and S/4 timeline

    Clean core is a direction, not a destination. If you have no near-term Public Cloud move, we prioritize the cleanup that unblocks business value first and sequence the rest.

Critical insight

Clean core is the precondition for both modernization and the AI era. Skip it and your S/4 upgrades stay painful and your agents stay unsafe to deploy. Do it and you get a platform SAP's tooling, and ours, can actually act on.

Capabilities

The work that gets your core clean and keeps it that way

Five tightly scoped workstreams. We start where the risk and the payback are highest, not with a boil-the-ocean rewrite.

01

Custom code analysis and triage

We inventory every modification, enhancement, and extension, then classify it against SAP's Clean Core levels A through D and your own usage data.

  • Map development objects to cloud-readiness and upgrade-stability levels (SAP Note 3578329)
  • Separate the genuinely dirty (most implicit and explicit enhancements, obscure UI techniques) from techniques that are fine to keep
  • Rank by upgrade risk, business value, and effort, so the backlog reflects reality

02

Side-by-side extension migration to BTP

We move off-core logic onto SAP BTP using the ABAP Cloud model and clean APIs, so custom function lives where it can be changed without touching the digital core.

  • Rebuild on-stack modifications as side-by-side extensions on BTP
  • Replace direct table access and tight coupling with released APIs and events
  • Stand up the BTP foundation (Integration Suite, Build, Cloud ALM) the extensions run on

03

Core decoupling roadmap

A sequenced plan that ties cleanup to your RISE and S/4HANA timeline, with clear calls on what to refactor, what to move, and what to retire.

  • Decouple integration and custom logic from the core ahead of an S/4 move
  • Sequence around go-lives so cleanup unblocks the program instead of stalling it
  • Document point-to-point integrations and dependencies before anything moves
  • SAP LeanIX to map the application landscape and target architecture first, so the decoupling sequence reflects how the systems actually connect

04

Continuous, side-effect-free upgrades

Once the core is standard and extensions are decoupled, we set up the governance and automation that keep releases boring.

  • Automated checks that flag new code drifting back toward Level C or D
  • Regression and test-data tooling so each release is faster than the last
  • Coding standards and DevOps guardrails that hold the line after we leave

05

RISE and S/4HANA readiness

We get your landscape into a state where RISE with SAP and the S/4HANA transition land cleanly, and where SAP's agent-led migration tooling can actually help.

  • Readiness assessment against the target edition (Private vs Public Cloud) constraints
  • Remediate the custom code that would otherwise block or slow the conversion
  • Position the clean core as the foundation for Joule and SAP Business AI
Real impact

Clean core work we have actually shipped

100%

of in-scope integrations code-reviewed and passing initial functional testing

A building products manufacturer

We are moving a building-products manufacturer's legacy PI/PO integration core onto SAP BTP Integration Suite, aligned to clean-core principles, without stopping the manufacturing lines. Every integration process map is documented in Signavio, as the blueprint for the eventual ECC-to-S/4HANA move.

CloroxClorox
Fit-to-standard

clean-core foundation for autonomous finance on S/4HANA, Datasphere, and SAC

Clorox's Elevate program took a clean-core approach: fit-to-standard as the ground rule, duplicative boundary apps rationalized, and guardrails routing data through Datasphere so SOX key-control reports source from the SAP core. We helped stand it up and bridge the Finance team into SAP architecture. Presented publicly by Clorox and Mindset at two SAP summits.

How we engage

Assess, move, then keep it clean

Clean core is a direction, not a one-time project. We deliver quick wins early and build the governance that holds afterward.

  1. Phase 1

    Assess and triage

    3 to 6 weeks

    We inventory your custom code and integrations, classify against the Clean Core levels, and hand you a prioritized roadmap that says exactly what to refactor, what to move to BTP, and what to leave alone.

  2. Phase 2

    Decouple and migrate

    3 to 9 months

    We refactor the high-risk custom code, rebuild off-core logic as side-by-side extensions on BTP, and decouple integrations. Quick wins land first so the core gets measurably cleaner before the big moves.

  3. Phase 3

    Enable continuous upgrades

    Ongoing

    Automated checks, coding standards, and DevOps guardrails keep new development from drifting back toward a dirty core, so releases stay side-effect-free and the system stays ready for SAP Business AI.

Common questions

Clean core, answered straight

Does clean core mean ripping out all our custom code?
No. It means keeping the digital core standard and upgrade-safe while your custom logic moves to where it can change without blocking a release. We classify code against SAP's Clean Core levels A through D. Some techniques people assume are dirty are actually Level B and fine to keep. The decision about what is worth refactoring rests with you, guided by real risk and business value, not dogma.
What does clean core have to do with AI?
Everything. SAP's agents, Joule and the Autonomous Enterprise tooling shown at Sapphire 2026, act on your live system. An agent can only behave reliably on a core that is standard, governed, and decoupled from custom code. A messy core makes agents unsafe, because they automate against logic they cannot reason about. Clean core is the precondition for trustworthy SAP Business AI, not a separate initiative.
How does this fit with our RISE or S/4HANA move?
Clean core is the work that makes the move land cleanly. SAP's agent-led migration tooling promises real effort reduction, but it assumes a standard, well-governed core to reason about. We get your custom code triaged and your integrations decoupled before the conversion, so the migration is faster and the tooling can actually help. If you have no near-term move planned, we prioritize the cleanup that unblocks business value first.
Where do the extensions go once they come off the core?
Onto SAP BTP as side-by-side extensions, built with the ABAP Cloud model and connected through released APIs and events instead of direct table access. That is where your differentiation lives and changes on its own clock. See our SAP BTP work for how we stand up that foundation.
Is clean core a one-time project or ongoing?
Ongoing. The initial cleanup is a project, but staying clean is a discipline. We set up automated checks, coding standards, and DevOps guardrails so new development does not drift back toward a dirty core. That is what keeps upgrades side-effect-free and the system ready for each new SAP release.
Recent thinking

From our Insights.

All Insights
Adjacent practices

More of our SAP technical work.

SAP BTP

The foundation your SAP estate extends, integrates, and runs AI on.

Read more

SAP Integration Suite

Retire PI/PO before 2027 and build the integration layer your agents will run on.

Read more

Application Management Services

SAP support from the people who understand the architecture, not a generic helpdesk.

Read more

Business Data Cloud

The path from BW to intelligent enterprise

Read more

S/4HANA

The core your business runs on, and the foundation everything else gets built on top of.

Read more

DevOps for SAP

Ship SAP changes on demand, without putting the system of record at risk.

Read more

Talk to a Clean Core partner.

The first call is a working session, not a pitch. Bring a real problem and we’ll whiteboard it with you.

Start a conversation