Most cutover plans describe how traffic moves to the new cloud in careful steps. The rollback section is usually one line: revert if something goes wrong. That line hides the hardest part. By the time a cutover starts, DNS records have changed, routes have been withdrawn in one place and announced in another, connections are open on paths that did not exist an hour earlier, and some data has already been written on the new side. Reversing a cutover is not the forward plan played backwards. It is its own network design, and it needs to be written, timed, and tested before the window opens.
1. Name the point of no return before you start
Every cutover has a moment after which a simple rollback stops being possible. It might be the first write accepted only on the new side, the moment an old queue is drained and deleted, or the step where a shared database changes format.…