scribase
Migrate from Clerk

Paste a secret key. Your users land on a backend with no per-user bill.

Clerk bills by monthly active user once you pass its free tier, and its API does not export password hashes on any plan, by design. Scribase pages your whole user list with one secret key, keeps ids, verified email/phone status, and linked OAuth providers, and sends every imported user a one-time password-reset link — then auth has no MAU meter, ever, on any paid plan.

Four steps in the console: connect the source, review a dry run that writes nothing, run it, and read the verification report. Your place is saved if you close the tab; credentials never are.

What moves

Everything a Clerk app runs on

Users
Every user, with a deterministic id derived from their Clerk id, so a second run converges instead of duplicating.
Verified status
Email and phone verification exactly as Clerk recorded it — an already-verified user stays verified.
Linked sign-in
Google, GitHub, Microsoft, Apple, Discord, GitLab, and more become auth.identities rows, so "Sign in with X" keeps working.
Profile fields
First/last name, username, and public/unsafe metadata, carried into user metadata.

What stays the same

  • User ids, mapped old-to-new in public.clerk_user_id_map so app data that stored a Clerk id still joins
  • Verified email and phone status, exactly as Clerk recorded it
  • Linked OAuth providers, so returning users can still sign in with the same one
  • Banned and locked users stay blocked after the move

What you do by hand

  • Passwords are never copied, because Clerk's Backend API has no endpoint that returns a password hash, on any plan — not a gap in this importer. Scribase emails every imported user with an address a one-time password-reset link right after a real run.
  • Clerk organizations, invitations, and active sessions are not part of this import — only users and their linked providers move; recreate organizations on Scribase separately.
  • MFA (TOTP, backup codes) cannot be exported from Clerk either, for the same reason passwords cannot; affected users re-enroll.
How it works

Plan, run, prove

  1. Step 1

    Open the import wizard

    In the console, start a new import and choose Clerk. Pick the Scribase project and environment the users land in.

  2. Step 2

    Paste the secret key

    From the Clerk dashboard, API Keys, copy a Secret key (sk_live_... or sk_test_...) — not the publishable key. It is sent once to read your user list and is never stored.

  3. Step 3

    Plan it

    The dry run reads Clerk only. It pages every user and reports how many will move, which sign-in providers it can map automatically, and the password-hash limitation above — before anything is written.

  4. Step 4

    Run it, then read the report

    Confirm to write the users and their linked identities. The report lists how many moved and repeats every finding from the dry run; the verdict is fail-closed.

The verification report

Old versus new, table by table

Every import ends with this. The verdict is VERIFIED only when every row count and checksum matches, every policy is present, and the sign-in proof passes. The numbers below are an example of the format.

TableClerk rowsScribase rowsChecksum
public.profiles12,40812,408 match
public.orders88,21488,214 match
public.order_items240,977240,977 match
Also checked: RLS policy parity, auth user count, storage object count, and a sign-in with an account you control. Verdict: VERIFIED
Migration help

A large or unusual move? Tell us about it.

The importer runs in the console today. If your app is large or you want a second pair of eyes on the dry run, tell us your size and we will reach out to help.

FAQ

Migrating from Clerk

Will my users be able to sign in right away?

With a linked OAuth provider, yes — one click, same as before. With a password, no: Clerk's API does not export password hashes on any plan, so Scribase emails a one-time reset link to every imported user with an address right after the run.

Does this stop the Clerk MAU bill?

Once your app points at Scribase Auth instead of Clerk, yes — Scribase's plans are a flat per-project price with no per-monthly-active-user meter, so a spike in signed-in users does not change the bill.

What about my Clerk organizations?

They are not part of this import — only users and their linked sign-in providers move. Recreate organizations on Scribase after the users land.

Is it safe to run twice?

Yes. Each user's id is derived deterministically from their Clerk id, so a second run against the same Clerk instance converges instead of duplicating users.