I didn’t know when I started the project that the runbook was going to support over $2 billion of divestiture income. I just knew that the migration plans had to be bulletproof. This is what happened.

At one company; the lift-and -shift was not the norm. In a situation of divestiture, two companies must be able operate independently once the cutover has been completed. There is no period of grace.

The runbook should have accounted for cutover procedures, rollbacks, stakeholder signing-off gates, identity separation milestones, in that order. Quest Migration Manager allowed the migration of more than 500 Azure objects. Each dependency was documented prior to any issues.

It was the fact that all stakeholders could read and act on it, not just technical details. It was the ability of all stakeholders to read and act, whether they were in the identity, business, security or network fields.

Engineers create migration planning. Executives ratify business continuity instruments. The runbook is both.

Divestiture Migrations are a separate discipline. The engineers have a unique skill set.

The migration guidebook is not just a technical manual. It’s a business-continuity tool.

#Divestiture #M365Migration #AzureMigration