Lovable Migration Checklist
A vendor-neutral guide to escape Lovable Cloud and own your code. Whether you're moving to Vercel, Netlify, Railway, or self-hosted infrastructure, this checklist walks you through every step: from pre-migration questions to post-deployment verification.
Why You Need a Lovable Migration Checklist
Lovable's built-in hosting is preview-optimized, not production-hardened. Builders migrate for control, predictability, and scale.
Billing You Can Predict
Lovable's credit-based billing scales unpredictably with your API usage. Flat-rate hosting means you pay the same whether your app processes 100 requests or 10,000 per day. No surprise bills. No monthly budget anxiety.
Code Ownership
Your code belongs in a Git repository you control, not locked inside Lovable's cloud. Once your project syncs to GitHub, you own it. You can fork it, branch it, self-host it, or sell the business—without Lovable's permission.
Production Infrastructure
Lovable's hosting is built for fast demos. Production apps need database backups, autoscaling, secrets management, and monitoring. Self-hosted or managed platforms give you that foundation from day one.
Built for teams who need reliability
The Migration Framework
Four core steps that every Lovable migration follows, regardless of your target platform.
Choose Your App
Select an app to get started.
Sync Code to GitHub
Lovable syncs automatically to GitHub when you click the GitHub icon in your project. Your code is now in a repo you control.
Prepare Local Environment
Clone your repo, install dependencies, and create a `.env.example` file. Never commit secrets. Test locally to ensure the app runs outside Lovable's sandbox.
Export Database & Secrets
Export your Supabase schema, auth users, and seed data. Migrate API keys and third-party credentials to your hosting platform's secrets manager.
Deploy to Hosting Platform
Connect your GitHub repo to your hosting platform. Configure build settings. TLS is provisioned automatically. Your app is live in minutes to hours.
Do You Actually Need to Migrate?
Not every Lovable project should migrate. Ask yourself these questions first.
Cost Analysis
How much are you spending on Lovable Cloud today? Calculate your monthly credit usage and project it annually. Then compare to your target platform's pricing. A small hobby app might pay the same (or more) after migration. A production app with 100K monthly users will likely save money on flat-rate hosting.
Timeline & Downtime Tolerance
Migration takes 3 days (frontend-only export) to 8 weeks (full-stack with database verification). How long can your app be unavailable? If your app generates revenue, plan for zero-downtime migration using blue-green deployment or dark launching.
Technical Skill
You will manage environment variables, GitHub secrets, database migrations, and CI/CD pipelines. If you've never used GitHub or configured a .env file, learn those basics first. Many hosting platforms automate the rest.
Compliance & Data Residency
Lovable Cloud hosts in the US. If you need GDPR compliance or EU data residency, you must migrate. Check your target platform's data center locations before committing.
Lovable's Future
If Lovable's built-in hosting meets your needs, staying is fine. Migration is not mandatory. Your code syncs to GitHub either way. Only migrate when you hit a hard limit: cost, compliance, or infrastructure requirement.
Your Migration Timeline
Each step depends on your app's complexity. A simple frontend-only export: 3 days. A full-stack app with database and auth: 4-8 weeks.
Sync Your Project to GitHub
Click the GitHub icon in your Lovable project. Lovable syncs automatically. Verify your code, `.env.example`, and `package.json` are in the repo.
Clone Locally and Test
Run `git clone`, `npm install`, and `npm start`. Verify your app runs outside Lovable's sandbox. Note any differences in behavior.
Extract Database Schema
Export your Supabase schema using `pg_dump` or Supabase's UI. Export auth users and seed data. Test the export—corruption here breaks everything.
Migrate Database to Target Platform
Import schema, users, and data to your target database. Run queries to verify data integrity. Check row counts, foreign key constraints, and auth token validity.
Configure Secrets & Environment Variables
Add API keys, database credentials, and third-party service tokens to your hosting platform's secrets manager. Do not commit them to Git. Test that your app can read them.
Deploy to Hosting Platform
Connect your GitHub repo. Configure build settings (Node version, build command, start command). Deploy. TLS is automatic. Verify the URL resolves.
Update DNS and Go Live
Update your domain's CNAME or A record to point to the new hosting platform. Wait for DNS propagation (up to 48 hours). Test the custom domain in production.
Database Migration: Your Critical Path
This is where migrations fail. Exporting Supabase schema, users, and data requires careful testing. Plan 1-2 weeks for this step alone. Verify every table, every row, every foreign key before you decommission Lovable Cloud. Data loss is not recoverable.
Migration Resources You Can Trust
Lovable migration is not speculative—thousands of builders have done it. Here's what makes it reliable.
Industry Standard Stack
Your migrated app uses GitHub, Node.js, PostgreSQL, and standard hosting platforms. These are not niche tools. They're used by 100K+ production apps worldwide. If it breaks, the answer is documented.
No Lock-In After Migration
Once you migrate, your code and data belong to you. You can self-host, switch platforms, or sell the business. No vendor approval required. No migration-out fees.
Battle-Tested Process
Northflank, Railway, Vercel, and Netlify have published detailed Lovable migration guides. Multiple GitHub repos contain open-source migration tooling. The process is standardized.
Production-Ready Infrastructure
Flat-rate hosting platforms provide autoscaling, daily backups, secrets management, and monitoring. Your app can handle 1M requests per day on the same infrastructure you started with.
Ship: Flat-Rate Hosting for Migrated Apps
Ship is a self-hosted PaaS. Deploy your migrated Lovable app with zero DevOps overhead and predictable, flat-rate pricing. No credit-based billing. No surprises.
Loading pricing...
Lovable Migration: Common Questions
It depends on your app's complexity. A frontend-only export (no database changes): 3 days. A full-stack app with database, auth, and third-party integrations: 4-8 weeks. The database migration step is your bottleneck—testing and verifying data integrity takes 1-2 weeks alone. Start by inventorying what you need to migrate: API keys, database tables, user auth tokens, file storage, edge functions. That inventory will tell you the real timeline for your project.
Ready to Own Your Code?
You've planned the migration. Ship handles the hosting piece. Deploy your migrated app with predictable pricing and zero DevOps overhead.