← All stories · Outgrowing the builder

Move a Lovable project into your own repo early

Non-technical PM outgrew Lovable and rebuilt on Next.js · Reddit r/vibecoding · u/ZvenDan · Jun 2026

Over about three weeks a PM shipped an education platform, started in Lovable, hit its limits, moved to their own repo with Claude Code, and then rebuilt on Next.js for SEO.

The honest numbers

As stated by the source. Not independently verified.

Lesson

Get your code into your own Git repo early, and check whether your framework suits SEO before launch.

Fix prompt

Copy this into your own AI tool (Cursor, Lovable, Claude Code, Bolt…). It's general guidance written by us. Review what the AI suggests before applying it.

I built my app with Lovable and want to make sure I'm not locked in. 1) Explain where each part of my app lives: code, database, file storage, auth, serverless functions and secrets, and which of them I can export. 2) Tell me how to get the code into my own GitHub repo and keep it in sync. 3) List what would need rebuilding if I moved hosting or backend, and roughly how hard each part is for a beginner. 4) Give me a step-by-step exit plan that keeps the current app live until the new one is tested. Don't change anything until I've approved your plan. Never ask me to paste API keys, passwords or .env contents; tell me where to check them myself.
LovableClaude CodeCodexCursorVercelSupabase

Source: Reddit r/vibecoding ↗

The Honest Build. Real stories, not hype.

Every week: real stories of what building with AI actually took, the one lesson worth keeping, and the security slip-ups to avoid. Free, unsubscribe anytime.