Lovable
Keeps: Its Supabase database, when the project is in your own Supabase account: the app keeps using it, and nothing new is created. On Lovable Cloud, the data moves to a project of yours, users and passwords included.
Watch for: Older projects need a small vercel.json, or pages like /dashboard 404. Newer ones are often built for Cloudflare Workers: Launchpad spots it and gives you the request to paste into Lovable so they run on Vercel.
Moving a Lovable app, step by step →
Bolt
Keeps: Your Supabase project, by setting its address and key, or a new one Launchpad creates.
Watch for: A .env exported into the repository puts your keys where anyone with access can read them, and an import written with the wrong capital letters works on a Mac and fails on the build server.
Moving a Bolt app, step by step →
v0
Keeps: Everything: it's Next.js. Launchpad points POSTGRES_URL at the new database, so @vercel/postgres works unchanged.
Watch for: @vercel/kv's variable names, AI routes anyone can call in a loop, and type errors the build is set to ignore.
Moving a v0 app, step by step →
Replit
Keeps: The server and pages, on your own server, and its database code as it is: both use DATABASE_URL. The data comes across with launchpad db restore.
Watch for: Sign-in with Replit accounts and Replit's own storage only work on Replit, so they change first. The server listens on port 5000 unless told otherwise.
Moving a Replit app, step by step →