No. It forces a decision, which is a different thing.
Mainstream maintenance for SAP ECC ends on 31 December 2027. Extended maintenance runs to 2030 at a premium. The July 2026 commitments from SAP to the European Commission apply globally to on-premise customers for ten years, removing the reinstatement fee, capping back-maintenance and permitting split support.
Taken together, that leaves three viable paths open rather than one. Each carries a different hiring profile, which is the part most 2027 commentary skips.
Path one: migrate
The default assumption, and the right answer for many organisations. It is also the most demanding in hiring terms.
What it needs:
- A solution or enterprise architect with a live conversion behind them, not an implementation
- A data lead who owns migration, master data quality and cutover readiness
- Integration capability across BTP and the wider data estate
- Business process owners who will still be there after go-live
- Contract capacity for genuine peaks: cutover, testing surge, security redesign
The timing problem. Between 20,000 and 25,000 legacy customers have still to move, in programmes running twelve to twenty-four months. Everyone choosing this path is competing for the same architects in the same window, and specialist SAP roles already take more than ninety days to fill against roughly forty-four for general IT.
The date is not the constraint. The number of people who have done an end-to-end conversion is the constraint.
For the hiring sequence, see Who do you actually need to hire for an S/4HANA conversion?
Path two: extend
Staying on ECC through extended maintenance, or moving to third-party support.
Underrated, and made considerably more viable by the 2026 commitments. For organisations whose ECC estate is stable, whose competitive advantage does not sit in the ERP, or whose capital is committed elsewhere, this is a defensible commercial decision rather than a failure to act.
What it needs, and this is the part that gets missed:
- Retention planning for the ECC-experienced people already in the building
- Basis, security and functional skills maintained rather than allowed to drift
- Contract and software asset management capability that understands what the commitments actually permit
The risk is not technical. It is demographic. ECC-experienced professionals are retiring, and the pool is thinning at the same time as the S/4HANA pool. Choosing to extend does not remove your hiring problem. It changes which market you are hiring in.
Path three: a hybrid
Split support, partial migration, or migrating specific functions while the core stays put. The commitments explicitly permit split support, which makes this more workable than it was.
What it needs: both skill sets, which is the most demanding option of the three from a hiring perspective, and integration capability to hold the two estates together.
Why has the deadline conversation been so noisy?
Because a deadline is easier to sell than a decision.
The honest position is that the 2027 date is real, the extension options are also real, and which path suits depends on things a vendor timeline cannot know: your capital position, your competitive exposure, and whether your ERP is a differentiator or a utility.
What is not in doubt is the labour market underneath. In ASUG's 2026 Pulse survey of 663 members, 36% cite maintaining internal skills as a significant challenge and 22% struggle to retain knowledgeable staff through turnover. That applies whichever path you choose.
Two hiring markets, not one
This is the practical consequence.
The S/4HANA market is tight and getting tighter, concentrated on conversion-proven architects, BTP and integration, and post go-live product and process ownership.
The ECC market has stayed valuable longer than most forecasts predicted, because the commitments made staying a legitimate strategy for a meaningful share of customers.
Both are thinning, and for the same reason. The generation that built these systems is retiring.
An organisation that decides to extend and assumes its hiring problem is deferred has misread the situation. It has chosen the market with fewer new entrants.
What should you do in the next six months?
- Decide which path you are on, and say so internally. Programmes drift when the decision is implied rather than made.
- Map the skills that path needs against the people you already have. Include who is likely to retire.
- Start the scarce searches early. More than ninety days to fill is the average, not the worst case.
- If you are extending, plan retention now. The people who know your ECC estate are the ones being approached.
FAQ
What exactly happens on 31 December 2027?
Mainstream maintenance for SAP ECC ends. Extended maintenance is available to 2030 at a premium. Systems do not stop working.
Do the European Commission commitments apply outside Europe?
They apply globally to on-premise customers, for ten years, and they removed the reinstatement fee, capped back-maintenance and permitted split support.
Is staying on ECC a reasonable strategy?
For some organisations, yes. It is a commercial decision rather than a technical one, and it carries a retention problem rather than a migration problem.
How early should we start hiring for a conversion?
Before the systems integrator is selected, if possible. The architect should be part of that decision rather than inherit it.
Read next:The Initiate 7-Stage Mapped Search Methodology
Planning your SAP hiring strategy? Book a client consultation.
