A companion guide by Carol Monroe

Your app grew up

And that's a beautiful thing.

You started with an idea, built it on Lovable Cloud, and now it has real users. Whether you stay, go hybrid, or fully migrate to your own Supabase, this guide walks you through every path.

What's new on Lovable See your paths

Before you migrate, look at what you have now

Lovable Cloud has changed a lot. Some of the reasons people used to migrate might not apply anymore. Here's what's new.

Test and Live Environments

Separate dev and production databases. Build in Test, publish to Live. Automatic backups before each publish.

Region Selection

Choose where your app runs: Americas, Europe, or Asia Pacific. Lower latency for your users.

Claude Sonnet 3.7

The latest AI model powers all builds. Better code generation, fewer errors, smarter decisions.

Cross-Project Referencing

Use @project-name to pull patterns and components from other projects in your workspace.

Custom Auth Emails

Send authentication emails from your own domain. Automatic DNS setup with SPF, DKIM, DMARC.

Browser Testing

AI tests your app in a real browser. Clicks buttons, fills forms, catches bugs visually.

Workspace Knowledge

Define shared rules and coding standards once. Applies to every project in your workspace.

Per-Project Usage

See exactly how each project consumes resources. Transparent breakdown of database, compute, and storage.

New Integrations

Twilio, Linear, Telegram, Perplexity, ElevenLabs, Firecrawl, Miro, and more via shared connectors.

When it's time to move

Not everyone needs to migrate. But if any of these feel familiar, it might be time to explore your options.

Every change feels risky because there's no dev/prod separation that fits your workflow
You need SQL access to debug, optimize, or run custom queries
You need auth providers or configurations not available in Cloud
You want custom email templates with your own branding
You need to give your team direct database access
Your costs are unpredictable and growing faster than your revenue
You need compliance, multi-region failover, or custom VPC access
You want to use your data with other tools (Claude Code, Cursor, custom scripts)

If none of these apply, Lovable Cloud might still be the best place for you. And that's totally fine.

Choose your path

There's no wrong answer here. Each path works for different stages and different needs.

Stay on Cloud

Optimize what you have

Lovable Cloud has grown a lot. Use the new features to get more control without leaving.

  • Enable Test/Live environments
  • Set up Workspace Knowledge
  • Use cross-project referencing
  • Monitor usage per project
  • Upgrade instance size as needed
Lovable Cloud docs
Most popular

Go Hybrid

Own your database, keep building in Lovable

Migrate your backend to your own Supabase but keep using Lovable for the frontend. Best of both worlds.

  • Full SQL access and monitoring
  • Any auth provider you need
  • Custom email templates
  • Keep building UI in Lovable
  • Deploy frontend to Vercel/Netlify
External deployment guide

Full Migration

Complete control, your infrastructure

Move everything to your own Supabase and deploy wherever you want. Full ownership, full responsibility.

  • Complete database control
  • CI/CD with GitHub Actions
  • Multi-environment workflows
  • Custom domain + hosting
  • Scale on your own terms
Migration skill for Claude Code

Tools and guides for the journey

The community has built incredible tools for this. You're not doing it alone.

Official Lovable Docs

Step-by-step backend migration using Supabase CLI, CSV export, and manual setup.

docs.lovable.dev
NEW

Dreamlit Exporter

Open source. Migrates data, users (no password resets!), and storage. Local CLI or hosted.

github.com/dreamlit-ai

Bobby's GitHub Import

New Lovable project + GitHub import + connect your own Supabase. Best for starting fresh.

lovable.dev/products/git-import

Carol's MCP Migration Guide

Full migration using Lovable MCP + Supabase MCP. Production-tested, automated, preserves passwords.

carolmonroe.com/blog

Migration Skill for Claude Code

Production-tested skill using Lovable MCP. Install with npx skills add and it automates the entire migration.

github.com/CarolMonroe22
NEW

Migration Skill for claude.ai Chat

Same migration from claude.ai chat, no CLI needed. Includes 16 documented traps from real-world testing.

github.com/CarolMonroe22

mr_pants99's Auth Migration

Supabase CLI + createUser() script for auth migration. Preserves user IDs and password hashes.

r/Supabase

After you migrate

A few things to check once everything is running on your own Supabase.

Run a security audit

Check RLS policies, function permissions, storage policies, and API exposure.

Test authentication flows

Sign up, log in, password reset, OAuth. Make sure everything works for your users.

Verify storage files

Check that images, documents, and uploads load correctly with the new URLs.

Update hardcoded project IDs

Search your codebase for old Supabase project IDs and replace with environment variables.

Set up monitoring

Enable Supabase dashboard alerts, check query performance, set up error tracking.

Rotate any shared credentials

If you used a migration tool that accessed your keys, rotate them now.

Need help with your migration?

I've helped dozens of people migrate from Lovable Cloud to their own Supabase. Whether it's a quick question or a full walkthrough, I'm here.

Find me on Discord Read more guides

@carolmonroe on Discord