Back

How to Disconnect from Lovable Cloud

No disconnect button? Here's the workaround that actually works.

Category

Migration

Date

December 26, 2025

Reading time

3 min

Views

105

Share

📌Before you start

Update (May 2026): Lovable Cloud still can't be disconnected, but the process to move to your own Supabase is now much easier. The Lovable MCP gives you full SQL access to export everything - including auth users with original passwords. See the 2026 Migration Guide for the updated process.

The Problem

You enabled Lovable Cloud, but now you want to use your own Supabase project instead. You look for a disconnect button... and there isn't one.

This is a known limitation. Once Lovable Cloud is enabled, there's no official way to disconnect it from that project.

The Workaround

This solution works by creating a fresh project that imports your code but lets you choose a different backend.

What You'll Need

  • Your Lovable project connected to GitHub
  • A Supabase project ready (if you want your own backend)
  • ~10 minutes

Step 1: Make Sure GitHub is Connected

If your project isn't on GitHub yet:

  1. Go to your Lovable project settings
  2. Connect to GitHub
  3. Wait for the initial push to complete

Step 2: Create a New Blank Project in Lovable

  1. Go to Lovable dashboard
  2. Create a completely new, empty project
  3. Don't add anything to it yet

Step 3: Import from GitHub

In your new blank project:

  1. Go to settings
  2. Choose "Import from GitHub"
  3. Select the repository from Step 1

Step 4: Choose Your Backend

Here's the key moment — when Lovable asks about Supabase:

  • Select your own Supabase project instead of Lovable Cloud
  • Or choose no Supabase if you want to start fresh
⚠ī¸Heads up

Important: If you accidentally click "Enable Cloud" at this step, you'll be locked into Lovable Cloud again with no way to undo. Be very careful here.

Step 5: Publish

Deploy your new project. You now have your complete app running without Lovable Cloud.

Important: What About Your Data?

⚠ī¸Heads up

Warning: This workaround gives you a fresh backend. Your existing data from Lovable Cloud won't automatically transfer.

If you need the data:

  • Export it before starting (contact support@lovable.dev)
  • Use the Lovable AI to query and display data, then manually save it
  • For complex data, this might require more planning

If you're okay starting fresh:

  • This is actually the cleanest approach
  • No legacy data issues
  • Perfect for switching to production with a clean slate

Why This Works

ℹī¸Note

Note: The trick is that the GitHub repo contains your code, not your backend configuration. When you import into a new project, Lovable treats it as a fresh setup and asks which backend you want.

Related

If you're planning to migrate your data too, check out the full Migration Guide with community resources and step-by-step instructions.

*Thanks to the Lovable community for discovering and sharing this workaround.*

Related skill: Lovable Cloud Migration — the complete migration workflow for your AI agent.

Quick fix — paste into your AI tool

Help me disconnect from Lovable Cloud and switch to my own Supabase:

1. Connect my current project to GitHub
2. Create a new blank Lovable project
3. Import my code from the GitHub repo
4. Connect to my own Supabase project (not Lovable Cloud)

Guide me through each step.

Works with Lovable, Cursor, Claude Code, ChatGPT, Windsurf, and more

Enjoyed this?

Carol Ships: building, shipping, figuring it out.

Have another workaround to share?

Start the thread below!

Comments

No comments yet. Be the first to share your thoughts!

Recommended Notes

Migrate from Lovable Cloud Using Claude Code

15 min read

Export Your Lovable Cloud Data (Using Claude Code)

4 min read

Migrating from Lovable Cloud to Your Own Supabase

14 min read

Back to Field Notes