Migration Plan
Plan a safe technical migration (schema, data store, hosting platform, service or API version, framework, or vendor) as a staged parallel-change plan. Covers an inventory of what moves and who depends on it, a compatibility matrix for old and new code against old and new data, a data preservation plan with reconciliation checks, backfill duration math, phases with entry and exit gates, a cutover and point-of-no-return decision, a rollback per phase, and a cleanup step. Use when someone asks how to migrate a database, move to a new platform or provider, change a schema without downtime, version or retire an API, plan a cutover, or write a rollback plan. Do not use for an audit of existing code health (use codebase-audit), for the target design itself (use technical-architecture), for infrastructure definitions (use iac-setup), or for live incident handling (use coordinate-production-incident).