Migrating from Lovable
How to take a Lovable app to production with Doable
Lovable is great at the build half, describe an app, get a working prototype in the browser. The deploy half is where Doable comes in: export the Lovable project to GitHub, run one command, and your app is live behind HTTPS in a real Docker container that you fully own.
This is the most common Lovable + Doable pattern: prototype in Lovable, ship with Doable. From that point on, Doable owns the deployment lifecycle, rollbacks, env vars, custom domains, BYO server support all work the same as any other project.
Step by step
- 1
Export your Lovable project to GitHub
In Lovable, use the Export to GitHub button. This creates a normal Node/React repo (no Lovable-specific scaffolding to unwind).
- 2
Clone the repo locally
Standard git clone, the repo is yours.
git clone https://github.com/<your-username>/<your-repo>.git - 3
Install the Doable CLI and log in
One-time setup. Or use the MCP plugin if you deploy from Claude Code.
npm install -g doable-cli && doable login - 4
Set any env vars Lovable injected
If your Lovable app uses Supabase / OpenAI / etc., copy those vars into Doable. Encrypted at rest with AES-256-GCM, injected at container start.
doable env set OPENAI_API_KEY sk-... - 5
Deploy
From the cloned repo directory. Doable detects the runtime (Vite, Next.js, Astro, plain React, all work) and builds it.
doable deploy - 6
Optional: connect a custom domain
Available on Starter ($15/month) and above. Apex or subdomain, automatic Let's Encrypt HTTPS.
doable domain connect <hostname>
Why this combo works
Lovable and Doable solve different problems. Lovable is at its best when you don't have code yet and want a working prototype from a prompt. Doable is at its best when you have code (yours, an AI's, or Lovable's) and want to ship it to a real URL with one command.
Because Lovable's export is a normal repo, there's no platform-specific scaffolding to unwind, it builds and runs anywhere a normal React/Vite/Next project does. Doable just deploys it.
After the migration
Continue iterating in your editor (with Claude Code, Codex, Cursor, whatever you prefer) and `doable deploy` to push changes. The dev loop is identical to any other repo from this point on.
If you ever want to add a database, `doable addon attach postgres <neon-url>` (or Supabase, Upstash, Atlas, your own URL) injects it as an encrypted env var. No schema lock-in to Lovable's chosen stack.
FAQ
Do I lose anything by moving off Lovable's hosting?
You lose the in-browser preview-and-iterate loop, but you've already exported the code, so you can iterate locally with the editor of your choice. Most users keep using Lovable for new prototypes and use Doable for deployed projects.
Can I keep using Lovable while the app is deployed via Doable?
Yes. Pull the latest Lovable export into your local repo, commit, and `doable deploy`. Or set up the GitHub App for auto-deploy on push.
What about Supabase / OpenAI keys Lovable was using?
Copy them into Doable as env vars (`doable env set KEY value`). They're encrypted at rest and injected into your container at start time, same shape as any other env var.
Is there a price difference?
Lovable's pricing is per-message-credit (you pay for each AI generation). Doable is flat per month ($0/$15/$39). Different bills for different things, most teams pay both, since they cover different parts of the lifecycle.
No credit card. Deploy your first project in under a minute.