← All insights

The Migration Clock

The 2027 deadline is yours to set

SAP's 2027 maintenance cliff may be the best sales tool enterprise software has ever produced. Before a vendor's clock sets your timeline, know what the clock says and who profits when you panic.

A hand setting a red piece among rows of numbered calendar dominoes at sunset

Every few weeks I'm in a version of the same conversation. A senior leader says, half stating it and half asking, "We're on SAP, so we have to be off ECC by 2027, right?" The way they land on "right" tells me they've already accepted the premise. They've stopped asking whether to move and started asking how fast.

That premise is worth slowing down on. Almost everything expensive about an ERP migration flows from the decision made in that moment, and the moment is usually set by a deadline that people who profit from your urgency have described to you many times.

Start with the dates, because most of the fear comes from getting them wrong.

Older enhancement packs: mainstream maintenance ended at the end of 2025

2025. For older packs, the clock already ran out

SAP mainstream maintenance for ECC 6.0 and Business Suite 7 ends on December 31, 2027, for enhancement packs 6 through 8. If you're on an older pack, that clock already ran out at the end of 2025. So far the urgency story holds. The part that rarely makes the briefing is what comes after December 2027.

If you haven't started by the middle of 2026, you aren't finishing a clean program before December 2027

2026. A shared deadline raises the price of the people you need

This should shape your timing more than anything else, and it's the point your integrator is least likely to raise, because it works in their favor. A manufactured deadline concentrates demand. Everyone is told to move by the same date, so everyone reaches for the same finite pool of S/4HANA architects, FI/CO specialists and program managers at the same time, and the price of that talent has climbed.

20%
Rise in specialist rates since 2023. Market estimate
$162B
Value tied up in the SAP skills gap worldwide. Industry estimate

A serious migration runs 18 to 36 months. If you haven't started by the middle of 2026, you aren't finishing a clean program before December 2027. You're finishing a rushed one, at premium rates, with the B team, because the A team was booked 18 months ago. The deadline helps whoever holds the implementation capacity and gets to price it.

December 31, 2027: mainstream maintenance ends for ECC 6.0 and Business Suite 7, EHP 6 to 8

2027. 2027 is when the price of staying goes up

The lights don't go out in 2027. What changes is the price of staying, and you can negotiate and plan around a price change. Vendors and integrators have a strong commercial interest in you walking into the room picturing a blackout instead.

Half of SAP's own customers are staying, on purpose

If 2027 were the emergency it gets sold as, you'd expect a stampede. There isn't one. Gartner projects that roughly 17,000 of SAP's 35,000 or so ECC customers will still be on legacy at the end of 2027.

54%
Of members of SAP's German-speaking user group still running ECC or Business Suite somewhere in the estate, surveyed in early 2026. DSAG
37%
Of ECC users targeting a move before the deadline. Nearly half were planning to ride extended maintenance to 2030. DSAG
A cliff edge with a painted-backdrop valley propped up on a film stage: the 2027 cliff is a pricing change in a costume
Paid support runs on past the cliff, to 2030, 2033 and 2040.

Plenty of them are large, well-run enterprises with the talent to move. They did the math and decided the extra runway is worth more than hitting an arbitrary date with a rushed program.

Extended maintenance runs through 2030, at a premium

2030. Plan for extended maintenance and negotiate from that position

Nearly half of DSAG's ECC users were planning to ride extended maintenance to 2030. It costs a premium, but it buys runway.

Start by confirming your own facts: which enhancement pack you're on and your real end date, not the one in the sales deck. Then run a true total-cost comparison of staying on extended maintenance, migrating, or moving to third-party support, in your numbers, over 5 years.

If you can't start until late 2026, that's your plan: budget for extended maintenance and negotiate with the runway it gives you. A date shouldn't force a bad go-live.

A transition option for private-cloud customers runs into 2033

2033. RISE trades the licenses you own for a rental

When you do move, SAP will steer you toward its bundled cloud offer, rebranded in 2025 and repriced along the way, with features pulled out of the base package and AI tooling priced on its own. Read the service levels before you sign.

