When something breaks at 2 AM during cutover, does your team open the runbook or start texting people?

I designed the Azure Migration Runbook that was used across 3 successful migration plans connected to billions in divestiture revenue. A runbook at that scale isn’t a checklist.

It’s the operating manual for every person on the migration team at every point in the cutover window.

What made it useful: decision trees for the failure scenarios most likely to occur, not generic guidance. Specific rollback triggers with thresholds, not “if something goes wrong.”

Contact escalation paths tied to workloads, not organizational titles.

Most runbooks fail because they describe what the migration does, not what the team does when it breaks. Those are two completely different documents.

What’s missing from your current migration runbook?

#MigrationRunbook #AzureMigration #Migration