Zero-Downtime Migration and Cutover Plans
Get phased database, system, and infrastructure migration plans with compatibility gates, data validation, and executable rollback paths.
Before & after
Same prompt, same agent — the only difference is the skill.
Database migrations are risky because they can break your application if something goes wrong. You need to think about your rollback strategy first in case you need to abort. Testing the migration on a copy of your production database is important to catch issues before you do it for real. You'd want to have a communication plan so your team knows what's happening. Compatibility checks are important—make sure your application code is compatible with the new schema before you migrate. Timing matters too; you want to do it during low-traffic hours. Having a runbook that documents every step helps.
I'll architect a zero-downtime database migration with compatibility checks, staged rollout, and explicit rollback paths. MIGRATION STRATEGY PHASE 0: DUAL-WRITE SETUP (24 hours before cutover) Deploy code that writes to BOTH old and new database simultaneously. Reads still come from old DB. Verify data consistency: new DB receives same writes as old DB. PHASE 1: MIGRATION RUN (low-traffic window, approximately 2 hours) Backfill data: copy all old DB data to new DB (validate row counts, checksums match) Run data integrity checks: spot-check 1000 random rows across tables for correctness PHASE 2: READ SWITCHOVER (5-minute window) Update app to READ from new DB (still writing to both) Monitor query latency, error rates for 30 minutes If anything breaks: ROLLBACK (switch reads back to old DB in 30 seconds; dual-write is still active) PHASE 3: CLEANUP (hours 4-24 after cutover) Verify old DB has received no writes for 6 hours Decommission old database (after keeping backup for 7 days) ROLLBACK PLAN T+0 to T+6 hours: full rollback available (dual-write still active, revert to old DB, ~30 sec downtime) T+6 to T+48 hours: rollback needs careful data reconciliation (dual-write off) T+48 hours: rollback risky (data diverged, manual work needed) RUNBOOK CHECKLIST Backup old DB before any migration Test migration on staging clone Identify which queries change performance (index new DB appropriately first) Notify ops team of maintenance window Monitor CPU, disk, connection pools during migration Plan communication: status page, Slack updates DELIVERABLE Step-by-step migration plan with checkpoints, rollback triggers, monitoring dashboard config, and runbook.
About this skill
“We can switch traffic back” stops being a rollback plan once the new system has accepted writes. This skill turns database migrations, infrastructure cutovers, and system replacements into phased plans that account for mixed versions, data movement, and the moment reversal becomes unsafe.
What it does
- Maps compatibility across old and new applications, schemas, APIs, workers, and infrastructure.
- Chooses expand-contract, replication, staged traffic shifts, or a bounded maintenance window based on actual constraints.
- Defines backfill ordering, concurrent-write handling, reconciliation, and authoritative data ownership.
- Builds cutover gates around correctness, replication lag, errors, latency, and recovery time.
- Specifies rollback triggers, commands or control actions, data consequences, and points of no return.
- Reviews existing plans for missing dependencies, unsafe dual writes, and unsupported zero-downtime claims.
What you get
A migration plan sized to your request, with a phase sequence, compatibility checks, validation evidence, cutover instructions, and recovery paths. Missing details become explicit assumptions and hold points, so a provisional plan stays useful without pretending it is ready to execute.
Best for
Engineers and technical leads moving production databases, replacing services, changing infrastructure, or reviewing a high-risk cutover before scheduling it.
SKILL.md preview
---
name: zero-downtime-migration-and-cutover-plans
description: >-
Plans database, system, and infrastructure migrations by mapping mixed-version compatibility, authoritative data ownership, validation gates, and phase-specific recovery paths. Use when the user says "plan a zero-downtime migration", "move our production database", "replace this service without breaking clients", "review our cutover plan", "can we roll back after switching writes?", "our backfill keeps falling behind", or "my migration keeps locking the table".
---
# Zero-Downtime Migration and Cutover Plans
… (sign up to view the full skill)Featured in
More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.