The challenge

The deadline is fixed. The way most companies meet it is not working well.

Every ECC customer faces the same dates, the same technical debt and the same delivery model. Here is what that means, and every option you have today.

The deadline

SAP Business Suite 7 and ECC mainstream maintenance ends at the end of 2027. Extended maintenance runs to the end of 2030, at a premium. SAP’s CEO has said of the 2027 date, “We will stick to that.”1

There is a narrow additional option. A time-bound “transition option” covers business continuity from 2031 to 2033, and an update dated 13 October 2026 says subscriptions may run until the end of 2035 “with further prerequisites.” Those include moving to SAP ERP, private edition on HANA before the end of 2030 and running a system of at least 2 TB. SAP’s CEO described it as for “very few large customers.”2

The target moves too. S/4HANA on-premise now ships a major release every two years, with seven years of mainstream maintenance each.3 Landing on S/4HANA is not the end of the upgrade calendar.

How many companies have not moved?

Three studies give three different answers, because they measure three different things.

About 39%

of roughly 35,000 ECC customers had bought or subscribed to S/4HANA licenses by the end of Q4 2024, per Gartner as reported. That measures license purchase, not go-live.4

56%

of 168 ASUG members were live on or moving to S/4HANA in 2025, up 11 points from 2024. Of those, 44% chose brownfield, 29% bluefield and 26% greenfield. That measures intent and progress in a North American user group.5

54%

of 198 DSAG member companies in German-speaking countries still use ECC or Business Suite. Of those with ECC investments, 37% plan to switch by end-2027 and almost half by end-2030. That measures what is running today.6

The samples differ in size, region and definition, so they should not be added or averaged. The common thread: a large share of the installed base is still on ECC, and many plans already assume dates after 2027.

Why these programs are hard

Context is scattered. The rules your business runs on live in custom code, configuration tables, spreadsheets and people’s heads. Vendors estimate that a quarter to a half of ECC custom code is unused, and ECC systems commonly carry a few million lines of it.7 Nobody can say which half.

Procedures drift from the system. Written standard operating procedures describe how people think the process works. SAP processes things in its own way. The gap shows up downstream, usually as finance errors. We heard it from the CFO of a multi-billion-dollar company weeks before its IPO, who could not say what the company’s cash position was. A bank CFO told us the same thing.

Customizations were made to put out fires. Many were built under pressure, for one situation, by someone who has since left. They work, nobody documented why, and the program inherits them.

Custom keys on major tables. Some companies changed primary keys on large tables. Moving them can mean unloading entire tables rather than migrating increments, which reshapes the cutover plan and the downtime window.

People have to relearn their jobs. Experienced staff move through SAP GUI transaction codes without thinking. Fiori is a different way of working, and retraining a finance or logistics team is a program of its own.

The calendar is not yours. Quarter-end, year-end and seasonal peaks close the windows when systems can be touched. A slipped milestone can cost a quarter, not a week.

One of our partners has lived all of this from the buyer's chair.

“I’m the not-so-proud owner of a failed SAP migration. It was not pretty.”Phil Wiser, partner, who stopped an ECC-to-S/4HANA program three years in

Cost and overrun

In the SAPinsider 2025 benchmark, 62% of respondents cited high cost and 55% cited project length as migration challenges. The project-length figure was up from 37% in 2024.8

An indicative vendor-published benchmark of more than 80 migrations from 2023 to 2025 puts all-in cost for mid-complexity programs at $5–14M for 300–1,000 users, $12–35M for 1,000–5,000 users and $28–75M for 5,000–15,000 users, with complex programs reaching $150M or more. Brownfield programs planned at 15–24 months ran a median of 20–30 months. Global rollouts planned at 24–48 months ran 30–60. SI fees were 45–60% of program spend, and client staff time added another 20–35%.9

This is not specific to SAP. Research from McKinsey and the University of Oxford found large IT projects (over $15M) ran 45% over budget on average.10 At the extreme, a European retailer reportedly spent about €500M on an SAP program before cancelling it in 2018. That figure is reported, not confirmed by the companies.11

Why the integrator model will not fix itself

A systems integrator earns revenue from billable hours. More consultants and longer timelines mean more revenue. That is not a criticism of any one firm; it is how the model pays. We have seen a Big Four firm recruiting 700 consultants for one client’s SAP upgrade.

Adding people to a program with scattered context adds coordination cost faster than it adds output. An integrator has little reason to shrink its own headcount, and you are the one who carries the overrun.

The options you have today

Ordered roughly from least to most change. Costs and timelines vary widely with scope and customization; figures cited are from the sources listed below.

