Migrate from Lovable to Claude Code
To migrate from Lovable to Claude Code, your Lovable project's code goes into a GitHub repo you own and onto hosting you choose, with Claude Code set up so you or your developer keep building it by asking.
Where you are
You built the app in Lovable and real people use it, and you've outgrown building it one prompt at a time. You're switching from Lovable to Claude Code so that you, or a developer you trust, can work on the code itself. Lovable hands you the code through GitHub, and your app keeps running on Lovable's hosting, keys and backend until each of them is moved.
What you get
- Your Lovable app's code in a GitHub repo in your name, building and running outside Lovable.
- Your app hosted where you choose, such as Vercel, with your domain moved across after every flow is tested.
- Your keys for Stripe, OpenAI and email set up again outside Lovable, where you can see and change them.
- The AI features in your app moved onto an account in your name, so they keep working without Lovable.
- The rules and decisions you gave Lovable written into the repo, so Claude Code starts from what Lovable knew about your app.
- Claude Code set up on the repo, so the next feature is something you ask for and can read before it goes live.
- A note in the repo of where everything lives now, for you or the next developer.
How it goes
- You export your Lovable code to GitHub, which Lovable allows on every plan, and share the repo with me.
- I list everything your app still gets from Lovable, from hosting and keys to the AI it calls and the backend.
- The app runs on its new hosting beside the Lovable one, with Claude Code set up and every flow tested, from sign-up to payment.
- On the day of the switch your domain moves across, and the Lovable version stays in place until the new one has held up under real use.
What moves from Lovable to Claude Code, and what stays
Lovable syncs your code to GitHub both ways, on one branch, so the code is already out and Lovable can keep editing beside Claude Code while you switch. The switch changes where the code is written, and nothing else moves by itself. A code export carries neither your database nor the files your users uploaded, and Lovable keeps running the hosting, the domain, the keys and the AI your app calls until each one is moved on purpose.
Source Lovable, Deployment, hosting, and ownership options
Your database, sign-in and uploaded files can stay on Lovable Cloud while you build in Claude Code, running on the same Lovable credits as your hosting. When you want to migrate off Lovable entirely, moving them is a Lovable Cloud to Supabase migration, and it can come after the switch.
Source Lovable, Built-in backend
The work
Saif is the true definition of not compromising on quality.
The first reply lists what your app still needs from Lovable after the code is out, and the order to move each part.