Replit Migrate
Migrate Replit apps to web (Vercel, Cloudflare, standalone) or native iOS/macOS. Risk-ordered plans with lessons encoded from real migrations.
The Answer
Scan a Replit project, produce a risk-ordered migration plan for web or native, and avoid redoing the mistakes that bit earlier migrations.
The Problem It Solves
Replit apps mix runtime, database, secrets, and deployment into a single environment. Lifting one out touches all four at once. First-time migrations miss the weird parts: the in-memory session store, the bundled SQLite, the vendored Python dependency, the Replit Auth cookie that stops working on Vercel.
How It Works
/replit-migrate:scan inspects a project and classifies runtime, dependencies, datastore, auth, and deployment patterns. /replit-migrate:migrate web or native generates a plan ordered by blast radius, with high-risk items first. For native iOS and macOS, the plan uses XcodeGen for project generation and documents the manual App Store Connect steps that no tool automates cleanly.
What Makes It Different
Lessons from real migrations ship as encoded skills: auth weighting for Replit Auth to native, schema parsing for Drizzle and SQLAlchemy ports, XcodeGen plist gotchas, IBR enforcement for UI parity. The CLI and plugin share the same code, so local scripting and Claude Code workflows produce identical plans.