/
Contact usSee pricingStart building
Node
​

    About Stytch

    Introduction
    Integration Approaches
      Full-stack overview
      Frontend (pre-built UI)
      Frontend (headless)
      Backend
    Migrations
      Migration overview
      Migrating users statically
      Migrating users dynamically
      Additional migration considerations
      Zero-downtime deployment
      Defining external IDs for users
      Exporting from Stytch
    Custom Domains
      Overview

    Authentication

    DFP Protected Auth
      Overview
      Setting up DFP Protected Auth
      Handling challenges
    Magic Links
    • Email Magic Links

      • Getting started with the API
        Getting started with the SDK
        Replacing your password reset flow
        Building an invite user flow
        Add magic links to an existing auth flow
        Adding PKCE to a Magic Link flow
        Magic Link redirect routing
    • Embeddable Magic Links

      • Getting started with the API
    MFA
      Overview
      Backend integration
      Frontend integration
    Mobile Biometrics
      Overview
    M2M Authentication
      Authenticate an M2M Client
      Rotate client secrets
      Import M2M Clients from Auth0
    OAuth
    • Identity providers

      • Overview
        Provider setup
      Getting started with the API (Google)
      Add Google One Tap via the SDK
      Email address behavior
      Adding PKCE to an OAuth flow
    Connected AppsBeta
      Setting up Connected Apps
      About Remote MCP Servers
    • Resources

      • Integrate with AI agents
        Integrate with MCP servers
        Integrate with CLI Apps
    Passcodes
      Getting started with the API
      Getting started with the SDK
    • Toll fraud

      • What is SMS toll fraud?
        How you can prevent toll fraud
      Unsupported countries
    Passkeys & WebAuthn
    • Passkeys

      • Passkeys overview
        Set up Passkeys with the frontend SDK
    • WebAuthn

      • Getting started with the API
        Getting started with the SDK
    Passwords
      Getting started with the API
      Getting started with the SDK
      Password strength policy
    • Email verification

      • Overview
        Email verification before password creation
        Email verification after password creation
    Sessions
      How to use sessions
      Backend integrations
      Frontend integrations
      Custom claims
      Custom claim templates
      Session tokens vs JWTs
      How to use Stytch JWTs
    TOTP
      Getting started with the API
      Getting started with the SDK
    Web3
      Getting started with the API
      Getting started with the SDK

    Authorization

    Implement RBAC with metadata

    3rd Party Integrations

    Planetscale
    Supabase
    Feathery
    Unit

    Testing

    E2E testing
    Sandbox values
Get support on SlackVisit our developer forum

Contact us

Consumer Authentication

/

Guides

/

About Stytch

/

Migrations

/

Migration overview

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.

migration image

Before you start

This set of migration guides assumes you are using Stytch’s Consumer APIs and SDKs. If you are using our B2B APIs, please see our B2B Migration Guides.

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 handled in your stack? Will you be integrating the Stytch 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. Static data migration strategy
  2. Dynamic data migration strategy
  3. Migrating authentication related logic
  4. Deploying your Stytch integration to production
  5. Exporting from Stytch

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

migration strategies

What's next

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

Before you start

Key questions and considerations

Migration guides

What's next