Migrating to Iden

What changes when you move identity governance to Iden, what stays the same, and where to start. Per-vendor migration guides indexed here.

3 min read · Last updated September 2026

You've decided to switch. The current tool is too slow, too expensive, or both. The next question is what the move looks like.

Pick the vendor you're leaving below, and the per-vendor guide walks through the move. Each guide follows the same structure, because the migration follows the same shape regardless of where you're coming from.

What changes when you move

Three things shift on day one.

You stop waiting on professional services. There aren't any. The team that runs your stack today is the team that runs this. Setup is measured in days, not months. The first 15 apps connect inside the first hour.

You stop paying for connector coverage in tiers. SCIM or not, plan tier or not, custom or not. Everything is covered the same way, at the same price. The SCIM tax goes away.

You stop thinking about identity work as a queue. The HRIS becomes the source of truth. Onboarding, offboarding, and access changes flow from there without anyone clicking through 5 tools. Permissions go fine-grained per app: channel-level, repository-level, project-level. Group-level is the floor, not the ceiling.

What stays the same

The SSO stays. The HRIS stays. So does the access request channel, whatever you run it through. This is a governance layer on top of the stack you already have. The IdP keeps running. The HRIS keeps doing what it does. It plugs into both, treats the HRIS as the source of truth, and executes from there. Migration is not a rebuild.

The shape of each guide

Nine sections, every time.

  1. Why teams leave that vendor.
  2. What changes day one.
  3. Concept mapping: their term, and its equivalent here.
  4. The playbook: export, connect HRIS, parallel-run, cut over, decommission.
  5. Common gotchas specific to that vendor.
  6. Timeline by stack size.
  7. Rollback plan if you need it.
  8. FAQs.
  9. Where to ask for help.

Plan for a parallel run. The window covers the audit-trail handoff, the first full joiner-mover-leaver cycle on the new system, and one access-review run. After that the old tool gets decommissioned, or kept as a soft fallback. The per-vendor timeline section tells you what's realistic for your stack.

Pick your starting point

Migration guides publish on a rolling schedule. Live guides are linked. The rest are in the queue.

Microsoft Entra ID Governance is not on this list. Iden runs alongside Entra rather than replacing it, the same way it runs alongside Okta SSO. The Entra comparison covers where the line sits.

Need a hand picking the path

Migration office hours run weekly. The same team that builds the product runs them. Bring whatever shape your stack is in. We will tell you what's realistic, and the honest answer is sometimes "stay where you are for now."

Related playbooks

How to automate offboardingMost offboarding fails because tools were never built to reach the apps that matter. What zero-touch offboarding actually means, why most automation breaks, and what a working flow looks like on the day someone leaves.
How to give a new joiner day-one accessWhat birthright access means in practice, how role-based policy replaces the manual onboarding queue, and what a working day-one looks like.
How to handle a role changeThe mover is the lifecycle event nobody automates. Why role changes leave more standing access than departures do, what a working handover window looks like, and how to make the old role expire without breaking the new one.
How to provision apps without SCIMMost identity tools stop at the apps with SCIM. That's about 20% of the average stack. How to provision the other 80%, end to end, without the manual queue.
IAM vs IGA: what's the differenceIAM and IGA solve different problems but get used interchangeably. Where the line is, what each one does, and how to tell which gap you're hitting.
Keep Okta SSO, add IdenWhat Okta SSO does, what it doesn't, and how Iden plugs in as the governance layer on top. Setup walkthrough, common patterns, where the responsibilities split.
What to do after Okta is deployedWhat teams find in the first months after deploying Okta. The gaps Okta leaves by design, the work that needs to happen next, and how to scope the next 90 days of identity work.