The full dashboard
Table editor, SQL editor, logs, backups — the entire Supabase Studio, not a locked-down sandbox.
Chrome extension · Lovable Cloud → Supabase
Move off Lovable Cloud to your own Supabase — without resetting a single password.
Migrator copies your entire backend — database schema, every row, auth users with their original password hashes, storage files, and Edge Functions — into a Supabase project you fully own. A few clicks, one one-time bridge, your Cloud left intact.
Your dump streams source → destination and is never stored on our servers.
Moves
Database schema
All your data
Auth users + passwords
Storage files
Edge Functions
How it works
Three honest steps. Your Cloud stays live the whole time.
No reverse-engineering, no black box. Migrator uses the same open bridge pattern the community exporter does, then runs a standard Postgres migration you could audit yourself.
-
Connect & drop the bridge
Paste your Supabase project ref and personal access token. Migrator has your Lovable project deploy a tiny one-time migrate-helper function, gated by a single-use access key. That key lets the engine read the source database URL and service-role key — nothing else.
one-time bridge -
Verify against a baseline
Before anything moves, Migrator peeks the source: tables, approximate row counts, users, and buckets. You review the plan and confirm it matches what you expect — so migration day holds no surprises.
preview & confirm -
Migrate — Cloud untouched
pg_dump streams schema, then data, then auth.users with their hashes; storage copies bucket-by-bucket and functions redeploy. The source is a read-only export — your Lovable Cloud project keeps running until you decide to switch.
read-only source
What gets migrated
Your whole backend, faithfully — down to the password hashes.
Everything moves as standard Postgres and Supabase primitives. No proprietary format, nothing to translate by hand.
| What | How it moves | What you keep |
|---|---|---|
| Database schema | pg_dump --schema-only across your app schemas, restored with psql | Tables, columns, types, constraints, functions and triggers — recreated exactly. |
| Table data | pg_dump --data-only, streamed row-by-row into the destination | Every row, exactly as it was. No sampling, no truncation. |
| Auth users | auth.users + auth.identities copied as ordinary table data | Original bcrypt password hashes — your users sign in with the same password, no reset. |
| Storage | buckets & files copied via the /storage/v1 API, bucket-by-bucket | Every file and your bucket layout, intact. |
| Edge Functions | redeployed into the destination via the Supabase Management API | Your functions live and running on your own project. |
Your frontend app code stays in your own repo — that is its home. Migrator moves the backend data plane and can redeploy your functions; your React app is never something we host or touch.
Why your own Supabase
Stop renting your backend. Own it.
The same Postgres, now on a project with your name on it — full access, real keys, your billing.
Your service-role key
Real anon and service-role keys you control, for your own server-side code and integrations.
Custom auth emails
Bring your own SMTP, templates, and sending domain for confirmations, magic links, and resets.
Your own billing & limits
Pay Supabase directly and scale on your plan — no middleman between you and your infrastructure.
Your RLS & SQL
Write row-level-security policies, run migrations, enable extensions — it is genuinely your database.
No lock-in
Standard Postgres and open Supabase primitives. Take a dump and leave whenever you like.
Pricing
One license key. One full migration.
Simple by design: you pay per migration, not per row, per user, or per gigabyte.
License key
Per migration
1 key= 1 complete migration
Activate a key in the extension and run one full migration — at any size.
- Schema, data, auth, storage & functions — all included
- Any size — no row, user, or storage caps
- Passwords preserved, source left intact
- Charged once per run — safe to retry within a run
How keys work
Redeem a key like LVB-XXXX-XXXX-XXXX inside the extension. Its uses are added to your balance; each migration spends exactly one.
Need several?
Multi-use keys are available — one code that covers several migrations, for agencies and multi-project teams.
Payments
Online checkout isn't live yet — keys are issued directly for now. Add to Chrome and request one to get started.
FAQ
Straight answers
Does it really move passwords?
Yes.
auth.users and auth.identities are copied as ordinary table data, so the original bcrypt password hashes come across untouched. Your users sign in with the exact same password — no reset emails, no forced re-registration.Is my data safe?
Your database dump streams straight from the source to your destination and is never stored on our servers. Any temporary export artifacts expire automatically. The
migrate-helper bridge is gated by a single-use access key that only works during your migration — and you can delete it right after.Does it change my Lovable Cloud project?
No. The source is a read-only export (
pg_dump). Your Cloud project keeps running exactly as it is until you have confirmed everything landed in Supabase — then you cut over on your own schedule.What about my Edge Functions and frontend?
Your frontend app and the source of your Edge Functions live in your own repo or Lovable project — that's the source of truth, and Migrator leaves it there. Migrator moves the backend (schema, data, auth, storage) and can redeploy your Edge Functions into the destination project. Your React frontend is never something we host or migrate.
What do I need to get started?
Chrome, your Lovable project open in a tab, a Supabase project with a personal access token (PAT) and project ref, and a license key. The extension walks you through connecting, previewing, and running the migration.
How does the one-time bridge work?
Migrator has your Lovable project deploy a tiny
migrate-helper edge function, gated by a single-use access key. Inside Supabase, that function can read the project's SUPABASE_DB_URL and SUPABASE_SERVICE_ROLE_KEY — native env vars — which is what lets the engine run a standard pg_dump/psql migration. Remove it as soon as you're done.
Get Migrator
Own your backend in a few clicks.
Add the extension, connect your Supabase, activate your license key, and migrate — schema, data, users with passwords, storage, and functions. Your Lovable Cloud stays live the whole time.
Keys are issued directly while online payments are being set up. Redeem LVB-XXXX-XXXX-XXXX inside the extension.