Migrating your auth to Stytch

This migration guide covers the process of migrating your app's existing authentication system over to Stytch. Here we provide generalized guidance that applies to any authentication setup, including authentication built in-house as well as solutions like Auth0.

migration image

Before you start

This set of migration guides assumes you are using Stytch’s B2B SaaS Authentication API and SDKs. If you are using our Consumer Authentication API, please see our Consumer Authentication Docs.

In order to complete any of the migration guides, you'll need the following:

  • A Stytch account if you don't have one already.
  • A Stytch B2B Auth project. If you don't have one already, in the Dashboard, click on your existing project name in the top left corner of the Dashboard, click Create a new project, and then select B2B Saas Authentication.
  • The project Test environment's project_id and secret from the API keys section. You'll need to pass these values into the Authorization request header for every Stytch API call.

Key questions and considerations

Before you start, you should consider the following questions about your migration requirements:

  • How is your data model structured? Is there a 1:1 relationship between users and organizations? Or can users belong to multiple organizations?

  • How many authentication factors do your users have? Do your users have only one primary factor like email? Or multiple factors like email and phone?

  • Do you need to transfer existing Single Sign-On (SSO) connections with identity providers?

  • Do users have defined roles and permissions for authorization?

  • Does your user base use passwords to authenticate? Are there passwordless users? A mix of both?

  • Where is authentication handled in your stack? Will you be integrating Stytch's API and SDKs into your backend or frontend?

Migration guides

Depending on how you answered the previous questions, our recommended approaches and strategies will differ. We've split them into multiple step-by-step guides organized by migration use cases:

  1. Reconciling data models
  2. Static data migration strategy
  3. Additional migration considerations
  4. Zero down-time deployment
  5. Exporting from Stytch

What's next

Consider the following:

How does your user and organization data model compare to Stytch's as explained in the next section: Reconciling user and organization data models?