Topic starter
17/08/2026 4:41 pm
TL;DR: SAP IDM’s 2027 end-of-life is pushing organisations to reassess identity governance architecture, especially where workforce, external, and non-human identities now span cloud, SAP, and non-SAP systems, according to Saviynt. The transition pressure is less about replacement software than about consolidating workflows, policy enforcement, and access governance across a larger identity estate.
Editorial analysis by NHI Mgmt Group, based on content published by Saviynt: “From SAP to Saviynt: A Smart Move for Modern Identity Governance”.
Key questions
Q: What breaks when SAP IDM is retired before its governance workflows are replaced?
A: The main failure is not authentication, it is lifecycle control.
Q: Why does SAP IDM retirement force identity teams to rethink governance scope?
A: Because the identity estate has expanded beyond SAP-centric administration.
Q: When should organisations prioritise a converged IGA model over best-of-breed tools?
A: Prioritise convergence when manual reconciliation, audit prep, or inconsistent access state is becoming routine across provisioning, review, and SaaS visibility.
Practitioner guidance
- Map the full identity estate before replacement planning Inventory SAP, cloud, external, and non-human identities together so the target architecture reflects actual governance scope rather than the legacy SAP boundary.
- Reassess workflow and policy dependencies Document where roles, approvals, SoD checks, and provisioning logic are embedded in SAP IDM customisations so you can judge what must be rebuilt, not just migrated.
- Evaluate converged governance coverage Test whether the replacement can combine IGA, application access governance, and PAM without splitting review evidence or administrative ownership across tools.
Bottom line: SAP IDM retirement is forcing organisations to confront whether their current governance model can still span a much broader identity estate.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
17/08/2026 4:46 pm
SAP IDM retirement is really an identity governance architecture problem, not a product swap. The article’s strongest point is that the governance model that worked for a SAP-centred estate no longer matches how organisations operate. Cloud adoption, LoB applications, and mixed identity types have turned IGA into an enterprise control-plane problem. The practitioner conclusion is to redesign for cross-application governance rather than recreate the old SAP boundary in a new tool.
A few things that frame the scale:
- Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.
A question worth separating out:
Q: How should teams handle custom workflows during an SAP IDM migration?
A: Teams should treat custom workflows as control logic, not just configuration. If a workflow drives approvals, SoD checks, or provisioning exceptions, it needs to be redesigned and tested in the target state before cutover. Otherwise the organisation migrates technical functionality while preserving governance fragility.
👉 Read our full editorial: SAP IDM end-of-life is forcing a broader IGA reset