By Turn on GitHub sync in Project settings and the code is in a repository you own, on every plan. The data is the hard part: if the app runs on Lovable Cloud there is no automatic transfer, so the database, files and secrets have to be exported and rebuilt in your own Supabase project.
Lovable's terms are clear on ownership. You own what you create, and the app can be hosted anywhere. Getting it out takes three separate moves: the code, the backend, and the hosting.
Step 1. Get the code. Open Project settings, Git, and connect GitHub. Lovable creates a new private repository under your account. It cannot link an existing one. Changes made in Lovable sync to GitHub, and changes pushed to the active branch sync back into Lovable, so you can keep editing in either place. Paid plans can also download a zip from the same screen.
Step 2. Find out which backend you have. Click the Cloud icon in the editor. If you see Lovable's own screens for tables and users, the app runs on Lovable Cloud. If you see the Supabase logo and a link to the Supabase dashboard, you own the backend already and step three is all that is left.
Step 3. Move the backend if it is Lovable Cloud. Supabase's own support page explains that a Lovable Cloud project is not owned by your Supabase account, does not appear in your dashboard, and cannot be disconnected or switched in place. There is no automated way to transfer it. The path is:
- Create a new Supabase project under your account.
- Export the database and import it into the new project. Lovable's self-hosting guide notes that moving only the database does not carry over sign-in, storage, realtime or Edge Functions. Those are recreated from the code and the migrations in your repository.
- Download the storage files and upload them to the new project's buckets.
- Recreate secrets and scheduled jobs. They are not exported.
- Point the app at the new project, update OAuth settings in Google or GitHub, and add your domain to the allowed redirect URLs. Sessions do not carry over, so users sign in again.
- Run the two-account test on the new project. Access rules travel with the schema, but confirm it.
Step 4. Host it. Older React apps build to static files and run on Netlify, Vercel, Cloudflare Pages or any static host, with a fallback rule so refreshes do not 404. Apps created from May 13, 2026 use TanStack Start and need a host that runs server code. Lovable's Publish button still publishes only to Lovable hosting, so your new host deploys from GitHub. Once the app no longer calls Lovable services, it runs without a subscription.
Money and time. Code only, with your own Supabase already in place, sits at the bottom of the $300–$25,000 band for moving off a builder, often a day. A full Lovable Cloud move with data, files, sign-in and payments sits in the middle and takes one to three weeks. See pricing.
Get help when the app has real users and you cannot afford a gap in sign-in, when payments or webhooks are involved, or when the export has tables you do not recognize. Lovable Cloud to Supabase covers the data move in detail.
Check these
The code lives in a Git repository you own
Connect GitHub or export the project. If the builder account is lost, the product should not be.
Database backups run automatically and a restore has been tested
Check what your database plan actually includes, then restore a backup into a test project once.
Secrets live in the host's environment settings
Keys belong in environment variables on the server, not in the repository or in front-end code.
Sign-up confirmation and password reset work end to end
Use a real inbox. Check that the link arrives, points to your live domain, and works once.
Top-rated companies for Lovable apps
Ranked by our score: published prices, scope of work, AI tools named, timing and a low-risk first step. How we score.
- 1Afterbuild Labs10.0/10Best for: A check before launchFree first step · from $49
- 2Redlab10.0/10Best for: A full rescue by one team that keeps buildingFree first step · from $490
- 3Vibe Code Rescue (Lev Arakelyan)9.0/10Best for: A one-off check and a cleanupFrom $299
Related questions
Can I keep using Lovable after I export?
Yes. GitHub sync works both ways, so you can host the front end elsewhere and still prompt in Lovable. If you move the backend too, AI features and connectors that ran through Lovable need replacing, and Lovable cannot debug a host it does not control.
Will my users have to sign up again after the move?
No, if you export the users table and auth data into the new project. They will have to sign in again, because sessions do not carry over. Password reset emails must point at the new project before you switch.
Sources: Lovable docs: GitHub integration; Lovable docs: Self-hosting; Lovable docs: Deploying and hosting outside Lovable; Supabase: Can't access Supabase project when using Lovable Cloud.