Bring your existing project to Scribase, no rewrite
Import in, keep your client code, and keep the option to export out.
Moving a project in is one command: scribase import brings it over with user IDs preserved, your client code keeps working, and scribase export means your data is always yours to take.
The problem today
- Client rewrites when switching backends
- Auth migrations that force every user to reset a password
- Getting locked in
How Scribase helps
Import with a dry run
scribase import moves schema, data, auth.users, storage objects, and RLS policies, resumably, with --dry-run to preview exactly what moves.
No client rewrite
The data plane is contract-tested with the standard client SDK and CLI, so they keep working by changing the URL and keys.
Export keeps the door open
scribase export writes a bundle that boots elsewhere, so your data is never locked in.
The capabilities behind it
Every claim above maps to a feature Scribase ships. Here are the ones this use case leans on most.
Frequently asked
Will my users have to reset their passwords?
No. Import preserves user IDs and identities, so existing sessions and password logins keep working.
Can I see what will move before I commit?
Yes. Run scribase import with --dry-run to see exactly which tables, users, and objects will and will not move.