Lovable migration guides: export, move and own your code
Download your Lovable code, move it between GitHub repos, and migrate from Lovable Cloud to your own Supabase project without losing data.
Start here
Getting your code out of Lovable: the full guide
A Lovable migration is really three migrations: frontend, backend, hosting. What each export path moves, which one-way doors break sync, and the safe order.
Read the guide7 more guides
-
Lovable Cloud vs your own Supabase: how to choose
Lovable Cloud vs Supabase is close to a one-way door. The documented tradeoffs, the credit pool that bills your hosting, and what switching later really costs.
-
How to download your code from Lovable
Two routes to download Lovable code (a ZIP from the code editor and Git sync) the plan gate on both, and the backend pieces neither one exports.
-
Migrating from Lovable Cloud to your own Supabase
There is no one-click Lovable Cloud to Supabase migration. The honest manual runbook: export, schema, RLS, edge functions, storage, secrets, auth and rollback.
-
Lovable GitHub sync: how it really works
Lovable GitHub sync is two-way but only one branch at a time, and it can never import an existing repo. Every rule, limit and failure mode.
-
Moving a Lovable project to a different repo
Transferring the repo breaks Lovable sync. Move Lovable project to another repo or GitHub org safely: what breaks, what you lose, and when support has to re-attach it.
-
Running an exported Lovable app on your machine
Blank white screen after export? Run Lovable app locally without the guesswork: pick the right Node, fix the missing env vars, and handle the backend that stayed behind.
-
Self-hosting a Lovable app, and what you lose
How to self host Lovable app code on Vercel, Cloudflare Pages or Netlify: build settings, SPA rewrites, and the crawler pre-rendering you leave behind.