Why Now Is the Right Time to Migrate to IDABUS

For many companies, Microsoft SharePoint has formed the foundation of critical business processes for years — including the Microsoft Identity Manager (MIM) Portal, which is technically built on SharePoint.

But it is precisely this foundation that is coming to an end:
Microsoft will end support for SharePoint Server 2016 and 2019 on 14 July 2026. From this date onwards, no more security updates, bug fixes or technical support will be provided.

In concrete terms, this means:

• Continued operation is entirely at your own risk.
• Security gaps are no longer being closed
• Compliance and data protection requirements are becoming more difficult to meet
• In the event of a malfunction, there is no manufacturer support.
  
  

Since the MIM Portal is based directly on SharePoint, this end of support affects not only the platform itself, but your entire portal infrastructure. Anyone who continues to operate the MIM Portal beyond July 2026 will be using a central IAM component without manufacturer support – with corresponding risks for stability, security and auditability.

The migration to IDABUS is therefore not purely a technical modernisation, but a strategically necessary decision to secure your IAM landscape.

Your previous investments will be retained

We are aware that many organisations have made considerable investments in the MIM Portal over the years – in:

• Role and authorisation concepts
• approval workflows
• Data models and object structures
• Customised adjustments and processes
  
  

However, switching to IDABUS does not mean losing these investments.

IDABUS was designed so that existing structures could be adopted.

With our specially developed migration tool, configurations, workflows, role models and data can be transferred to IDABUS in a largely automated process.

So you retain:

• Your proven processes
• Your technical concepts
• Your organisational logic
  
  

And win at the same time:

• A modern, fully supported platform
• Technological independence from SharePoint
• A long-term stable foundation for your identity and access management
  
  

Important note: MIM Sync will continue to be supported for the time being.

A common misunderstanding concerns the MIM synchronisation service (MIM Sync).

This is not directly affected by SharePoint. Microsoft offers extended support for MIM 2016 until 9 January 2029.

This means:
The synchronisation engine can continue to be operated even if the portal is migrated. This means that there is no immediate pressure to take action to replace it completely in one step.

Strategic outlook: IDABUS Sync from the end of 2027

However, we are already thinking ahead.

OCG is currently developing its own IDABUS Sync component, which will be available at the end of 2027. This will enable us to completely transfer the synchronisation layer to the IDABUS world in the medium term.

The aim is to create a comprehensive platform:

• without Microsoft legacy dependencies
• without SharePoint connection
• with clear technological prospects for the future
  
  

Here, too, we rely on a structured, loss-free migration process so that existing connectors, logic (MA and MV extensions) and synchronisation rules can be transferred, thereby protecting existing investments.

Our recommended approach: gradual modernisation

In our experience, a step-by-step approach is the safest and most economically sensible strategy:

Phase 1 (until July 2026):
Migration from the MIM portal to IDABUS – to safeguard against the end of SharePoint.

Phase 2 (modernisation):
As IDABUS has significantly more functionality than MIM, a consolidation or modernisation phase is recommended.

Phase 3 (from the end of 2027):
Planned migration from MIM Sync to IDABUS Sync.

This approach offers clear advantages:

• Minimised project risk
• Predictable budget allocation
• No “Big Bang” scenario
• Technical stability during transformation
• Protection of all previous investments
  
  

This creates a modern, future-proof IAM architecture – without unnecessary time pressure, but with a clear strategic direction.

More information to follow

Further details on the IDABUS sync roadmap, technical architecture and specific migration scenarios are available at:

• in the next newsletter
• on our social media channels
• as well as in the IDABUS User Group
  
  

Let us take the next step together – towards a long-term stable and secure IAM platform.

Do you have any questions or would you like to discuss the next steps? Contact us by telephone or email – together we will find the right solution.