Executive Clarity · Decision 1 of 8

The ECC Decision Timeline

2027 is a date. 2030 is a backstop. The July 2026 EU commitments changed the economics in between. Here is how to decide.

The question

When does your organisation actually have to leave SAP ECC — and which of the paths between now and 2030 is yours: migrate, buy time with extended maintenance, qualify for SAP's transition option, or use third-party support as leverage?

Decision factors

The documented facts

  • Mainstream maintenance for SAP ECC 6.0 with Enhancement Packages 6–8 ends on December 31, 2027. SAP offers extended maintenance through December 31, 2030 at a premium of roughly two percentage points on the maintenance base (SAP's published maintenance strategy for SAP Business Suite 7, SAP Note 1648480).
  • For SAP ERP 6.0 without an enhancement package, and with EHP 0–5, mainstream maintenance already ended on December 31, 2025 — with no extended-maintenance option. Those systems run in customer-specific maintenance today: no new support packages, no new legal changes, fixes on request only.
  • Maintenance for Enhancement Packages 0–5 already ended in December 2025, with no extension offered.
  • In early 2025 SAP announced the RISE-based "SAP ERP, private edition, transition option", which extends ECC support beyond 2030 for qualifying customers — targeted at very large or complex ECC landscapes and tied to a commitment to move to SAP S/4HANA.
  • In July 2026 the European Commission accepted legally binding commitments from SAP in its ERP maintenance-and-support antitrust case (opened September 2025). SAP must allow customers to terminate maintenance on unused licences ("shelfware"), let customers segment their landscape and source maintenance for parts of it from third parties — or drop it — and has eliminated reinstatement fees for returning customers. The commitments apply globally for ten years under a monitoring trustee (European Commission press release IP/26/1554).

Inference

  • The EU commitments materially strengthen the customer's negotiating position for the 2027–2030 window: third-party support for part of the landscape is now a credible, reversible option rather than a one-way door, because reinstatement penalties are gone.
  • Extended maintenance is best understood as an insurance premium on a migration plan that already exists — not as a strategy. Its cost is predictable; the cost of entering 2028 without a committed plan is not.
  • The transition option signals that SAP itself expects a long tail of complex ECC landscapes past 2030 — but qualifying for it means committing to S/4HANA, so it is a migration on-ramp, not an escape hatch.

Point of view

Treat 2027 as firm and 2030 as the absolute backstop. The organisations in trouble in 2029 will not be the ones who chose a "wrong" path — they will be the ones who deferred the choice. Audit your ECC usage now, decide which processes genuinely need re-design rather than conversion, and put a named executive owner on the timeline.

First: your EHP level decides your real deadline

"2027" is shorthand that only applies to the newest ECC releases. The honest first step is an inventory question, not a strategy question:

  • EHP 6–8: the 2027/2030 window above applies. You are deciding how to use time you still have.
  • EHP 0–5 (or no EHP): the deadline has already passed. Since January 2026 these systems run in customer-specific maintenance — reduced scope, no legal changes — whether or not the board has been told. The decision is no longer "when do we move" but "how long do we accept operating out of maintenance, and what bridges it".
  • The bridge option: an upgrade to EHP 8 returns an older ECC system to mainstream maintenance until end-2027 (and the 2030 extension) — a legitimate risk-reduction move for landscapes whose S/4HANA or Cloud ERP migration realistically lands after 2027, priced against simply accelerating the migration itself.
THE ECC DECISION FORK SAP ECC today Which EHP level runs today? EHP 0–5 / none EHP 6–8 Deadline already passed Mainstream ended Dec 31, 2025 · no extension running in customer-specific maintenance Mainstream until Dec 31, 2027 extended maintenance to Dec 31, 2030 at a premium — time to decide, not to defer bridge: upgrade to EHP 8 Does the business still depend on substantial custom ABAP and carried-over ECC processes? No — standardise Yes — keep control GROW with SAP SAP Public Cloud · multi-tenant clean core by contract · greenfield RISE with SAP SAP Private Cloud · dedicated instance custom ABAP · brownfield conversion Conditional, not ideological — the July 2026 EU commitments restored the time to decide deliberately.
The ECC decision fork — derived from the sapperment decision guides RISE vs GROW and Public vs Private Cloud.

Conditional, not ideological — the recommendation grid

If

You can complete migration before end-2027

Standard path: plan against mainstream maintenance, avoid the extended-maintenance premium entirely, and bank the EU-commitment flexibility as negotiation leverage on the way.

If

Your migration is realistically multi-year past 2027

Budget extended maintenance to 2030 explicitly — as a line item with an end date — and sequence the landscape so the highest-risk processes convert first.

If

Your landscape is very large or unusually complex

Evaluate the SAP ERP, private edition transition option — but price in what the S/4HANA commitment means before treating it as bought time.

If

Parts of your landscape are stable and low-change

The July 2026 commitments make segmented third-party support (or dropping shelfware maintenance) a legitimate lever — use it deliberately, not as avoidance.

Monday-morning questions

  • Which enhancement-package level does each productive ECC system actually run — and is any of them already in customer-specific maintenance without the board knowing?
  • Which enhancement-package level is each of our ECC systems actually on — and which already left maintenance in 2025?
  • What do we pay today for maintenance on licences nobody uses, and what would termination under the EU commitments save?
  • Who owns our 2027 date — by name, at executive level?
  • If the programme slips a year, is extended maintenance budgeted — or assumed?

Where this sits in the decision chain

This is decision 1 of 8 in the Executive Clarity decision library. Once the timeline is owned, the next decision is the deployment model: SAP Public Cloud vs Private Cloud.

Sources

  • European Commission press release IP/26/1554 — Commission accepts binding commitments by SAP (July 2026).
  • SAP maintenance strategy for SAP Business Suite 7 (SAP Note 1648480; access requires an SAP account).
  • Industry analyses of the ECC support market, including third-party support providers' coverage of the 2027/2030 dates.

Editorial standard: facts, inference and point of view are kept separate above. Published 2026-08-02 · By Andreas BORN.