Move your backend without resetting a single password
Each importer plans first, writes only after you confirm, keeps user ids and password hashes, and finishes with a verification report that compares every table old versus new.
From Supabase
Move a Supabase project to Scribase in one run: schema, data, RLS policies, auth users with password hashes and storage. Checksummed per table. Needs a project ref and service key — not for a plain Postgres database with neither.
User ids, so every foreign key and every issued JWT subject still matches
From Postgres
One command moves a plain Postgres database to Scribase: schema, grants, data, RLS policies and a checksummed verification report, no project ref or service key needed.
Row data and constraints, byte for byte, with a checksum proving it
From Firebase
Move Firestore, Firebase Auth, and Cloud Storage to Scribase. Password users keep their passwords through Firebase scrypt support.
Passwords: users sign in with the password they already have
From InstantDB
Move every namespace, $users, and $files to Scribase with ids preserved, then verify every table with row counts and checksums.
Entity ids, so every link and every stored reference still resolves
Step-by-step guides
Migrate a Supabase project without a password reset
Step-by-step: move a Supabase project to Scribase with one importer run, keep every password, copy storage, verify row counts, swap the supabase-js URL and key.
Migrate a Neon database to Scribase
Move a Neon Postgres database to Scribase: one scribase import postgres run for schema, data, RLS and verification, or pg_dump and scribase migrate by hand. Keep @neondatabase/serverless, add auth and storage.
Moving to a new project or account?
Moving a Supabase project to another project or account
Three ways to move a Supabase project to another one: Restore to another project, Project Transfers, or manual dump/restore — what each keeps.
Firebase Realtime Database limits, all in one place
Every hard limit on Firebase Realtime Database: connections per plan, 32-level nesting depth, write throughput, payload size, and read/query ceilings.