ECC after 2027: the real deadlines and the options left

SAP announced its Business Suite 7 maintenance timeline back in 2020, and it has not moved since. With a little over a year to go before the first date, here is what each deadline actually means and what you need to have done to use each option.

The three dates

31 December 2027: end of mainstream maintenance. For SAP ECC 6.0 on enhancement packages 6 to 8, and for most of the Business Suite 7 family (CRM, SRM, SCM including APO, PI/PO, Solution Manager), standard maintenance ends. Your system keeps running. What stops is the stream of legal changes, new fixes and standard support at the normal price.

31 December 2030: end of extended maintenance. Customers can buy extended maintenance for 2028 to 2030 at a premium on their existing maintenance fees. It covers ongoing fixes and support but no new functionality. After 2030 there is no standard support of any kind.

2031 to 2033: the SAP ERP, private edition transition option. Announced by SAP's CEO in early 2025, this is not an extension of ECC maintenance. It is a cloud subscription for running ECC as SAP ERP, private edition, as a bridge to S/4HANA. The conditions reported so far are strict:

• It is tied to a RISE with SAP commitment.
• The database must be SAP HANA. ECC on Oracle, DB2 or SQL Server does not qualify until it has been migrated.
• The system must have moved to SAP ERP, private edition before the end of 2030.
• It covers ECC only, not the other Business Suite products.
• It is priced above an equivalent subscription before 2031, and commentators expect the uplift to grow the later a customer commits.

Why 2027 is closer than it looks

A medium-sized ECC to S/4HANA conversion typically needs several months of assessment and preparation before the first conversion run, then multiple test cycles and a cutover window that avoids peak season and year-end. Large greenfield or selective programmes run longer. Working backwards from the end of 2027, many companies that have not started are already relying on extended maintenance, whether or not they have budgeted for it.

What you can do in ECC right now

Whichever approach you choose, a lot of useful work happens in the old system:

• Run SAP Readiness Check and get an honest view of simplification items, add-ons and custom code.
• Clean customer and vendor master data ahead of Business Partner conversion. Duplicates and incomplete records are the most common reason the CVI step stalls.
• Retire unused custom code. Usage data from production typically shows a large share of Z-programs are never called.
• Archive old data to shrink the database and the conversion downtime.
• Decide your target deployment model with your SAP account team, since it determines which of the options above you can use.

Choosing a path

Brownfield conversion keeps history and configuration and is usually the fastest technical route. Greenfield re-implementation gives a clean start and a chance to adopt standard processes, at the cost of a longer design phase. Selective data transition sits between the two and suits companies consolidating several ECC systems. The right choice comes from assessing your actual system, not from a preference, and the assessment itself is a small investment compared with paying for 2028 to 2030 by default.