AI Prompt for Zero-Downtime Migration Planning
Plan a database, API, or system migration with rollback strategy, data integrity checks, and phased rollout steps.
What it does
Generates a phased migration plan for moving from one system to another — database schema changes, API version upgrades, service replacements, or infrastructure moves. The plan includes the parts that engineers usually forget until they’re mid-migration: rollback procedures, data integrity verification, and the specific order of operations that avoids downtime.
Example output
A 3–4 line excerpt of what this prompt produces.
Phase 2: Dual-write with verification (Days 4–10) All writes go to both old and new datastores. Read path stays on old. Nightly reconciliation job compares row counts and checksums — any divergence >0.01% halts Phase 3 entry.
Rollback procedure: Kill the dual-write flag (env var, no deploy needed). New datastore becomes orphan; old datastore has received every write and is fully consistent. Data cleanup: truncate new datastore tables, re-run seed job. Estimated rollback time: <3 minutes to flag flip, <20 minutes to full cleanup.
Prompt structure
The sections this prompt guides the model through.
- 1. Migration Strategy
- 2. Pre-Migration Checklist
- 3. Phase Plan
- 4. Data Integrity Verification
- 5. Post-Migration Cleanup
- 6. Risk Register
Opening lines
The first lines of the prompt itself.
Create a migration plan for the following change.…
One rule from the prompt
A single rule — the full prompt contains more.
Break the migration into discrete, independently deployable phases. Each phase must have exact rollback steps — if you can't roll back a phase, you've scoped it too large. If the constraints make zero-downtime impossible, say so explicitly.
Unlock the full prompt
Part of the Engineering Toolkit Pack — 7 prompts for CHF 19.
View pack — CHF 19