Migrate from Lovable Cloud Using claude.ai Chat

Update (July 2026): Lovable Cloud now has official Export, Pause and Remove buttons, and the recommended flow changed. The skill is now v2 and ends with the official same-project switch: verify, remove Cloud, connect your own Supabase to the same project. For the full picture start with the new Migrate from Lovable Cloud with AI guide, it covers the current claude.ai route (connectors + ready prompts) and the Claude Code route side by side. The full walkthrough with screenshots has every dashboard step.

This is one of my favorite ways to migrate from Lovable Cloud.

I've written about this before - there's the original step-by-step guide, the Claude Code export method, and the full MCP migration guide. Those guides predate the official Export and Remove buttons, so treat them as reference - if you're starting a migration today, begin with the updated flow linked in the note above.

But this one is different. This is a skill that runs directly from claude.ai chat - the regular Claude you already use. No CLI, no terminal, no GitHub setup. Connect the Lovable MCP and the Supabase MCP, tell it what you want, and it handles schema, data, auth users (with passwords), storage, and edge functions.

One thing to know: since v2 (July 2026), the frontend never moves. The skill migrates the backend, verifies everything before anything is removed, and then walks you through the official switch: remove Lovable Cloud and connect your new Supabase to the same Lovable project - same code, same repo, same URL. Duplicating the project and pushing code separately is now just the fallback for when you need to keep the original Cloud project untouched.

---

Which skill, which tool

Where you are	What to use
claude.ai chat	The Migrate with AI guide (current flow), or this skill (v2, ends with the same-project switch)
Claude Code (CLI or web)	The Code version (full migration including frontend)
No AI tools	The step-by-step guide still works

---

What you need

Both MCPs connected in claude.ai chat. If you haven't set them up yet, follow the MCP setup guide - it covers both claude.ai chat and Claude Code CLI.

• Lovable MCP - added as a custom connector
• Supabase MCP - already in the connector directory, just click Configure

That's it.

---

How it works

The skill runs through these phases:

Phase	What happens
Scan source	Reads your Lovable Cloud database structure
Create destination	New Supabase project via MCP
Schema	Tables, enums, RLS, functions, triggers, sequences, indexes
Auth	Users AND identities with original bcrypt hashes
Data	Every row using a token-efficient SQL pattern
Storage	Files via temporary edge function
Edge functions	Deployed with correct settings per function
Verify	Audit comparing source vs destination, before anything is removed
The switch	You remove Lovable Cloud and connect your own Supabase to the same project (guided)

The frontend never leaves its project - the switch keeps your code and repo exactly as they are.

---

Things to keep in mind

While building this version, I ran into things that cause silent failures during migration. A few to watch for:

• Lovable changed its default tech stack to TanStack Start on May 6, 2026. If you're migrating an older project, you need to specify tech_stack: "classic" when creating the new project or the build will fail.
• Custom database functions like handle_new_user are not part of the table schema. If they don't get migrated, new user signups will work but the profile won't be created.
• auth.identities needs to be migrated alongside auth.users. Without it, login works but password recovery and session refresh break.
• Sequences need their current last_value. Otherwise you get duplicate order numbers or colliding IDs.
• Each edge function has its own verify_jwt setting in supabase/config.toml. Deploying them all with the same setting breaks webhooks or opens security holes.

There are more - all documented in the traps file on GitHub.

---

Get the skill

Install:

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

GitHub: CarolMonroe22/lovable-cloud-to-supabase-migration-chat

Or just start a chat: Open claude.ai, connect both MCPs, and say "I want to migrate my Lovable Cloud project to my own Supabase."

---

Resources

• Migration skill for Claude Code (full migration including frontend)
• Migration skill for claude.ai chat (v2, same-project switch)
• Full MCP migration guide
• Step-by-step migration guide
• Lovable MCP docs
• Supabase MCP docs