The problem
SAP ends mainstream maintenance for ECC 6.0 at the end of 2027. Extended maintenance is available until 2030, at a higher fee. After that there is no more support, apart from a limited exception through SAP itself. Even so, a large share of ECC users have not yet planned a move: in a survey by the German-speaking SAP user group DSAG (early 2026), only just over a third expected to have moved before the end of 2027.
Why it keeps coming back
- Opaque systems. After twenty years, nobody knows exactly what is running, which integrations exist and which custom code is still in use.
- An unclear business case. A migration costs a lot; what it delivers is often vague.
- Too few people. Experienced SAP specialists are scarce, and the same people also run day-to-day operations.
Our approach
- Facts first. We read out the system: release, components, functions in use, integrations and custom code. Then you know where you stand, without assumptions.
- Then returns. What does a move deliver, what does staying cost, and which parts are better off outside SAP? Returns first, then control, then technology.
- Then the route. Converting to S/4HANA, extending temporarily, or replacing parts with lighter software. Often it is a combination.
- Testing without risk. In our own SAP lab we test integrations and custom code before they touch your system.
What to watch out for
- Do not start with the date, but with the inventory. A good inventory makes every route cheaper.
- Clean up custom code before the migration, not after.
- Include integrations: every integration has to work again in the new situation and may have licence implications. Plan moving integrations as a separate workstream.
Would you like advice on SAP ECC after 2027? Request a free advice conversation.
Sources
Updated on