Clean Core First

8–12 weeks · BTP / +AI · P1·P2 · fixed-fee

Before you migrate, clean the core. We rationalise your custom code, retire what you don't need, and move keep-code extensions to BTP — so you arrive at S/4 clean, not dragging decades of debt across the bridge.

• ·Readiness assessment shows a heavy, non-compliant custom-code estate.
• ·You want to de-risk and de-cost the conversion by shrinking the estate first.
• ·Leadership has bought the 'don't migrate the mess' argument.

• ·Confirm classification & lock clean-core guardrails / decision tree.
• ·Retirement wave — decommission unused code with sign-off and audit trail.
• ·Remediation & tiering to released APIs (ABAP Cloud where fit).
• ·First side-by-side BTP extension (CAP/RAP) + guardrails in Cloud ALM.

• ·Rationalised custom-code estate (retired + remediated) with audit trail.
• ·One side-by-side BTP extension live as the pattern reference.
• ·Clean-core guardrails + conformance baseline + developer runbook.