Code Migration Planning Assistant

You are a technical lead who plans large-scale code migrations. Create a migration plan for this project.

Migration type: [LANGUAGE / FRAMEWORK / ARCHITECTURE / DATABASE / CLOUD]
From: [CURRENT STATE]
To: [TARGET STATE]
Codebase size: [LOC OR ROUGH SIZE]
Team size: [DEVELOPERS AVAILABLE]
Timeline constraint: [DEADLINE IF ANY]
Business constraints: [DOWNTIME TOLERANCE / FEATURE FREEZE / ETC.]

Provide:

**Migration Assessment**

Complexity Analysis:
- High complexity areas
- Dependencies to manage
- Integration points
- Data migration needs

Risk Assessment:
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|

**Migration Strategy**

Recommended Approach: [Big Bang / Strangler Fig / Parallel Run / Incremental]
- Rationale:
- Trade-offs:

**Phase Plan**

**Phase 0: Preparation** (Week 1-2)
- [ ] Comprehensive testing of current system
- [ ] Documentation of current behavior
- [ ] Team training on target technology
- [ ] Tooling setup

**Phase 1: Foundation** (Week 3-4)
- [ ] Core infrastructure setup
- [ ] CI/CD pipeline for new system
- [ ] Monitoring and observability
- [ ] First component migration

**Phase 2: Incremental Migration** (Week 5-X)
- Component migration order (prioritized)
- Parallel running strategy
- Validation criteria for each component

**Phase 3: Cutover** (Week X)
- Final migration steps
- Rollback triggers
- Success criteria

**Phase 4: Cleanup** (Week X+1)
- Old system decommission
- Documentation updates
- Lessons learned

**Rollback Plan**
- Triggers for rollback
- Rollback procedure
- Data synchronization during parallel run

**Testing Strategy**
- Comparison testing
- Performance benchmarks
- Integration testing
- User acceptance criteria

**Communication Plan**
- Stakeholder updates
- User notifications
- Documentation

**Success Metrics**
- Technical metrics
- Business metrics
- Timeline metrics

You are a technical lead who plans large-scale code migrations. Create a migration plan for this project.

Migration type: [LANGUAGE / FRAMEWORK / ARCHITECTURE / DATABASE / CLOUD]
From: [CURRENT STATE]
To: [TARGET STATE]
Codebase size: [LOC OR ROUGH SIZE]
Team size: [DEVELOPERS AVAILABLE]
Timeline constraint: [DEADLINE IF ANY]
Business constraints: [DOWNTIME TOLERANCE / FEATURE FREEZE / ETC.]

Provide:

**Migration Assessment**

Complexity Analysis:
- High complexity areas
- Dependencies to manage
- Integration points
- Data migration needs

Risk Assessment:
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|

**Migration Strategy**

Recommended Approach: [Big Bang / Strangler Fig / Parallel Run / Incremental]
- Rationale:
- Trade-offs:

**Phase Plan**

**Phase 0: Preparation** (Week 1-2)
- [ ] Comprehensive testing of current system
- [ ] Documentation of current behavior
- [ ] Team training on target technology
- [ ] Tooling setup

**Phase 1: Foundation** (Week 3-4)
- [ ] Core infrastructure setup
- [ ] CI/CD pipeline for new system
- [ ] Monitoring and observability
- [ ] First component migration

**Phase 2: Incremental Migration** (Week 5-X)
- Component migration order (prioritized)
- Parallel running strategy
- Validation criteria for each component

**Phase 3: Cutover** (Week X)
- Final migration steps
- Rollback triggers
- Success criteria

**Phase 4: Cleanup** (Week X+1)
- Old system decommission
- Documentation updates
- Lessons learned

**Rollback Plan**
- Triggers for rollback
- Rollback procedure
- Data synchronization during parallel run

**Testing Strategy**
- Comparison testing
- Performance benchmarks
- Integration testing
- User acceptance criteria

**Communication Plan**
- Stakeholder updates
- User notifications
- Documentation

**Success Metrics**
- Technical metrics
- Business metrics
- Timeline metrics