Migrating from Supabase
The usual playbook is to dump the database and compare a few queries. HostSpry moves the database, the authentication users and the file storage — and checks each of them against the source.
The source is opened read-only. Nothing is written to your Supabase project.
What a database dump alone leaves behind
A dump of the database carries tables and rows. It does not carry the files in Storage, and roles, row-level security policies and authentication identities need care to survive the move.
Supabase documents how to move a project. What is usually missing is verification: knowing afterwards that each part arrived intact.
What HostSpry moves and checks
- Schema, extensions and row-level security policies.
- Authentication users and identities. Password hashes are carried when their format is portable (measured: bcrypt).
- Table data, with counts and content compared.
- Storage buckets and objects, with sizes, types, owners and bytes compared.
What does not move
- Active sessions — users sign in again after the move.
- Anything that exists only inside the running platform and has no equivalent on the destination. The plan names it before you authorise; it is never dropped silently.
How we find your project
When your repository is analysed, the project reference it uses is recorded as evidence. After you connect your Supabase account, we look for that exact reference among the projects the connection can see — by reference, never by name — and tell you if it is in another account or organisation.
Migration report
- steps applied
- 6
- checks passed
- 11
- checks failed
- 0
- indeterminate
- 0
Request access
Tell us which project you want to move. We start with a rehearsal against a disposable destination.