[Home](https://easyiga.com/) / Migration / SAP IdM # Move from SAP IdM to midPoint. Our team plans and delivers migrations from SAP Identity Management to standard midPoint. We assess the roles, integrations and custom processes you rely on, then agree a phased transition. easyIGA is an optional addition, evaluated in a scoped pilot. [Discuss your SAP IdM migration](https://easyiga.com/contact#form) ## Plan around the maintenance deadline SAP states that maintenance for SAP Identity Management ends in 2027, with extended maintenance available until 2030. Confirm the terms that apply to your contract. Use the remaining time to test your replacement before retiring the existing system. [SAP’s maintenance announcement](https://community.sap.com/t5/technology-blog-posts-by-sap/preparing-for-sap-identity-management-s-end-of-maintenance-in-2027/ba-p/13596101) ## Prepare the configuration behind today’s access A list of applications is a useful start. The assessment also needs the logic that turns an HR change into an account or a role assignment. Prepare these records with your SAP Basis, HR and application teams. ### Identity stores and matching rules Identify the authoritative source for each attribute and how SAP IdM links a person to existing accounts. Include custom entry types, identifiers and inactive identities so the new system does not create duplicates or reactivate former employees. ### Business roles and technical privileges Map role inheritance, direct privileges and time-limited assignments to the access they produce in each target. Ask role owners which exceptions still serve a business need. Carry forward approved access, rather than copying every historical exception. ### Provisioning jobs and custom code Inventory repositories, jobs, dispatchers, scripts and approval tasks. Record their schedules, credentials and error handling. Custom behaviour needs an explicit implementation decision in midPoint; exporting SAP IdM configuration does not make that behaviour portable. ### SAP and non-SAP dependencies List system versions, interfaces and owners, including any planned S/4HANA or HR changes. Decide how existing SAP Cloud Identity Services fit into the target architecture. Check each connector against the operations you need, including account disabling and role removal. [SAP documentation on provisioning and system dependencies](https://help.sap.com/docs/SAP_IDENTITY_MANAGEMENT/d376345fb4e94928a70036ddf91d690b/2f8af286449c4453a8514ba598938581.html) ## Prove the transition with a representative workflow Use a department transfer as a pilot scenario. Compare the intended role change with the actual SAP and non-SAP accounts. Test a failed write and an expired assignment as well as the successful case. Agree which platform writes to each target during parallel operation. Before cutover, agree acceptance criteria, a rollback procedure and responsibility for unresolved changes. Keep historical approvals and audit records accessible under your retention rules. Archive access must be tested before SAP IdM is decommissioned. [Read the SAP IdM migration planning guide](https://easyiga.com/blog/sap-identity-management-no-version-to-upgrade-to) ## Agree the migration scope with our team Our team has delivered 14+ midPoint deployments. We assess your SAP IdM environment and prepare a written migration scope, including connector work, data cleanup and cutover responsibilities. The target is standard open source midPoint. An easyIGA pilot can separately evaluate everyday requests and access reviews for your users. For the free initial consultation, bring your SAP IdM version, connected-system list and one process that relies on custom logic. These details help us identify the work to assess first; timing and price follow the agreed scope. [What our migration service includes](https://easyiga.com/services#migration) [Request a free migration consultation](https://easyiga.com/contact#form)