Skip to content
Skills Library
DevOps & cloud · Planning

cloud-migration

/cloud-migration

Migrate workloads to the cloud with honest 6R triage, dependency mapping, and rehearsed cutovers with rollback. Use when planning a datacenter exit or moving systems between clouds.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Migrate workloads to the cloud with honest 6R triage, dependency mapping, and rehearsed cutovers with rollback. Use when planning a datacenter exit or moving systems between clouds.

Original author description

Migrate workloads to the cloud with honest 6R triage, dependency mapping, and rehearsed cutovers with rollback. Use when planning a datacenter exit or moving systems between clouds.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 56 lines, 400 words
SKILL.md preview
---
name: cloud-migration
description: Migrate workloads to the cloud with honest 6R triage, dependency mapping, and rehearsed cutovers with rollback. Use when planning a datacenter exit or moving systems between clouds.
---

# Cloud migration

Migrations fail on undiscovered dependencies and unrehearsed cutovers,
not on the copying. Inventory first, move in dependency order, and
never cut over anything you cannot cut back.

## Method

1. **Inventory before strategy.** Every application with: owner,
   criticality, data stores, inbound/outbound dependencies (from
   network flows and connection logs, not memory), compliance
   constraints, and licensing. The dependency map decides move groups;
   apps that chat constantly move together or suffer cross-premises
   latency.
2. **Triage with the 6Rs, honestly.** Rehost (lift-and-shift: fastest,
   deferred benefits), replatform (swap self-managed DB for managed:
   the usual sweet spot), refactor (rearchitect: only where the
   business case is explicit), repurchase (SaaS replaces it), retire
   (10-20% of any old estate; the cheapest R), retain (compliance or
   latency pins it). Default rehost/replatform under deadline;
   refactoring during migration doubles both risks.
3. **Land on a prepared foundation.** Accounts/projects, network
   (see cloud-networking), IAM baseline (see iam-design), logging, and
   IaC pipelines (see infrastructure-as-code) exist before the first
   workload arrives. Migrating onto console-clicked infrastructure
   imports the old mess into the new bill.
4. **Move data with CDC, not downtime.** Bulk-load a snapshot, stream
   changes (log-based CDC; see change-data-capture) until lag is
   seconds, verify counts and checksums continuously. For files,
   sync + delta passes. The data pipeline running clean for a week is
   the prerequisite for any cutover date.
5. **Cut over behind a switch you control.** DNS TTLs dropped in
   advance, traffic moved by weighted routing or a proxy layer,
   old system kept in sync (reverse replication if writes move) for
   the rollback window. Rehearse the whole cutover and the rollback
   on the staging copy: the rehearsal timing becomes the runbook (see
   runbook-writing). Cut low-risk groups first; the crown jewels go
   last with the practiced playbook.
6. **Close the loop per wave.** Hypercare window with old-vs-new
   dashboards (latency, errors, cost), then decommission on a date:
   the old servers left "just in case" are the migration's unfinished
   30%. Post-wave review feeds the next wave's plan.

## Boundaries

- Lift-and-shift carries oversized on-prem specs into per-hour
  billing; schedule the rightsizing pass (see cloud-cost-optimization)
  within the first quarter or the business case quietly dies.
- Latency-sensitive pairs split across premises during a long
  migration need measured tolerance, not hope; sequence them into one
  wave when in doubt.
- Cloud-to-cloud moves change the egress math and the managed-service
  mappings, but the method (inventory, CDC, rehearsed cutover) is
  identical; the trap is assuming service equivalence without testing.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
arjunprabhulal/devops-skills100MIT
j4flmao/agent-skills95MIT

Database snapshot: 13.11.2026 · package version 02cd4c3d8fee (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 87gcp-to-aws
    Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to…
  • 90cloud-architect-role
    Operate as a cloud architect who lays the landing zone, governs cost, and sequences migration for an organization. Use when asked to stand up a cloud foundation, put guardrails and cost controls in place, or plan how workloads move to the cloud.
  • 100overview
    Strategic, vendor-neutral guidance across AWS, Azure, and GCP: cloud selection, multi-cloud strategy, cross-cloud service equivalence mapping, Well-Architected design principles, migration patterns (7 Rs), and FinOps cost management. Use when deciding which cloud to use,…
  • 100gcp-to-aws
    Migrate workloads from Google Cloud Platform to AWS — plus AI and agentic workloads from any provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, migrate…
  • 90aws-migration-cutover-architect
    Plan, review, and de-risk AWS migrations and cutovers across discovery, dependency mapping, wave planning, AWS Application Migration Service, Migration Hub, test launches, acceptance tests, downtime windows, rollback, DNS, data consistency, and post-cutover validation. Use for…
  • 100azure-migrate-landing-zone-cutover
    Plan and stress-test Azure migration cutovers across landing-zone readiness, Azure Migrate assessments, dependency sequencing, permissions, rollback, and operational ownership. Use when a migration plan needs a go/no-go verdict instead of vague optimism.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.