Leaving the builder — four new migration guides under ship-own-stack
The most common question from people who ship something in Lovable, Replit, Emergent or Base44 is "how do I get out of this when I need to?" The ship-own-stack pillar now answers that, per builder, with verified source citations.
See Ship & own your stack pillarThe ship-own-stack pillar had a "you're ready to leave Lovable or Bolt" page and a "first deploy on Vercel + Supabase" walkthrough. The middle was missing — how do you actually move a project off the specific builder you used?
That's now four guides:
- Migrate from Lovable — the cleanest exit. Vite + React frontend goes to Vercel; you choose whether to move the Supabase project or keep it.
- Migrate from Replit — Railway has the official path. Most of the work is removing
.replit/replit.nix, translating the run command, and migrating Postgres withpg_dump. - Migrate from Emergent — three services, three hosts. Frontend on Vercel, FastAPI on Railway, MongoDB on Atlas.
- Migrate from Base44 — the tightest-coupled of the four. The exported code still calls Base44 services, so the realistic first move is "move only the frontend" — not a full rebuild.
What is in every guide
The structure is the same across all four because the failure modes are the same. Auth redirect URLs break first. CORS breaks second. Build-passes-locally-fails-on-host is almost always a missing environment variable. Database migration is the boring part; replacing the auth layer is the hard part.
Each guide cites the builder's own documentation for the export path, plus the host-side migration guide where one exists (Railway's Replit guide is the gold standard — no other builder→host pair is documented that thoroughly).
What the hub page does now
graduate-from-nocode is rewritten as the general migration hub. It keeps the five graduation signals — cost cliff, customization wall, performance, lock-in, team size — and now also covers what migrating actually moves, the shape of every migration in seven phases, and explicitly what graduating does not fix. The per-builder guides link from the bottom.
Why this batch
The "migrate from X" queries are searched, documented unevenly across the internet, and the answer is concrete enough to be useful — not a "depends on your situation" punt. The pillar already had the deploy walkthrough waiting to receive these graduates. Net new surface is zero (slugs under an existing pillar); content density inside the pillar roughly triples.
More spotlights: See the archive →