SailPoint IdentityIQ (IIQ) is identity governance software you host, upgrade and customise yourself, often with BeanShell rules, custom workflows and plugins. Identity Security Cloud (ISC) is SailPoint's SaaS platform, configured through identity profiles, transforms and workflows, with code as a last resort. ISC suits teams that want less to run; IIQ suits estates that depend on deep custom logic. Moving between them is a redesign, not a copy.
Working on this now? Discuss your SailPoint programme and we answer within one business day, or message us on WhatsApp.
The differences that matter
Both platforms cover the core of identity governance: aggregating accounts from sources, joiner-mover-leaver automation, roles, Segregation of Duties policies, access requests and certification campaigns. Where they differ is who runs the platform and how you change its behaviour.
| IdentityIQ | Identity Security Cloud | |
|---|---|---|
| How it is delivered | Software you host, patch and upgrade | SaaS run and updated by SailPoint |
| How you change behaviour | Java and BeanShell rules, custom workflows, tasks and plugins | Identity profiles, transforms and ISC workflows; rules only where nothing else works |
| Custom code review | Your team decides what is deployed | Cloud-executed rules are reviewed by SailPoint before deployment |
| Reaching on-premise systems | Directly from your IdentityIQ servers | Through a SailPoint virtual appliance in your network |
| Common connectors | Active Directory, JDBC, Web Services, SCIM 2.0, REST | Active Directory, Microsoft Entra ID, JDBC, Web Services, SCIM 2.0, REST |
| Who carries upgrade effort | Your team, as upgrade projects | SailPoint, as part of the service |
When IdentityIQ still fits
- Your governance depends on custom logic that has no configuration equivalent yet, and the business is not ready to simplify it.
- Policy or contracts require the identity platform to run inside your own infrastructure.
- You have a stable, well-run IIQ estate and a capable team to keep upgrading it, and no pressing reason to change platforms this year.
Staying on IdentityIQ is a reasonable decision in these cases, but it is still worth knowing what your estate contains. An inventory of rules, workflows and connectors pays for itself whichever way you decide later.
When Identity Security Cloud fits
- You are starting an identity governance programme and have no IdentityIQ estate to carry.
- Your team spends more time keeping IdentityIQ running and upgraded than improving governance.
- Most of your applications can be reached through standard connectors (directories, HR systems, JDBC, SCIM or REST APIs).
- You want to adopt SailPoint's newer capabilities as they ship rather than through upgrade projects.
What changes if you move from IdentityIQ to ISC
A move is a redesign of how the platform is customised, not a lift-and-shift. These are the points that shape the plan:
- IdentityIQ rules, workflows and tasks are not portable. SailPoint's developer-community guidance is that each one is re-expressed as ISC configuration, a transform, an ISC workflow or a reviewed rule, or retired.
- Identity and role models, SoD policies, access requests, certifications and email templates map more closely and can often be moved in bulk with SailPoint's tooling, though their logic still needs review.
- Accounts and entitlements are re-aggregated from the sources in ISC. IdentityIQ audit history does not move, so decide how it will be archived for your retention period.
- Both platforms can run side by side. Moving sources in waves, and reconciling identities, accounts and entitlements before each cut-over, keeps joiner-mover-leaver and certifications working throughout.
- In June 2026 SailPoint announced Agentic Acceleration, AI-assisted tooling for converting IdentityIQ configurations. It speeds up conversion; deciding what should move, testing against real HR data and reconciling access still has to be done.
Questions to answer before you decide
- How many BeanShell rules, custom workflows and plugins are in production, and which are still used?
- Which applications rely on custom connector code rather than a standard connector?
- Is there a hosting or data-residency requirement that rules out SaaS?
- What did your last two IdentityIQ upgrades cost in time and effort?
- How long must IdentityIQ audit history be kept, and where?
- Which certification campaigns and SoD reports must keep running without a gap during any change?
IIQ or ISC for US, UK and UAE organisations
The platform choice is the same in every country; what changes is the hosting question. Where identity data must stay in a region, that requirement can decide between a self-hosted IdentityIQ estate and SaaS, so settle it first.
- UAE and the Gulf: in April 2025 SailPoint announced its first Middle East SaaS instance, regionally hosted and citing demand for data sovereignty. If regional hosting is why you run IdentityIQ, ask SailPoint whether that instance meets your regulator's requirements before you rule ISC out. Our UAE work is IdentityIQ 8.x for a bank and a healthcare provider; see SailPoint identity governance in Dubai and the UAE.
- United Kingdom: our UK reference is an Identity Security Cloud implementation for a global mining and metals company, covering Active Directory and Entra ID as identity sources, application onboarding and joiner-mover-leaver automation. See SailPoint for UK organisations.
- United States: our US references are two Identity Security Cloud programmes, for a Fortune 500 distributor and a cybersecurity firm, the second with production support after go-live. See SailPoint consulting services.
Our experience on both platforms
MappOptimist engineers have implemented IdentityIQ 8.x for a healthcare provider and a bank in the UAE, and Identity Security Cloud for a global miner in the UK and a Fortune 500 distributor and a cybersecurity firm in the US. These are implementations, not migrations; they are the depth on each side that a migration draws on.
Frequently asked questions
What is SailPoint ISC?
SailPoint ISC (Identity Security Cloud) is SailPoint's SaaS identity governance platform. It controls who has access to which applications: joiner, mover and leaver provisioning from HR or directory sources, access requests, access certifications, role-based access and Segregation of Duties policies. SailPoint runs and updates the platform, and you change it mainly through configuration rather than custom code. In August 2026 SailPoint introduced Human Fabric, which it describes as the evolution of Identity Security Cloud.
What is the difference between SailPoint IIQ and ISC?
IIQ (IdentityIQ) is SailPoint's identity governance software that you host, upgrade and customise yourself, often with BeanShell rules and plugins. ISC (Identity Security Cloud) is SailPoint's SaaS platform, run and updated by SailPoint and changed through configuration, with custom rules as a last resort. Both cover access requests, certifications, roles and Segregation of Duties policies.
Is SailPoint Atlas the same as Identity Security Cloud?
In practice, yes. SailPoint describes Atlas as the multi-tenant SaaS platform that serves as the foundation of Identity Security Cloud, and it is not sold on its own. So a comparison of IdentityIQ with Atlas is a comparison of IdentityIQ with ISC: self-hosted software you customise against a SaaS platform you configure. IdentityIQ is separate software and does not run on Atlas. In August 2026 SailPoint introduced Human Fabric, which it describes as the evolution of Identity Security Cloud.
Can Identity Security Cloud be hosted in the Middle East?
SailPoint announced its first Middle East SaaS instance in April 2025, regionally hosted, citing data sovereignty demand. The announcement does not name a country, so confirm with SailPoint whether it meets your regulator's data-residency requirements before choosing between IdentityIQ and ISC.
Should I migrate from SailPoint IdentityIQ to Identity Security Cloud?
Migrate when your team spends more time running and upgrading IdentityIQ than improving governance, when most of your applications can be reached through standard connectors, or when you want SailPoint's new capabilities without upgrade projects. Stay on IdentityIQ for now if policy requires the platform inside your own infrastructure, or if your governance depends on custom logic the business is not ready to simplify. Either way, start with an inventory of your rules, workflows and connectors: it shows what would move, what needs a redesign and what can be retired.
Can SailPoint IdentityIQ run on-premises, in the cloud or as a hybrid?
IdentityIQ is software you install and run yourself, on servers in your own data centre or on cloud infrastructure you manage, so you also own patching and upgrades. Identity Security Cloud is SaaS run by SailPoint; it reaches on-premises sources such as Active Directory and internal databases through a virtual appliance installed in your network, which is how most hybrid estates are connected. During a phased migration, both platforms run side by side until each wave is reconciled.
Is IdentityIQ being replaced by Identity Security Cloud?
SailPoint's SaaS platform is where its new capabilities are announced, including Human Fabric in August 2026, which SailPoint describes as the evolution of Identity Security Cloud. Check SailPoint's current support policy for your IdentityIQ version when you plan; this guide does not state support dates.
Can we customise Identity Security Cloud as much as IdentityIQ?
Not in the same way. ISC is designed to be configured: identity profiles, transforms and ISC workflows cover most needs, and rules are a last resort. Cloud-executed rules are reviewed by SailPoint before deployment, and connector-executed rules run on the virtual appliance. Deep Java customisations and IdentityIQ plugins have to be redesigned or retired.
How long does an IdentityIQ to ISC migration take?
It depends on what the IdentityIQ estate contains: the number of applications, custom rules, workflows and connectors. That is why we start with an inventory and give estimates after it, rather than before.
Can we run IdentityIQ and ISC at the same time?
Yes. A phased migration runs both platforms side by side. Authoritative sources move first, then applications in waves, and each wave is reconciled before provisioning and certifications switch to ISC.
Can MappOptimist engineers work on both platforms?
Yes. Our published SailPoint work covers three Identity Security Cloud and two IdentityIQ implementations. You can bring in individual SailPoint engineers, a dedicated team, or white-label delivery if you are a consultancy running the programme.
Sources
- SailPoint developer documentation (developer.sailpoint.com): cloud-executed and connector-executed rules.
- SailPoint developer community: IdentityIQ to Identity Security Cloud migration guidance.
- SailPoint announcements: Agentic Acceleration (June 2026) and SailPoint Human Fabric (4 August 2026).
- SailPoint press release, 23 April 2025: first SaaS instance in the Middle East.
- SailPoint blog, 10 October 2023: A guide to SailPoint Atlas (Atlas as the foundation of Identity Security Cloud).
- MappOptimist SailPoint case studies: three Identity Security Cloud and two IdentityIQ implementations.