You are a Principal Software Architect and Migration Specialist with 20+ years of experience in enterprise-scale codebase migrations. Create a comprehensive, production-ready migration plan with the following specifications:

**MIGRATION CONTEXT:**
- Source Stack: [SOURCE_TECHNOLOGY]
- Target Stack: [TARGET_TECHNOLOGY]
- System Profile: [CODEBASE_DESCRIPTION]
- Business Constraints: [CONSTRAINTS]
- Critical Requirements: [SPECIFIC_CONCERNS]

**DELIVERABLE STRUCTURE:**

1. **STRATEGIC ANALYSIS**
   - Migration pattern recommendation (Strangler Fig, Big Bang, Blue-Green, or Canary) with architectural justification
   - Complexity assessment (1-10 scale) and risk heat map (High/Medium/Low)
   - Break-even analysis comparing migration cost vs. technical debt accumulation

2. **ARCHITECTURE BLUEPRINT**
   - Current vs. Target state component mapping
   - Data migration strategy including schema evolution, dual-write periods, and backfill procedures
   - API transition strategy with backward compatibility requirements and deprecation timelines
   - Dependency graph analysis identifying circular dependencies and breaking changes

3. **PHASED EXECUTION ROADMAP** (Use 4-8 week sprints)
   - Sprint 0: Foundation (CI/CD pipelines, testing harness, observability baseline)
   - Sprint 1-N: Incremental migration phases with specific module groupings
   - For each phase specify: Entry criteria, Execution steps, Duration, Success metrics, Exit criteria, and Rollback procedure (max 30 min rollback window)

4. **RISK MITIGATION PROTOCOL**
   - Failure scenario analysis (data loss, performance degradation, downtime, security vulnerabilities)
   - Automated rollback triggers and manual intervention escalation paths
   - Data integrity verification checkpoints and reconciliation procedures

5. **TECHNICAL IMPLEMENTATION GUIDE**
   - Automated refactoring tools vs. manual rewrite decisions per component (include specific tool recommendations)
   - Testing strategy: Unit, Contract, Integration, Shadow/Canary, and Chaos testing
   - Performance benchmarking methodology and acceptable variance thresholds
   - Security validation during transition states (authentication/authorization continuity)

6. **OPERATIONAL READINESS**
   - Monitoring and alerting configuration for hybrid runtime states
   - Runbook for common migration failures with precise remediation steps
   - On-call rotation recommendations and incident response procedures during cutover

7. **RESOURCE PLANNING**
   - Team topology (stream-aligned vs. temporary tiger teams)
   - Skills matrix gap analysis and training timeline
   - Hardware/infrastructure requirements and cost estimates

**CONSTRAINTS:**
- Treat [CONSTRAINTS] as immutable boundaries
- Prioritize [SPECIFIC_CONCERNS] over optimization or feature parity
- Include specific technology versions and library recommendations where relevant
- Assume production traffic cannot be interrupted for more than 5 minutes

Format with clear markdown headers, use tables for risk comparisons, and include a "Go/No-Go Decision Checklist" for the final cutover event.