Most DACH SAP customers moving to S/4HANA carry years of custom code from ECC. SAP's mainstream maintenance for ECC 6.0 ends at the end of 2027, with optional extended maintenance until the end of 2030, so the pressure to migrate is real. The recurring risk in these programmes is that new custom development recreates the same upgrade problems, only on a newer platform. SAP's answer is clean core: extensions that use stable, released interfaces so the core can be upgraded without breaking them. Clean core has a practical advantage for companies using an external team: it turns architecture guidance into checkable rules. If extensions must meet a defined clean core level, that level can be written into the acceptance criteria of a Werkvertrag and verified by tooling. This guide explains how.

Where DACH SAP customers stand

The DSAG Investment Report 2026, based on 198 member companies surveyed between December 2025 and January 2026, shows how far the migration has progressed and how far it still has to go. 56 percent of respondents run S/4HANA on premises (2024: 44 percent) and 17 percent in the private cloud, yet 54 percent still operate SAP ECC or older Business Suite releases. Among respondents still investing in ECC, only 37 percent plan to switch by the end of 2027, while almost half aim for the end of 2030, which means paying for extended maintenance. AI opens a second front: 43 percent have implemented AI use cases, but 77 percent of those run non-SAP solutions in production, and 16 percent plan high or medium investment in BTP AI services (2024: 2 percent). Budgets are tighter at the same time, with 28 percent expecting lower SAP spending in 2026. With Bitkom counting 79,000 unfilled IT positions in Germany in 2026, the custom code that must be rebuilt cleanly will compete for scarce developers.

SAP's clean core levels

In August 2025, SAP published a four-level model for classifying extensions.

LevelWhat it meansUpgrade risk
AFully compliant. Uses only publicly released, stable SAP interfaces. Side-by-side on SAP BTP, or on-stack with ABAP CloudLowest
BMeets level A criteria and also uses classic SAP APIs and technologies that are documented and generally upgrade-stableLow
CPartially compliant. Accesses SAP internal objects, typically for legacy scenariosMedium, requires monitoring of SAP changes
DNot recommended. Modifications, write access to SAP tables, implicit enhancementsHighest, significant technical debt

SAP names the ABAP Test Cockpit (ATC) as the key tool for code-level governance. ABAP Cloud enforces the use of released objects through syntax checks.

Choosing the extension pattern

Each requirement should be assigned an extension pattern before development starts. The following decision table covers the most common cases.

RequirementPreferred patternTypical technology
Additional field or simple logic on a standard business objectKey user extensibilityCustom fields and logic in Fiori apps
Tightly coupled logic that needs transactional consistency with S/4HANAOn-stack developer extensibilityABAP Cloud, RAP business objects, released APIs
New application with its own lifecycle, users or dataSide-by-side on SAP BTPCAP (Node.js or Java), SAP Build, released OData or event APIs
Integration with third-party systemsSide-by-side integrationSAP Integration Suite, events via SAP Event Mesh or Advanced Event Mesh
Process automation and approvalsLow-code side-by-sideSAP Build Process Automation

A useful rule: prefer on-stack ABAP Cloud when data consistency with core transactions matters, prefer BTP when the extension has its own lifecycle or user base, and treat anything that would land in level C or D as an exception that needs an architecture decision record.

Clean core as an acceptance criterion

Under a Werkvertrag (BGB §631) with sprint-based acceptance (BGB §640), the following criteria make clean core enforceable:

Each delivered on-stack development object passes the agreed ATC check variant without findings of priority 1 or 2. No delivered object is classified as clean core level D. Any object classified as level C is listed in the release notes with an approved architecture decision record that names the internal object used and the reason no released alternative exists. Side-by-side extensions use only released APIs listed in the SAP Business Accelerator Hub for the client's release.

This wording shifts discussions from opinion to evidence. Either the ATC run is clean or it is not. Either an exception was approved or it was not.

Working remotely in an SAP landscape

SAP projects have specific access and governance requirements that matter more than in typical software projects:

  • Landscape and transports. Development in the development system, transports through quality to production under the client's change management. The external team does not release transports to production.
  • Authorisations. Developer roles restricted to the development system and to the packages in scope. No access to production data by default.
  • BTP accounts. Separate subaccounts for development, test and production, with the external team's access limited to development and test.
  • Version control. ABAP code in gCTS or abapGit, BTP code in Git, with the same review discipline as any other codebase.
  • Test data. Anonymised or synthetic test data in development and quality systems, especially where HR or customer data is involved. Where personal data is accessible from India, a data processing agreement and Standard Contractual Clauses are needed.

Dealing with legacy custom code

Migration programmes usually inherit thousands of custom objects. A pragmatic sequence for an external team:

  1. Run usage analysis to identify custom code that is no longer executed. Retire it rather than migrate it.
  2. Run the S/4HANA readiness checks and classify remaining objects by clean core level.
  3. Group level C and D objects by business capability and decide per group: replace with standard, rebuild as level A or B extension, or accept temporarily with a documented exception.
  4. Rebuild in priority order, with each rebuilt capability delivered as a sprint result with its own acceptance.
  5. Track the share of custom code by level over time as a programme metric.

Governance cadence

Clean core erodes quietly unless someone looks at it regularly. A light cadence is enough: ATC results reviewed in every sprint acceptance, a monthly review of open level C exceptions with the client's SAP architect, and a quarterly check against SAP's release notes for changes to internal objects that level C extensions depend on. The external team prepares the data, the client's architect decides. That division keeps architectural authority inside the company while the delivery work sits with the team.

What to check before engaging a remote SAP team

  • Experience with ABAP Cloud and RAP, not only classic ABAP.
  • Experience with CAP and BTP services relevant to your landscape.
  • Willingness to have every delivery checked by ATC with your check variant.
  • A German-speaking contact who can work with your business process owners on requirements.

For commercial benchmarks on S/4HANA work in DACH, see our separate field note on SAP pricing.

This article is general information and not legal advice. Contract and data protection questions should be reviewed by a qualified lawyer.

Clean core is easiest to hold when it is written into acceptance rather than left to goodwill. A niogod™ pod for SAP work pairs a German-speaking Projektleiter for your business process owners with engineers delivering under a Werkvertrag whose Abnahme includes your ATC check variant and the agreed clean core level, as described on the pod page. If your S/4HANA move is planned before the end of 2027, it is a conversation worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights