SAP ECC End of Life: What 2027, 2030 and 2033 Mean for Your S/4HANA Team

Last updated: October 31, 2026

By Mike Carter, Managing Director at KORE1

SAP ECC end of life comes in three stages, with mainstream maintenance ending December 31, 2027, paid extended maintenance ending December 31, 2030, and a transition option running 2031 to 2033 for systems already moved. On October 13, 2026, SAP added that those subscriptions may run to 2035, with further prerequisites. Each stage asks for a different team.

Most articles on this stop at the dates. Fair enough, the dates are what got searched. But nobody’s program ever failed because a CIO misread a calendar. Not one.

Programs fail because somebody picks a path in March and staffs it like a different path in June.

So this one runs the other way around. Pick your date, and I’ll tell you who you need and when they have to show up. We recruit these seats through our SAP consultant staffing desk, so weigh my opinions with that in mind. Who’s scarce and what they cost in the open market is covered over there, and I won’t repeat it. This is the calendar and the org chart. That’s it.

One piece of arithmetic first, because it changes everything below. Today is the end of October 2026. December 31, 2027 is 14 months out. Our hub puts a real S/4HANA conversion at 18 to 30 months to plan, execute, and stabilize. If you haven’t started, you aren’t beating 2027.

You just aren’t.

That’s not a disaster. It does mean the live question stopped being “how do we make the deadline” a while ago, and became “which deadline are we buying, and what does the team look like while we wait for it?”

What SAP ECC End of Life Actually Means, Date by Date

SAP ECC end of life means the end of SAP’s maintenance commitments for ECC 6.0, not the software shutting off. Your system keeps running on January 1, 2028. Nothing goes dark. What changes is what SAP will fix, what it will ship, and what it charges. The support ladder has four rungs, and each one moves work from SAP’s desk to yours.

Those dates come from SAP’s Business Suite 7 maintenance strategy and its transition option update. Check them against your own contract. I’m a staffing guy, and SAP’s lawyers wrote that page, not me.

You’ll notice 2026 sits at the top of a table about 2027. Odd, right? Blame the fine print. Customers who sign for SAP ERP, private edition in 2026 get a standard 20 percent uplift when they switch to the transition option in 2031. Sign in 2027 or later and the uplift isn’t disclosed, with final pricing promised closer to 2028. So there’s a real commercial date 61 days from now that almost no deadline article mentions. It only matters if you’re heading down that road. If you are, somebody should call SAP this week. Seriously.

And what about 2033, the number in the headline? Still real. The max success plan requirement is written around 2031 to 2033, and that’s the window SAP has actually priced and described. SAP’s own 2025 announcement told customers to craft their plans on that basis. The 2035 extension is two years of possibility behind a door whose lock nobody outside SAP has fully described in public. Budget to 2033. Treat 2035 as a parachute you hope you never test.

Where Everyone Else Landed

The German-speaking user group DSAG ran the most useful recent read, 198 senior leaders surveyed from December 2025 through January 2026, and The Register reported the split. Thirty-seven percent of ECC users want to switch by the end of 2027. Among members still investing in the old platform, almost half plan to migrate by the end of 2030. Four percent of ECC users are targeting 2033.

Four.

Gartner’s less cheerful about the people who answered that way, estimating in a 2025 analysis that four in ten of today’s ECC customers will still run it in key business areas by 2030. Regional survey, analyst forecast, different years, so don’t stack them. But the shape matches what comes in on our intake calls, and it isn’t subtle, because the crowd is converging on 2030, which means the crowd will want the same Basis lead in the same 18 months.

The Four Paths and the Team Each One Needs

Here’s the part I actually wanted to write. The seats below are contract unless I say otherwise, because almost none of this work is permanent, and that’s the whole reason it’s so expensive to get wrong. Conversion mechanics live on our S/4HANA conversion staffing page. What follows is only the decision and the headcount.

Path 1: You’re Already Mid-Program and Aiming at 2027

Lucky you. Mostly. Check the date on your plan again, because this path has shrunk to the companies whose mock conversions are already behind them. The danger now isn’t scope. It’s attrition at the worst possible moment, when your integrator’s second-string people rotate in and your own team is two-thirds of the way through a very long year. Add a cutover lead if nobody owns that weekend by name, and book contract SAP test cycle support through the final rehearsal.

Then plan hypercare past your first year-end close. Not your go-live. Your first close. That’s when the FICO questions show up, and it’s why a FICO consultant on a contract that ends at go-live plus 60 days is a false economy.

Path 2: End of 2030 on Extended Maintenance

This is where most of you will land. It’s the boring answer, and it’s the one I’d pick if nothing about your systems forces another answer. SAP charges two percentage points on your maintenance basis for the three years. On a $5 million basis that’s $100,000 a year. Run that next to the rest of this section and it’s barely a rounding error, which is why I get a little impatient when a steering committee spends two meetings on it.

The real cost of Path 2 is that you’re running two systems’ worth of people. Your best ECC person gets pulled onto the conversion, because they’re the only one who knows why that Z-table exists, and somebody has to answer the tickets they used to answer while the month-end close carries on as if nothing is happening. That backfill seat is the single most skipped line in the plans we see. Every time. Fill it first. Our page on when each program seat starts goes phase by phase, and it’ll save you a spreadsheet.

Here’s a planning example, labeled as one, not a client file. Picture a $700M equipment maker in Peoria on ECC 6.0 EHP 8, brownfield conversion, kicking off April 2027 with a 24-month plan and go-live in April 2029. That’s 16 months on extended maintenance after the 2027 line.

At 160 hours a month and the $130 to $220 an hour our ERP consultant rate guide shows for SAP contractors through a staffing firm, 161 seat-months runs roughly $3.3 million to $5.7 million. That’s on top of your integrator, not instead of it. Against that, the $100,000 a year for extended maintenance looks like what it is. Small.

Now compare those durations to normal contract work. KORE1’s median IT contract assignment runs 136 days across 410 ended assignments. These seats run roughly three to six times that. Nobody on this list is a typical contractor, so don’t let procurement paper them like one, with a six-month term and a renewal fight every February that some other recruiter will happily use as an opening. Write the end date as a milestone. Go-live. First close. Not a month.

Path 3: Private Edition by 2030, S/4HANA by 2033

Everybody calls this the RISE route, and it’s worth being precise about why that’s loose. What SAP actually requires is that your systems sit on SAP ERP, private edition, on SAP HANA, before December 31, 2030. Then you may buy a subscription centered on ECC, without the full Business Suite 7 scope. SAP’s original announcement calls it targeted at larger and complex systems and says customers finishing by 2030 won’t need it. The August update adds a 2 TB minimum.

People hear “more time.” Read it again. It’s two projects.

Wave one moves a system to a new home and, if you’re still on Oracle or DB2, to a new database, with older third-party technology like old Java versions no longer supported on the way through. That’s a Basis administrator‘s project with an interface team around it, and functional consultants mostly stand around. Wave two is the same S/4HANA conversion you were avoiding, later, at an uplift, with your best people three years older and possibly gone. Staff wave one lean. Six to eight people, maybe, for a year. Then expect a gap. Maybe a long one. The trap is letting the program office dissolve in that gap, because nobody will remember why anything was decided when wave two starts up around 2031.

Keep one permanent program owner across both waves. If you do nothing else on this path, do that. Please.

When is Path 3 the right call? A multi-terabyte system with heavy industry add-ons, several acquisitions still half-integrated, and a board that won’t fund a 2029 go-live for reasons that are actually good, as opposed to the usual reason, which is that nobody wants to be the one who asked. If you’re at 800 GB and just nervous, you don’t qualify anyway.

Path 4: Stay on ECC Past 2030

Nobody on an SAP sales call wants to say this out loud, but it’s a legitimate choice for some companies. A division you intend to sell. A plant that closes in 2032. It just isn’t free. The bill lands in your headcount.

Skip extended maintenance, or outlast it, and you drop to customer-specific maintenance. SAPinsider’s October 2026 breakdown lists what that means, namely no new support packages, no updates for legal changes, limited technology updates, and a charge for solving problems not yet known to SAP. Read “no updates for legal changes” as a job description. Because it is one. A new tax rule or an e-invoicing mandate in a country you sell into becomes your ABAP developer’s and your functional lead’s problem, on the regulator’s schedule, and the regulator has never once asked how your Q3 is going. Gartner has also called third-party support a viable option, naming Rimini Street, Spinnaker Support, and Support Revolution as examples, and that shifts some of this work without removing the need for people who understand your customizations.

There’s newer bargaining room here. SAP’s maintenance and support commitments, in effect since July 2026 after the European Commission case, apply globally and run 10 years. You can split your SAP footprint into commercial installations and choose a support model, a provider, or no support for each, and SAP has waived its reinstatement fee. So the retiring plant and the core ledger don’t have to sit on one contract anymore, which matters a lot if you’re staffing them differently.

