Skip to content
Dashboard
Theme
Theme

Migrate

Guides for moving existing enterprise connections and directories to OhAuthCat without asking your customers' IT admins to reconfigure anything they do not have to.

View Markdown

Move enterprise connections and directories from Polis, WorkOS, Auth0, a CSV/SAML archive or an ImportBundle with the import API or the ohauthcat migrate CLI. Every import is planned and reviewed before it creates organizations, connections and directories, and each organization switches, and rolls back, on its own.

  1. Choose Polis, WorkOS, Auth0 or CSV/SAML metadata and create a plan.
  2. Review items, blockers and plan.source_skipped. A skipped source object is absent from the bundle; a blocker describes work needed for an included object.
  3. Check imported-profile limits, then run the import. Resolve configuration requirements, verify domains, test sign-ins and activate connections.
  4. Switch one organization, watch sign-ins and keep the old provider available for rollback.

Use migration levers to decide which IdP settings change. Apps owning their callback can use forwarding. Session cutover maps imported profiles; export produces portable configuration.

Imported bundles never carry passwords, OIDC client secrets, SCIM bearer tokens or SP private keys. Auth0 source credentials are used only during the request that reads the tenant and are never stored. Domain verification and activation are not inherited. The WorkOS compatibility bridge and imported SAML ACS aliases are implemented backend capabilities.

The SDK migration helpers read per-organization routing and resolve authenticated legacy sessions in your application. They do not move traffic or validate an old provider token for you. Review the cutover checklist and session resolver contract before enabling them.