A cutover checklist we copy into every roadmap
· James van der Berg
Every migration roadmap we deliver ends with an appendix derived from this list. Wording changes per client; the categories rarely do.
Traffic and naming
- Lower TTL on public DNS records 48 hours before switch
- Confirm health-check paths match what the load balancer actually calls
- Verify webhook URLs registered at partners point to the new hostname
Secrets and identity
- Rotate API keys that were ever copied into tickets
- Test service-to-service auth from the new subnet, not just from developer laptops
- Document which break-glass accounts remain active for 72 hours post-cutover
Background work
- Pause or drain queues before final data sync; note resume commands
- Compare cron schedules in old and new environments line by line
- Ensure dead-letter queues are monitored with the same alerts as primary queues
People on the phone
- Support desk script with “known slow” symptoms versus outage symptoms
- Named decision-maker for rollback with a single communication channel
- Post-cutover retrospective date already in calendars
Need a roadmap built around your dates? See our migration roadmap engagement.