[Home](https://easyiga.com/) / Migration / Microsoft MIM # Move from Microsoft MIM to midPoint. A MIM migration starts with the flows that keep your directories and applications consistent. Our team maps those dependencies and plans the move to standard midPoint. easyIGA is an optional pilot for the people who request, approve and review access. [Discuss your MIM migration](https://easyiga.com/contact#form) ## Use the support period to validate your replacement Microsoft lists extended support for MIM 2016 through 9 January 2029. Check your installed version, service pack and dependent components separately. A product support date does not establish that every component in your environment has the same lifecycle. [Microsoft’s MIM lifecycle](https://learn.microsoft.com/en-us/lifecycle/products/microsoft-identity-manager-2016) ## Separate the responsibilities currently handled by MIM ### Synchronisation and identity matching Inventory management agents, connected data sources, run profiles and rules extensions. Document how connector-space objects join to the metaverse, which source wins when attributes disagree and when changes are exported. Use that information to design equivalent mappings in midPoint. ### Service, Portal and approval workflows If you use MIM Service and Portal, collect sets, Management Policy Rules, workflows and custom forms. Identify the owner of each approval and the business reason for it. Decide which processes to keep, simplify or retire before rebuilding them. ### Active Directory and Microsoft Entra dependencies Trace the path from HR through MIM to Active Directory and any onward synchronisation to Microsoft Entra ID. Record account identifiers, group ownership and the attributes used downstream. Replacing MIM does not by itself replace Microsoft Entra Connect or the sign-in service. ### Additional MIM components Check whether your deployment also uses Certificate Management, Privileged Access Management, password reset or BHOLD. Assign each required capability a separate target solution and acceptance test. Do not treat a directory-synchronisation pilot as proof that these functions have been replaced. [Microsoft’s component and dependency guidance](https://learn.microsoft.com/en-us/microsoft-identity-manager/microsoft-identity-manager-2016) ## Test matching before enabling writes Start with a limited population and compare the proposed changes with existing accounts. Check join rules and attribute precedence before enabling writes. Incorrect matching can create duplicate accounts; an unexpected authoritative value can overwrite an attribute used by another application. During parallel operation, assign one writer for each governed target object or attribute. Test a leaver, a failed export and recovery after an outage. Check the account and group result in the target, not only the completion of a synchronisation run. Agree the cutover sequence and rollback criteria in writing. Preserve required request history and configuration records before decommissioning MIM. Include the team that operates AD and Entra in the acceptance decision. [Read the MIM replacement planning guide](https://easyiga.com/blog/microsoft-identity-manager-2029-extension) ## Turn the inventory into a scoped migration Our team has delivered 14+ midPoint deployments and has migration experience with Microsoft MIM. We assess the flows and custom logic to move, then agree the implementation work, parallel operation and handover. Standard open source midPoint is the target; an easyIGA pilot is optional. For the free initial consultation, bring your MIM component list, management agents and one identity flow diagram. Include any custom extensions and the systems that depend on MIM. We use these facts to define the assessment before quoting the migration. [What our migration service includes](https://easyiga.com/services#migration) [Request a free migration consultation](https://easyiga.com/contact#form)