← Back to all products

Cloud Migration Playbook

$49

Step-by-step migration framework: assessment, planning, execution, and validation with rollback procedures.

📁 22 files

JSONPythonTerraformYAMLMarkdownAWS

📄 Product Preview

Try the interactive reader and demo tools below, or get the full product with all content unlocked.

📖 Interactive Reader (Free Preview) ⚙ Try Demo Tools 📦 Download Free Sample

📁 File Structure 22 files

cloud-migration-playbook/ ├── LICENSE ├── README.md ├── cloudformation/ │ └── migration-hub-setup.yaml ├── docs/ │ ├── architecture.md │ ├── migration_phases.md │ ├── rollback_procedures.md │ └── validation_checklist.md ├── examples/ │ ├── assessment_template.json │ └── wave_plan.yaml ├── free-sample.zip ├── guide/ │ ├── 01_what-s-included.md │ ├── 02_quick-start.md │ └── 03_faq.md ├── index.html ├── scripts/ │ ├── dependency_mapper.py │ ├── migration_readiness_checker.py │ ├── rollback_planner.py │ └── wave_planner.py └── terraform/ ├── dms_replication.tf ├── dns_cutover.tf ├── landing_zone.tf └── variables.tf

📖 Documentation Preview README excerpt

Cloud Migration Playbook

A complete, battle-tested framework for migrating workloads to AWS: from initial assessment through validation, with rollback procedures and IaC templates at every stage.

This playbook is the distillation of real migration projects -- covering the 6 R's strategy, wave-based migration planning, landing zone setup, database migration via DMS, DNS cutover automation, and validation checklists. Built for cloud architects and migration leads responsible for moving production workloads.

What's Included

Category	Files	Description
Terraform	`landing_zone.tf`, `migration_hub.tf`, `dns_cutover.tf`, `dms_replication.tf`, `variables.tf`	IaC for landing zone, Migration Hub, DMS, and DNS cutover
CloudFormation	`migration-hub-setup.yaml`	AWS Application Migration Service setup
Scripts	`migration_readiness_checker.py`, `dependency_mapper.py`, `rollback_planner.py`, `wave_planner.py`	Assessment, dependency mapping, rollback planning, wave scheduling
Docs	`architecture.md`, `migration_phases.md`, `rollback_procedures.md`, `validation_checklist.md`	Deep reference docs for every migration phase
Examples	`wave_plan.yaml`, `assessment_template.json`	Ready-to-use planning documents

Migration Strategy Overview (The 6 R's)


┌─────────────┬──────────────┬───────────────────────────────────────────┐
│ Strategy    │ Effort       │ When to use                               │
├─────────────┼──────────────┼───────────────────────────────────────────┤
│ Rehost      │ Low          │ Lift-and-shift. Fast migration, optimize  │
│ (Lift&Shift)│              │ later. Best for meeting a deadline.       │
├─────────────┼──────────────┼───────────────────────────────────────────┤
│ Replatform  │ Low-Medium   │ Minor cloud optimizations during move.    │
│ (Lift&Tinker│              │ E.g., move to managed DB (RDS).          │
├─────────────┼──────────────┼───────────────────────────────────────────┤
│ Refactor    │ High         │ Rearchitect for cloud-native. Containers, │
│             │              │ serverless, microservices.                │
├─────────────┼──────────────┼───────────────────────────────────────────┤
│ Repurchase  │ Medium       │ Replace with SaaS. E.g., on-prem CRM →   │
│             │              │ Salesforce, Exchange → O365.              │
├─────────────┼──────────────┼───────────────────────────────────────────┤
│ Retire      │ None         │ Decommission. No longer needed.           │
├─────────────┼──────────────┼───────────────────────────────────────────┤
│ Retain      │ None         │ Keep on-prem. Not a fit for cloud yet.    │
└─────────────┴──────────────┴───────────────────────────────────────────┘

Prerequisites

AWS Account with Organizations set up (recommended)
Terraform >= 1.5.0
Python >= 3.10 (stdlib only -- no pip packages needed)
AWS CLI configured with admin credentials for the migration account
Network connectivity between source and target environments (VPN or Direct Connect)

Quick Start

1. Run Migration Readiness Assessment


python3 scripts/migration_readiness_checker.py
# Generates a scored assessment of your migration readiness

2. Map Application Dependencies

... continues with setup instructions, usage examples, and more.

📄 Code Sample .py preview

scripts/dependency_mapper.py #!/usr/bin/env python3 """ Application Dependency Mapper ============================== Builds a dependency graph of applications and generates migration wave groupings based on dependency relationships. Why dependency mapping matters: If App A depends on App B's database, you can't migrate App A first -- the latency of cross-network database calls would kill performance. Either migrate B first, or migrate both in the same wave. This tool: 1. Generates sample application inventory with dependencies 2. Builds a directed dependency graph 3. Performs topological sorting to determine safe migration order 4. Groups applications into waves that respect dependencies 5. Visualizes the dependency graph as ASCII art Usage: python3 dependency_mapper.py python3 dependency_mapper.py --format json python3 dependency_mapper.py --output deps.json No external dependencies -- Python stdlib only. """ import argparse import json import logging import random from collections import defaultdict, deque from dataclasses import dataclass, asdict, field from datetime import datetime from pathlib import Path logging.basicConfig(level=logging.INFO, format="%(asctime)s [%(levelname)s] %(message)s") logger = logging.getLogger(__name__) @dataclass class Application: """Represents an application in the migration portfolio.""" app_id: str name: str tier: str # "web", "app", "data", "middleware", "infra" criticality: str # "critical", "important", "standard", "low" migration_strategy: str # One of the 6 R's dependencies: list[str] # App IDs this depends on environment: str # ... 253 more lines ...

Buy Now — $49 Back to Products