with one click
migration-readiness
// Assess a workload's readiness to migrate to AWS using Well-Architected principles, covering the 7 Rs, dependencies, risks, and a migration plan.
// Assess a workload's readiness to migrate to AWS using Well-Architected principles, covering the 7 Rs, dependencies, risks, and a migration plan.
Generate a Well-Architected-aligned Architecture Decision Record (ADR) that documents a design decision with context, options evaluated, trade-offs, and WA pillar impact.
Analyze an AWS architecture for cost waste, right-sizing opportunities, and pricing model improvements aligned with the Well-Architected Cost Optimization pillar.
Assess a workload's operational excellence posture against the Well-Architected Operational Excellence pillar, covering organization, preparation, operation, and evolution. Use this skill when evaluating CI/CD practices, observability, incident management, runbook coverage, or operational maturity.
Evaluate a workload's performance efficiency against the Well-Architected Performance Efficiency pillar, covering resource selection, scaling, monitoring, and optimization opportunities.
Identify single points of failure, assess recovery capabilities, and produce a prioritized remediation plan aligned with the Well-Architected Reliability pillar.
Deep-dive security posture assessment against the Well-Architected Security pillar, covering identity, detection, infrastructure protection, data protection, and incident response.
| name | migration-readiness |
| description | Assess a workload's readiness to migrate to AWS using Well-Architected principles, covering the 7 Rs, dependencies, risks, and a migration plan. |
| version | 1.1.0 |
Ask the user:
What workload are you planning to migrate? Please share:
- Current environment (on-premises, other cloud, colocation)
- Application stack (languages, frameworks, databases, middleware)
- Dependencies (other systems it talks to, shared databases, network requirements)
- Business drivers (cost, agility, compliance, end-of-life hardware, etc.)
- Timeline constraints (optional)
If context is already provided, proceed directly.
For the workload, evaluate which strategy fits:
| Strategy | When to use |
|---|---|
| Rehost (lift & shift) | Fast migration, minimal changes, optimize later |
| Replatform (lift & reshape) | Small optimizations during move (e.g., managed DB) |
| Refactor (re-architect) | Need cloud-native benefits, willing to invest |
| Repurchase | Replace with SaaS (e.g., CRM → Salesforce) |
| Retire | No longer needed |
| Retain | Not ready to move yet |
| Relocate | VMware workloads → VMware Cloud on AWS |
Recommend a strategy with justification based on the user's drivers and constraints.
For each pillar, classify readiness as:
Classify each risk by severity:
Flag:
Output:
# Migration Readiness Assessment: {Workload Name}
## Summary
- **Recommended strategy**: {strategy}
- **Overall readiness**: {Ready / Conditionally Ready / Not Ready}
- **Estimated effort**: {T-shirt size with justification}
- **Key risks**: {top 2-3}
- **Estimated timeline**: {weeks/months}
## Migration Strategy Rationale
{Why this strategy fits the workload and business drivers}
## Readiness Scorecard
| Pillar | Readiness | Score (1-5) | Key Gap |
|--------|-----------|-------------|---------|
| Operational Excellence | 🟢/🟡/🔴 | {score} | {gap} |
| Security | 🟢/🟡/🔴 | {score} | {gap} |
| Reliability | 🟢/🟡/🔴 | {score} | {gap} |
| Performance Efficiency | 🟢/🟡/🔴 | {score} | {gap} |
| Cost Optimization | 🟢/🟡/🔴 | {score} | {gap} |
| Sustainability | 🟢/🟡/🔴 | {score} | {gap} |
## Risks and Blockers
| Risk | Severity | Impact | Mitigation | AWS Service |
|------|----------|--------|------------|-------------|
| {risk} | 🔴/🟡/🟢 | {impact} | {mitigation} | {service} |
## Pre-Migration Checklist
{What must be done before migration starts, ordered by priority}
## Migration Plan
### Phase 1: Assess & Mobilize (Weeks 1-2)
{Discovery, dependency mapping, landing zone setup}
### Phase 2: Migrate (Weeks 3-6)
{Data migration, application migration, testing}
### Phase 3: Optimize (Weeks 7-8)
{Right-sizing, cost optimization, performance tuning}
## AWS Services for Migration
| Category | Service | Purpose |
|----------|---------|---------|
| Server migration | AWS MGN | Rehost EC2 workloads |
| Database migration | AWS DMS | Replicate databases with minimal downtime |
| Data transfer | DataSync / Snowball | Large-scale data movement |
| Schema conversion | AWS SCT | Convert database schemas |
| Network | Direct Connect / VPN | Hybrid connectivity |
| Landing zone | Control Tower | Multi-account governance |
## Cost Comparison
| Category | Current (monthly) | Estimated AWS (monthly) | Savings |
|----------|-------------------|-------------------------|---------|
| Compute | {current} | {estimated} | {delta} |
| Storage | {current} | {estimated} | {delta} |
| Networking | {current} | {estimated} | {delta} |
| Licensing | {current} | {estimated} | {delta} |
| **Total** | {total} | {total} | {delta} |
After delivering the assessment, offer:
Would you like me to:
- Design the AWS landing zone architecture?
- Create a detailed data migration plan?
- Estimate AWS costs in more detail (instance mapping, storage tiers)?
- Build a pre-migration testing strategy?
- Identify quick wins to demonstrate value early?