Migrate from Supabase to Layerbase
Move your Supabase Postgres to a managed Layerbase database in one guided pass. Paste an access token, pick a project, and we copy the schema, data, and auth users. Read-once, your Supabase project is never modified, and credentials are never stored.
Using Supabase Auth? Your users come across with their passwords intact. We copy the auth.users rows with their bcrypt hashes untouched, so no one has to reset a password, and you manage them from the Auth console once the migration finishes.
Why switch
Why teams leave Supabase
Your auth users come with you
Supabase Auth stores credentials in your database. We copy the auth.users rows with their bcrypt hashes untouched, so nobody resets a password, and you keep managing users from the Layerbase Auth console.
Flat pricing, no usage meters
A real Postgres on the Free tier, then $5/mo Solo or $15/mo Pro. No per-request billing, no egress surprises, and paid databases are never paused.
A guided, read-once migration
Paste a Supabase access token and we list your active projects. Pick one, paste its database password once (Supabase never exposes it via API), and we copy schema and data in a single pass.
The same Postgres you already use
Standard connection strings, pooled and direct, TLS by default, a web SQL console, and the drivers and ORMs you already run. No proprietary client.
How it works
Four steps, one pass
- 1
Create a free account or sign in
Sign in with Google or GitHub. No credit card is needed to start, and the migration wizard opens with this platform already selected.
- 2
Connect your account
Paste a Supabase access token (Account, then Access Tokens). We list your active projects so you can pick one. Supabase never exposes the database password through its API, so you paste that once for the project you choose.
- 3
Pick what to migrate and name it
Choose what to bring over, give the new Layerbase database a name, and start the migration. Progress streams live in the dashboard.
- 4
We copy it in one pass
The migration reads from Supabase once and never writes to it. Credentials are used for the copy and never stored. When it finishes, you land in your new database with a live TLS connection string.
Questions
Common Supabase migration questions
Will my Supabase project be modified?+
No. The migration is read-once: we connect, copy the schema and data, and disconnect. Nothing is written to your Supabase project and it keeps running throughout.
Do my users have to reset their passwords?+
No. Supabase Auth keeps credentials in the auth.users table inside your database, and we copy those rows with their bcrypt hashes intact. Sign-in keeps working against Layerbase.
What credentials do I need?+
A Supabase access token (Account, then Access Tokens) so we can list your projects, plus the database password for the project you pick. Supabase never exposes that password through its API, so you paste it once. Neither credential is stored after the migration.
What about Storage, Edge Functions, and Realtime?+
The migration covers your Postgres database: schema, data, and auth users. Supabase-specific services like Storage buckets, Edge Functions, and Realtime channels are separate products and do not transfer.
Ready to leave Supabase?
Sign in, and the migration wizard opens with Supabase already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.