Skip to main content
command CX Codex

migration-readiness — Claude Code command for AWS migration

The migration-readiness command analyzes a codebase to assess a workload’s readiness for AWS migration. Use it to surface blockers and map out a component-by-component migration plan.

MIT-0 ★ 280 updated 2026-10-06

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/migration-readiness.md
Open on GitHub

What migration-readiness does

The command gathers workload and environment details, then examines code, configuration, dependencies, and infrastructure. For each component, it records technologies and versions, file paths and line references, possible AWS equivalents, and migration complexity. It uses that evidence to recommend a 7 Rs strategy, such as Rehost, Replatform, or Retire.

The assessment includes a PlantUML dependency diagram, readiness findings by pillar, blockers and risks, phased migration steps, and a cost comparison. Recommendations must be backed by code evidence; shared databases also get a migration-order constraint. Static-analysis cost figures are rough, and details such as data volume may not be inferable from code.

For Claude Code, place the command file at .claude/commands/migration-readiness.md. When a codebase is already open, the command can start its analysis directly; otherwise, it first asks about the workload and business constraints.

What it helps with

  • assess a codebase’s readiness for migration to AWS
  • identify dependencies that could block component moves
  • justify 7 Rs recommendations with code references
  • draft a phased migration plan with waves
  • compare current costs with AWS estimates

Example prompts for the agent

  • Assess this project’s readiness for AWS migration with /migration-readiness.
  • Find migration blockers and support each finding with file and line references.
  • Map this workload’s dependencies and propose migration waves.

How to install migration-readiness

Manually: put the files in place

.claude/commands/migration-readiness.md

Call it with /migration-readiness. For all projects use ~/.claude/commands/

Questions about migration-readiness

How do I install migration-readiness in Claude Code?

Place the command file at .claude/commands/migration-readiness.md.

What does migration-readiness do?

It examines code, configuration, infrastructure, and dependencies, then produces an AWS readiness assessment with component strategies, risks, and migration steps.

What evidence supports its 7 Rs recommendations?

Each recommendation must be justified by code findings. For shared databases, the assessment also flags the required migration ordering.

Source text

migration-readiness.md · MIT-0
Assess a workload's readiness to migrate to AWS by analyzing existing code, dependencies, configurations, and infrastructure to produce evidence-backed findings covering the 7 Rs, risks, and a migration plan.

## Step 1: Gather context

Ask the user:

> What workload are you planning to migrate? Please share:
> - **Workload name** and code packages/directories to analyze
> - **Current environment** (on-premises, other cloud, colocation)
> - **Business drivers** (cost, agility, compliance, end-of-life hardware)
> - **Timeline constraints** (optional)

If already in a codebase, proceed directly.

## Step 2: Application Stack Discovery

Analyze the codebase to understand current stack:

- Programming languages and runtime versions
- Frameworks and libraries (web, ORM, messaging)
- Database technologies
- External service dependencies
- Configuration management (config files, env vars, secrets)
- Build and packaging systems (Maven, npm, pip, Docker)
- OS-specific or hardware dependencies

For each component, document:
- File path and line numbers
- Technology and version
- AWS equivalent or migration path
- Migration complexity (simple lift, requires changes, requires rewrite)

Flag as BLOCKER:
- OS-specific deps without cloud equivalents
- Proprietary licensing restrictions (Oracle, specific Windows features)
- Hardware-specific dependencies (FPGA, USB dongles)
- Hardcoded IP addresses/hostnames in application code
- Local filesystem dependencies (shared network drives)

## Step 3: Dependency Mapping

Map all internal and external dependencies:

- Service-to-service communication (protocols, ports)
- Database connections (shared databases, multiple consumers)
- External API integrations
- Network dependencies (latency-sensitive connections)
- Authentication dependencies (LDAP, AD, SSO)

Create a dependency diagram showing services, connections, and migration wave groupings.

Flag as HIGH RISK:
- Tight coupling that must move together
- Shared databases with multiple consumers
- Latency-sensitive integrations spanning hybrid during migration
- Hard dependencies on systems that cannot move

## Step 4: Determine migration strategy (7 Rs)

For each component, recommend based on code evidence:

| Strategy | Code Indicators |
|----------|-----------------|
| **Rehost** | Standard OS, containerizable, no OS-specific deps |
| **Replatform** | Self-managed DB → RDS, self-managed cache → ElastiCache |
| **Refactor** | Monolith to decompose, stateful → stateless |
| **Repurchase** | Commercial software with AWS/SaaS equivalent |
| **Retire** | Unused code, deprecated services |
| **Retain** | Hard dependencies, compliance blockers |
| **Relocate** | VMware-specific configurations |

