C1.ai to join Workday. Read the announcement →

SailPoint IdentityIQ to Identity Security Cloud: Migrate or Modernize?

By The C1 Team
SailPoint IdentityIQ to Identity Security Cloud: Migrate or Modernize?

SailPoint IdentityIQ (IIQ) is SailPoint’s customer-hosted identity governance and administration (IGA) platform. Identity Security Cloud (ISC), formerly IdentityNow, is SailPoint’s SaaS identity security platform. Moving from IdentityIQ to ISC means changing products, not just versions: roles, rules, integrations and review processes must be mapped, rebuilt and tested. Before committing, IIQ owners should compare three paths: upgrade IIQ, migrate to ISC, or modernize on a different enterprise IGA platform such as C1.ai.

Years of rules, roles and integrations can contain essential business controls alongside workarounds nobody wants to maintain again. The next platform should preserve those controls and make everyday governance easier. Start with a process your team knows well: when someone changes departments, how much work does it take to remove their old access and confirm it is gone?

IdentityIQ, IdentityNow and Identity Security Cloud#

SailPoint IdentityIQ, IdentityNow and Identity Security Cloud are related names, but they do not describe interchangeable products or deployment models.

ProductWhat the name means for an IIQ customer
SailPoint IdentityIQ (IIQ)Customer-hosted enterprise IGA. Staying means continuing to operate and maintain that platform, including its integrations and customizations.
SailPoint IdentityNowSailPoint's earlier SaaS identity offering, rebranded as Identity Security Cloud. ISC encompasses and builds on IdentityNow features.
SailPoint Identity Security Cloud (ISC)SailPoint's cloud identity security offering. Moving from IIQ changes the platform and operating model; it is more than a product-name change.

The relationship between IdentityNow and ISC does not establish that subscriptions, modules or commercial terms are identical. Compare the actual proposed scope with the capabilities your organization uses today.

Nor should migration planning start with an assumed IdentityIQ retirement deadline. IdentityIQ remains an active product: SailPoint announced IdentityIQ 9.0 on October 6, 2026. A support deadline for your installed version is a separate matter from retirement of the product line. Confirm your version and support entitlement with SailPoint before treating an upgrade or migration as mandatory.

This distinction gives you room to make a better decision. If customer hosting and specific IIQ customizations still serve the business, an upgrade may be appropriate. If platform maintenance or everyday governance work has become the constraint, use the migration assessment to evaluate what should change.

Why IdentityIQ teams reconsider the platform#

IdentityIQ’s flexibility is the reason many enterprises chose it. The same flexibility creates the work that pushes teams to reconsider. On G2, reviewers list cost and a steep learning curve among SailPoint’s most common drawbacks, and one notes that IdentityIQ "requires an extensive knowledge of development" (G2). Customer-hosted infrastructure, upgrade cycles and custom rules all need specialist owners, and every new application adds to that maintenance.

That makes a migration decision a chance to modernize. If the burden comes from hosting, ISC addresses it. If it comes from how lifecycle, access and review work is built and maintained, a modern platform such as C1.ai changes the operating model itself.

What should improve after migration?#

An application count is a poor description of an identity program. Two estates with the same number of applications can demand very different amounts of work. One may rely mainly on standard integrations. Another may have private systems, custom approval paths and access inherited through several layers of groups and roles.

Start with the recurring work that consumes your team's time. Pick a few outcomes you can measure now and test during an evaluation: how long a new hire waits for access, how often fulfillment becomes a help-desk ticket, how much manual work follows a review denial, or how long it takes to change a lifecycle policy safely. Establish a baseline before asking a vendor to improve it.

Then distinguish controls you must preserve from implementations you can reconsider. A rule that prevents incompatible access may encode a necessary control. The script, ticket handoff or approval chain used to enforce it may be replaceable. Carry forward the requirement and ask each platform to demonstrate its proposed implementation.

That creates three credible paths:

PathStrongest reason to choose itWhat changes and what to prove
Stay on or upgrade IdentityIQCustomer hosting and existing customizations remain valuable, and your team can support them.The platform remains customer-hosted. Verify upgrade work, application coverage and continued operating cost.
Move to Identity Security CloudYou want SailPoint's SaaS model, its target capabilities fit, and continuity with the vendor matters.Platform and deployment change. Verify converted and redesigned processes, their dependencies and commercial scope.
Evaluate C1.aiYou want to change how enterprise lifecycle, access and review work gets done.Workflows move to C1.ai's SaaS platform with application-specific integrations. Prove required operations, controls and recovery behavior.

The decision should account for the next application and policy change as well as the current estate. Ask who will implement those changes, what specialist work they require and who owns the result when an integration fails. A platform can meet today's requirements while leaving tomorrow's operating burden largely intact.

Moving from IdentityIQ to ISC: assistance matters, testing still belongs to you#

