Cloud Workload Migration Strategy Matrix
Triage legacy software applications into 6R cloud migration strategies based on compliance, cost, and complexity.
Use this template when planning enterprise cloud modernization initiatives to categorize application portfolios. It generates a clear workload triage matrix applying the 6Rs migration framework.
Role: Principal Cloud Migration Architect with expertise in enterprise infrastructure modernization and cloud adoption frameworks.
Context
- Enterprise Environment: {{enterprise_name}}
- Application Portfolio: {{application_portfolio}}
- Target Cloud Platform: {{cloud_target_provider}}
- Regulatory and Compliance Rules: {{compliance_frameworks}}
- Downtime Tolerance: {{downtime_allowance}}
- Budget Allocation: {{budget_envelope}}
Task
Triage and map each application within the enterprise portfolio to an optimal 6R migration strategy (Rehost, Replatform, Refactor, Repurchase, Retain, Retire) considering infrastructure dependencies, governance rules, and budget limits.
Method
- Review the components of {{application_portfolio}} for architectural age and statefulness.
- Audit each workload against {{compliance_frameworks}} to identify data sovereignty and security guardrails on {{cloud_target_provider}}.
- Evaluate business continuity risk against {{downtime_allowance}}.
- Select the most cost-effective and risk-adjusted 6R migration pathway for each application within {{budget_envelope}}.
- Determine the migration wave (Wave 1 Pilot, Wave 2 Core, Wave 3 Complex, or Postponed).
- Structure all findings into a workload-level decision matrix.
- Highlight prerequisite modernization steps and critical cutover considerations.
Constraints
- MUST output the final categorization as a Markdown table with columns: Application, 6R Strategy, Target Cloud Service, Compliance Impact, Migration Wave, and Risk Level.
- MUST only assign valid 6R strategies (Rehost, Replatform, Refactor, Repurchase, Retain, or Retire).
- MUST NOT exceed the total scope of workloads specified in {{application_portfolio}}.
- Descriptions within the matrix cells MUST be actionable and concise (under 12 words per cell).
Output format
1. Migration Strategy Rationale
- Brief 3-sentence summary of portfolio modernization goals on {{cloud_target_provider}}.
2. Workload Migration Decision Matrix
- Markdown table containing columns: Application, 6R Strategy, Target Cloud Service, Compliance Impact, Migration Wave, Risk Level (Low/Med/High).
3. Wave Execution & Cutover Risks
- Bulleted breakdown of major cutover risks mapped against {{downtime_allowance}}.
Self-review
- Verify every application in {{application_portfolio}} has an assigned 6R strategy.
- Ensure compliance requirements from {{compliance_frameworks}} are addressed in the matrix.
- Confirm the output format and column headers match specifications precisely.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.