Stuck on Bolt, Lovable, or Replit — And Can't Move Off
You built your MVP on an AI platform. It worked. Now you need to scale — and you discover that migrating away is harder than building was.
This is platform lock-in: the modern form of vendor dependency in AI-generated codebases. The platform controls the credentials, the deployment pipeline, and often the database access. Exporting to GitHub produces a codebase that cannot run independently. The founder is trapped — continuing to pay for a platform they've outgrown, or facing a painful migration.
What We Observe
Platform lock-in manifests differently per tool, but the pattern is consistent:
- Lovable: "You're stuck tweaking via GitHub or living with what the AI hands you." Users report that exported code requires significant work to run outside Lovable's environment. Edge functions don't deploy independently.
- Bolt.new: "Can't access database or secrets inside Bolt." Credentials are managed by the platform. Disconnecting from Bolt breaks integrations.
- Replit: "Apps need to function off of Replit." Production deployment outside Replit's hosting requires infrastructure knowledge the platform abstracted away.
- v0: Code generated for Vercel's ecosystem has implicit dependencies on Vercel-specific features.
Real client language:
- "Decouple our development and deployment workflows from Lovable — without breaking production or impacting customers." — Upwork job post ($25–$47/hr)
- "GitHub must become the single source of truth." — same listing
- "Lovable doesn't provide the credentials." — r/lovable
- "Trying to salvage a generated codebase often turns out to be a frustrating endeavour." — r/lovable
- "Migrate your Bolt, Lovable, Cursor, or Replit project to a clean React/Next.js environment." — Upwork freelancer listing
The Structural Cause
AI builder platforms abstract infrastructure to make generation fast. This abstraction becomes a trap:
- Credentials managed by platform — Database connections, API keys, and deployment secrets live inside the platform, not in the developer's control
- Platform-specific deployment — Edge functions, serverless routes, and hosting configurations are tied to the platform's infrastructure
- Non-standard code structure — Generated code follows the platform's conventions, not industry-standard patterns. Migration requires restructuring, not just copying.
Remediation Path
Migration from a platform follows three steps:
- Audit — Identify all platform dependencies: credentials, deployment config, platform-specific APIs, non-standard patterns
- Decouple — Extract credentials to environment variables, replace platform-specific APIs with standard equivalents, restructure code to run independently
- Deploy independently — Set up CI/CD, hosting, and database access outside the platform. Verify the application runs identically.
The goal: "GitHub becomes the single source of truth" and the application runs on any hosting provider.
This Is a Symptom Of
- Hidden Technical Debt (PF02) — Platform-specific debt compounds the general structural debt
- Comprehension Debt (PF10) — The platform abstracted away infrastructure the founder now needs to understand
FAQ
Can't I just export to GitHub and keep going?
Exporting to GitHub gives you the source code, but not the infrastructure. Credentials, deployment configuration, edge function routing, and database access typically need to be recreated manually. The export is a starting point, not a finished migration.
How long does platform migration take?
For a typical AI-generated MVP, migration takes 3–7 days depending on complexity. The main variable is the number of platform-specific integrations (auth, payments, database, deployment).