01What comes across
Each provider's own file. Read as it is.
| From | The file | What comes across |
|---|---|---|
| Auth0 | Its user export, one JSON record per line | Email, name (or the nickname), phone |
| Amazon Cognito | A CSV in Cognito's user-import layout, columns matched by name | Email, name (or the given and family names), phone |
| Azure AD B2C | The Microsoft Graph list of users | Email (from the sign-in identity, the mail or the user principal name), display name, mobile phone |
Passwords and second factors do not come across — no provider exports them in a form another can use.
02The move
Five steps. In this order.
Your old provider
Export your users
Use the provider's own export: Auth0's user export, a Cognito user CSV, or the Microsoft Graph list of your B2C users.
Qeet ID console
Import them into an organisation
Each row becomes a person. A row that cannot be read, or has no email, is reported with its line and the reason, and the rest carry on. Everyone imported can be given a role, and their ids come back.
Your people
Choose how they sign in first
Passwords cannot come across, so imported people sign in with a passkey or a magic link — or set a password through a reset you send.
03Good to know
Small things, before the big day.
A bad row stops nothing
It is reported with its line, its code and the field at fault.
Phones are tidied, not completed
Formatting is removed; a missing country code is not added.
Roles take seats
A role given during an import counts against the plan's seats.
One request per file
Each file is imported in a single request, so a very large export is best split.