Migration

Switch SSO providers without calling your customers

Move your connections without asking your customers’ IT admins to change anything, wherever that’s technically possible. Importers for WorkOS and Ory Polis come first.

The move

Three ways we keep the move invisible

  1. Your domain, re-pointed

    If SSO already runs on your own domain, change one DNS record. The identity provider sees the same URLs and the same entity ID.

  2. One field for the IT admin

    If SSO runs on your old vendor’s domain, the IT admin updates one field. We send them a pre-filled guide for their identity provider.

  3. Same profile IDs

    Profile IDs your app already stored keep matching, so there is no data migration in your database.

DNS for sso.yourapp.com
Before
CNAMEold-vendor.example
After
CNAMEthe target shown in your OhAuthCat dashboard

Nothing changes in your customers’ identity providers

WorkOS compatibility

Coming from WorkOS

A WorkOS-compatible API lets your existing integration keep working while you move to the OhAuthCat SDK at your own pace. It is included for six months after you migrate; extended support is a paid add-on for months 7 to 18, and the compatibility layer ends after month 18.

The migration guide and the importer are still in development.

Start free

Compatibility API after you migrate
  1. Months 1–6Included
  2. Months 7–18Paid extended support
  3. After month 18Compatibility layer ends