The SLA
The standard agreement lands around 99.7% uptime, below the 99.9% most enterprises treat as table stakes. Closing that gap reportedly costs 30% to 50% more on license fees.
The trade
Signing the subscription usually means giving up the perpetual licenses you already own. You swap an asset you control for a rental whose renewal terms the landlord sets.
The move
That may still be the right call. It's a strategic decision about leverage, though, and it deserves independent licensing eyes before a signature instead of after.

If you're reopening the platform anyway, look past the deployment model. The 2027 deadline is a rare chance to reconsider the platform itself.

If you run Oracle E-Business Suite instead: Premier Support to at least 2037

2037. Oracle, Workday and Microsoft all want your finance estate

While SAP has been manufacturing urgency, its competitors have been selling stability and momentum.

Oracle

Extended EBS support to 2037 and sold continuity instead of a cliff, while Fusion Cloud ERP posted record numbers, with hundreds of go-lives a quarter.

That's the opposite of a deadline, and it takes urgency away as a lever.

Workday

Past nine and a half billion dollars in revenue, in roughly two-thirds of the Fortune 500 for HCM, and using that beachhead to go after the finance layer.

The pitch is blunt: you're already here for HR, so add Financials instead of re-implementing on SAP.

Microsoft

Pressing the upper mid-market, where Dynamics rides the Azure and Teams ecosystem.

Wins on the sticker shock of a full rebuild more than on features.

For a CIO that's leverage you didn't have a year ago, because three credible vendors want your finance estate. Use it in the room, and weigh them on fit and total cost.

Third-party support for ECC and S/4HANA is committed through 2040

2040. The bigger risk is carrying your old mess across

Suppose you do everything on time. Your biggest risk is still rebuilding your existing mess on a newer platform.

A brownfield lift-and-shift appeals because it's the fastest path. It also carries every customization and every data-quality problem straight across the bridge: duplicate records stay duplicated and stale master data stays stale. SAP's own surveys put customization and process change among the top barriers to migration, and custom code routinely runs past 30% of a brownfield project's scope. You spend a fortune and end up with the same customizations and the same bad data on a newer platform.

There are public examples of what happens when speed and a fee incentive override governance.

$172 million
Zimmer Biomet sued Deloitte in 2025 over an S/4HANA program the suit says was pushed live before it was ready.
£19M to £216M+
Birmingham City Council's Oracle program, budgeted near £19 million, is now projected to cost north of £216 million. The independent audit put the failure on governance and process rather than the software.

Decide greenfield versus brownfield on purpose, knowing which one carries the mess forward. Clean the data and rationalize the process before you move.

Your date, set by your readiness

Your year. Set your own timeline, then negotiate from it

If you engage an SI, get named resources and milestone commitments in the contract; a logo and a polished proposal don't commit anyone. In a capacity crunch the proposal team and the delivery team are rarely the same people.

Above all, run a hard governance check before anyone tells you you're ready. The most dangerous sentence in any ERP program is "we will be fine for go-live," and it's most dangerous when the person saying it only gets paid if it's true.

Countdown dial showing SAP 2027 decision milestones and the shrinking decision window
The decision window closes well before the deadline does.

The 2027 date is real, but what you do about it is your decision. It helps to have someone independent on your side of the table, paid to finish the program rather than bill more of it.

Sources

SAP maintenance strategy, for the mainstream end of December 31, 2027, extended maintenance to 2030, and transition to 2033 (support.sap.com; ASUG). Rimini Street support through 2040 (The Register, Jun 2025). Oracle EBS 12.2 Premier Support to at least 2037 (Oracle). Gartner projection of roughly 17,000 ECC holdouts by 2027 via CIO.com (2025). DSAG Investment Report 2026 via The Register (Feb 2026). RISE / "Cloud ERP Private" repricing and the 99.7% SLA (The Register, May 2025; CIO.com). FY results from SAP/ASUG, Oracle (Jun 2026), and Workday (Feb 2026). Zimmer Biomet v. Deloitte (UpperEdge; MassDevice, Sept 2025). Birmingham City Council Oracle program (The Register, Jan 2026). Skills-gap and rate data (ConnectingExperts/EGI; Panorama Consulting).

Let's talk

Make the 2027 call on your terms, not the vendor's.

An independent read on stay versus move, platform fit, and SI commitments, before you sign, is the cheapest leverage you will find.