Lovable to your own hosting: the checklist

If your developer, or your AI builder, disappeared tonight, could you still run your app? Moving out of Lovable, Bolt or Replit into accounts in your own name is how you make the answer yes. This is the checklist we follow, in order.

First, five accounts that must be in your name

• Code: a GitHub organisation you own, not a personal account belonging to someone else.
• Domain: registered to you, with the login in your password manager.
• Hosting: the project in your own cloud account.
• Database: your own Supabase or Postgres project, with backups that live outside the platform.
• Payments: your own Stripe account, with webhook secrets you can rotate.

Then move in this order

• Push the code to a GitHub repository you own. Lovable's GitHub sync works on every plan (only its ZIP download is paid), and Bolt can export to GitHub or a ZIP.
• Take a full backup of the database and store it outside the platform.
• Move the data into your own database first, and check the row counts match.
• Deploy the app onto your own hosting against the new database, on a staging address.
• Set every secret in the new environment, then rotate the old ones.
• Point the payment webhooks and auth callbacks at the new address.
• Test sign-up and one real payment end to end, then switch the domain.

Why the order matters

Moving the app before the data is how records get lost: users keep writing to the old database while the new one goes live. On Bolt, check anything that relied on the in-browser preview, because some native packages and database drivers behave differently on a real server. On Replit, check for files or SQLite written to storage that resets on redeploy.

On every project we run, all five accounts are yours from day one, not after the final invoice. We quote the move as a fixed price after the free verdict.