Replacement of SAP IDM What comes next?

Migrations often take more than 12 months. Those who don’t plan ahead today will soon find themselves under pressure due to a lack of preparation.

Most companies are currently focusing on tools as part of their SAP IDM migration. But they’re overlooking the answer to a much more important question:

What actually runs on SAP IDM?

 

Why act now?

The problem arises even while the system is still running

SAP has announced that it will discontinue its identity management system in 2027:

SAP IDM is currently still operational at most companies and running smoothly. That’s not the problem. The problem lies in the complex structures that have developed over time, the lack of documentation, and the limited resources—a situation that, over the years, hardly anyone can keep track of.

This only becomes apparent once the migration begins. As a result, additional costs are incurred and avoidable time is wasted.

The four biggest risks associated with replacing SAP IDM:

Risk 01

No one fully understands the system anymore
HR is tied to it. ERP too. Not to mention various custom solutions. Dependencies only come to light during the project—by which point it’s already become expensive.

Risk 02

Migrations are taking longer than planned
The process takes at least 12–18 months. Anyone who hasn't started by 2026 will not be able to meet the end-of-support deadline.

Risk 03

Experienced consultants are becoming harder to find
Consultants who are truly capable of handling such migrations are already in high demand. The number of projects isn't decreasing.

Risk 04

NIS2 & DORA are becoming nearly impossible to meet
Without updates and patches, the attack surface grows. It is nearly impossible to demonstrate compliance with a system that no longer receives support.

 

SAP IDM Replacement, Migration, Risks, Assessment, Requirements Analysis

Our Approach

Understand first, then act

We never start by asking about the tool. Before One Identity, Entra ID, or any other platform comes into play, it must be clear what actually needs to be migrated.

Here's how we do it:

Status Report

Analysis of the existing SAP IDM environment, including all dependencies, customizations, and undocumented processes.
Duration: 4–6 weeks

Requirements Analysis

What must the successor solution be able to do? NIS2, DORA, GxP, SOX—all compliance requirements are addressed early on.
In parallel with the analysis

Vendor-neutral selection

Only once the context is clear does comparing platforms make sense. We recommend what fits your landscape, not what sounds good.
Duration: 2–4 weeks

Migration & Operations

Structured migration with a clear timeline. Business operations continue after go-live, with no handover gap and no loss of knowledge.
12–18 months total

SAP IDM Replacement, Migration, Steps, Assessment, Requirements Analysis

What We Offer

Do you know what's going on at your place?

Most companies believe that—until we take a closer look together.

We conduct a detailed analysis of your SAP IDM environments to determine exactly what is in place and what that means for a migration.

Platform Expertise

Brand-independent: what's right for you.

We are familiar with all the relevant platforms and will recommend the ones that best suit your environment, your team, and your needs.

Vendors for IAM Operations Logos visualized
Overview of data protection

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.