Migrate to Kinde for user authentication
Get started
Migrate your users from Clerk to Kinde. Clerk supports exporting hashed passwords, and Kinde supports bcrypt — so your users can sign in with their existing passwords without a forced reset.
See Clerk’s documentation on exporting users.
Rename the columns in your Clerk export to match what Kinde expects. The only required column is email — everything else is optional but recommended.
| Clerk column | Rename to | Notes |
|---|---|---|
primary_email_address | email | Required — primary sign-in identifier |
email_verified | TRUE or FALSE | |
id | id | Keep as-is — helps match records on re-import |
first_name | first_name | Keep as-is |
last_name | last_name | Keep as-is |
primary_phone_number | phone | International format, e.g. +61555111555 |
password_digest | hashed_password | bcrypt hash — preserves existing passwords |
password_hasher | hashing_method | Value will be bcrypt |
For the full list of supported CSV fields — including organizations, roles, and permissions — see Prepare your CSV in the bulk import guide.
If you are importing hashed passwords, enable password authentication in Kinde before importing. See Password authentication.
See the bulk import guide to learn more.
Review the CSV for missing or duplicated values before importing. Kinde flags errors during import and reports them. Most errors can be fixed by editing the CSV and re-importing — records already imported without changes are skipped.
If you need help with your migration, contact Kinde support.