Migrate to Kinde for user authentication

Moving to Kinde from another auth provider? Choose a migration method below, then follow the export guide for your current provider.

What you can migrate

Link to this section

• Users — email, name, phone, external ID
• Hashed passwords — bcrypt, sha256, md5, crypt, wordpress supported
• Organizations — for multi-tenant apps
• Roles and permissions — assigned per user and per organization

Before you migrate

Link to this section

Set up the following in Kinde before importing users:

1. Authentication methods — enable password authentication if you’re migrating passwords; enable passwordless or social sign-on if users will need to re-authenticate.
2. Organizations — create organizations in Kinde if you use multi-tenancy or separate user groups.
3. Roles and permissions — add roles and permissions before importing if you want to assign them to users on import.

Choose your migration method

Link to this section

Bulk import

Link to this section

Export your users to a CSV or JSON file and import them into Kinde in one go. Works with hashed passwords — users keep their existing password with no reset required.

Best for: Teams doing a planned cutover with a defined migration window.

Bulk import users →

Create users with the API

Link to this section

Provision users in Kinde programmatically during the migration window — for example, by intercepting sign-ups or sign-ins in your existing system and pushing them to Kinde in parallel.

Best for: Catching new registrations and password changes during a migration window; teams with custom auth systems.

Create users with the API →

Drip-feed migration

Link to this section

Users migrate automatically as they log in. A Kinde workflow validates each login against your legacy system and creates the user in Kinde on first successful sign-in. No downtime. No bulk export required.

Best for: Teams that want zero downtime and a seamless user experience. Recommended for most teams.

Drip-feed migration tutorial →

Hard cutover (maintenance window)

Link to this section

Take the service down, export all users, import into Kinde, then bring it back up. Simple, but requires planned downtime.

Best for: Small user bases where a short maintenance window is acceptable.

Use the bulk import guide with the maintenance window variant.

Provider export guides

Link to this section

Each provider has its own export format and limitations. Select your current provider for export steps and key considerations:

• Auth0 →
• FusionAuth →
• Clerk →
• Supabase →
• Firebase →
• AWS Cognito →
• Azure B2C →