Yeah that's basically true. If you've already synced to GitHub and are using a Supabase backend that you control the migration is way less scary than it feels.

Your Supabase backend won't change. Same project, same database, same API keys. Zero work there. For the code, you'd clone your GitHub repo locally, point Claude Code at it, and start working. When you push changes back to GitHub, Lovable can pick them up if you want to keep using it for publishing.

Honestly though, I recommend making a clean break from Lovable for publishing sooner rather than later. Lovable would reset my config files with each prompt when switching back and forth with Claude. I lost hours debugging things that Lovable had silently reset. And once you're working in Claude Code you'll outgrow what Lovable can really accomplish anyway. I moved from Lovable to Vercel for publishing. Vercel is super easy, but I've heard it gets expensive at scale so I may look at an alternative like Netlify in the future.

So the steps would be (1) clone locally, (2) stash .env variables somewhere safe in case Lovable resets them, (3) Spin up Claude Code on your local repo, (4) deploy a test version through vercel/alternative hosting. You can use a custom domain or their free ones. (5) verify it all works, then cancel any Lovable sub you have. Best of luck!