ECC end of maintenance: what 2027, 2030 and 2033 really mean

Every ECC customer has heard “2027”. Fewer can explain what actually stops that year, what it costs to keep going, and why some companies talk about 2033. If you are the one who will sign off the S/4HANA go-live, those dates set the back end of your test plan, so it is worth getting them exactly right.

The timeline in one table

2027: mainstream maintenance ends

In 2020 SAP committed to mainstream maintenance for Business Suite 7 core applications, including ECC 6.0, until the end of 2027, and aligned SAP NetWeaver 7.5 to the same dates^[1],[2]. Mainstream maintenance is what most customers think of as “support”: legal changes, corrections and updates delivered as part of the standard fee.

2028 to 2030: extended maintenance, at a price

From 2028 to 2030 SAP offers optional extended maintenance at a two-percentage-point premium. Customers who do not opt in by the end of 2027 move automatically to customer-specific maintenance, which is a much thinner service than its name suggests^[1],[2]. Extended maintenance buys time; it does not remove the move.

2033: the transition option, and who qualifies

In February 2025 SAP announced the SAP ERP, private edition, transition option. SAP describes it as non-mandatory. It can be purchased from 2028 and used from 2031 to 2033. To qualify, a customer must run ECC 6.0 at EhP 6 or higher on SAP HANA, move into Private Edition before the end of 2030 with a RISE commitment, and accept an expanded fee versus a comparable subscription. It covers ECC, not the full Business Suite, and it is explicitly not an extension of on-premise maintenance^[3],[4].

Your test tooling has a deadline too

Many SAP test programs still run on Solution Manager Test Suite. SolMan 7.2 mainstream maintenance also ends at the end of 2027. Extended maintenance to 2030 covers only selected functions, including Test Suite and ChaRM, and SAP recommends moving to SAP Cloud ALM before the end of 2027; Cloud ALM is not a one-to-one replacement^[5]. If your regression suite lives in SolMan, its migration belongs in the same plan as the S/4HANA move.

Where companies actually are

The German-speaking user group DSAG reported in February 2026 that 54% of its surveyed members still run ECC somewhere, down from 68% in 2024. Asked when they plan to finish switching, 37% said by the end of 2027, 48% by 2030 and 4% by 2033^[6]. In other words, roughly half of the companies in that survey are planning to be on S/4HANA only after mainstream maintenance ends.

Schedules also slip. A 2025 Horváth study of 200 companies found S/4HANA projects ran 30% longer than planned on average and only 8% finished on time, with underestimated testing and data migration among the causes^[7]. Work backwards from your maintenance date with that in mind.

Working backwards from your date

1. Pick the real date. End of 2027, or end of 2030 if you will pay for extended maintenance. Decide this before planning, not during.
2. Subtract hypercare and a buffer. At least one month-end close in hypercare, plus a contingency for the 30% average overrun.
3. Subtract cutover rehearsals. Two or three mocks and a dress rehearsal, each needing a reconciled result.
4. Subtract SIT and UAT. Two integration cycles and UAT, sized from your process library.
5. What is left is your build window. If it is not enough, the conversation about scope, approach or extended maintenance needs to happen now.

The phase-by-phase migration test plan and the free migration test plan and readiness checklist templates turn this into a schedule.