Lovable Cloud to
your own Supabase.

Where to move it first (checked November 6, 2026): the backend goes to a Supabase project you own, because Lovable Cloud runs on the same open-source Supabase stack and the app code barely changes. The frontend can stay on Lovable's own publishing, so you keep building in Lovable; if you want it off Lovable too, Vercel, Netlify or Cloudflare host the same build. Who does the move depends on how much of the app you want moved. If you only need a copy of your data, Lovable's own Export project data (More, Database, Manage, Settings) is free and gives you the full database with your users. If you want the whole app running on a Supabase project you own, including storage files, edge functions, secrets, Google sign-in and the cutover, that is our fixed-price Lovable Cloud to Supabase migration: $150 for 1 to 5 tables, $350 for 6 to 15, $600 for 16 or more, usually 1 to 2 days, and you keep building in the same Lovable project. The same job is on Upwork at the same prices. If you want off Supabase too and onto your own server, see our Lovable app on your own server service ($500 setup).

We do, as a fixed-price service: $150 for 1 to 5 tables, $350 for 6 to 15 and $600 for 16 or more, usually done in 1 to 2 days. We move the database with your auth users (they keep their passwords), storage files, edge functions, secrets and Google sign-in to a Supabase project in your name, switch the app over in your quietest hour, and you keep building in Lovable. Supabase's own help article says there is no automated way to transfer a backend from Lovable Cloud to your own Supabase account (checked November 1, 2026), so the move is manual work either way.

Open the project in Lovable and click the Cloud icon in the top bar. If you see screens for Database tables and Users managed inside Lovable, the app is on Lovable Cloud: the project will not show up in your Supabase dashboard, and you have no service role key or database URL. If you see the Supabase logo, your Supabase project name and links to the Supabase dashboard, it already runs on your own project and there is nothing to migrate. This is how Supabase describes it in its help center (checked November 1, 2026).

Not one click, but there is an official export (checked October 14, 2026, docs.lovable.dev). Under More, Database, Manage, Settings (the menu moved there in October 2026), Export project data gives you the full database, structure and data, including your users and their password hashes, so they keep their passwords after a correct restore into Supabase. It does not include storage files, edge function code, secrets, sign-in provider settings or API keys, and users who are signed in at the switch have to sign in again. Limits: databases up to 15 GB, an export file of at most 5 GB, one export every 24 hours, and only while the backend is running, so a project paused for lack of credits has to be resumed first.

Yes. Lovable has an official export under More, Database, Manage, Settings, and afterwards the same Lovable project can be connected to a Supabase project you own. The export covers the database, including auth users. Storage files, stored file URLs, secrets, Google sign-in and the cutover need extra work, which is what we take care of.

No. Lovable's native Cloud Export includes auth users with their password hashes, so after a correct restore everyone signs in with the password they already have. Users who signed in with Google need your own Google OAuth client set up, which we do as part of the move.

It is the database part. It leaves out storage files, edge function code and secret values, and it does not fix file URLs saved with the old host, Google sign-in, the public role's access after a restore, or the published site still pointing at the old backend. Those are the steps that break apps, and they are the steps we handle.

The built-in export handles databases up to 15 GB of storage, and the export file itself stops at 5 GB. Mention the size when you book the call so we can plan the export path before anything is touched.

Yes. It is the same Lovable project, just connected to your own Supabase instead of Lovable Cloud. You keep prompting and shipping the way you do now.

The heavy lifting happens on the new project while your app keeps running. The switch itself is short, and we schedule it for your quietest hour.

On Lovable Cloud you do not get the Supabase dashboard, the service role key or the database URL, and you cannot pick your plan, region or storage limits. With your own project you see everything, choose the plan that fits, and pay Supabase directly. Supabase has a free tier and paid plans start at $25 a month.

Yes. Every Supabase project is a full Postgres database, and the database behind Lovable Cloud is Supabase Postgres too, so your tables, RLS policies, functions and triggers move as Postgres, with no conversion step. The difference is access: on your own project you get the connection string, so psql, pg_dump, Prisma, Drizzle or a BI tool can connect directly, which Lovable Cloud does not allow.

Since June 2026, Lovable Cloud is billed in credits from the same balance you use to build. Every plan gets a 20 credit monthly Cloud grant (marked temporary by Lovable). After that, database server time, database storage, file storage, network traffic, compute and realtime all draw from your general credits. A bigger instance size uses more credits per hour, and stored files keep costing credits while a project is paused.

The published site stays up, but AI features stop and the built-in backend pauses shortly after the balance reaches zero, so users cannot sign in or load data. Lovable says the data stays safe but cannot be accessed or exported until the services run again, and you may need to click Wake up after adding credits. On your own Supabase project, running out of Lovable credits only stops building.

A fixed price based only on the number of tables: $150 for 1 to 5 tables, $350 for 6 to 15 and $600 for 16 or more. Every plan moves everything: tables and data, RLS policies, functions and triggers, auth users, storage files, edge functions and secrets.

Usually 1 to 2 days from access to switch-over, including testing sign-in, data counts and the main user flows against the old backend. Very large databases or many edge functions can take longer, and we tell you before we start.

Editor access to your Lovable project and an invite to your Supabase organization. We have step-by-step guides for both.