Proudly supported byPanelAlphaPanelAlpha
Join us on DiscordStart Migration

Move from Lovable: step-by-step migration guides

Leaving Lovable doesn't mean starting over. Choose where to go next and we'll walk you through every step.

Claude Code, Codex or Cursor?

Claude Code

A coding agent from Anthropic.

Runs inClaude app or terminal
AccountClaude plan or API credits
PriceA Claude plan, Pro $20 a month or $17 billed yearly, or API credits. No free plan
Project notesCLAUDE.md
Should you leave Lovable for Claude Code?

Codex

A coding agent from OpenAI.

Runs inCodex app or terminal
AccountChatGPT plan or API key
PriceIncluded in every ChatGPT plan, also the free one. Plus is $20 a month. Or an OpenAI API key
Project notesAGENTS.md
Lovable vs Codex

Cursor

A code editor with an AI agent.

Runs inCursor app
AccountCursor account
PriceFree plan. Plus is $8 a month for Grok models only. Claude, GPT and other models cost extra, by usage
Project notesAGENTS.md
Lovable vs Cursor

What happens to your app when you leave Lovable?

Your code is yours. But your app is more than just code. Some things move with you, others need extra work.

What you can keep

  • Your app's code. React, Tailwind and shadcn/ui, on Vite or TanStack Start.
  • Your GitHub repository. The code Lovable pushed is yours.
  • Database migrations and Edge Functions saved in your repo.
  • Images and other files in the public folder.
  • Your custom domain. You'll just need to point it to the new host.

What doesn't move automatically

  • Your database. It stays on Supabase, or in Lovable Cloud if Lovable set it up. A Lovable Cloud database has to move if you leave Lovable.
  • User logins. They're managed by Supabase Auth, not your code.
  • API keys and secrets. You'll need to set them again.
  • Your lovable.app address. That stays with Lovable.
  • Lovable editor and chat history. These don't come with your code.

Our guides walk you through four stages

Your setup

Answer a few questions to get steps tailored to your app.

Preparation

Set up the accounts and tools needed for migration.

Migration

Follow the instructions and check the result of each step.

Final check

Test everything before switching. Your old Lovable app stays online until you're ready.

Before you start, whatever your destination

  • Export the database first

    Make a backup of the database with the Supabase CLI. Do this before you change anything. It is the one part you cannot rebuild from code. If the app runs on Lovable Cloud, you have no Supabase project: use Export data in Lovable instead. The backup guide shows both.

    Back up the database of a Lovable app

  • Make a copy of the project

    Connect GitHub and push, or download the code. You want a version you can go back to.

  • Write down every key and setting

    Supabase URL and publishable key, any third-party API keys, environment variables. The new place needs all of them.

  • Check who controls the domain

    If the domain is connected to Lovable, find the registrar login. You will change DNS at the end.

Additional resources for your Lovable migration

All guides

Comparisons, exports and the parts that break most often. Each article links back to the step-by-step route it belongs to.

Your app, without the Lovable label
AI buildersOct 29, 2026 · 3 min read
Remove the Edit with Lovable badgeHide it on Lovable hosting, and the Lovable title, preview and icon your code keeps.
What Lovable costs, before and after
AI buildersOct 27, 2026 · 3 min read
Lovable pricingFree, Pro and Business, what running your app costs and your bill after you move.
A remote control, not a way out
AI buildersOct 26, 2026 · 3 min read
Lovable MCP serverDrive Lovable from Claude Code, Codex or Cursor, and what it does for a move.

More Lovable guides

Every article about moving from Lovable in one list.

See all guides

Ready to leave Lovable?

Pick a destination above. Answer a few questions and follow your plan step by step.

Start Migration