All perspectives
SD-WAN·July 15, 2025·7 min read
Why your SD-WAN migration needs a rollback plan before a single command
The cheapest insurance in network engineering: a tested, written rollback that any engineer on call can execute under pressure.
Rollback is not a slide in the change record. It is a tested sequence of commands, with timing, decision points, and a named owner who can execute it without a second opinion at three in the morning.
On SD-WAN migrations we write the rollback first, then the forward plan. If we cannot describe — in plain prose — how the site returns to its prior state within fifteen minutes, the migration is not ready, regardless of how elegant the overlay design looks.
What a real rollback contains
- The exact configuration archive the site is rolling back to, with a checksum and a known-good restore date.
- The named engineer on call, their out-of-band path, and a secondary contact.
- The decision criteria — what specifically triggers rollback, with thresholds, not vibes.
- The communication plan: who is told, when, and through which channel.
"A migration without a tested rollback is not a migration. It is a hope."