Lovable Cloud To Supabase Migration

Lovable Cloud to Supabase Migration

[](https://github.com/CarolMonroe22/lovable-cloud-to-supabase-migration) [](https://github.com/CarolMonroe22/lovable-cloud-to-supabase-migration) [](./LICENSE)


Migrate your entire Lovable Cloud project to your own Supabase. Schema, data, auth users and identities, storage, edge functions with correct verify_jwt, cron jobs, and a verified switch of the SAME Lovable project to your own Supabase. Password resets are the official default; an advanced MCP route can preserve existing hashes when available and explicitly approved.

From	Lovable Cloud (managed backend)
To	Your own Supabase project (full dashboard, custom emails, service role key)
What moves	Schema, data, auth users and identities, storage, edge functions, cron jobs; passwords require reset by default or the optional MCP route
How	Official Export + Remove + Connect on your existing project (primary path), with the full MCP rebuild kept as fallback

Install

npx skills add CarolMonroe22/lovable-cloud-to-supabase-migration

Once installed, your AI agent picks it up automatically whenever you ask about migrating from, exporting, or removing Lovable Cloud.

v4.1.2 - Practical password guidance

The skill now focuses directly on the migration decision: use password resets by default, or choose the optional MCP route only when its capability and security checks pass.

v4.1.0 - Password export clarification

Lovable's current documentation says the official project export does not contain user passwords in a usable form, so the supported default is a password reset. That is different from the advanced MCP path: `query_database` can still acce