SAP has postponed the end of mainstream support for SAP Identity Management until 2027. For many companies, this is welcome news. But if you stop thinking about it now, you’ll find yourself under considerable pressure in 2026.
In this article, we explain why most projects fail due to a lack of preparation and what specific steps you should take.

 

Why SAP IDM projects are now on the agenda

Most companies know their SAP IDM system pretty well. It’s been running for years, has been expanded, customized, and somehow kept growing. HR is tied to it. ERP is too. Not to mention various custom solutions. And no one has a complete overview anymore.

The problem isn't the system. The problem is that no one has a complete overview anymore, and that's exactly what makes the project expensive.

 

The same thing happens with almost every transfer:

  • Things are coming to light that were never documented

  • Logic that no one can explain anymore

  • Dependencies that only become apparent during the project

 

What Makes Projects Challenging Right from the Start

The pattern is almost always the same: First, a target platform is selected—often based on demos or discussions with the manufacturer. Then the project gets underway. And only then does the actual analysis begin.

This is exactly where things get tricky.

  • The platform doesn't fit seamlessly into the existing landscape

  • The IT department does not have sufficient capacity for migration and operations

  • The requirements were overestimated

The project is still moving forward, of course. But it’s becoming a struggle, costly, and unnecessarily complicated. The mistake is made right at the start. In practice, this means that projects take significantly longer than expected, budgets have to be adjusted later on, and internal teams are tied up for months.

 

Understand first, then decide

Before discussing tools, three key questions need to be addressed:

  1. What Actually Runs on SAP IDM

  2. What requirements must be met (e.g., NIS2, DORA, internal audits)?

  3. What can we realistically do, both internally and externally?

Only once this has been thoroughly addressed does a platform comparison make any sense. A thorough preliminary analysis takes four to six weeks—and that’s exactly the part that saves time, money, and stress down the line.

 

So the platform isn't the starting point

Whether it’s One Identity, Entra ID, or something else: the tools are rarely the problem. The right choice always depends on the context, the environment, the team, and the requirements. If you start by focusing on the tools, you’re missing the most important part.

 

What makes sense now

At the beginning, it’s not about finding the perfect strategy; it’s about clearly understanding your own situation:

  • What's really on today?

  • Which of these is critical?

  • What can we sustain in the long term?

That will take you further than any strategy on paper.

Key Takeaways

The most important points at a glance
  • Start early
    Migrations often take more than 12 months. Those who don’t plan for 2026 will find themselves under pressure.
  • Analysis Before Tool Selection
    First understand what’s currently in place, then decide which platform is the right fit.
  • Assess resources realistically
    Experienced consultants are already in high demand. It pays to start early.
  • Incorporating Compliance fromthe Start
    NIS2, DORA, and internal audit requirements must be incorporatedinto the planning process from the very beginning.

Have you thought about these points yet?
More on this in our conversation

 

If you're at that point right now, it makes sense to start right here.

Are you using SAP IDM but aren't sure where to go from here?

We regularly examine existing environments in detail to determine what is actually in place and what that means for the migration.

→ Request a quote now with no obligation

Back to overview