When Does SAP ECC Support End? The Real 2027 Deadline, Explained by EHP Version

SAP ECC maintenance timeline at a glance

When does SAP ECC support end?

SAP ECC 6.0 and the wider SAP Business Suite 7 reach the end of mainstream maintenance on December 31, 2027. SAP then offers optional extended maintenance through the end of 2030 at a premium of two percentage points on your maintenance base. After 2030, only customer-specific maintenance remains, which provides no new fixes, legal or tax updates, or patches.

That is the headline date. Your actual deadline can be earlier, because it depends on the Enhancement Package (EHP) version you run and the specific components and industry add-ons in your landscape. Some older releases and component stacks already lost mainstream maintenance in 2025. So the first question is not how to get to S/4HANA. It is which deadline actually applies to us.

Your path off ECC

ECC 6.0 to a 2027 Readiness Assessment to SAP S/4HANA. Start with the assessment; the migration itself typically runs 18 to 36 months.

Yes. SAP ECC 6.0 shipped across a series of Enhancement Packages, numbered EHP 0 through EHP 8, and the maintenance clock is not uniform across everything in your system.

• Core ECC on a current EHP generally reaches the 2027 mainstream date. If you are on an older EHP, you may need an EHP upgrade just to stay in mainstream maintenance until 2027.
• Industry solutions and add-ons such as IS-U, IS-Oil, retail, or banking components can carry their own maintenance timelines that do not automatically match the core.
• Third-party and bolt-on components integrated into ECC may age out independently.

The practical result: two companies both running ECC 6.0 can have materially different effective deadlines. The only way to know yours is to inventory the actual EHP level, components, and add-ons in your production landscape.

Extended maintenance runs from 2028 to the end of 2030 at a premium of two percentage points on top of your existing maintenance basis. It keeps standard support running during a longer migration, but it does not add new innovation. Treat it as a bridge, not a destination.

You move to customer-specific maintenance. In practice that means no new corrections, no legal or regulatory update patches, and steadily rising security and compliance risk. It is a holding state, not a supported one, and it is not a place to run a core ERP long term.

SAP leadership has repeatedly confirmed that the 2027 date is not moving for the general customer base. The only widely signaled flexibility is tied to committing to a cloud transition (RISE with SAP) for large, complex landscapes. That is an exception, not a reprieve.

Across more than 100 SAP landscape assessments, the same patterns recur:

• Teams assume they have until 2030 because they have heard extended maintenance, without realizing it is paid, time-boxed, and innovation-frozen.
• EHP levels are older than IT believes, quietly shortening the real runway.
• The migration timeline is underestimated because scope is measured in modules, not in custom code, interfaces, and data debt, which are the things that actually drive the calendar.

The companies that move calmly are the ones that started with a clear-eyed inventory 24 to 36 months out. The ones that scramble treated 2027 as a single, distant, uniform date.

Most enterprises should plan for 18 to 36 months. The timeline depends far more on custom code volume, interface count, and data quality than on the number of SAP modules you run. Start with a landscape assessment so you are sizing the work against reality, not against a module count.