SailPoint offers a substantive migration path. Agentic Acceleration, announced June 16, 2026, uses SailPoint Virtual Architect to analyze IdentityIQ configuration exports and plan the target ISC design. SailPoint says the program is provided at no additional cost to customers upgrading from IdentityIQ or competitive legacy solutions, delivered through its forward-deployed engineers.

That assistance belongs in the evaluation. So does an explicit account of what it covers. A conversion program does not establish that subscriptions, partner services, internal staffing, testing and overlapping operations are all free. Ask SailPoint to map the proposed assistance to your inventory and identify the work that remains with your team.

Nelnet migrated from IIQ to ISC with partner ProofID, which reports onboarding and migrating 50 to 75 applications across the original implementation and the migration. That shows a real transition path, although it does not set a schedule for your environment or benchmark today's acceleration program.

Custom rules are where vendor continuity needs a closer look#

IIQ and ISC run rules in different contexts. Existing logic needs to be mapped to the supported target design; retaining the SailPoint name does not guarantee identical behavior.

In ISC, cloud-executed rules require SailPoint review before deployment (SailPoint cloud rules documentation). That creates a dependency to account for when planning rule changes. The review checks rule integrity; it does not prove that your business process grants and removes the right access. Connector-executed rules follow a different process, run with connector context on a virtual appliance and do not require that cloud-rule review (connector rules documentation). Treating every ISC rule as subject to the same approval process would overstate the constraint.

The practical question is what each retained customization becomes. Some requirements may fit ISC lifecycle states, access profiles or other supported configuration. Others may need rule-based logic. Ask for the target design, the change process and a test of the outcome. Neither a successful conversion nor an approved rule closes that work.

C1.ai takes a different approach. Instead of porting IIQ code, teams rebuild each requirement as configurable lifecycle, request and review policy. That is the moment to retire custom logic nobody wants to maintain while keeping the control it enforced.

Inventory the dependencies, not just the configuration#

For each application, record its business owner, identity authority, account and entitlement operations, current provisioning owner, dependent rules and workflows, proposed target implementation and audit-record location. Add a test case, migration wave and rollback owner so the inventory can guide decisions.

Include service and agent accounts where they exist. Their ownership and removal triggers may differ from employee lifecycle events. For example, an employee's departure can leave a service account without a responsible owner even when the employee's own accounts are correctly removed.

Use this inventory to retire unused roles, grants and logic before recreating them. Every dependency you retain should have an owner and a reason to exist.

The enterprise case for evaluating C1.ai#

C1.ai, formerly ConductorOne, brings lifecycle management, access and reviews into a SaaS operating model, with connector deployment options for private systems. For an IIQ owner, that is the chance to replace customer-hosted infrastructure and custom code with policy-driven governance the identity team can change itself.

C1.ai supports automated account provisioning through lifecycle and birthright configuration. Hire-date triggers, dynamic groups and birthright profiles replace much of the custom joiner logic IIQ teams maintain today, and access request workflows handle exceptions through web, Slack, Teams and APIs.

Zscaler reports expanding to more than 250 applications over 12 months, with new-hire access in about ten minutes on fully connected applications and 60% fewer help-desk provisioning tickets. Those outcomes make the enterprise case tangible: sustained application rollout accompanied by less manual provisioning work.

Reviews present a different opportunity. Moving the IGA platform to SaaS does not remove legacy applications from the governance scope. C1.ai's access review capabilities cover campaign scoping through remediation, tracking whether each revocation reached the target system and storing the decision alongside the outcome.

PriceSmart reports reducing quarterly access reviews from three months to two or three weeks across legacy and cloud systems.

Connectivity needs the same attention. C1.ai supports self-hosted connectors for private systems, with outbound connections to its SaaS control plane. That covers a hybrid estate without hosting the governance platform, and credentials for private systems stay inside your network.

For applications without a ready connector, Baton and its SDK let teams build integrations for custom and homegrown systems. Review connector capabilities at the operation level, from syncing access to provisioning and deprovisioning, to plan each migration wave. Access conflict controls carry segregation-of-duties checks across connected applications.

A useful C1.ai evaluation combines a representative SaaS application, a difficult private integration and an access review that results in a denial. Follow that decision through remediation, inspect target-system access and retrieve the evidence. That shows what the new operating model looks like on your own estate.

For a wider market view, see the SailPoint alternatives guide and our identity modernization guide.

Compare the full cost of the destination#

The most useful commercial comparison combines transition cost with the cost of running the program afterward. Request a scoped proposal for the required subscriptions and modules, then account for implementation and partner services, internal staff, replacement of customizations, testing, reviewer training and evidence retention.

Include overlap licensing and connector hosting. During a phased move, the old platform may remain necessary for longer than the first successful campaign or provisioning event suggests. Budget against the dependencies that must disappear before retirement.

C1.ai includes implementation with purchase (C1.ai vs SailPoint), which removes one of the largest transition variables from the comparison. For SailPoint’s cost drivers, see our SailPoint pricing guide.

