Menu

Individual skill

platform-migration

0upvotes

Migrating applications between platforms — planning, data movement, and cutover — vendor-neutral methodology.

skills/platform-migration/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Moving an app between platforms (PaaS to PaaS, PaaS to cloud, cloud to PaaS)
is a high-stakes project: data must move intact, downtime must be minimal,
and rollback must be possible. This skill covers the migration methodology —
inventory, strangling, dual-running, and cutover — that works regardless of
source and destination.

## When to use

- Planning a move between hosting platforms or cloud providers
- Estimating migration effort and risk
- Moving databases with minimal downtime
- Cutting over DNS and traffic safely
Back to top