OptionWhat it isWhat it costs youWhat you give up
Extended maintenance to 2030Stay on ECC, pay SAP’s premium for support after 2027.1A premium on support fees for up to three years, and the migration is still ahead of you.Time you could use to start. The deadline arrives at the same size, with less runway.
Transition option (2033–2035)A time-bound subscription for continuity after 2030, for a narrow set of customers.2A 2 TB minimum, a move to private edition on HANA before end-2030, and a standard 20% uplift from 2031 for 2026 sign-ups.Flexibility. You commit to SAP’s terms and still migrate later. It is also aimed at very few large customers.
Third-party supportKeep ECC and buy support from an independent provider.12 13 SAP’s 2026 commitments also let you split a landscape and pick a support model per installation.14Providers claim up to 50% off annual support fees; Gartner’s market page says typically 50% versus direct. One provider claims ECC 6.0 support through 2040 (vendor claim).Access to new SAP releases and fixes. It lowers run cost but does not modernize anything.
Brownfield conversionConvert the existing system to S/4HANA, carrying history, data and customizations.Within the benchmark bands above, typically 20–30 months for programs planned at 15–24.9You carry your technical debt, including the unused custom code, forward.
Greenfield reimplementationStart a new S/4HANA system and redesign processes.The longest and most change-heavy S/4 route: full process redesign, testing and retraining.Continuity. You re-decide every process, and the business pays for the attention.
Selective data transition (bluefield)Convert selectively: keep the parts worth keeping, redesign or archive the rest.Needs a clear view of what is worth keeping. That analysis is itself significant work.Simplicity. It is a hybrid, and hybrid programs carry both kinds of complexity.
RISE with SAPSAP’s bundled subscription of software, infrastructure and basic services, with S/4HANA in an SAP-managed private cloud.15A subscription instead of a license and hosting split; standard production SLA of 99.7%.Some control over infrastructure and timing. It is a commercial wrapper; you still have to migrate.
Replace SAP with another ERPMove to Oracle Fusion, Workday, Dynamics 365 or another large ERP.A full reimplementation. Birmingham City Council’s replacement began at a £19M estimate plus £1M contingency and is now forecast at £144.4M, with go-live slipping. It is a public-sector outlier, and a caution.16The rules you built in SAP, unless someone captures them first. Programs fail when nobody knows what to map.
Clean coreKeep a lean SAP core and extend around it with services you own.Work to move customizations off the core and rebuild them elsewhere.Convenience. You take on an architecture to maintain, in return for a core that upgrades without pain.

What all of these have in common

Every option above except waiting is executed the same way: a systems integrator staffs a large team, works through the context by hand and bills for the hours. The only choice is which destination to pay the army to reach.

That is the assumption we challenge. With the right context, AI agents can do much of the execution work, and a small senior team can direct them. The destination can then be chosen on its merits, not on what the delivery model can afford.

Next: see how a small senior team plus agents works, what it costs and how we are paid.

Sources

  1. The Register, 28 Jan 2025. SAP extends support deadline
  2. SAP News Center, 4 Aug 2025 (updated 13 Oct 2026). RISE with SAP journey: SAP ERP, private edition, transition option updates
  3. SAP News Center, 2022. New SAP S/4HANA release and maintenance strategy
  4. The Register, 20 Mar 2025, reporting Gartner. SAP sees little progress in S/4HANA migration
  5. ASUG, 3 Oct 2025. SAP S/4HANA adoption trends, insights and advice
  6. DSAG, 26 Feb 2026. DSAG Investment Report 2026
  7. SAP Community, Aug 2026 (vendor estimates, not SAP-published). Get started with the ABAP custom code migration process
  8. SAPinsider, Feb 2025. SAP S/4HANA Migration: Detailed Findings
  9. VendorBenchmark, Apr 2026 (indicative vendor-published benchmark). SAP S/4HANA migration cost benchmark
  10. McKinsey & University of Oxford, 2012. Delivering large-scale IT projects on time, on budget, and on value
  11. Consultancy.uk (reported, not confirmed by the companies). Cancelled SAP introduction after sinking €500 million
  12. Rimini Street (vendor claim). Support for SAP ECC 6 and S/4HANA releases through 2040
  13. Gartner Peer Insights. Independent third-party software support of megavendors
  14. SAP Support Portal. On-premise maintenance and support commitments, effective 10 July 2026 for ten years
  15. Forrester, 20 Aug 2025. Navigate with confidence: the migration options for SAP ECC customers
  16. The Register, 29 Jan 2026. Birmingham Oracle ERP fiasco now £144M and still not working