Software Workload Cloud Migration Assessment Matrix
Score and categorize legacy enterprise software workloads into a multi-dimensional cloud migration matrix.
Use this template when planning an infrastructure transition from on-premise legacy architectures to modern cloud platforms. It provides structured risk, complexity, and migration pathway scores.
Role: Lead Cloud Solutions Architect with 15+ years guiding large-scale enterprise modernization and cloud adoption frameworks.
Context
- Enterprise Client: {{enterprise_name}}
- Legacy Workloads: {{legacy_workloads}}
- Target Cloud Environment: {{target_cloud_provider}}
- Regulatory Compliance: {{compliance_standard}}
- Migration Window: {{migration_timeframe}}
- Downtime Constraint: {{downtime_tolerance}}
Task
Produce a workload migration assessment matrix for {{enterprise_name}} that analyzes {{legacy_workloads}} across architectural readiness, security posture, and business criticality to recommend specific 6-R migration pathways into {{target_cloud_provider}}.
Method
- Analyze the functional architecture and dependency graph of each component in {{legacy_workloads}}.
- Evaluate regulatory obligations and security requirements enforced by {{compliance_standard}}.
- Quantify data storage volumes, network latency sensitivity, and statefulness for every workload.
- Score each application on migration complexity, technical debt, and business risk (scale of 1-5).
- Map each system to a definitive 6-R strategy (Rehost, Replatform, Refactor, Repurchase, Retain, or Retire).
- Account for {{downtime_tolerance}} during cutover window sequencing.
- Assign each workload to an implementation phase within {{migration_timeframe}}.
Constraints
- Matrix rows MUST cover every application provided in {{legacy_workloads}}.
- Migration recommendations MUST fully comply with {{compliance_standard}} parameters.
- You MUST NOT assign 'Refactor' without explicitly noting architectural dependencies in the notes column.
- Use standardized 6-R terminology exclusively for migration strategies.
Output format
1. Assessment Criteria Definition
A four-point scoring rubric explaining Risk, Complexity, Business Value, and Readiness metrics.
2. Workload Migration Decision Matrix
A Markdown matrix formatted with the following headers: | Workload Name | Architectural Type | Compliance Risk (1-5) | Complexity (1-5) | Business Criticality (1-5) | 6-R Strategy | Target Service ({{target_cloud_provider}}) | Migration Wave |
3. Migration Sequencing Plan
A structured phase-by-phase breakdown (Phases 1 through 4) detailing workload cutovers against {{migration_timeframe}} and maintenance windows.
Self-review
- Ensure every component in {{legacy_workloads}} has an assigned 6-R strategy.
- Verify target cloud services match native offerings of {{target_cloud_provider}}.
- Confirm cutover sequencing stays within {{downtime_tolerance}} limits.
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.