SAP ERP HCM
Your HR system is on a clock. Your succession plan does not have to wait for it.
Dates verified against SAP's published maintenance guidance. SAP has revised these before; confirm against SAP's own maintenance strategy page before making a decision on them.
The timeline
| System | Date | Status |
|---|---|---|
| SAP ERP HCM 6.0, no enhancement package, and EhP 1–5 | Mainstream maintenance already ended | |
| SAP ERP HCM 6.0 with EhP 6, 7, or 8 | Mainstream maintenance ends | |
| Extended maintenance for EhP 6/7/8 | Optional, from 2028, at a premium above existing maintenance |
After extended maintenance ends, the remaining route is customer-specific maintenance: no further legal or tax updates, and restricted security patches. For an HR system holding payroll-adjacent data, that is usually the point at which the decision makes itself.
What this actually means for succession
Most of the end-of-maintenance conversation is an IT conversation: database, custom code, integration surface, cutover risk. Succession planning rarely gets its own line in that plan, and it is the process most likely to quietly stop during the migration years.
That matters because succession is the one HR process where a pause is invisible until it is expensive. Payroll failing is obvious within a fortnight. A succession plan that nobody has revisited since the migration kicked off looks completely fine until a critical seat empties and the named successor turns out to have left, or never to have been ready.
There is also a data problem worth naming early. Successor nominations and talent pools generally export. The reasoning behind them generally does not, because it was never in the system: it lived in the calibration meeting, the facilitator's notes, and a spreadsheet on somebody's drive. Audit that before the migration rather than after.
The options, including the one that is not us
Migrate to SAP SuccessFactors. SAP's own route, and the right one if you want the full HCM suite from a single vendor, have the budget for the programme, and would rather have one throat to choke than a best-of-breed stack. If that describes you, the honest comparison is on our SuccessFactors comparison page, which says where it wins.
Take extended maintenance and buy time. Available from 2028 to the end of 2030 at a premium. Sensible when the organization genuinely cannot absorb another major programme yet, and a deferral rather than a decision.
Decouple the talent processes from the HRIS decision. Succession planning needs a roster, a set of criteria, and somewhere to hold scored judgments. It does not need payroll or time and attendance in the same system. Running it separately keeps the process alive on a fixed cadence while the larger decision takes as long as it takes, and it removes one workstream from an already large migration.
Where SuccessionStack fits, and where it does not
SuccessionStack is not an HRIS and will not replace SAP ERP HCM. It does one thing: it takes your leadership population and turns it into scored, defensible succession plans with readiness windows, a recorded reason behind every score change, and modeling of what happens when someone leaves. It imports a roster by CSV, so it does not need an integration project scheduled against a migration that already has enough of them. If you want the fuller picture of what that involves, start with succession planning software.
SAP ERP HCM and succession: common questions
See where your bench breaks before it matters.
Bring your real org chart. We show you the succession gaps, cascade risks, and bench depth in a 30-minute walkthrough. IT security questions answered on the same call.
IT review first? The FAQs answer the security questions honestly →