The staffing risk on Path 4 is retention, and I’d rank it above everything else on this page. Your ECC veterans can read this calendar too. They already have. A senior ECC Basis person in 2029 has every incentive to go chase conversion money, and the people who stay on a frozen system are not always the ones you’d pick. Pay them. Well. Write retention into the plan, and if you’re leaning on ongoing outside help, compare a named SAP support team to a ticket queue before renewing anything.

Who to Bring In First, Whatever You Picked

Order matters more than headcount. A lot more. Our IT searches average 17 days to fill, and our 12-month retention sits at 92 percent. Good numbers. I’d still give a senior conversion lead about 60 days of runway, because the good ones are finishing somebody else’s cutover when you call, and they’re not going to walk off it for you, nor would you want the kind who would.

• A custom code inventory comes before anybody’s hiring plan. Four to six weeks of an ABAP developer’s time, reading your Z-objects with the usage data in hand. Contract ABAP developers can do this before you’ve picked an integrator, and the answer reshapes every seat count above.
• Backfill. Yes, again.
• Your Basis or HANA lead, because everything else queues behind a working sandbox.
• Data migration, and later than people think, unless your master data is a mess. Is it? ERP data migration specialists will tell you within a week, usually with some enthusiasm.

Run a regulated plant? Add a seat most plans leave out. A validation lead who didn’t build what they’re testing. A 2026 estimate from Colin Boothe’s firm, Foretopia, on a regulated NetSuite integration, which is a different ERP but the same discipline, put validation at roughly 30 percent of base hours, and his standing point is that a much cheaper bid usually got cheaper by leaving something out. Their change-control process also refuses to bundle changes to dodge assessment, a rule that’s going to feel very annoying around your fourth mock conversion and very wise at audit.

Sometimes you don’t need us. Really. If your integrator’s fixed-bid team really does cover everything, including backfill and hypercare, and your internal team has bandwidth, buy nothing from anyone yet. Just get the seat list in writing with names, because “the partner will handle it” is where a lot of the backfill line above went to die. When you do need contract SAP seats, or want to plug gaps inside an integrator-led build through SAP staff augmentation, that’s a different conversation than buying a project.

What CIOs Ask Before They Pick a Date

Does SAP ECC actually stop working after 2027?

No, ECC keeps running after December 31, 2027, because only SAP’s mainstream maintenance ends that day.

What you lose depends on what you bought. Extended maintenance carries you to the end of 2030 for two extra percentage points. Without it you’re on customer-specific maintenance, which is a much thinner promise.

We haven’t started. Can we still make 2027?

Not on a normal timeline, since 14 months remain and a real conversion takes 18 to 30.

Two percentage points on what, exactly?

Your maintenance basis, for all support offerings in the Business Suite 7 scope, from the start of 2028 through the end of 2030.

So $5 million of basis costs $100,000 more a year. It’s optional, and SAP intends it for customers in longer conversions. Confirm your own basis with your account team. Contracts vary.

Is 2035 the new deadline now?

Only for a narrow group, because 2035 applies to transition option subscribers who meet further prerequisites SAP points to in Note 3591251.

The system still has to reach private edition on HANA before the end of 2030. Miss that, and neither 2033 nor 2035 is available to you. SAP’s 2025 note says there are no changes for customers running on-premise after 2030. So on-premise gets no 2033.

Third-party support instead. Does that let us skip S/4HANA altogether?

For a while, yes, and Gartner calls it viable for organizations keeping ECC past the mainstream deadline.

It buys time. It often saves money. It doesn’t freeze the world around you. Your ECC skills market keeps thinning either way, so budget for retention as if you were the last company running it, because in your town you might be.

Which hire comes first if the budget only covers one?

Four to six weeks of a senior ABAP developer doing a custom code inventory beats every other first dollar we can name.

Contract, not perm. It tells you how big everything else is, it’s useful on all four paths, and it’s cheap enough to approve without a steering committee.

Pick the Date, Then Send Me the Seat List

Three decisions, in order. Whether 2026’s published uplift matters to you, which closes in 61 days. Which of the four paths you’re on. And who fills the backfill seat, since that’s the one that gets forgotten.

If you’ve got a plan, even a rough one, send it to our SAP desk and we’ll mark up the seats and the start dates. If what you need first is a number for the budget meeting, request a bill rate quote for the roles above and I’ll have someone get back to you with the range for your metro.