SAPCodeMonkeyOne SAP HCM Deadline Already Passed
One SAP HCM deadline has already gone by, and many organizations haven't noticed. Four dates, three paths, and the trap hiding inside a runway that runs all the way to 2040.
If you work in SAP HCM, you have heard about 2027 so often it has become background noise. So start somewhere else: there is an HCM deadline that has already gone by, and a surprising number of organizations have not noticed. The S/4HANA Compatibility Mode for HCM — the arrangement that let you keep classic HCM running inside an S/4HANA system after a conversion — ended at the close of 2025, with usage rights expiring on 1 January 2026. That did not get postponed. It happened, and it is worth checking today.
Four dates, not two
2025: Compatibility Mode for HCM on S/4HANA, already expired. 2027: mainstream maintenance for SAP ERP HCM ends, following Business Suite 7. 2030: extended maintenance ends, at additional cost, with the extended phase for payroll specifically beginning in 2028. 2040: SAP HCM for S/4HANA — H4S4 — carries you to here. That last date is why HCM is different from every other Business Suite module: it is a runway most SAP professionals will not see the end of in their current role.
What H4S4 actually is
H4S4 is the S/4HANA version of the HR module you already know — same functionality, same familiar interface, running on S/4HANA technology, available on-premise, private cloud or public cloud. Unusually among SAP migrations, it is not really a transformation project: a classic brownfield approach works, more comparable to an enhancement package upgrade than to an S/4HANA finance conversion. Two caveats: some legacy pieces do not survive — Manager's Desktop and Training and Event Management will not work in H4S4 — and it is worth cleaning the system up before the move, since this migration is unusually cheap to take that opportunity in.
Bridge, not destination
The part vendors will not lead with is that H4S4 is explicitly a bridging technology. That is its stated purpose: to give existing customers time to complete the HR cloud transformation. SAP's investment focus has moved to effectively cloud-only, so the innovation goes into SuccessFactors and Employee Central Payroll. H4S4 gets maintained; it does not get transformed. Both facts are true at once — you have until 2040, and you are running something that has stopped being the future. It remains the right answer for many organizations. It just should not be mistaken for a decision that has been made.
Three paths, and the one most take
You can go fully cloud with SuccessFactors and Employee Central Payroll; stay on H4S4 on-premise until 2040; or — where most large organizations actually land — run a hybrid, with SuccessFactors Employee Central as the master-data system combined with SAP Payroll and Time Management from H4S4. Cloud for the talent and self-service layer, on-premise for the parts nobody wants to move. For a large organization with complex country payroll, that hybrid is frequently the most defensible architecture available, not a halfway house.
Payroll sets the timeline
HCM moves slower than every other module because of payroll. It is country-specific, legally exacting in a way almost nothing else in SAP is — get it wrong and people are not paid correctly — and it carries data-protection sensitivity that makes organizations cautious about where it runs. Extended maintenance for ERP HCM Payroll begins in 2028 and ends at the close of 2030. Employee Central Payroll is the cloud answer, but payroll is the workstream that decides when the whole transition is actually finished, which is why the recommended approach is to move modules gradually and avoid a big bang.
What it means for you
The good news is real: a 2040 runway means on-premise HCM skills have a far longer half-life than almost anyone else's in the SAP world, and payroll and time domain knowledge is regulatory rather than technical, so it does not move when the platform moves. That is also the trap. A runway that long is exactly long enough to feel safe and exactly short enough that spending it standing still is a decision made by default. The scarce person spans both worlds — Employee Central above, on-premise payroll below, and the integration between them. The platform expires; the domain does not.
Sources & further reading
- SAP Community — Connecting Employee Central with SAP HCM for S/4HANASAP's own post confirming the 2040 maintenance window, the 2027 date and the hybrid model. Verified live.
- SAP Help — Employee Central PayrollThe cloud payroll path and its integration with on-premise HCM. Verified live.
- SAP Support — Release, Upgrade & MaintenanceThe authoritative Business Suite 7 maintenance dates. Verified live.
Maintenance dates, compatibility scope and H4S4 functional gaps vary by release and region — Compatibility Mode scope in particular depends on what was licensed and how the conversion was done. Verify against SAP's published maintenance strategy. SAP guidance, transaction availability and dates change between releases and editions. Verify anything here against SAP Help for your own situation before you commit to it. This article is independent commentary and is not affiliated with SAP or any implementation partner.