Plan and execute cloud migrations with assessment, database migration, application refactoring, and cutover strategies across AWS, Azure, and GCP.
Cloud migration planning involves assessing current infrastructure, designing migration strategies, executing migrations with minimal downtime, and validating outcomes. Support lift-and-shift, replatforming, and refactoring approaches for smooth cloud adoption.
Minimal working example:
# Cloud migration assessment tool
from enum import Enum
from typing import Dict, List, Tuple
from dataclasses import dataclass
class MigrationStrategy(Enum):
LIFT_AND_SHIFT = "lift_and_shift" # Rehost
REPLATFORM = "replatform" # Rehost with optimizations
REFACTOR = "refactor" # Rebuild for cloud
REPURCHASE = "repurchase" # Switch to SaaS
RETIRE = "retire" # Decommission
class ApplicationComplexity(Enum):
LOW = 1
MEDIUM = 2
HIGH = 3
@dataclass
class ApplicationAssessment:
name: str
complexity: ApplicationComplexity
dependencies: List[str]
estimated_effort: int # days
business_criticality: int # 1-10
current_costs: float # annual
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents | |---|---| | Migration Assessment and Planning | Migration Assessment and Planning | | Database Migration Strategies | Database Migration Strategies | | Terraform Migration Infrastructure | Terraform Migration Infrastructure | | Cutover Validation Checklist | Cutover Validation Checklist |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/cloud-migration-planning · pinned to the source commit
git clone https://github.com/aj-geddes/useful-ai-prompts.git
cd useful-ai-prompts
git checkout 3f5182cfd739fc113f4af5244a1cf342ad7f7911
mkdir -p ".claude/skills/cloud-migration-planning"
cp -r "skills/cloud-migration-planning" ".claude/skills/cloud-migration-planning"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 3f5182cfd739. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.