Move from Auth0 to Sendora.
Move users + passwords + SSO from Auth0 to Sendora Authentication. Most migrations take a day.
Step-by-step
- 1
1. Export users + bcrypt hashes from Auth0
Use Auth0 Management API `GET /api/v2/users` to export every user with their `password_hash` (bcrypt). Auth0 exposes hashes on a per-account basis — request export via support if not already enabled. Export as JSON.
30 min - 2
2. Bulk-import into Sendora
Use Data Sync module's hash-import endpoint: `POST /v1/auth-service/users/bulk-import`. Sendora accepts bcrypt / scrypt / argon2 hashes natively — users keep their existing passwords, no forced reset. Detect algo from hash prefix automatically.
30 min - 3
3. Mint Sendora API keys + drop the SDK
Create a project in Sendora dashboard, mint a `pk_*` public key (auto on project create). Install `@sendoracloud/sdk-web` + SSR companion for Next.js/Remix/SvelteKit, or RN / iOS / Android equivalents. SDK init takes one argument: `{ apiKey }`.
30 min - 4
4. Swap Auth0 React (or equivalent) for Sendora SDK calls
Replace `useAuth0()` with `sendora.auth.getCurrentUser()` and friends. `signIn`, `signUp`, `signOut`, `signInWithGoogle/GitHub/Apple/...`, `enrollMfa`, `verifyMagicLink`, `verifyEmailOtp`, `signInWithPasskey` all mirror Auth0's UX shape. Sample diffs ship in the migration repo.
1-2 hours per app - 5
5. Reconfigure social providers
Migrate Google / GitHub / Apple / Microsoft / LinkedIn / Facebook / Discord client_id + client_secret from Auth0 to Sendora's per-provider credential UI (encrypted at rest, AES-256-GCM). Apple takes a `.p8` private key + team_id + key_id.
1-2 hours - 6
6. (Optional) OIDC / SAML SSO + SCIM provisioning
For Business+ orgs running enterprise SSO: import IdP metadata XML at `/auth-service/sso/saml/:orgId/metadata` (one-click ingest in dashboard). SCIM endpoint URL + bearer token surfaces in dashboard for IdP-side provisioning config.
Half a day to a day per IdP - 7
7. Cut over DNS + monitor
Flip your app's auth UI to Sendora SDK builds. Auth0 tenant can stay live in read-only mode for 7 days as a safety net (Sendora doesn't depend on it). Monitor /auth/* error rates via Sendora Health (observability) — alert via Slack if anything spikes.
1 hour
Watch-outs
- Auth0 Rules / Actions don't port directly — review what each rule does, port the logic into Sendora's custom JWT claim templates (Growth+) or a webhook handler.
- Universal Login customization (CSS, branding, copy) needs to be re-applied via Sendora's auth UI customizer.
- MAU pricing exit — Auth0 may bill an annual minimum even after you stop using it; check your contract.
Authentication
Identity that's already wired to your product — not a black-box you bolt CRM plugins onto.
Auth0 gives you logins. Clerk gives you logins. Sendora gives you logins that already know what the user did in your app, what they consented to, which experiment they're in, which audience they belong to, and how to message them across every channel — because identity, events, profiles, messaging, and support all share one tenant. Auth0 + Mixpanel + Customer.io + Zendesk + Intercom in one bill, one SDK, one user_id.
Read full Authentication pageStuck on the migration? We'll help.
Launch partners get white-glove migration help direct from the engineering team. Free plan covers real product use during the parallel-run period.