Lovable Cloud to Supabase Migration FAQ
Quick answers about safety, cost, time and what happens to your data.
Your questions answered
Is it safe to migrate Lovable Cloud to Supabase with this tool?
Yes. You sign in with Supabase's official OAuth screen and GitHub access is read-only. Credentials are used in memory during a request and are never stored or logged. The tool only writes to your new project and never changes Lovable Cloud, so your original data stays intact.
How long does a Lovable Cloud to Supabase migration take?
Most projects finish in 20 to 40 minutes including creating the Supabase project. Large tables take longer because rows are inserted in batches of 500.
Can I lose data during the migration?
The migration only copies data into a new project. Lovable Cloud is never modified, so nothing is deleted and you can repeat the process. Keep your CSV exports as a backup anyway.
How much does it cost?
The migrator is free. Supabase has a free tier, and larger projects may need a paid plan. See supabase.com/pricing for current limits.
Will my users keep their passwords?
Yes for email and password accounts. User ids and bcrypt password hashes are copied exactly, so existing logins keep working. Social logins like Google must be re-enabled in your Supabase dashboard.
Do I need to know how to code?
No. The wizard guides you step by step. You only copy and paste a couple of SQL queries and drop files into the page.
What about edge functions and secrets?
Code is deployed with the Supabase CLI. The tool lists your functions, the secret names they use and the exact commands. Secret values are never exported, so you re-enter them.
What if my Lovable project has no supabase/migrations folder?
The tool includes a SQL query that rebuilds your schema from the live database. It is a best-effort rebuild, so review the result before running it.
Can I move back to Lovable Cloud later?
Your Lovable project still points to its original backend until you change the environment variables, so you can switch back by restoring the old values.
How much does Lovable Cloud cost?
Lovable Cloud is billed by usage on top of your Lovable plan, so the cost depends on database size, storage, bandwidth and function calls. Our Lovable Cloud pricing guide explains what drives the cost and how to estimate it.
Can I self-host a Lovable app?
Yes. Export the code through GitHub, build it, host the static files anywhere and point it at your own Supabase project. See how to self-host a Lovable app.
How do I export my project from Lovable?
Sync it to GitHub for the code, export each table as CSV, export users with a SQL query and download your storage files. The export guide combines all four.
Does Supabase have vendor lock-in?
Less than most backend platforms: it is built on open-source Postgres and can be self-hosted, and your data exports in standard formats. See the portability section of our comparison.
Does Lovable offer a migration service?
Check the official Lovable documentation for what Lovable itself offers. This site is an independent free tool, and a done-for-you migration service is on the waitlist.
Can someone migrate my Lovable prototype to a real backend for me?
You can do it yourself in about 20 to 40 minutes with the free tool. If you would rather have it done for you, join the done-for-you waitlist.
Is this affiliated with Lovable or Supabase?
No. This is an independent community tool. Lovable and Supabase are trademarks of their respective owners.
More detail: the complete guide, troubleshooting and Lovable Cloud vs Supabase.