Own your Lovable app on real hosting
Your database, sign-in users and uploaded files come with it. One backup command on your computer, one upload, one deploy.
Run this on your own computer. A browser opens to sign in to Lovable; pick your project and the backup is saved to your Downloads folder.
macOS / Linux
curl -fsSL https://migrate-lovable.hostwares.com/install.sh | bash
Windows (PowerShell)
irm https://migrate-lovable.hostwares.com/install.ps1 | iex
Your data comes with it
Your database structure, Your app's logic, All your data, Sign-in users, Uploaded files. Users sign in with the passwords they already have.
Backups you can restore
Your project's Backups page lists its restore points, and a restore is made into a separate copy, so your live data is never overwritten.
Your own domain
Every app goes live on a free hostwares.app address with HTTPS. Add your own domain whenever you're ready.
No lock-in
Your code stays in your own GitHub repository, and your data sits in a Supabase project your app talks to with the standard Supabase client.
How it works
- 1
Create the destination
A Supabase project for your data and a site for your app.
- 2
Back up your Lovable project
Run one command on your own computer. Nothing from Lovable passes through our servers.
- 3
Restore into your project
Upload the backup in your project's Restore tab.
- 4
Connect your app and deploy
Point the site at your new project, then it rebuilds.
- 5
Check it's live
Open your app and sign in.
Every click and command is in the migration guide.
Or let HW do it
Say "migrate my Lovable app" to HW, our AI. It creates your project and site, hands you the one command to run, waits for your upload, connects and deploys the site, then shows you what was restored next to what was backed up. The backup and the upload are the only steps you do yourself.
Questions
Do I have to give Hostwares my Lovable password or any keys?
No. The backup tool runs on your computer and signs in to Lovable in your own browser. The access token stays on your machine, nothing from Lovable passes through our servers, and the tool asks for no key.
What exactly moves?
Your database structure: Every table, column, relation and enum from your project's migrations. Your app's logic: Every database function your app calls, every access rule, trigger and view - copied from your live project, including the ones created outside its migrations. All your data: Every row in every table. Sign-in users: Accounts keep their existing passwords, so your users sign in exactly as before. Uploaded files: Images, PDFs and other files from both public and private storage, with their folders and file types. Your app's code moves through GitHub.
What about files in private storage?
They come across too. While copying, the tool briefly makes those storage buckets readable, then locks them again as soon as the copy ends.
Will my app need code changes?
Usually not: you set your project's address and public key as environment variables and redeploy. Apps that use Lovable-only services, such as its AI features or edge functions, may need a small amount of rewiring.
My backup is large. Is there a limit?
Uploads in the dashboard go up to 200 MB. For a bigger backup, open a support ticket and we restore it for you.
Can the AI do it for me?
Yes. Tell HW "migrate my Lovable app". It sets up the destination, gives you the one command to run, waits for your upload, connects and deploys the site, and reports what was restored against what was backed up.