---
title: "Migrate Lovable Cloud to Supabase: 9-step checklist | Zeroic"
description: "Migrate Lovable Cloud to Supabase without losing users: what the export carries, what you move by hand, and the cutover order that avoids lost writes."
url: https://zeroic.in/blog/migrate-lovable-cloud-supabase
---

[The Zeroic Journal](https://zeroic.in/blog)

[No-code](https://zeroic.in/blog/topic/no-code) October 27, 2026 6 min read

# Migrate Lovable Cloud to Supabase: a nine-step checklist

Lovable's export carries your schema, buckets and password hashes but not your secrets or files. Here is the order that keeps your users signed up.

By Khushi Arora Partner @ Zeroic

On this page

1. [What Lovable’s export carries over](#what-lovables-export-carries-over)
2. [Migrate Lovable Cloud to Supabase in nine steps](#migrate-lovable-cloud-to-supabase-in-nine-steps)
3. [Check grants before the October 30 change](#check-grants-before-the-october-30-change)
4. [Credentials to rotate during the move](#credentials-to-rotate-during-the-move)
5. [What changes after you leave Cloud](#what-changes-after-you-leave-cloud)
6. [Which route fits your app](#which-route-fits-your-app)
7. [How WordUp’s Supabase app stays with its owners](#how-wordups-supabase-app-stays-with-its-owners)

On this page 7 sections

1. [What Lovable’s export carries over](#what-lovables-export-carries-over)
2. [Migrate Lovable Cloud to Supabase in nine steps](#migrate-lovable-cloud-to-supabase-in-nine-steps)
3. [Check grants before the October 30 change](#check-grants-before-the-october-30-change)
4. [Credentials to rotate during the move](#credentials-to-rotate-during-the-move)
5. [What changes after you leave Cloud](#what-changes-after-you-leave-cloud)
6. [Which route fits your app](#which-route-fits-your-app)
7. [How WordUp’s Supabase app stays with its owners](#how-wordups-supabase-app-stays-with-its-owners)

To migrate Lovable Cloud to Supabase, you move four things: the database, the storage files, the auth and function settings, and the secrets. Lovable’s export carries your schema, storage bucket rules and user password hashes, but not your secrets or live sessions. Plan one write freeze, because Lovable allows one full database export every 24 hours.

Two dated changes make this week a good time to do it carefully. Lovable switched Cloud database changes to Drizzle migration files on October 7, and Supabase applies its Data API grant change to every existing project on October 30. Both affect the order below.

## What Lovable’s export carries over

Lovable’s [hosting guide](https://docs.lovable.dev/tips-tricks/external-deployment-hosting) splits the move into what travels through SQL migrations and what you do yourself.

**Moves with the migration files:**

- Tables, columns, indexes, RLS policies, functions and triggers.
- Storage buckets and their access policies.

**Moves, but only if you export it:**

- Table data, through a full database export (a PostgreSQL custom-format `.backup` archive, not a SQL file).
- User accounts, with password hashes, inside that same export.
- Storage files, which you download and upload again.

**Does not move:**

- Secrets: “Secrets stored in Lovable are not part of the export.”
- Sessions: everyone signed in has to sign in again.
- Auth provider settings, such as Google or GitHub sign-in.
- App connectors and AI features, which keep running through Lovable until you replace them.

Lovable also says there is no automatic migration in either direction. Its [Supabase integration docs](https://docs.lovable.dev/integrations/supabase) describe the manual route as exporting the data, connecting the new backend and asking Lovable to rebuild the schema. The restore route below keeps your data and policies exactly as they are, so it is the one we would rehearse first.

## Migrate Lovable Cloud to Supabase in nine steps

1. **Sync your code.** Turn on Git sync or download the `.zip` (a paid plan feature). You want the repository in your own account before anything else.
2. **Create the destination.** Make a new Supabase project in your own organization, in the region closest to your users. Create it fresh: Lovable warns that two Lovable projects sharing one Supabase project overwrite each other’s secrets.
3. **Apply the schema.** Run the files in `drizzle/migrations/` in the order given by `meta/_journal.json`. Lovable’s docs say these files “do not run through `supabase db push`”, so apply them separately.
4. **Restore the data.** Request the full export under More, Database, Manage, Settings. Run `pg_restore --list` on it, then restore selected objects. The [pg_restore docs](https://www.postgresql.org/docs/current/app-pgrestore.html) cover `--use-list` for picking items and `--single-transaction` so a failed restore leaves nothing half-applied. Restoring the whole archive over an initialized Supabase database can conflict with existing objects, so test on a throwaway project first.
5. **Upload the storage files.** Supabase’s [restore guide](https://supabase.com/docs/guides/platform/migrating-within-supabase/dashboard-restore) notes that bucket and file metadata come back with the database, but the files themselves do not.
6. **Recreate auth and secrets.** Set up each sign-in provider, add the new project URL to every OAuth redirect list, and enter each secret again. Deploy Edge Functions from `supabase/functions/` with the Supabase CLI.
7. **Replace remaining Lovable calls.** Search the code for connectors, AI features and the old backend URL. Each one still runs through Lovable, and bills your Lovable credits, until you swap in your own provider account.
8. **Freeze writes and copy the delta.** Records written after your export are not in it. Pause user writes, scheduled jobs and webhooks, take the final export, copy changed storage files, restore, then switch traffic.
9. **Retire the old backend last.** Keep it for a week of live traffic. Removal is permanent, so verify first.

## Check grants before the October 30 change

On April 28, Supabase announced that new tables in the `public` schema stop being exposed to the Data API automatically. The [changelog](https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically) says the setting reaches all existing projects on October 30, 2026, and that existing tables keep their current grants.

That matters for your migration because your new project is a new set of tables. If a table lacks a grant, PostgREST returns error `42501` (permission denied for table), and your app looks broken even though the data is there. Supabase says migrations that create `public` tables should include the `GRANT` statements next to the RLS and policy statements.

Its notice doesn’t address restored projects, so test instead of assuming. After the restore, call every table through the Data API as an anonymous visitor and as a signed-in user. Also watch `pg_restore --no-privileges`: it skips GRANT and REVOKE statements entirely. Our [Lovable security checklist](https://zeroic.in/blog/lovable-app-security-issues) covers the RLS side of the same check.

## Credentials to rotate during the move

The move is the cheapest time to rotate, because you are re-entering secrets anyway.

- **Database password:** the new project has its own. Never reuse the old one.
- **Third-party keys:** Stripe, email, SMS and AI provider keys that lived in Lovable secrets. Issue new ones and revoke the old ones after cutover.
- **OAuth client secrets:** if you created the OAuth app yourself, update its redirect URLs and rotate the secret.
- **Keys committed to the repository:** search the Git history before you make the repository public to anyone new.

## What changes after you leave Cloud

Lovable’s docs list built-in features that stop applying once a project runs on your own Supabase: the Database, Users and Storage views, managed backups, pausing and resizing, and Lovable Auth emails. You take on backups, upgrades and monitoring. Supabase’s plan, not Lovable credits, pays for the database from then on.

In return you get a database you can reach with any tool, and a migration history in your repository. Lovable’s own [changelog](https://docs.lovable.dev/changelog) says Cloud now refuses changes that could break a published app, such as dropping a column, unless you enable backward-incompatible migrations. On your own Supabase you decide that rule.

## Which route fits your app

Your situationRoute

Prototype, a few test users, no paying customersLet Lovable rebuild the schema on a new Supabase project and re-enter the data

Paying users, one database, no Edge FunctionsRestore from the export, rehearse once, cut over

Stripe, AI features or many Edge FunctionsRestore route plus a connector inventory before you freeze writes

Writes that cannot pauseIncremental copy with your own database tool, which is a project of its own

App slow or expensive on Cloud, but schema is messyFix the schema first, then move; see [why Lovable apps slow down](https://zeroic.in/blog/lovable-app-scaling-problems)

## How WordUp’s Supabase app stays with its owners

We built WordUp Tutoring’s learning app on Next.js and Supabase as one fixed-scope build, and the team has kept building with us on a retainer since. The principle behind that engagement is the same one behind this checklist: the client owns 100% of the code, infrastructure, docs and credentials. Read the [WordUp Tutoring case study](https://zeroic.in/wordup-tutoring) for how that engagement ran.

If your app is stuck inside a builder, our [Code Rescue service](https://zeroic.in/services/code-rescue) and the wider [migrations hub](https://zeroic.in/migrations) cover the other moves we do, and [the Bubble to Supabase guide](https://zeroic.in/blog/migrate-bubble-app-supabase) shows the same export-then-rehearse pattern on another platform.

For a Lovable app, [our Lovable and Bolt migration service](https://zeroic.in/lovable-and-bolt-migration) covers the full move: repository, hosting, database and cutover.

## Frequently asked questions

**Can I move my Lovable Cloud app to my own Supabase project?**

Yes, but it is not a one-click switch. Lovable's docs name managed Supabase and self-hosted Supabase as supported destinations, and the move is an export and restore: schema from migration files, data from a database export, storage files downloaded and re-uploaded. Auth providers, secrets and Edge Functions are set up again on the new project.

**Do my users keep their passwords after the move?**

Yes. Lovable's docs say user accounts are included in the database export with their password hashes, so users keep their passwords when you restore into a Supabase project. Sessions do not carry over, because the new project signs them with its own keys, so everyone who is signed in has to sign in again.

**Does the Lovable export include secrets and Edge Function code?**

Edge Function code is in your repository under supabase/functions and deploys with the Supabase CLI. Secrets are not exported: Lovable's docs say secrets stored in Lovable are not part of the export. You create each API key and token again on the new project, which is also a good moment to rotate them.

**How long does a Lovable Cloud migration take?**

Lovable doesn't publish a duration, and it depends on database size, storage volume and how many Lovable services the app still calls. The docs tie the length of your write pause to how long the export and restore take on a rehearsal run. Do that rehearsal first, then schedule the final cutover around the measured time.

**What happens if I delete the Lovable database too early?**

Removal is permanent. Lovable's docs say removing the database deletes the backend, including exports saved to its storage, and your users' accounts and files go with it. Download and verify the export and the storage files first, restore them into the new project, and only remove the old database after the new app has run on live traffic.

## References

1. [Lovable - Deploying and hosting outside Lovable](https://docs.lovable.dev/tips-tricks/external-deployment-hosting)
2. [Lovable - Self-hosting](https://docs.lovable.dev/tips-tricks/self-hosting)
3. [Lovable - Connect your own Supabase project](https://docs.lovable.dev/integrations/supabase)
4. [Lovable - Cloud](https://docs.lovable.dev/integrations/cloud)
5. [Lovable - Changelog](https://docs.lovable.dev/changelog)
6. [Supabase - Breaking change: tables not exposed to the Data API automatically](https://supabase.com/changelog/45329-breaking-change-tables-not-exposed-to-data-and-graphql-api-automatically)
7. [Supabase - Restore a dashboard backup](https://supabase.com/docs/guides/platform/migrating-within-supabase/dashboard-restore)
8. [PostgreSQL - pg_restore](https://www.postgresql.org/docs/current/app-pgrestore.html)

#lovable#supabase#migration#lovable-cloud#ownership

More from the journal

[ No-code

## [Supabase permission denied for table on new tables](https://zeroic.in/blog/supabase-permission-denied-table)

Supabase stopped granting API access to new tables on October 30. Here's why your AI builder's new feature broke, the fix, and the rule that keeps it fixed.

Khushi Arora Nov 16, 2026 · 7 min read

[ No-code

## [How to migrate Bubble app to Supabase without password resets](https://zeroic.in/blog/migrate-bubble-app-supabase)

A step-by-step Bubble exit for the data layer: exports, Postgres tables, row level security, files, and moving every user without a reset email.

Khushi Arora Oct 9, 2026 · 9 min read

[ Software engineering

## [Hiring a developer to fix Lovable app bugs: what to ask first](https://zeroic.in/blog/developer-fix-lovable-app)

Run Lovable's own scans, prepare five things for day one, and know which answers in a quote mean you should keep looking.

Khushi Arora Oct 30, 2026 · 7 min read

## Hear from Khushi within 24 hours.

**Khushi Arora** Partner @ Zeroic

Want a second pair of eyes on your cutover plan? Send us your database size, user count and the Lovable services your app still calls. A senior engineer will tell you what to rehearse first.

[See Lovable migration](https://zeroic.in/lovable-and-bolt-migration), or [book a 30-minute call](https://zeroic.in/book)

Pages [Services](https://zeroic.in/services) [Work](https://zeroic.in/work) [Blog](https://zeroic.in/blog) [About](https://zeroic.in/about) [Guide for AI](https://zeroic.in/llms.txt)

Services [Audits](https://zeroic.in/services/ai-audit) [MVP Sprint](https://zeroic.in/services/mvp-development) [Retainer](https://zeroic.in/services/senior-developers) [Code Rescue](https://zeroic.in/services/code-rescue) [AI development](https://zeroic.in/ai-development-company) [Fractional CTO](https://zeroic.in/fractional-cto-services)

Solutions [Fix AI-built apps](https://zeroic.in/code-rescue-by-tool) [AI services](https://zeroic.in/ai-services) [Migrations](https://zeroic.in/migrations) [Bubble to code](https://zeroic.in/bubble-to-code) [Build an app like](https://zeroic.in/build-an-app-like)

Industries [Marketplaces](https://zeroic.in/marketplace-app-development) [B2B SaaS](https://zeroic.in/saas-mvp-development) [FinTech](https://zeroic.in/fintech-app-development) [Telehealth](https://zeroic.in/telehealth-app-development) [EdTech](https://zeroic.in/edtech-app-development) [All industries →](https://zeroic.in/industries)

Developers [Bubble](https://zeroic.in/hire-bubble-developers) [React](https://zeroic.in/hire-react-developers) [Python](https://zeroic.in/hire-python-developers) [AI & LLMs](https://zeroic.in/hire-ai-developers) [API integrations](https://zeroic.in/api-integration-services) [All developers →](https://zeroic.in/developers)

Contact [Email](mailto:zeroic.in@gmail.com) [WhatsApp](https://wa.me/919873927225) [LinkedIn](https://www.linkedin.com/company/zeroic/) [X (Twitter)](https://x.com/PrashantAbbi) [Book a call](https://zeroic.in/book)

© 2026 Zeroic [Privacy](https://zeroic.in/privacy) [Terms](https://zeroic.in/terms)

Built in India · Shipping globally

SINCE
