How to migrate your Lovable Cloud website to another host or cloud service
Migrating a Lovable Cloud website is mostly about control, portability, and risk management. You need to know where the code lives, what framework it uses, which environment variables are required, how the app builds, where the domain points, and what services the site depends on. The safest migration is planned and tested before changing live DNS or turning off the old deployment.
Quick verdict
Use GitHub as the handoff point when possible. Confirm the project builds locally or on the new host, copy required environment variables, test forms and integrations, then switch the domain only after the new deployment works.
Target topics covered
Know what you are moving
Before migrating, identify whether the project is a simple website, a Next.js app, a React app, a Supabase-backed app, or a product with payments, email, analytics, and custom domains. A simple static website is easier to move than an app with authentication, database policies, API keys, and server-side routes. Make a short inventory before touching the live site.
Migration checklist
A migration has several moving parts. Missing one can cause a site that builds but does not work for users.
- GitHub repository or exported code
- Package manager and build command
- Environment variables and API keys
- Database and authentication services
- Domain and DNS records
- Forms, analytics, payments, and email integrations
Use GitHub as the source
If your Lovable project is connected to GitHub, use that repository as the source for the new host. Pull the latest code, check the package file, and identify the build command. Many modern web hosts can deploy directly from GitHub. This makes migration cleaner because updates can continue through a normal repository workflow.
Choose the new host
The right host depends on the stack. A Next.js app may fit Vercel, Netlify, Cloudflare Pages, or another Node-capable host depending on features used. A static build may work almost anywhere. If the app uses server functions, image optimization, middleware, or database calls, confirm the new platform supports those features before switching.
Environment variables
Most migration failures come from missing environment variables. These may include Supabase URL and keys, analytics IDs, email provider keys, Stripe keys, OpenAI keys, or other service credentials. Copy only the values that are needed, keep secret keys out of the browser, and test production and preview environments separately when the host supports them.
Copy-ready migration prompt
Help me migrate a Lovable website from Lovable Cloud to [new host]. Audit the project for framework, build command, environment variables, API integrations, Supabase usage, forms, analytics, payments, domain settings, and deployment risks. Produce a step-by-step migration checklist with tests to run before switching DNS.
Test before DNS changes
Deploy the new version on a preview URL first. Test every public page, navigation link, form, login flow, payment flow, and integration. Check the mobile layout and page speed. Confirm analytics loads on the preview if appropriate. Only change DNS after the new deployment works. Keep the old deployment available until the domain has fully switched and users can complete the main actions.
Example migration sequence
A safe migration starts with code access, not DNS. First, connect or export the project to GitHub. Second, deploy that repository to the new host using a preview URL. Third, add environment variables and confirm the build command. Fourth, test pages, forms, authentication, integrations, and mobile behavior. Fifth, set up domain records on the new host but do not switch until the preview works. Sixth, lower DNS risk by making the change during a quiet traffic period and keeping the old deployment available. This sequence gives you a rollback path if something fails.
Migration risks to document
Write down the risks before the move. The point is not to make migration complicated; it is to avoid surprises after the domain changes.
- Missing environment variables
- Different build behavior on the new host
- Forms sending to the wrong destination
- Authentication callbacks using old URLs
- Analytics or pixels not loading
- DNS records pointing to the wrong service
Rollback plan
Every migration should have a rollback plan. Keep the old deployment untouched until the new one is proven. Save the previous DNS records before changing them. Note who has access to the domain registrar, GitHub repository, hosting account, and third-party tools. If the new deployment fails after launch, you should know whether to revert DNS, restore a previous commit, fix an environment variable, or temporarily send traffic back to the old host. A rollback plan turns a stressful migration into a controlled change.
After migration
After the domain points to the new host, test the live site again. Check SSL, canonical URLs, redirects, sitemap, robots file, forms, analytics, and critical user journeys. Watch logs for build or runtime errors. If the site uses a database, check that new records are written correctly. Migration is finished only when users can do the same work on the new host without noticing the change.
Related Lovable guides
Frequently asked questions
Can I move a Lovable website to another host?
Yes, if you have access to the project code and the new host supports the app's framework and required services.
What is the safest way to migrate?
Use GitHub as the source, deploy to a preview URL, copy environment variables carefully, test everything, and switch DNS last.
What can break during migration?
Common issues include missing environment variables, wrong build commands, broken forms, auth errors, domain misconfiguration, and unsupported platform features.
Should I turn off Lovable Cloud immediately?
No. Keep the old deployment available until the new live deployment is tested and DNS propagation is complete.
Do I need a developer for migration?
Simple sites may be manageable without one, but apps with authentication, payments, databases, or custom APIs should be reviewed carefully.
Build faster with a better Lovable prompt
Turn the strategy from this guide into a structured Lovable prompt with pages, user roles, data, states, and acceptance criteria.