How do you migrate Lovable Cloud to your own Supabase?

Step by step

1. 1

   Create the destination project

   Dashboard → Supabase → New: order a dedicated Supabase pack and create a project. It comes with Postgres, Auth, Storage, Realtime and Studio, generated keys and a URL with HTTPS. Keep the project's Overview open; the Restore tab and the "Connect to your frontend site" block are there.

2. 2

   Back up Lovable Cloud from your own computer

   Run the backup tool. It signs in to Lovable in your browser, keeps the token on your machine, and saves everything to Downloads/Hostwares/<project name>/: a backup-*.json with the database and users, a storage/ folder with the files, and a migrations/ folder. To copy files from private buckets it briefly makes them readable and locks them again when the copy ends.

   macOS / Linux

   curl -fsSL https://migrate-lovable.hostwares.com/install.sh | bash

   Windows (PowerShell)

   irm https://migrate-lovable.hostwares.com/install.ps1 | iex

3. 3

   1. Database: structure, logic and rows

   The backup holds every table, column, relation and enum from the migrations, every database function, access rule, trigger and view copied from the live project (including ones created outside migrations), and every row. Zip the whole folder and upload it in the project's Restore tab. A .json on its own restores the database and users but no file bytes.

   The Restore tab takes uploads up to 200 MB. A larger backup is restored for you through a support ticket. By hand, this step is a CSV export per table and a re-import that loses functions and rules.

4. 4

   2. Storage files

   Images, PDFs and other uploads from public and private buckets are in storage/ with their folders and file types, and the zip restore puts them back under the same paths. URLs your rows store as strings still point at the old host; one SQL update after the restore fixes them.

   Rewrite stored file URLs

   update public.posts set image_url = replace(image_url, 'https://<old-host>', 'https://<new-host>');

5. 5

   3. Auth users and settings

   Users are restored with their password hashes, so they sign in as before; no reset emails. What the backup cannot carry is Auth configuration: set Site URL and Redirect URLs to the new frontend address, re-enable the OAuth providers you used with their client IDs and secrets, and check the email templates.

6. 6

   4. Secrets, then the frontend

   Keys you typed into Lovable (payment, email, AI providers) are not exported by anything. Add server-side ones to the Supabase project's function secrets and browser-side ones on the site's Environment tab. Then deploy the frontend from the GitHub repository (Dashboard → Deployments → New), paste the VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY and VITE_SUPABASE_PUBLISHABLE_KEY values from the Overview block, and redeploy. Sign in with an existing account and open a page that shows uploaded files.

   Edge functions are deployed code, not data: redeploy them to the new project from the supabase/functions folder in the repository, and rewire any Lovable-only AI feature.

Questions