WorldITCOE
BriefingWorldITCOE4 min read

Still on ECC — or on S/4HANA on-premise? You have options

What the 2027 milestone actually changes, why it reaches S/4HANA on-premise customers too, and the three paths open to you.

What the milestone actually changes

SAP's mainstream maintenance milestone for eligible Business Suite 7 applications falls on December 31, 2027, with extended maintenance optionally available through 2028–2030 for eligible scope. It is a decision point, not a switch-off: the milestone changes what SAP will maintain, not whether your system keeps running.

That distinction matters, because the pressure it creates is commercial rather than technical. A system that runs your business on December 30, 2027 will still run it on January 2, 2028. What changes is who supports it, and on what terms.

Why this reaches S/4HANA on-premise customers too

It is easy to read the 2027 conversation as an ECC-only story. It isn't. Organizations already live on S/4HANA on-premise face their own version of the same question: each S/4HANA release carries its own mainstream maintenance end date, which means a recurring upgrade cadence, and alongside it a steady push toward a cloud subscription model.

If you have already absorbed the cost and disruption of an S/4HANA migration, the question is not whether to modernize. It is whether the next upgrade — or the next platform change — earns its own business case, on your timing.

The three paths

None of these is the default right answer. The right one depends on your business priorities, risk profile, economics, technical landscape, and readiness for change.

  • Stay & Optimize — continue on your current release, ECC or S/4HANA on-premise, while improving support, reducing costs, and modernizing selectively around a stable core.
  • Bridge & Prepare — hold the core stable while deliberately reducing custom-code complexity, rationalizing integrations, and improving data quality, so a future transformation starts from a stronger position.
  • Transform — move to a new platform if, and when, readiness, economics, and the business case justify the investment.

Where independent support fits

Independent, third-party support for SAP — such as Rimini Street's — is what makes the first two paths viable in practice. It covers the running landscape, including the custom code that standard maintenance typically won't touch, along with integrations, tax and regulatory updates, and security response.

Rimini Street states clients can reduce annual SAP support fees by up to 50%. Individual results vary; this is not a guaranteed or expected saving. Their published service commitments include a 10-minute response SLA for P1 (Priority 1) cases and 24/7/365 coverage, under a rolling 15-year support commitment rather than a fixed calendar end date.

A sensible next step

Start with the free 30-minute SAP strategy discussion. It is a conversation about your landscape and your options, with no obligation and no pressure toward a particular path — and it is not the paid SAP Freedom & Future Assessment. If the Assessment turns out to be the right next step, we will say so on the call.

← All resources

Start with facts. Not assumptions.

A 30-minute SAP strategy discussion — free, no obligation, and no pressure toward a particular path. It is not the paid SAP Freedom & Future Assessment; if the Assessment turns out to be the right next step, we'll say so on the call.

Book a free 30-minute discussion