Write a Migration Rollback Plan

Write a migration rollback plan for the following change:

System / service: [SERVICE OR DATABASE]
Migration type: [SCHEMA, DATA, INFRA, CONFIG, FEATURE FLAG, ETC.]
Environment sequence: [DEV → STAGING → PROD]
Change summary: [WHAT IS CHANGING]
Owner / on-call: [NAME OR ROLE]
Maintenance window: [START–END OR N/A]
Dependencies: [SERVICES, QUEUES, JOBS, CLIENTS]
Success criteria for go-live: [CHECKS THAT CONFIRM SUCCESS]
Known risks: [RISKS]

Requirements:
1. Describe pre-migration backups, freeze windows, and verification steps.
2. Define go / no-go criteria before production execution.
3. Provide a step-by-step forward migration runbook and a matching rollback runbook.
4. Include time estimates, responsible roles, and communication points (Slack/status page).
5. Specify data integrity checks, monitoring signals, and error thresholds that trigger rollback.
6. Cover partial failure scenarios (migration succeeds, app fails; one replica lags; dual-write issues).

Deliverables:
1. A clear rollback plan document with Forward Plan, Rollback Plan, and Validation sections.
2. A checklist that can be used during the live change.
3. A post-incident / post-migration notes template.