Briefly describes the migration steps for OIM 12c to SailPoint IIQ 8.4

Which IIQ version are you inquiring about?

Version 8.X

Share all details related to your problem, including any error messages you may have received.

Hi Team,

we are planning to migrate the current environment from Oracle Identity Manger 12c to Sail Point IIQ 8.X.
In that migration process how to build the OIM api(lookups,user,etc) related code in SailPoint IIQ.
and what all are prerequisites need to follow in that migration process.
if anyone previously migrated the same, any documents related to migration or steps highly appreciated.
let me know, if any details or further information from my end.

Migrating from Oracle Identity Manager (OIM) 12c to SailPoint IdentityIQ (IIQ) 8.4 requires careful planning and execution. Here’s a breakdown of your questions:

Building OIM API Code in SailPoint IIQ

While OIM relies on its own APIs, SailPoint IIQ utilizes a different approach. Here’s how to handle your OIM API usage in the new environment:

  • Connectors: Instead of custom code, SailPoint leverages pre-built connectors or creates custom connectors to connect to target systems like user directories and applications. SailPoint offers a wide range of connectors out-of-the-box, and you can develop custom connectors if needed.
  • SailPoint IdentityIQ scripting: SailPoint uses scripting languages like XACML and IIQScript for automating workflows and access governance processes. You can potentially translate some OIM API logic into these scripts for specific functionalities within SailPoint.

Prerequisites for Migration

  • SailPoint Expertise: Having a team with SailPoint IIQ expertise is crucial for a smooth migration. This includes understanding connectors, workflows, and best practices for SailPoint.
  • Data Mapping: Map your OIM data model to the SailPoint data model. This might involve identifying user attributes, entitlements, and other relevant data points that need to be migrated.
  • Environment Setup: Set up a SailPoint IIQ environment that mirrors your production OIM environment as closely as possible for testing purposes.
  • User Access Review: Review user access in OIM and identify any potential inconsistencies or unnecessary entitlements. This helps establish a clean slate for access management in SailPoint.

Migration Resources

While there might not be a single document outlining the entire migration process, here are helpful resources:

  • SailPoint Documentation: The SailPoint documentation offers resources on connectors, workflows, scripting, and best practices: https://documentation.sailpoint.com/
  • SailPoint Community: The SailPoint community forum allows you to connect with other SailPoint users and potentially find migration experiences or ask questions: https://developer.sailpoint.com/
  • Consulting Services: Consider SailPoint consulting services for a guided migration process with their expertise: https://www.sailpoint.com/

Additional Tips

  • Start with a Proof of Concept (POC): Begin with a small-scale migration of a specific user population or application to test the migration process and identify any challenges.
  • Phased Approach: Consider a phased migration where you gradually migrate users and applications to minimize disruption.
  • Testing: Thoroughly test your SailPoint configuration and workflows before migrating production data.

By following these steps and leveraging available resources, you can successfully migrate your environment from OIM 12c to SailPoint IIQ 8.4. Remember, a well-planned and executed migration can significantly improve your identity governance and access management practices.

2 Likes