Mainstream maintenance for SAP ECC 6.0 (EHP 6–8) ends December 31, 2027. SAP has confirmed there will be no further extensions. For enterprises still running ECC, the runway is shorter than the calendar suggests.
What Actually Ends, and When
Two dates get conflated in most coverage, and the difference matters for your planning.
December 31, 2025 was the deadline for SAP ECC 6.0 running Enhancement Packages 0 through 5. That mainstream maintenance has already ended. If your landscape falls in this group, you are already operating past standard support.
December 31, 2027 is the deadline that applies to the majority of the installed base: ECC 6.0 with Enhancement Packages 6, 7, or 8.
Customers who haven’t moved to S/4HANA or opted into extended maintenance by that date aren’t cut off outright. SAP automatically shifts them into what it calls customer-specific maintenance: a reduced tier with no new legal or regulatory updates, limited security patches, and no new features.
The system does not stop running on January 1, 2028. What stops is SAP keeping it compliant, secure, and current the way mainstream maintenance does today. For finance, HR, and supply chain systems in regulated industries, that gap compounds fast.
The Math Isn’t on Your Side
Public estimates of S/4HANA adoption vary by source, but the available ones put licensed adoption among ECC customers well under half, with one SAP migration advisory placing it around 39%. However you slice it, a large share of the installed base is still somewhere between “evaluating” and “haven’t started,” and the clock is not waiting for either.
Advisory estimates for a typical S/4HANA migration range from about 12 to 36 months, depending on scope, the depth of customization to unwind, and whether the path is brownfield or greenfield. Even at the fast end of that range, a project greenlit today, mid-2026, is already a tight fit for a December 2027 cutover. A project that starts after the deadline has passed is not a migration anymore. It’s a fire drill, run on SAP’s commercial terms instead of yours.
Three Paths Forward
None of these are permanent exemptions from moving off ECC. Each buys a different kind of time, at a different cost.
Cloud or on-premise, brownfield or greenfield, this is the only option that gets ahead of the deadline instead of reacting to it.
- Requires committing budget and scope within this fiscal year to realistically land before Dec 2027
- Opens access to SAP’s native AI tooling, including Joule, which depends on a standardized core
Available for EHP 6–8 customers from 2028 through 2030, at roughly a 2-percentage-point premium (commonly cited as a 9-12% total cost increase with annual index adjustments included).
- A bridge, not a destination: a migration plan still has to sit behind it
- Skip it, and the system defaults to the reduced customer-specific maintenance tier
SAP has a private edition transition option that can extend runway further for eligible customers. Sources disagree on the exact end date, 2030 versus 2033, likely reflecting different offers, so confirm current terms directly with SAP. Third-party providers offer an alternative bridge entirely outside SAP’s timeline.
- Buys flexibility on timing, not a permanent exemption
- Third-party paths typically forfeit access to new SAP innovation built for S/4HANA
Decide From a Position of Strength
Organizations that come out ahead treat 2027 as a planning deadline, not a migration deadline. The actual cutover needs to land well before the maintenance clock runs out, which means an honest inventory of your ECC footprint, a clear-eyed call on what’s genuinely custom versus what can move to standard, and a realistic read on your organization’s own delivery speed, now, while there’s still room to choose the path.
Not sure where your ECC environment actually stands?
Varchai has spent over a decade inside Oracle and SAP landscapes across life sciences, BFSI, engineering & construction, and hospitality, the kind of regulated, multi-entity estates where a rushed ECC migration is the most expensive mistake on the table.
