Migrate from SAP IDM
Migrate from SAP IDM to Anugal before the 2027 deadline
SAP Identity Management 8.0 mainstream maintenance ends on 31 December 2027, with no like-for-like successor from SAP. Anugal is where your identity lifecycle goes next. We map what IDM does today, rebuild the rules that still matter on Anugal, migrate in validated waves and keep your IDM history retrievable after the system is gone.
What the 2027 Deadline Means for SAP IDM
Mainstream maintenance for SAP IDM 8.0 ends on 31 December 2027. SAP has not announced a like-for-like successor to SAP IDM, so there is no next IDM release waiting at the end of it. SAP IDM customers need a new home for joiner, mover and leaver logic, approvals and provisioning.
Extended maintenance runs to 2030 for an extra one-time charge, and SAPinsider reports that it covers critical issues only. That pays to keep the same product, the same scripts and the same gaps running for longer. It moves the date. It doesn’t remove the migration.
What Waiting or Patching Costs You
Logic nobody documented
Custom scripts, approval chains and HR-triggered rules decide who gets access to what. Few of them are written down, and the people who built them have often moved on. Every month of waiting leaves fewer people who know why each rule exists.
A rushed cutover
Waiting compresses the migration into a rush, and switching every target system at once leaves no fallback. Microsoft's own SAP IDM migration guidance tells organizations to plan a staged approach for scenario migration.
SoD checks that fall between tools
IDM provisions access. If nothing checks that access for separation-of-duties conflicts first, conflicting access can reach SAP unchecked.
Technical users and AI agents left off the list
Most inventories start with people. Every service account, technical user and AI agent with SAP access still needs an owner, a purpose, an access boundary and a review trail.
Evidence that stops at the cutover date
Auditors will ask who had access before, during and after the move. For financial entities, DORA's technical standards require a lifecycle process from creation to termination of every account, unique identities for ICT third-party staff and records of identity assignments.
The Anugal Difference
Migrate from SAP Identity Management to Anugal, Stage by Stage
Anugal is the destination for what SAP IDM does for you today.
We move the requirement, not the workaround. We map identities, roles, applications, workflows and controls before anything moves, decide with you which rules still reflect a real control, rebuild those on Anugal, and keep your IDM history retrievable long after the system is gone.
Typical program: from 6 months, delivered in validated wavesWant the full method? Read our step-by-step SAP IDM migration guide.
- 1
Discover
Map what SAP IDM does for the business.
We inventory identities, roles, repositories, connectors, workflows and SoD policies, and record what every IDM job, script and HR trigger does, so nothing silently disappears in the move.
You get: discovery report, scope and migration backlog
- 2
Design
Design the target governance model on Anugal.
Joiner-mover-leaver lifecycle rules, approval routes, role model and SoD rules, rebuilt for the requirement, not copied from the workaround.
You get: target governance blueprint, signed off by you
- 3
Migrate
Move in validated waves, never big-bang.
Identities, roles and assignments move wave by wave with deKorvai, our migration engine. Where continuity needs it, IDM and Anugal run in parallel as a safety mechanism. Accounts and permissions are reconciled before each wave closes.
You get: reconciliation report for every wave
- 4
Verify & go live
Prove it works before cutover.
Functional, integration and user acceptance testing, access and control reconciliation, and audit-readiness checks, then a planned go-live with hypercare.
You get: test evidence pack and go-live sign-off
- 5
ArchiveAUDIT-READY
Keep the history, not the system.
Provisioning history, request and approval trails, audit logs and identity records move into a read-only, searchable archive, so you can answer an auditor years from now without keeping SAP IDM alive.
You get: searchable archive you can retrieve from on demand
- 6
Retire
Switch SAP IDM off with confidence.
Once the archive is verified and you sign off, we decommission SAP IDM components, connectors and the infrastructure behind them, ending maintenance and running costs.
You get: decommissioning checklist and closure report
Your move to Anugal, stage by stage
Conceptual flowDiscover
Map what the system does
Design
Target model on Anugal
Migrate
Validated waves
Verify & go live
Prove it works before cutover.
Archive
Read-only, searchable history
Retire
SAP IDM switched off
Running systems
The parallel run is a safety mechanism, never the end state. Stage length and scope vary by estate.
ARCHIVE BEFORE YOU RETIRE
Switch SAP IDM off. Keep every answer an auditor may ask for.
- Provisioning history, request and approval trails, audit logs and identity records move into a read-only archive.
- Search and retrieve by user, role, system or date, whenever audit, legal or security needs it.
- No more licenses, patching or infrastructure kept alive only to look things up.
What You Get on Anugal
Joiners, movers and leavers, governed
Joiners get the access their role justifies from the first day, driven by HR events. Movers lose obsolete access as new access is assigned. Leavers have access revoked across applications and directories, with the evidence kept.
SoD checked before provisioning
Requested access is evaluated against enterprise-wide SoD rules, and provisioning follows validated SoD outcomes.
Emergency access under control
Access is time-bound, scoped to specific systems or roles, sessions are recorded, and a post-use review is mandatory.
Access reviews with context
Certifications bring entitlement, usage and risk context together, so reviewers can document retain-or-revoke decisions.
One route for requests during the move
Requests and approvals follow one governed route while target systems move wave by wave.
Non-human identities in scope
Service accounts are registered with an owner and a purpose. AI agents are governed for ownership, privileges, access reviews and accountability.
An audit trail from day one on Anugal
Decisions, actions, exceptions and outcomes are recorded as append-only audit records as each decision happens.
Why Migrate to Anugal
One platform for identity lifecycle and access risk
Lifecycle, SoD checks, emergency access and audit records run on Anugal. You don't rebuild IDM in one tool and add a separate risk check beside it.
SAP and non-SAP reach
Anugal executes across directories, SAP systems, SaaS platforms, legacy and custom applications, and assesses SoD conflicts across applications, roles and business functions.
Legacy systems come along
Systems without modern APIs connect through Anugal Studio, so the migration doesn't stop at the systems with clean connectors.
Discover first
Discovery maps identities, roles, applications, workflows and controls before anything moves, so dependencies are on the table before the first wave. With a typical program running from about six months, an early start keeps extended maintenance a fallback rather than the plan.
Evidence that carries through the move
One append-only trail on Anugal, and a searchable archive of your IDM history, helps support audit-ready evidence for internal audit and regulators.
DORA's technical standards ask financial entities for a unique identity per staff member, including ICT third-party staff. NIS2 lists access control policies among required risk-management measures. Neither obligation pauses for a migration.
APRA has flagged incomplete inventories of privileged user and system accounts, and privileged access not always approved and granted for a valid business need and a specified time, as common weaknesses. Where such gaps could materially affect an entity, APRA treats them as a material control weakness notifiable under CPS 234 paragraph 36.
Where Anugal Sits After SAP IDM
Anugal takes over the identity lifecycle that SAP IDM runs today, alongside:
Already on Microsoft Entra?
Microsoft's own SAP IDM migration guide points to an external GRC product, through partner integrations, for fine-grained separation-of-duties checks. Anugal adds that SAP access governance beside Entra.
SAP Cloud Identity Services
SAP's reference architecture has an identity management solution upstream that replicates identities into the Identity Directory. After IDM retires, Anugal governs the decision and the execution in that position.
SAP GRC Access Control
It faces its own 2027 deadline. If IDM feeds users into Access Control today, settle the identity source first. See SAP GRC Access Control migration.
For SAP and IAM partners
Deliver the SAP IDM readiness assessment and the migration to Anugal as a fixed-scope service, next to your Entra or IGA practice.
Common Questions About SAP IDM Migration
Planning your move off SAP Identity Management? Start here.
When does SAP Identity Management support end?
Mainstream maintenance for SAP Identity Management 8.0 ends on 31 December 2027. Extended maintenance is available until 2030 at additional cost, and SAP has not announced a like-for-like successor. SAPinsider reports that extended maintenance covers critical issues only.
Is there a successor to SAP IDM?
SAP has not announced a like-for-like successor. SAP IDM customers therefore need a new home for their identity lifecycle. Anugal is built to be that home, with lifecycle, SoD checks before provisioning, emergency access and audit records on one platform.
How long does an SAP IDM migration to Anugal take?
A typical SAP IDM migration runs from about six months: discovery, data migration and configuration migration, followed by testing and sign-off. Larger estates move in additional waves.
How do we migrate from SAP IDM to Anugal?
In six stages: discover, design, migrate, verify and go live, archive, and retire. Identities, roles and assignments move wave by wave with deKorvai, our migration engine, and IDM components are decommissioned only after the archive is verified and you sign off. The readiness assessment is the first step.
What happens to our IDM scripts and custom connectors?
We inventory them first and record what each one does for the business. Rules that still reflect a real control are rebuilt on Anugal, and systems without modern APIs connect through Anugal Studio. We don't promise automatic conversion of IDM scripts. Moving the requirement is safer than copying the workaround.
Can we still access SAP IDM data after retirement?
Yes. Before SAP IDM is retired, its history is moved into a read-only, searchable archive, so audit and security teams can retrieve records whenever they need them.
Do we have to switch everything over at once?
No. We migrate wave by wave. Where continuity needs it, SAP IDM and Anugal run in parallel as a safety mechanism, never as the end state.
Can we migrate before the 2027 deadline?
A typical program runs from about six months, and larger estates add waves. How many target systems IDM provisions and how much custom logic it carries decide the number of waves, which is why the readiness assessment comes first. Extended maintenance to 2030 exists, and with an early start it stays a fallback rather than the plan.
Are technical users and AI agents in scope?
They should be. Service accounts are registered on Anugal with ownership and purpose metadata, and AI agents are governed for ownership, privileges and access reviews. Leaving them out of the inventory is one way orphan accounts survive a migration.
Start with an SAP IDM migration readiness assessment
We review your SAP IDM estate and show you scope, waves and timeline for the move to Anugal.
Migrating from SAP GRC too? See SAP GRC Access Control migration.