For ongoing operations, identify who maintains integrations, changes policies, resolves failed fulfillment and supports reviewers. Use your baseline to assess the proposed improvement. A vendor's migration assistance can reduce part of the transition effort while leaving substantial customer work elsewhere; a lower subscription quote can similarly obscure a heavier operating requirement.

Ask each vendor to show what is included, what depends on a partner and which assumptions could change the estimate. Compare that scope with the cost of continuing on IIQ. Avoid committing on the strength of a headline price or an untested promise of speed.

A phased migration checklist that protects the controls#

A phased transition can reduce the scope of each cutover. It also creates a period when responsibilities must be especially clear. Evaluate whether parallel deployment fits your environment, and specify which system observes access, which makes decisions and which performs each write.

Use a short acceptance checklist to keep the transition tied to those responsibilities:

  • Before choosing the destination: The IAM lead and application owners approve the inventory and performance baseline. Security accepts the mapping of retained controls, including any coverage exceptions; the program owner and finance accept the complete commercial scope. Remove obsolete dependencies before they become migration requirements.
  • Before each cutover: Application owners sign off the pilot's required operations, and control owners accept lifecycle, review-denial and failure tests. Include rehires, contractor expiry, conflicting access and service-account owner departure where relevant. Operations assigns one authoritative writer per application and action, reconciles queued work, freezes conflicting automation and accepts the stop and rollback procedures before expanding the wave.
  • Before retiring IIQ: The program owner confirms that no remaining process needs IIQ. Control owners sign off closed campaigns and fulfillment work, retained evidence and its retrieval. Operations revokes obsolete credentials and accepts responsibility for steady-state support.

Test a mover and a failed removal#

Consider a finance employee moving to another department. The new role needs access, and the old finance entitlement must be removed. Check where that entitlement originates: a direct grant, a group, a role or a birthright policy. Removing it in one place is insufficient if another assignment recreates it.

Then deliberately interrupt the removal path with a connector failure. The team should demonstrate how it detects the incomplete action, who resolves it, what a retry does and how the evidence distinguishes a requested removal from a completed one. Confirm that the old platform's automation cannot regrant the access after recovery.

This test exposes several risks that a successful onboarding demo can miss. It also gives security, application owners and operations a shared definition of success. In a C1.ai evaluation, the decision, the removal attempt and its outcome sit in one audit trail, so a failed removal stays visible until it is resolved.

Set rollback triggers before the wave begins, such as unexplained grant differences or removals that cannot be completed within your control requirements. Define which writes stop, how pending work is reconciled and who authorizes resumption. Returning responsibility to the old platform does not automatically undo target-system changes already made.

Do not assume historical audit records will import intact into the destination. Test retrieval under your retention policy before losing access to the old system. Parallel operation may be a useful bridge, but IIQ is not retired while another process still depends on it for fulfillment or evidence access.

Frequently asked questions#

What is the difference between IdentityIQ and Identity Security Cloud?#

IdentityIQ is customer-hosted enterprise IGA; Identity Security Cloud is SailPoint's cloud offering. Moving from IIQ to ISC changes the platform and requires teams to map and test existing integrations, workflows and controls.

How does IdentityNow relate to Identity Security Cloud?#

IdentityNow's SaaS capabilities underpin and are expanded by Identity Security Cloud. That relationship does not establish identical licensing, modules or commercial terms, which should be checked against the proposed subscription.

What does IdentityIQ 9.0 mean for migration planning?#

IdentityIQ 9.0 demonstrates that the product remains active. An organization should distinguish its installed version's support status from product retirement and evaluate upgrading alongside its cloud options.

Is SailPoint IdentityIQ end of life?#

No. SailPoint announced IdentityIQ 9.0 in October 2026, and the product remains active. Check the support dates for your installed version, which are separate from the product line, before treating a migration as mandatory.

How long does an IdentityIQ to Identity Security Cloud migration take?#

It depends on the number of applications, custom rules and workflows that need redesign. SailPoint’s Agentic Acceleration aims to shorten the process, but plan in waves and budget for testing and a period of overlap with IIQ.

What happens to custom rules during an ISC migration?#

Teams map IIQ logic to ISC's supported configuration and rule contexts, then test the business outcome. Cloud-executed rules require SailPoint review; connector-executed rules follow a separate process without that review requirement.

How can an enterprise phase an IdentityIQ migration?#

Move applications or processes in controlled waves, with one authoritative writer for each application and action. Establish reconciliation, recovery and evidence-retention procedures, then retire IIQ only after its remaining dependencies are removed.

What should enterprises test before replacing IdentityIQ with C1.ai?#

Test required operations on representative SaaS and difficult private applications, including lifecycle changes, review denial, removal failures and evidence retrieval. Verify exact connector capabilities and the ongoing administrative work before accepting the replacement design.

Put your hardest workflow in the evaluation#

Bring C1.ai a representative application, a difficult integration and a lifecycle or review process your team wants to improve. Evaluate C1.ai as a SailPoint alternative against the controls, operating work and transition requirements that will determine whether the move is worthwhile.