How to Export Your Lovable Cloud Database

What an export of a Lovable Cloud database includes

• Schema: tables, columns, constraints, functions, triggers and RLS policies.
• Data: the rows in every table in the public schema.
• Auth users: ids, emails and password hashes from the auth schema.
• Storage files: uploaded files, covered in the storage guide.

Export the schema from GitHub

1. 1Connect your project to GitHub

   Use the GitHub option in your Lovable project settings. If you have not done this yet, follow how to sync your Lovable project to GitHub.

2. 2Open the migrations folder

   In the repository, open supabase/migrations. Each .sql file is one change, named with a timestamp such as 20250412093000_create_profiles.sql.

   

3. 3Download everything

   Choose Code → Download ZIP. Keep the folder structure; the order of the files is the order of the filenames.

Export your Lovable Cloud database tables as CSV

4. 4Open the database view

   In Lovable, open the Cloud area and the database view. You will see a list of tables.

   

5. 5Export each table

   Open a table and choose the CSV export. Repeat for every table. Name files after the table, like orders.csv.

6. 6Check the row counts

   Write down the row count of each table now. After the import you will compare these numbers.

Export your database when there is no migrations folder

Some projects keep their structure only in the running database. You can rebuild it with a query that reads Postgres's system catalogs and prints CREATE statements for enums, tables, constraints, functions, RLS settings, policies and triggers. The migrator tool contains a tested version of this query in its schema step.

Be aware of the limits: it is a best-effort rebuild, so review the output, and sequences (serial counters) are not recreated. Most Lovable tables use uuid ids with gen_random_uuid(), so this rarely matters.

Export auth users

Run the query below in Lovable Cloud's SQL editor and export the result as CSV. The full workflow is in Migrate Lovable Cloud users to Supabase.

select id, email, encrypted_password, email_confirmed_at,
       raw_user_meta_data, raw_app_meta_data, created_at
from auth.users
order by created_at;

Check that your export is complete

For background on Postgres exports, see the Supabase database docs.

• The number of CSV files equals the number of tables in your schema.
• Each CSV has a header row that matches the table's column names.
• Rows containing commas, quotes or line breaks are properly quoted. Open one file in a text editor to check.
• You have saved the users CSV separately.

Frequently asked questions

Related guides