IIQ to ISC Migration

SailPoint IdentityIQ to Identity Security Cloud Migration

Migration is not a lift-and-shift. It requires evaluation, redesign, mapping, implementation, and validation of identity governance capabilities for the ISC platform.

Why Migration Is More Than an Export

IdentityIQ configuration generally cannot be transferred to Identity Security Cloud as-is. ISC is a SaaS platform with different architecture, configuration models, extensibility patterns, operational boundaries, and implementation approaches.

Existing capabilities must be inventoried and mapped deliberately: what can be recreated with ISC configuration, what should be redesigned using transforms or native services, what requires connector or cloud rules, what can be simplified, and what should be retired rather than migrated.

Components Requiring Evaluation

Applications and application schemas
Correlation configurations
Provisioning policies and account creation profiles
Roles, access profiles, and access models
Rules and custom logic
Workflows and lifecycle processes
Identity attributes and identity profiles
Transforms and attribute logic
Certifications and access-review configurations
Integrations with HR, ticketing, directories, and enterprise applications
Customizations and custom connectors

Active Directory Migration: A Representative Example

Active Directory is a useful example because a mature IIQ deployment often combines connector configuration, schemas, correlation, IQService dependencies, provisioning logic, groups, Exchange-related behavior, and custom rules.

Active Directory in IdentityIQ

Direct Connector application with account and group schemas.
Correlation rules or configuration matching AD accounts to identities.
Provisioning forms, plans, policies, and rules for account creation and modification.
IQService dependencies for supported Windows/AD operations where required.
Group membership provisioning and entitlement governance.
Custom logic for OU placement, naming conventions, attribute population, or Exchange behavior.

Active Directory in ISC

Virtual Appliance-based source connectivity and ISC source configuration.
Schema and account/group attribute mapping recreated for the ISC source.
Correlation implemented using ISC correlation configuration and identity architecture.
Account creation and update behavior mapped to provisioning policies, transforms, and supported rule types.
Group governance and provisioning revalidated against ISC access-model patterns.
Testing validates aggregation, correlation, provisioning, deprovisioning, group management, and transition behavior before IIQ decommission.

Read the detailed Active Directory migration guide →

Our Migration Approach

A structured, phased approach from discovery and readiness through production validation.

Migration Readiness Assessment

Inventory applications, integrations, customizations, lifecycle logic, identity data, access models, dependencies, and migration complexity.

ISC Architecture Design

Define the target identity architecture, sources, identity profiles, attributes, transforms, lifecycle processes, access models, and integration patterns.

Application Migration Planning

Create application-by-application plans with redesign requirements, sequencing, dependencies, testing needs, and cutover approach.

Implementation Guidance

Provide hands-on architecture and technical guidance as ISC sources, configurations, policies, transforms, rules, and integrations are built.

Migration Validation

Validate aggregation, correlation, lifecycle, access requests, provisioning, deprovisioning, certifications, integrations, and exception paths.

Go-Live Readiness

Confirm operational, technical, and organizational readiness before production cutover and before IdentityIQ capabilities are decommissioned.

Planning an IdentityIQ to ISC Migration?

Start with a readiness assessment to understand your environment's complexity and build a realistic migration plan.

Request a Migration Consultation →