This skill should be used when the user asks to "plan a cloud migration", "assess workloads for migration", "design a landing zone", "create migration waves", or mentions 7R, rehost, replatform, refactor, lift-and-shift, or migration factory. [EXPLICIT] It produces comprehensive migration plans covering 7R assessment, workload analysis, wave planning, landing zone design, cutover execution, and post-migration optimization. [EXPLICIT] Use this skill whenever the user discusses moving workloads to the cloud, even if they don't explicitly ask for "cloud-migration". [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/migration-patterns.mdtemplates/output.docx.mdtemplates/output.htmlCloud migration moves workloads from on-premises or legacy environments to cloud platforms. This skill produces comprehensive migration plans covering 7R assessment, workload analysis, wave planning, landing zone design, execution patterns, and post-migration optimization. [EXPLICIT]
Migrar sin estrategia 7R es mover problemas de datacenter a la nube. Cada workload merece una clasificación explícita (rehost, replatform, refactor, repurchase, retire, retain, relocate). Wave planning reduce riesgo. Cutover rehearsal es obligatorio — nunca se hace un cutover en producción sin haber ensayado en staging.
The user provides a migration program or portfolio name as $ARGUMENTS. Parse $1 as the program/portfolio name used throughout all output artifacts. [EXPLICIT]
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40% — S1 7R classification + S3 wave plan + S5 cutover) | técnica (full 6 sections, default)Before generating migration plan, detect existing infrastructure context:
!find . -name "*.tf" -o -name "*.yaml" -o -name "inventory*" -o -name "*.csv" | head -20
If reference materials exist, load them:
Read ${CLAUDE_SKILL_DIR}/references/migration-patterns.md
Classify every workload using the 7R framework to determine optimal migration strategy. [EXPLICIT]
7R Strategies:
Classification Decision Matrix:
| Factor | Rehost | Replatform | Refactor |
|---|---|---|---|
| Business criticality | Low-medium | Medium | High (strategic) |
| Technical complexity | Any | Low-medium | High (code access required) |
| Timeline pressure | Urgent (<3 months) | Moderate (3-6 months) | Long-term (6-18 months) |
| Cloud benefit needed | Minimal | Moderate | Maximum |
| Budget | Low ($) | Medium ($$) | High ($$$) |
Output: Application-by-application classification table with strategy, rationale, effort estimate, risk level, and wave assignment.
Automated Discovery Tools:
| Tool | Provider | Method | Discovers |
|---|---|---|---|
| AWS Application Discovery Service | AWS | Agent or agentless | Server config, utilization, network connections, process data |
| AWS Migration Hub | AWS | Aggregator | Unified view across discovery + migration tools |
| Azure Migrate | Azure | Agent or appliance | Servers, databases, web apps, VDI; includes assessment + migration |
| Azure App Service Migration Assistant | Azure | Web app scan | .NET/Java web app readiness for Azure App Service |
| Google Cloud Migration Center | GCP | Agent or API import | Technical fit, TCO, migration complexity scoring |
| Cloudamize | Multi-cloud | Agent-based | Performance profiling, right-sizing, cost projection, dependency mapping |
| Flexera One | Multi-cloud | CMDB integration | License optimization, cloud cost modeling, portfolio rationalization |
Application Inventory Fields: Name, owner, business unit, criticality tier (T1-T4), technology stack, infrastructure requirements (CPU, memory, storage, network), performance baseline (response time, throughput, utilization), compliance requirements. [EXPLICIT]
Dependency Graph:
Data Gravity Analysis:
(data_volume_TB * access_frequency * compliance_anchors) -- higher score = harder to move(data_size_GB / bandwidth_Gbps) * 8 / 3600 = hours + 30-50% verification overheadApplication Difficulty Scoring:
(technical * 0.3) + (dependencies * 0.25) + (data_gravity * 0.25) + (compliance * 0.2)Migration Factory Model:
A migration factory standardizes repeatable processes across waves. Structure:
| Role | Responsibility | Staffing |
|---|---|---|
| Factory Manager | Wave scheduling, escalation, metrics | 1 per program |
| Migration Architect | Technical design per application | 1 per 10-15 apps |
| Migration Engineer | Execute rehost/replatform using tooling | 2-4 per wave |
| Test Lead | Validation scripts, acceptance criteria | 1 per wave |
| App Owner (from business) | Requirements, UAT sign-off, cutover approval | 1 per application |
Wave Design:
Pilot Selection Criteria:
Wave Calendar:
Account Structure:
Networking:
Security Baseline:
Governance Guardrails:
Rehost Tools: AWS MGN (Application Migration Service), Azure Migrate/Site Recovery, GCP Migrate for Compute Engine. Process: install agent, replicate, test, cutover, decommission.
Database Migration: Homogeneous (native replication, DMS continuous) or heterogeneous (schema conversion + DMS). Zero-downtime via continuous replication. Validate: row counts, checksums, sample comparison.
TCO Calculator Methodology:
| Cost Category | On-Premises | Cloud |
|---|---|---|
| Compute | Hardware amortization (3-5yr) | Reserved + on-demand instances |
| Storage | SAN/NAS, disk replacement | S3/EBS tiered pricing |
| Facilities | Power, cooling, DC lease ($8-15/kW/mo) | Included |
| Staff | FTE * fully loaded cost | Reduced (managed services) |
| Licenses | On-prem perpetual or subscription | BYOL, cloud-native, or included |
| Network | WAN circuits, load balancers | Egress fees, cross-AZ traffic |
| Migration (one-time) | N/A | Dual-run, tooling, consulting, training |
Cutover Rehearsal Checklist:
Perform a full dress rehearsal 1-2 weeks before each production cutover:
Rollback Decision Criteria:
Trigger rollback if ANY of the following occur during cutover:
| Condition | Threshold | Action |
|---|---|---|
| Error rate spike | >5x baseline for 15+ minutes | Immediate rollback |
| Latency degradation | P99 >3x baseline for 15+ minutes | Immediate rollback |
| Data integrity failure | Any checksum mismatch on critical tables | Immediate rollback |
| Functionality gap | Any Tier 1 feature non-functional | Immediate rollback |
| Cutover window exceeded | >80% of planned window with steps remaining | Assess and likely rollback |
| Monitoring blind spot | Key dashboards/alerts not functioning | Pause and remediate; rollback if >30 min |
Common Anti-Patterns:
| Anti-Pattern | Consequence | Mitigation |
|---|---|---|
| Skip discovery; migrate by guesswork | Missed dependencies cause outages during cutover | Run automated discovery 30+ days |
| Migrate without application owner | No UAT, no sign-off, unclear accountability | Require named owner before wave assignment |
| No cutover rehearsal | Surprises on go-live night, panic rollbacks | Mandatory dress rehearsal for every wave |
| Big-bang migration of entire portfolio | Maximum blast radius, no learning curve | Wave-based with pilot first |
| Underestimate data transfer time | Cutover window exceeded, forced rollback | Calculate transfer time + 50% buffer; use continuous replication |
| Retire nothing | Cloud costs add to existing costs | Enforce retire/retain classification in 7R assessment |
| No rollback plan | Cannot revert when issues found | Define rollback triggers and test procedure |
Parallel-Run Validation:
Functional Validation: Automated test suites, manual smoke testing of critical flows, integration testing with dependent systems, data validation.
Performance Baseline: Compare cloud vs. on-premises for latency, throughput, resource utilization. Document regressions.
Cost Optimization (post-migration):
Decommission:
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Rehost | Speed, low risk | No modernization | Datacenter exit deadline |
| Replatform | Some cloud benefit, moderate effort | Partial optimization | Managed DB, container runtime swaps |
| Refactor | Full cloud-native benefit | High effort, long timeline | Strategic, 5+ year lifecycle apps |
| Migration Factory | Repeatable, metrics-driven, scalable | Setup overhead, process rigidity | >20 applications, enterprise programs |
| Big Bang | Clean cutover, no hybrid period | High risk, long outage | Small portfolios (<10 apps), maintenance windows |
| Wave-Based | Incremental risk, learning curve | Hybrid period, dual costs | Large portfolios, enterprise migrations |
| Direct Connect | High bandwidth, low latency | Cost, 4-8 week lead time | Large data (>5TB), long-term hybrid |
Datacenter Exit with Hard Deadline: Favor rehost for speed. Accept technical debt. Plan post-migration optimization waves. Prioritize by lease expiry. [EXPLICIT]
Shared Database Serving Multiple Applications: Cannot migrate database independently. Options: migrate all consumers together, introduce API layer to decouple, or replicate and gradually cut over consumers. [EXPLICIT]
Mainframe Workloads: Specialized tools (Micro Focus, AWS Mainframe Modernization, Azure Mainframe Migration). Replatform to cloud-hosted emulation first, then gradually refactor. [EXPLICIT]
Compliance-Restricted Data: Data residency may limit regions. Encryption requirements affect replication tooling. Audit trail must be maintained through migration. [EXPLICIT]
No Source Code Available: Rehost is the only viable strategy. Containerization may be possible for binary apps. Evaluate repurchase with SaaS alternative. [EXPLICIT]
Before finalizing delivery, verify:
| Format | Default | Description |
|---|---|---|
markdown | Yes | Rich Markdown + Mermaid diagrams. Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
Default output is Markdown with embedded Mermaid diagrams. HTML generation requires explicit {FORMATO}=html parameter. [EXPLICIT]
Primary: A-01_Cloud_Migration_Plan.html -- Executive summary, 7R classification table, dependency map, wave plan, landing zone design, execution playbook, validation checklist, cost optimization targets.
Secondary: Application inventory spreadsheet, wave calendar, cutover runbook, rollback procedures, TCO comparison, decommission checklist.
Author: Javier Montano | Last updated: March 18, 2026
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.