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 which applies to any authentication setup, including authentication built in-house as well as Auth0, AWS Cognito, and Google Firebase.

Before you start

This set of migration guides assumes you are using Stytch’s Consumer APIs and SDKs.

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 Consumer 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 Consumer 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:

What are your application surface areas? Do you have a web app, mobile app, or both?
Does your user base use passwords? Are there passwordless users? A mix of both?
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?
Where is authentication integrated into your stack? Will you be integrating Stytch into your backend or with one of our frontend SDKs?

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:

To understand if migrating data statically or dynamically is a better strategy for you, see our high level recommendations below:

What's next

To start, we recommend checking out the migrating user data guides — statically or dynamically.