WorkOS migration

Migrate from WorkOS

Move AuthKit users, organizations, SSO connections, and Directory Sync into Authdog through a staged cutover that protects B2B sign-in continuity.

Bring your identity data

Keep users, not legacy constraints

Map existing identities into Authdog while your current system keeps serving production traffic. Validate data and sign-in behavior before changing application routes.

User profiles and verified email state
Social and enterprise identity links
Application roles and organization membership
Metadata needed by your authorization model

Migration plan

Move in four controlled steps

01

Export from WorkOS

Inventory WorkOS users, organizations, memberships, AuthKit usage, and SSO connections. Export each cohort and record Directory Sync group-to-role mappings.

02

Map users and access

Map WorkOS user ids to Authdog external identifiers, recreate organizations and memberships, and reconnect SAML/OIDC providers with Authdog ACS and redirect URLs.

03

Preserve sign-in continuity

Choose a password strategy for AuthKit users. Use progressive migration when hashes are unavailable, or move cohorts to magic link or SSO-first sign-in.

04

Cut over in stages

Run both systems during a defined transition window. Move one organization or application at a time, validate IdP login, then retire WorkOS API keys and connections.

Cut over without a big-bang release

Run migration rehearsals against an isolated Authdog environment. Compare user counts, identity links, claims, and authorization outcomes. Switch production only after your acceptance checks pass.

WorkOS-specific checks

  • Preserve each WorkOS user id as an external identifier before import.
  • Rebuild organization membership and roles from WorkOS exports, not from memory.
  • Schedule SSO ACS/metadata updates per customer domain.
  • Replace Directory Sync with Authdog provisioning or an equivalent SCIM path.
  • Update backends that validate WorkOS sessions or JWTs.

Ready to leave WorkOS?

Create an isolated Authdog environment, test your import, and plan a cutover that works for your users.