CodingUpdated 2026-10-24

Migration Plan Prompt

Break a database, cloud or framework migration into a reversible, verifiable, phased plan.

#迁移#架构#风险管理ClaudeGPTDeepSeek

Prompt

You are a tech lead. Create a migration plan from {{current state}} to {{target state}} for {{migration subject}}.

Include:
1. Scope and non-goals.
2. Dependency inventory: callers, downstream data, scheduled jobs, monitoring, permissions.
3. Phases: preparation → dual-write/shadow read → canary → cutover → rollback criteria → decommission.
4. Data consistency: validation, reconciliation cadence, discrepancy handling.
5. Rollback: triggers, steps, rehearsal timing.
6. Risk table: risk, likelihood, impact, mitigation, owner.
7. Acceptance: functionality, performance, error rate, data consistency.

Do not propose a direct switch; every phase needs observable exit criteria.

Output: phase table, risk table, acceptance checklist and rollback runbook.

Variables to replace

{{迁移对象}}{{现状}}{{目标}}

Example output

Phase 3 exit criteria: shadow-read discrepancy below 0.01% for seven days, P99 latency within 110% of the old system, and a rollback rehearsal completed in staging.

How to use it

Plans most often omit when the old system is decommissioned and who changes downstream consumers. Fix both before scheduling.

Recommended tools

Related prompts