SAP ECC mainstream maintenance ends in 2027: what you need to decide this quarter

SAP stops mainstream maintenancedefinitionWhat you're paying for today. Your normal fee gets you support packages and legal updates, and SAP fixes what breaks. for ECC 6.0 at the end of 2027, and two updates from SAP this month changed what the later dates mean. If your company still runs ECC, pick your route this quarter: convert, pay for extended maintenance as a bridge, sign up for the transition option, or live with reduced support. This guide sets out the dates, what each route gives you, and the checks we'd run first.

Nothing switches off on New Year's Day 2028. Orders still post and month-end still closes. What goes away, unless you pay for extended maintenancedefinitionAn optional paid extension for ECC from 2028 to the end of 2030. Support stays similar to mainstream, for two percentage points more on the maintenance basis., is the stream of support packages and legal updates. SAP's own maintenance strategy says the reduced level, customer-specific maintenancedefinitionThe reduced level you drop to without extended maintenance. No new support packages or legal updates, and SAP charges to fix problems it hasn't seen before., brings no new support packages and no updates for legal changes, and SAP charges you to fix problems it hasn't seen before.

Legal updates are where it usually hurts first. If payroll, tax reporting or e-invoicing runs in ECC, every rule change from a government lands on your team instead of SAP's. Auditors will also ask why the finance system no longer gets vendor fixes, and that's a harder conversation than it sounds.

You won't be alone in running late. Gartner, quoted by CIO.com in mid-2025, counted about 14,000 of 35,000 ECC customers on S/4HANA at the end of 2024 and projected 17,000 would still be on ECC in 2027. Among respondents to the German-speaking user group DSAG who are still investing in ECC, 37 percent want to switch by the end of 2027 and almost half plan to finish by the end of 2030, paying for extended maintenance along the way. That queue is the real risk. Experienced S/4HANA people get booked up as the date gets closer, and ISG's 2026 study found nearly 60 percent of SAP migrations running behind schedule and over budget.

For the Basis team: SAP's release strategy document, version 2026.1, says that from the first day of 2028 all Business Suite 7 core applications and their add-ons enter customer-specific maintenance unless you buy the extension. The extension doesn't cover everything, either. It leaves out any add-on whose end of maintenance SAP announced earlier, and anything that already has a follow-on release. Check each add-on and industry solution in the Product Availability Matrix before you assume it's covered.

The 2027 and 2030 dates haven't moved since SAP set them in 2020, and SAP said so again this month. What changed is the fine print around them. Four updates matter for an ECC plan, and the first one catches most teams by surprise.

The database change is the one to sit with. If ECC runs on Oracle, Db2 or SQL Server, the deadline for a system conversion is the end of 2030, and slipping past it leaves a new implementation as the only route. SAP says you can remove the database dependency by moving the system to HANA before then, though it doesn't recommend that as the long-term path, and the system still lands in customer-specific maintenance afterwards.

The compatibility pack change matters if you convert now. Compatibility packsdefinitionOld ECC functions SAP lets S/4HANA customers use for a limited time. When a pack expires, the right to use it ends, not only the support. let S/4HANA run some old ECC functions for a while, and they're listed in SAP Note 2269324. Because most of those use rights already ended for on-premise systems, a conversion today should plan to replace those functions inside the project. Don't count on carrying them across and fixing them later.

If you're on EHP 5 or older, you're already on the reduced level and the extension isn't open to you. SAP's advice to those customers has been to upgrade to EHP 6, 7 or 8 to get back under mainstream maintenance until 2027. That's a real project on its own, so ask SAP whether it still makes sense this late or whether the money is better spent on the conversion.

Most companies end up combining two of these. The usual pairing is extended maintenance as a bridge while a conversion runs. A large estate that can't finish by 2030 often pairs a HANA move with the transition optiondefinitionSAP's time-limited subscription for ECC systems that won't make it to S/4HANA by 2030. You run ECC on HANA in SAP's private cloud for a few more years while the move finishes..

Pricing for the transition option depends on when you sign. SAP says customers who signed in 2025 move across one to one, those who sign in 2026 get a standard 20 percent uplift when they switch in 2031, and pricing for later sign-ups hasn't been disclosed. The max success plan fee comes on top. That's a reason to run the numbers before the end of this year, even if you don't sign.

Third-party support is now easier to try. Under SAP's July commitments you can, subject to SAP's landscape-split conditions, move one installation to another provider and keep the rest with SAP, and coming back no longer carries a reinstatement fee. Rimini Street, for one, says it supports ECC 6.0 through 2040. Before you go that way, remember that SAP's own legal updates and support packages stop for that installation, and the S/4HANA move still has to happen at some point.

A sensible decision needs four facts about your own system, and most companies don't have them written down. They're cheap to collect compared with what they decide.

The pieces around ECC are on the same clock, which is easy to forget. Process Orchestration 7.5 leaves mainstream maintenance at the end of 2027, and SAP points customers to Integration Suite. SAP Identity Management 8.0 ends the same day and SAP isn't building a 9.0, so the system that hands out SAP roles needs a successor too. Plan those moves so they don't all hit the same cut-over weekend.

Our SAP S/4HANA page covers how we run the readiness check, the custom code analysis and the mock conversions, and the work around them on Integration Suite and access control.

# Release, EHP level and database
SAP GUI > System > Status > Component information
# Support package level per component
Transaction SPAM > Package level
# Switch on custom code usage collection
Transaction SCMON

Plenty of ECC estates end up squeezed because nobody owned the support date after go-live. S/4HANA moves on a two-year release cycle, each release with seven years of mainstream maintenance, so the next deadline is already on the way. Treat release upgrades as routine work and the next one won't need a board paper.

We do this work alongside SAP teams, from the first inventory to the last mock conversion. You can hire SAP engineers for the conversion stretch, and our ERP systems practice plans the move and the work around it. If you'd rather start with a clear list of what's at risk in your own system, ask for an assessment.