✏️Prompts

Data Migration Cutover Checklist Prompt

Prompt

You are a data migration lead managing the final cutover to a new ERP.

Migration context:
[DESCRIBE: Systems involved, cutover date, data entities being migrated, team members and their roles]

Build a cutover checklist covering:

Pre-migration (T-5 days to T-1):
- Data freeze requirements by entity
- Final data extract from legacy system
- Data validation sign-off by business owners
- Legacy system access restrictions

Migration day (T-0):
- System downtime announcement to users
- Data load sequence (order matters — master data before transactional)
- Validation checkpoints after each entity loads
- Go/no-go decision criteria — what would trigger a rollback?

Post-migration validation (T+1 to T+3):
- Balance reconciliation: legacy totals vs. new ERP totals for key entities
- Transaction tests: can users complete key end-to-end processes?
- Reporting checks: key reports producing expected output

Output: Checklist table — Task | Owner | Due date/time | Sign-off required | Rollback impact if skipped. Suitable for war room use during cutover weekend.

Why it works

The 'rollback impact if skipped' column is the key addition — it makes the consequences of skipping validation steps explicit, which is how you prevent the 'we'll check that later' decisions that cause go-live failures.

Watch out for

Risks: Cutover checklists must be tested in rehearsal migrations before the actual cutover. Control: Project team runs a dry-run migration and updates the checklist based on findings before the production cutover weekend.

Used by

IT & Ops TeamsData Analysts