Lovable · GitHub and Supabase
Lovable can keep your data in a built-in backend (the data and sign-in service it runs for you) or in a Supabase project you own. Supabase is that same kind of service: rows, sign-in, and files. This page is the extract: a GitHub copy of the code, a packed database export, and the storage files — so Cloud is not the only home those things have.
30 min · senior team · leave with a clear next step
Our apps' revenue
$1,696,729
Partner savings
$308,650
Projects shipped
110+
In plain words
Leaving Lovable is a GitHub-and-Supabase job. Connect Git sync, or download the codebase on a paid plan. Export the database as a PostgreSQL archive — a packed copy a restore tool can load. That archive includes accounts and password hashes, the scrambled form of passwords. It leaves out storage files, secrets, and sign-in provider settings. Done means the app starts from your copy and people can sign in on the Supabase project you admin.
What a GitHub push misses
Git sync moves the files Lovable wrote. It does not move the built-in backend, the storage bucket, or the keys Lovable hid.
Lovable’s export can include accounts and password hashes. GitHub does not. If you only synced files, people will not get in on the Supabase side.
Lovable saves the export into project storage. If you remove the database first, the export and the files go with it.
Lovable says there is no automatic move between the built-in backend and a Supabase project you own. You export, connect, and rebuild the shape by hand.
The archive skips secrets, API keys, and provider settings. Those must be made again on the Supabase project you admin.
The Lovable order
Do the GitHub or download step first so you have the code. Then export the database and pull storage while Cloud is still running.
01
Git sync works on every plan. A direct download lives under Project settings → Git, or the code editor, on a paid plan.
02
Use More → Database → Manage → Settings. Start the export. Lovable emails you when the packed archive is ready in Storage.
03
Pictures and uploads are not inside the archive. Pull them from More → Storage before anyone removes Cloud.
04
The export is not a paste-into-SQL file. A developer loads it with a restore tool. Then remake secrets and provider settings. People who were signed in will need to sign in again.
How to
Files first, then the packed database, then storage. Success is sign-in on a Supabase project you admin.
Step 01
Connect GitHub so two-way sync keeps a copy. Or, on a paid plan, download the codebase from Project settings → Git.
Step 02
Open Database settings and start the export. Wait for the email. Download the archive from Storage.
Step 03
The archive skips uploads. Download those files while the project still has Cloud.
Step 04
Use a restore tool that understands a PostgreSQL custom archive. Do not paste it into the SQL editor.
Step 05
Set API keys and providers on the new Supabase. Ask a known user to sign in. Lovable says they keep their password after a good restore.
Lovable pass or fail
Each line is a door you can try. Pass means that door works on a Supabase project you admin.
Pass: GitHub (or a paid-plan download) has the latest files.
Fail: the only copy still lives inside the Lovable project.
Pass: the packed database archive is saved somewhere you control.
Fail: you only have the GitHub repo and assume the rows are in it.
Pass: storage files are downloaded while Cloud is still running.
Fail: Cloud was removed and the export vanished with it.
Pass: users can sign in on the new host with the same Supabase auth.
Fail: they must make a new account because the user rows never left Lovable.
Pass: secrets and sign-in providers are set on the Supabase project you admin.
Fail: the app still reads keys that only exist inside Lovable.
Pass: the app starts from your copy with the Lovable project closed.
Fail: start still means opening Lovable.
Technical review: , CodeCross engineering
Read next
These pages are already on the site. Use them to pressure-test the bet before a call.
Get off Lovable
Stop running on Lovable Cloud after the GitHub copy and the archive are safe.
Lovable to production
Stay on Lovable if you only need a reliable sign-in, not a backend extract.
Production-ready checklist
Ship gates after the Supabase project is yours.
Book a discovery call
Bring the GitHub repo and the database export. We will say what Cloud still holds.
Verified on Clutch · 29 reviews
“What impressed us most about CodeCross was their ability to deeply understand our vision and translate it into a complete digital solution. Unlike many agencies that just focus on technical delivery, CodeCross approached our project like true partners.”
Harris Edelmam
CEO · Ombligo, Inc.
Read on Clutch“Their project management was top-notch.”
Greg Moreno Earle
Technology Executive · Driven Brands Inc.
Read on Clutch“Their eye for clean, modern design combined with technical excellence was very impressive.”
Robert Valentino
Founder · Lean Coach
Read on Clutch“We appreciated Codecross's practiced approach to development.”
Brice Wiley
Marketing Director · Lex Mundi
Read on Clutch“On the development side, everything has gone quite smoothly and perfectly.”
Brandon Patterson
Co-Owner · Cap Tech Services, LLC.
Read on Clutch“They are very thorough in their approach to the project.”
Lukas Haynes
Member Board of Directors · Protect Our Winters Action Fund
Read on ClutchWork with our team
Stay with the vibe-coding guides, or open booking and the Austin pages.
Continue
Index of Lovable intents.
Continue
Peel one layer while Cloud still answers, if this week is not the extract.
Continue
Wrap Cloud in place when leaving is the wrong job.
Continue
Show us the GitHub copy and the archive. We name the Supabase gaps.
Continue
If you want help taking the archive into Supabase.
Before you book
Prefer writing? Send project details and we reply within one business day.
No. Git sync copies project code to GitHub. User rows live in the built-in backend or in a Supabase project you connected. Use the database export for accounts and password hashes. Download storage files separately.
A packed PostgreSQL archive with structure and data, including accounts and password hashes. It does not include storage files, edge function code, secrets, sign-in provider settings, or API keys. Plan those as extra steps.
No. Lovable does not move a project between the built-in backend and your own Supabase in one step. Export the data, connect the new project, and rebuild the schema. Decide early which backend you want.
If you restore the export into a Supabase project, Lovable says users keep their passwords. Anyone signed in at switch time needs to sign in again. Test that door before you stop using Lovable Cloud.
Bring the GitHub repo (or the download), the database export, and how people sign in today. We will say what the archive missed before you remove Cloud.
Prefer writing? Send project details on the contact page.