Your codebase. Your database. Your hosting. Basic migrations $199
MIGRATE FROM LOVABLE

Lovable has an exit.
It’s more than a Git push.

Coming soon. We’re launching with Base44 migrations first. Contact us and we’ll let you know when Lovable migrations open.

Lovable says you own what you create and documents how to move it. But code, database, files, functions, sign-in and AI calls all move separately. We handle the pieces and the cutover, so nothing gets left running on the old platform.

Coming soonWE’RE STARTING WITH BASE44
Contact usTO HEAR WHEN LOVABLE OPENS
WHAT MOVES

What exports,
and what stays behind.

Git sync is on every Lovable plan, and a one-time ZIP download is on paid plans. Neither includes database records or uploaded files.

Usually moves

DOCUMENTED PATH
  • Source code, through Git sync or a ZIP download
  • Your schema, from the project’s migration files
  • Database records, through a requested export file
  • User passwords, because the password hashes are in that export

Needs separate work

NOT AUTOMATIC
  • Storage files, downloaded and uploaded to matching buckets
  • Edge and server functions, plus secrets and scheduled jobs
  • Sign-in providers and OAuth redirect URLs
  • App connectors and AI features, which run through Lovable until replaced
THE LOVABLE CATCH

Three things that
trip up a move.

Lovable’s guide is clear about most of these. They just take planning, especially for an app people are using right now.

The backend destination is limited

Lovable’s supported destinations are managed or self-hosted Supabase. It doesn’t support moving to plain PostgreSQL, and other backends need changes to your integration code. That shapes which hosts make sense.

Newer apps need a server host

Apps created from May 13, 2026 use TanStack Start, which runs server code. Older React and Vite apps build to static files. We check which yours is before you commit to a host.

The cutover has timing traps

Exports can be requested about once every 24 hours and miss anything written afterwards. Scheduled jobs can run twice if both backends stay live. Writes need a planned pause and a final export.

THE PATH

How a Lovable
move usually runs.

This is how we expect a move to run once we support this platform. Your current app keeps running until the new one is proven.

01

Connect the code and take inventory

We work from a repository you control and list the functions, jobs, connectors, secrets and AI calls your app relies on.

02

Build the new backend

Schema, records and files go to the new project, followed by functions, secrets and sign-in providers.

03

Test on a separate deployment

A second deployment points at the new backend, and we verify sign-in, reads and writes, uploads, functions and scheduled jobs.

04

Cut over in a planned window

Writes pause, a final export and restore run, and your domain moves. Signed-in users need to sign in again, because active sessions don’t carry over.

LOVABLE QUESTIONS

Before you
decide.

Ask a question
If Lovable documents the move, why hire someone?

You may not need to. If you’re comfortable with database restores, deploying functions and running a cutover, Lovable’s guide is a good place to start. We’re for owners who would rather hand that work over and get a tested result.

Will my users have to reset their passwords?

Lovable says users keep their passwords, because the hashes are in the export. They will have to sign in again, since active sessions don’t carry over. Sign-in providers also need setting up again at the destination.

What happens to my AI features?

Model calls run through Lovable’s AI gateway, so after the move they need your own account with an AI provider. Those usage costs are then billed to you directly.

Who looks after the backend afterwards?

You do, or whoever you appoint. Lovable points out that once you take on the backend, availability, backups, security and monitoring become your responsibility. We’ll be plain about that before you decide. See what you get at handoff.

When can you move Lovable apps?

We’re launching with Base44 first. Contact us and we’ll let you know when Lovable migrations open, along with pricing.

SOURCES

Vendor documentation checked November 2026. Plans and export paths can change, and every app gets its own review. AppExit is not affiliated with Lovable. Brand names belong to their owners.

START HERE

Lovable migrations
are coming soon.

We’re launching with Base44. Tell us about your Lovable app and we’ll let you know as soon as we can move it.

Contact us We’ll reply by email