SAP ECC end of life arrives in December 2027, when mainstream maintenance stops for the last supported versions of the ERP Central Component, the ERP (enterprise resource planning) suite a large share of SAP customers still run their books on. It has already happened once. The older enhancement packages lost mainstream maintenance at the end of 2025, and the systems running them kept booking invoices the next morning. If you are still weighing the move itself, ECC vs S/4HANA covers what actually changes.
That second fact matters more than the first. The deadline is a support cliff, not a shutdown, and it leaves you five real options rather than one. Every one of them has a price, a clock, and something you give up.
Ask Izzy
Got a question about the ECC deadline? Ask it here.
Izzy answers from this guide and our SAP research, for your system, not the generic case.
It also has a seller. SAP earns from RISE, the systems integrator earns from the migration, and the third-party support firm earns from you staying put. This is the version of the options list with the incentives labeled.
What the SAP ECC End of Life in 2027 Actually Means
SAP runs its old software through three phases, and “end of life” is shorthand for the first one ending. Here they are in plain English:
- Mainstream maintenance is the normal deal. Your annual fee covers support packages, legal and tax updates, and bug fixes.
- Extended maintenance is the same coverage, bought for a few extra years at a surcharge.
- Customer-specific maintenance is what you get automatically when the other two run out: the same fee, a smaller service, and no new support packages.
The 2027 date applies to SAP Business Suite 7 core applications, and for SAP ERP 6.0 that means the latest three enhancement packages (EhP 6, 7, and 8; an enhancement package is SAP’s term for a bundle of optional functional upgrades). Everyone on EhP 0 through 5 is already past their date. SAP’s own maintenance strategy page is the primary source for all of this, backed by SAP Notes 2881788 and 52505 if you have a support login.
| Milestone | Date | What it means for you |
|---|---|---|
| ECC 6.0, EhP 0 to 5: mainstream maintenance ends | December 31, 2025 (already passed) | No extended maintenance was offered. These systems are on customer-specific maintenance now. |
| ECC 6.0, EhP 6 to 8: mainstream maintenance ends | December 2027 | The deadline everyone means. Standard support stops at year end. |
| Extended maintenance (optional) | January 2028 to December 31, 2030 | Full support continues at a premium of two percentage points on the maintenance basis. |
| Customer-specific maintenance | Automatic after mainstream or extended ends | Same fee. No new support packages, no guaranteed legal-change updates. |
| SAP ERP, private edition, transition option | 2031 to 2033 | ECC-scope systems inside a RISE private-cloud subscription. Conditions apply (see Option 2). |
| S/4HANA maintenance commitment | End of 2040 | How long SAP has promised to support at least one S/4HANA release. |
One quiet warning about sources. The page Google currently features in its answer box for this query lists the EhP 0 to 5 cutoff as the end of 2026. SAP’s rule (only the latest three enhancement packages get 2027) and every other source put it at the end of 2025. Check dates against SAP, not against blogs, this one included.
The deadline has moved exactly once. In February 2020, SAP pushed the original 2025 date to 2027 and announced the 2040 S/4HANA commitment in the same breath. Back in 2022, Gartner counted 70% of Business Suite 7 customers still yet to migrate, which is roughly the pressure that makes people hope for a second extension. SAP leadership has said repeatedly there won’t be one. Plan as if they mean it.
If you already know you’re migrating and want the project anatomy (phases, teams, what the tooling does), that lives in our S/4HANA migration guide. This post stays on the decision before the project.
What Keeps Working on January 1, 2028
Your system does. ECC does not switch off when mainstream maintenance ends; SAP stops shipping new support packages and stops guaranteeing legal and regulatory updates under standard terms. Your invoices still post. Your payroll still runs. What changes is who fixes it when a tax rule moves or a security hole turns up, and what you pay for that. A support cliff, in other words, with a price attached to every way down.
One adjacent deadline has already passed for a different group: the Compatibility Packs that let on-premise S/4HANA customers keep running certain old ECC functions expired on May 31, 2026, with a small set of functions (in customer service, transportation, and process manufacturing) and RISE customers keeping rights to the end of 2030. It’s a reminder that SAP’s calendar keeps running whether or not you’re watching it.
The Five Real Options for the 2027 ECC Deadline, Compared
Page one of Google lists these options. It doesn’t compare them. So here is the comparison, on the terms that actually decide it: what you pay, how much time it buys, what you lose, and how you get out.
| Option | What you pay | Time it buys | What you give up | Who it fits | Exit path |
|---|---|---|---|---|---|
| 1. Migrate to S/4HANA | A project: Gartner puts large-enterprise costs anywhere from $2M to $1B | To 2040 and beyond | 18 to 36 months of project risk and budget | Boards that already funded the move | You stay in SAP, on a supported product |
| 2. RISE with SAP | A subscription (software, infrastructure, managed services); no public price list | To 2040 on S/4HANA; to 2033 for ECC via the transition option | Perpetual license, some control, some bargaining power | Companies that want SAP holding the infrastructure risk | Governed by contract term; read it before signing |
| 3. Extended maintenance | Maintenance fee plus 2 points; on a 22% base, about 9% more per year | Three years, to end of 2030 | Money, not functionality | Migrations already underway that won’t land by 2027 | Must finish moving by 2030 |
| 4. Third-party support | Providers claim about half your SAP fee; their commissioned study says 50% to 75% savings | Providers promise support into the 2040s | SAP patches, SAP legal updates, an easy road back | Stable, heavily customized ECC; exit-SAP roadmaps | Harder path back onto SAP maintenance |
| 5. Do nothing | Your current maintenance fee, unchanged | Indefinite, on a frozen product | New support packages and guaranteed legal updates | Nobody, on purpose | Any of the above, later, with less time |
Now the part the table can’t do alone: who should pick which.
- If your board already approved a transformation budget, migrate, and start now. The queue for good consultants is the real risk, not the software.
- If you’re mid-migration and it won’t land by December 2027, buy extended maintenance for the gap and don’t feel bad about it.
- If you want SAP to carry the infrastructure and can live with subscription terms, pick RISE, but read the exit clause before the pricing slide.
- If your ECC is heavily customized and stable, with no S/4HANA ambition this planning cycle, weigh third-party support against extended maintenance on real numbers.
- If your long-term plan is leaving SAP, third-party support is built for exactly that bridge.
- If you have no plan, you have picked Option 5 by default. It’s the most expensive choice per unit of support you get.
Every party quoting you a path to 2027 earns money from the path it quotes. That includes the consultancy with the webinar, the reseller with the readiness check, and SAP. The honest read is simpler than any of their decks: extended maintenance is the one option SAP sells that SAP would rather you not need, and doing nothing is the only option that costs full price for less product.
Option 1: Migrate to S/4HANA Before the Deadline
This is the baseline, and for most companies still on ECC it’s where they end up eventually. S/4HANA is SAP’s current ERP suite, built to run only on the HANA in-memory database, and it’s the product the 2040 commitment covers. The question isn’t whether it works. It’s whether you can get there on time.
Work backward. Typical migrations run 18 to 36 months, and Gartner reports clients planning three- to seven-year programs for complex estates. An 18-month project had to start by the end of June 2026 to finish before December 2027. If you’re reading this in the autumn of 2026 and haven’t kicked off, the calendar has made the choice for you: you’re migrating and buying time from Option 3 or 4 while you do it.
Cost moves on a few things: how much custom code you carry, how dirty your master data is, how many countries and company codes you run, and whether you go greenfield (rebuild processes from scratch) or brownfield (convert the existing system). That choice alone swings the custom-code workload hugely, and we compare the two approaches in greenfield vs brownfield. For what the schedule honestly looks like phase by phase, see how long an SAP migration really takes.
The Capacity Crunch Nobody Prices
Here is where the analyst numbers stop being trivia. CIO.com collected the major firms’ projections, and they agree on the shape:
| Source | Figure | What it says |
|---|---|---|
| Gartner (end of 2024) | ~39%, about 14,000 of 35,000 | ECC customers that had moved to S/4HANA |
| Gartner (projection) | ~17,000 | ECC holdouts by 2027, nearly half the base |
| Gartner (projection) | ~13,000 | Customers still on ECC in 2030, more than a third |
| IDC | 40% to 45% | ECC users staying on the old ERP through 2027 |
| Forrester | More than 40% | ECC customers still on it beyond 2027 |
| Livingstone (late 2025) | About half | ECC customers migrated or mid-migration |
Read those together and the arithmetic is uncomfortable. Something like 17,000 companies are trying to squeeze into the same three-year window, against a pool of experienced S/4HANA consultants that doesn’t grow on demand. That is pricing power for consultancies. For you, it shows up as higher day rates, junior staff on senior-priced roles, and start dates that slip before the project begins.
The quote tells you what one firm wants to charge. It doesn’t tell you which of the firms with actual bench capacity in 2027 fits your modules, industry, and size. That matching problem is what our engine does: describe your migration and watch it rank vendors for you, free, no signup.
And the payoff is real for some. IBM reported a 30% reduction in infrastructure-related operational costs after finishing its move to SAP’s cloud ERP in July 2024. Worth knowing: IBM also sells S/4HANA migrations. Both facts can be true.
Option 2: RISE with SAP (and the 2033 Escape Hatch)
RISE with SAP is a subscription bundle: S/4HANA software, the infrastructure it runs on, and a set of SAP-managed services, all under one contract (SAP has been folding it into the SAP Cloud ERP name, with GROW as the mid-market version). SAP holds the keys. You pay per year instead of owning a perpetual license.
SAP wants you here, and the numbers say why. Its cloud revenue grew about 26% year over year in the first quarter of 2025, and two-thirds of its new cloud customers were new to SAP entirely. The existing ECC base is the other big pool, and the 2027 date is the best tool SAP has for moving it.
The honest read: RISE moves you to subscription, and your bargaining power moves with it. Once your ERP runs on a contract with renewal dates, the negotiation happens on SAP’s calendar. Licensing changes ride along too. Full Use Equivalents (FUEs) replace the old named-user counting, Digital Access charges apply per document when other systems create records in SAP, and newer AI and analytics features are increasingly sold as add-ons rather than bundled in. None of that is hidden. All of it deserves a line in your business case.
The Private-Edition Transition Option
In February 2025 SAP announced the “SAP ERP, private edition, transition option,” and in August 2025 it published the terms. It lets customers keep running ECC-scope systems from 2031 to 2033, inside SAP’s private cloud. The conditions are strict:
- You must move to SAP ERP, private edition, on the HANA database before December 31, 2030.
- It’s only available with SAP’s “max success plan,” a premium services tier that became available in January 2026.
- SAP lists a minimum system size of 2 TB.
- Pricing depends on when you sign: 2025 signers were promised commercially equivalent terms, 2026 signers face a standard 20% uplift when switching, and pricing for 2027 and later wasn’t disclosed.
It’s a real option for large, stuck estates. It is also only sold with a RISE signature, and the price rises the longer you wait. That’s a design choice, and not an accidental one.
Option 3: Extended Maintenance, Renting Three More Years
SAP’s own wording for the price is “a premium of two percent points on the maintenance basis.” Translated: SAP maintenance typically runs 17% (standard support) or 22% (enterprise support) of your license value per year. On a 22% base, two more points takes you to 24%, which is roughly a 9% bigger annual check from 2028 through 2030.
What you get for it is everything you have today. Full support, patches, legal updates, for EhP 6 to 8 systems. Nothing new, nothing missing.
What it’s for is a bridge. A migration that’s already running and will land in 2028 or 2029 is exactly the use case, and paying two points is cheaper than rushing cutover to beat a date. As a strategy on its own, it only defers the same decision to 2030 with three years less room.
Extended maintenance is the product on this list SAP sells least enthusiastically. It exists because enough customers refused to be rushed in 2020.
Nobody selling you a migration leads with this option, because it makes their urgency slide less urgent. That’s fine. It’s still usually the right answer for the gap year.
Option 4: Third-Party Support, the Option Your Account Executive Won’t Raise
Third-party support means a firm other than SAP (Rimini Street and Spinnaker Support are the best known) takes over maintenance of your ECC system, usually for a fraction of SAP’s fee. It’s legitimate and established. Forrester, which sells nothing here, states it plainly: “Some companies, such as Rimini Street, offer third-party support for SAP ECC beyond 2030.”
The savings claims come mostly from the vendors, so label them that way. Rimini Street’s 2020 impact study, validated by Nucleus Research across 70 client cases, reports average savings of 75% on total maintenance costs and 50% on annual fees. An older Nucleus case (Color Spot, 2011) measured a 55.2% cut in ERP maintenance costs after leaving SAP maintenance. Rimini’s marketing headline goes higher than its own case averages. The cases are the numbers to use.
The trade is real, and the vendors’ own literature describes it. You leave SAP’s patch stream: security becomes the provider’s job, handled through what Spinnaker’s guide calls “full-stack intrusion detection, virtual patching, and compensating controls” instead of SAP code fixes. Tax and regulatory updates come from the provider, not SAP. And the road back onto SAP maintenance, if you later want S/4HANA on SAP’s terms, is harder than the road out.
The only parties who describe third-party support as reckless are the two parties it takes revenue from.
That doesn’t make it right for everyone. It fits a stable, heavily customized ECC system with no S/4HANA plan on this planning horizon, or a company whose long-term roadmap leads away from SAP. It fits badly if you want SAP’s newest capabilities in the next few years, because you won’t be on a path that gets them.
Option 5: Doing Nothing Costs the Same and Buys Less
Nobody on page one prices this option, which is odd, because most holdouts will take it. Doing nothing means sliding into customer-specific maintenance on January 1, 2028. Even Rimini Street, which would love you to leave, concedes it “costs the same as mainstream maintenance, and it has significantly reduced scope.”
Put numbers on it. Take a hypothetical company with a $10M license base on 22% enterprise support. It pays $2.2M a year in maintenance today. On customer-specific maintenance it pays the same $2.2M in 2028, for no new support packages and no guaranteed legal-change updates. Same invoice. Frozen product.
There’s a second cost, and it’s harder to see. Rimini’s April 2026 analysis splits SAP’s perpetual-license owners into two groups: ECC customers facing this deadline, and S/4HANA perpetual customers being pushed toward cloud subscription. Both have bargaining power precisely because SAP needs them to move. Deciding nothing spends that power and gets nothing back for it.
I’ve read enough renewal paperwork to know how this goes. The fee doesn’t drop just because the service did.
Bottom line: Doing nothing is a decision. It’s customer-specific maintenance at full price. Whatever you choose, choose it on purpose, with the number next to it.
Frequently Asked Questions
Will SAP ECC be supported after 2027?
Yes, but not on standard terms. Mainstream maintenance for ECC 6.0 on EhP 6 to 8 ends in December 2027. You can buy extended maintenance through 2030 at two extra percentage points, or you move to customer-specific maintenance automatically: same fee, no new support packages. Third-party providers also support ECC past 2030.
What is happening with SAP in 2027?
SAP ends mainstream maintenance for Business Suite 7 core applications, including ECC 6.0 on its latest three enhancement packages, in December 2027. Systems keep running. What stops is standard support: new support packages and guaranteed legal updates. SAP wants those customers on S/4HANA, which it supports until at least 2040.
Will SAP ECC be back in 2030?
No. 2030 is not a return date; it’s the end of optional extended maintenance, which runs from 2028 through December 31, 2030. After that, ECC customers are on customer-specific maintenance or third-party support. The one SAP-run path past 2030 is the private-edition transition option, 2031 to 2033, and it requires a RISE subscription.
How long will SAP ECC be supported?
By SAP on full terms: to December 2027 for EhP 6 to 8, or to the end of 2030 with paid extended maintenance. After that, SAP offers customer-specific maintenance with reduced scope, plus the 2031 to 2033 private-edition transition option for qualifying RISE customers. EhP 0 to 5 lost mainstream maintenance at the end of 2025.
Sources
- SAP, Maintenance strategy: the 2027, 2030, and 2040 dates, the two-point extended-maintenance premium, and customer-specific maintenance.
- SAP News Center, Updates for SAP ERP, private edition, transition option (August 2025): the 2031 to 2033 terms and pricing tiers.
- CIO.com, Nearly half of SAP ECC customers may stick with legacy ERP beyond 2027: Gartner, IDC, and Forrester projections, migration cost range, the IBM result, and SAP cloud growth.
- Rimini Street and Nucleus Research, 2020 third-party support impact study and the Color Spot case: vendor-commissioned savings figures, labeled as such above.
- Forrester, blog post on migration options for SAP ECC customers: the third-party support line quoted in Option 4.
The 2027 date isn’t the emergency. Unpriced options are. Put a number next to each of the five, pick one on purpose, and if the answer is a migration, browse migration partners by module and industry before the good ones are booked.
