The S/4HANA Decision in Front of You Right Now Is Not the Deadline

Mainstream maintenance for SAP ECC ends on 31 December 2027. That date has been sitting in roadmap decks for years, and most leadership teams still treat it as the decision point. It is not. The decision point moved, and it moved quietly, somewhere around the middle of this year.

Here is the arithmetic. A full-scope ECC to S/4HANA program in a complex enterprise runs somewhere between 18 and 36 months from mobilization to a stable close. It is August 2026. Roughly 16 months are left. If your program is not already in build, a clean landing before the deadline is not a plan. It is a hope with a Gantt chart attached.

That is not a catastrophe. ECC does not switch off. Licences stay valid. On 1 January 2028 your system will process finance, procurement and payroll exactly as it did the day before. What changes is what SAP sends you afterwards, and what it costs to keep receiving it.

The three positions that are actually left

Extended maintenance. A modest uplift on annual support fees, running to the end of 2030. It keeps legal and regulatory updates flowing. It has to be opted into, deliberately, with budget behind it.

Customer-specific maintenance. This is where you land if nobody opts in. It is the default, and it drops legal and regulatory updates entirely. For anyone running payroll, tax determination or statutory reporting out of ECC, that is a compliance gap that widens every quarter and is very difficult to explain to an auditor retrospectively.

A compressed program. Still achievable. But compression has to land somewhere, and in practice it lands in testing windows and data reconciliation, which is to say it lands in your first month-end close after go-live.

The first one is a decision. The second is what happens when no decision gets made. The third is a decision made under pressure, which is a different thing from a decision.

The part that gets decided by inaction

There is a second clock running alongside the first, and it does not appear on any roadmap slide. It is the resourcing clock.

The intuitive assumption is that consultant demand peaks in 2027 and then falls away. That is not what the market is showing. The migration workstream continues well past the deadline, driven by extended maintenance customers and complex enterprises that were always going to be late. Running alongside it is a second, growing market: optimization, clean core and stabilization work on systems that have already landed. Two markets, both drawing on the same finite pool of people who have done this five or six times before.

So the practical consequence of deferring your program is not that you get the same team later at the same price. It is that the deep, scarce skills get harder to secure exactly as your options narrow.

We see the sequencing problem constantly. A business case gets approved in March. The team does not get named until October. Nobody logs that gap as a delay, because nothing has technically gone wrong. But the program has already lost six months, and it lost them before a single system was touched.

What to do this quarter

Name your fallback explicitly. Do not let it be discovered in November 2027 by someone in procurement. Write it down, price it, and put it in the 2027 budget as a visible line item. Extended maintenance costs money. Customer-specific maintenance costs less on paper and considerably more in compliance exposure. That trade-off belongs in front of a CFO now, not later.

Second, separate the resourcing decision from the scope decision. Most organizations finalize scope first and then go looking for people, which puts the hardest-to-fill roles at the end of the process. Reverse it. Identify the three or four roles the program genuinely cannot run without, and secure those while the market can still supply them.

Third, be honest in the steering committee about what “on track” means. A program that starts on schedule with a half-built team has not started on schedule.

The takeaway

The deadline is not the decision anymore. What you are deciding this quarter is which version of late you are prepared to fund, and whether you can staff the version you have chosen. One of those choices gets made in a meeting. The other two get made by silence.

Hirekraft places senior SAP consultants into client delivery teams across the US and Canada. If your 2027 plan depends on people you have not secured yet, that is the conversation worth having this quarter rather than next.