Part of a good migration plan is the Roll Back or Back Out plan and the fact that you had one was commendable in and of itself. You would be surprised at how many times I have seen migrations without a Roll Back plan. Unforeseeable things happen all the time, especially in an environment where there are many people and even teams working a migration, and that is what the Back Out plan is for. Now, the fact that this was caught in a Test environment, to me, should be considered a Success. The success is that we uncovered an issue that hadn't been thought of or covered in the Development phase and that we prevented this from happening in the Production environment. Whenever doing these things we need to have these "Dry Runs" in the Test environment, which should be as close to mimicking the Production environment as possible, and as many Dry Runs as it takes before we have something that we are 99.99% sure is going to work in our Production environment because we worked out ALL the kinks in the Test environment.

Great Job to you and your team(s) for having the Back Out plan and for executing it when it was necessary.

Hopefully your next Dry Run will be the one that tells you that you are now ready for a push to Production.

Merrill