Migrate off MIM without losing your business rules.
Microsoft Identity Manager 2016 left mainstream support in January 2021, and extended support ends in January 2029. If you are still running MIM, you are carrying technical debt. Modern 42 migrates organisations from MIM to Microsoft Entra ID Governance and Lifecycle Workflows, preserving every business rule in the process.
Why organisations replace MIM.
MIM 2016, the successor to Forefront Identity Manager (FIM) 2010, was built for a different era of identity management. The platform has accumulated significant technical debt and Microsoft's investment has moved to Entra ID.
- MIM mainstream support ended January 2021 (extended support to January 2029)
- High maintenance burden: custom DLLs, complex workflows, synchronisation rules
- Difficulty recruiting engineers with current MIM skills
- No cloud-native integration with Microsoft 365
- Modern Entra ID capabilities eliminate the need for most MIM functions
What replaces MIM.
Microsoft Entra ID provides cloud-native replacements for every core MIM capability.
Entra ID Lifecycle Workflows
Microsoft Identity Governance
Entra ID Connect / Cloud Sync
HR-driven provisioning
SCIM application provisioning
Apporetum Identity State Model
Microsoft Identity Manager to Entra ID.
A direct comparison of capabilities between Microsoft Identity Manager (MIM) and its replacement Microsoft Entra ID Governance.
MIM rules analysed across Australian government and enterprise migrations. Every rule documented, validated, and either migrated or retired.
The business rules problem.
The most complex part of any MIM migration is mapping custom workflows, synchronisation rules, and business logic to the target platform. Many MIM and FIM environments have accumulated years of customisation that exists only as code, with no documentation and no design records.
We start every MIM migration by reverse-engineering the existing configuration and documenting every business rule. Nothing goes into the target environment without first being understood and validated. This phase is critical and cannot be skipped.
Equally important is knowing which rules should not be carried forward. Legacy workarounds, redundant logic, and rules that exist only because of MIM limitations have no place in a modern platform. We help you decide what to keep, what to simplify, and what to leave behind entirely.
The documentation produced during this phase has value independent of the migration. For many organisations, it is the first complete record of how their identity lifecycle actually operates.
Where MIM migrations stall.
Every MIM environment is unique. These are the areas where migrations fail when the team has not accounted for the full scope.
Undocumented business rules
Most MIM deployments have accumulated years of custom sync rules, stored procedures, and management agent logic that is poorly documented. Every rule must be understood before it can be replaced.
Custom Management Agents
Custom-built connectors for HR systems, databases, and legacy directories often contain critical business logic that cannot be directly lifted into Entra ID. Each agent requires analysis and re-implementation.
Active Directory dependencies
MIM often manages AD group memberships, attribute synchronisation, and provisioning flows that other systems depend on. Replacing MIM requires understanding every downstream dependency.
See the work delivered
Comparable engagements we have delivered. Client names are withheld; the work is not.
View all case studiesTransforming Identity and Cyber Capability for a Federal Government Department
A large Australian Government department partnered with Modern 42 to overhaul its identity infrastructure and strengthen its cyber security posture.
Identity Governance and Administration Uplift for a Major Retail Property Group
Continuing its IAM transformation journey, a major Australian retail property group engaged Modern 42 to define its Identity Governance and Administration (IGA) capability, laying the groundwork for automated identity lifecycle management.
Common questions
Everything you need to know about migrating from Microsoft Identity Manager to Entra ID.
What happens to our Active Directory synchronisation?
Will there be service disruption during migration?
Can all MIM workflows be replicated in Entra ID?
How long does a MIM migration take?
What does MIM mainstream support ending in January 2021 mean?
What happens when MIM extended support ends in January 2029?
Do you migrate Forefront Identity Manager (FIM) 2010 environments?
Do you carry all legacy rules into the new platform?
What if our MIM environment has no documentation?
Can you help with identity observability after migration?
Do you bring your own IP to engagements?
Microsoft Cloud Solutions Partner for Security
Modern 42 is a recognised Microsoft Cloud Solutions Partner for Security with the Identity and Access Management designation.
Let’s talk about your identity platform
No pitch decks. No pressure. Just a straightforward conversation about your Entra ID environment, what’s working, and what needs to change.
- Review your current Entra ID and identity architecture
- Identify migration paths and modernisation opportunities
- Get practical engineering guidance, no strings attached
Free 30 min discussion
No commitment required
Book a time that works for you. We’ll come prepared with initial observations about your identity platform and common engineering challenges.