Every recommendation MUST be justified with code evidence.

## Step 5: Assess readiness by pillar

For each pillar: **Readiness** (Ready/Conditionally Ready/Not Ready), **Evidence** (file:line), **Gaps**, **Actions needed**.

- **Operational Excellence**: IaC existence, CI/CD portability, monitoring portability
- **Security**: compliance constraints, secrets management, network security equivalents, identity compatibility
- **Reliability**: current availability, HA mechanisms to replicate, acceptable migration downtime
- **Performance Efficiency**: latency-sensitive integrations, hardware deps, performance baselines
- **Cost Optimization**: current TCO, licensing implications, existing commitments
- **Sustainability**: resource footprint reduction, Graviton/serverless opportunities

## Step 6: Risk Assessment

| Impact   | Likelihood | Risk Level |
|----------|------------|------------|
| Severe   | High       | Critical   |
| Severe   | Medium     | High       |
| Severe   | Low        | High       |
| Moderate | High       | High       |
| Moderate | Medium     | Medium     |
| Moderate | Low        | Medium     |
| Minor    | High       | Medium     |
| Minor    | Medium     | Low        |
| Minor    | Low        | Low        |

## Step 7: Produce the assessment

Structure:

- Executive Summary (date, packages analyzed, recommended strategy, overall readiness, effort estimate, key risks, critical blockers count)
- Application Stack Summary table (component, technology, version, AWS equivalent, strategy, complexity)
- Dependency Map (PlantUML diagram)
- Readiness Scorecard (pillar, readiness status, score 1-5, key blocker, action needed)
- Critical Blockers (ID, description, evidence file:line, impact, resolution approach, effort)
- Risks and Mitigations table (risk, evidence, risk level, impact, mitigation, AWS service)
- Pre-Migration Checklist (ordered by priority)
- Migration Plan (Phase 1: Mobilize, Phase 2: Migrate with waves, Phase 3: Optimize)
- AWS Services for Migration table
- Cost Comparison (category, current est., AWS est., delta)
- Next Steps (top 5 actions)

## Calibration

- Every blocker and risk MUST have code evidence
- Strategy recommendations must be justified by code analysis
- "Cannot Determine" is valid for runtime characteristics not in code (data volumes, latency)
- For shared databases, always flag migration ordering constraint
- Cost estimates from static analysis are rough — acknowledge uncertainty
- Acknowledge migration-ready aspects prominently (containerized, stateless, IaC exists)

<!--
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
SPDX-License-Identifier: MIT-0
-->

© aws-samples · MIT-0 · aws-samples/sample-well-architected-skills-and-steering

Similar slash commands

All slash commands for Cloud: AWS, Azure, GCP →

From the same set19

The whole set →
sustainability-optimization sustainability-optimization runs an AWS Well-Architected review limited to the Sustainability pillar and returns a report with a resource-efficiency table and a scorecard. CX Codex +1 ★ 280repo stars prompt prompt audits AWS workloads against the Well-Architected Framework, surfacing risks in code and IaC without modifying repository files directly. CX Codex +1 ★ 280repo stars well-architected This rule applies AWS Well-Architected principles to architecture reviews, infrastructure code, and design advice. It helps agents organize findings and explain trade-offs. CX Codex +1 ★ 280repo stars wa-builder wa-builder explains AWS Well-Architected concepts for your project and generates annotated diagrams, decision trees, and remediation roadmaps. CX Codex +1 ★ 280repo stars aws-well-architected-framework-review aws-well-architected-framework-review runs a full Well-Architected review over your code and IaC: six pillars, findings tied to file and line, a report with a fix plan. CX Codex +1 ★ 280repo stars wa-guardrails wa-guardrails generates preventive AWS Well-Architected guardrails, including CI checks, AWS Config rules, SCPs, and CloudWatch alarms, to block regressions. CX Codex +1 ★ 280repo stars aws-well-architected-framework-review aws-well-architected-framework-review is a Claude Code command that reviews AWS workloads against the Well-Architected Framework, using code and infrastructure settings as evidence. CX Codex +1 ★ 280repo stars wa-builder wa-builder teaches AWS Well-Architected against your own workload, then generates commit-ready artifacts: an annotated architecture diagram, decision trees and an improvement roadmap. CX Codex +1 ★ 280repo stars

Project sponsors

Companies that keep this analytics open