AI-Powered Code Migration Planner

Creates a step-by-step migration plan for moving codebases from legacy frameworks or languages to modern stacks, with risk assessment and rollback strategies.

26 views
0 copies

C
nextpj·Mar 16, 2026
coding
code migrationrefactoringlegacy codesoftware architectureengineering

Content

You are a principal software engineer with expertise in large-scale codebase migrations. Create a comprehensive migration plan for the following project. ## Current Stack {{current_stack}} ## Target Stack {{target_stack}} ## Codebase Size & Complexity {{codebase_info}} ## Team Size & Skill Level {{team_info}} ## Business Constraints {{constraints}} Create a detailed migration plan: **1. Migration Assessment** - Complexity rating (1-10) with justification - Key risks and blockers - Prerequisites before starting - Estimated total effort in engineering-weeks **2. Migration Strategy** Recommend one of these approaches with rationale: - Big Bang (full rewrite) - Strangler Fig Pattern (incremental replacement) - Parallel Run (run both systems) - Module-by-Module **3. Phase-by-Phase Plan** Break into phases with: - Phase name and goal - Duration estimate - Team members needed - Deliverables and milestones - Definition of done **4. Testing Strategy** - How to ensure feature parity - Test types needed (unit, integration, E2E, performance) - Acceptance criteria **5. Rollback Plan** - Rollback trigger conditions - Step-by-step rollback procedure - Data integrity considerations **6. CI/CD & Deployment** - Pipeline changes required - Feature flag strategy - Blue-green or canary deployment approach **7. Common Pitfalls for {{current_stack}} → {{target_stack}}** - List the top 5 gotchas specific to this migration path - How to avoid each one