The project plans stated 200 mailboxes. BitTitan’s migration scan revealed something different. Migrations can be held together or fall apart by the gap that exists between the documented environment, and the actual environmental environment.

The initial scope of the company was clean. The scan started.

Undocumented shared mailboxes. Permission structures not matching the documentation of the environment. Mailboxes that are too large or small require special handling. Archive boxes outside of the original scope. There was no project plan because nobody was aware of the existence of these mailboxes.

The wave schedule needed to be reconstructed based on the scan results. Batch sequencing had to be changed. Timeline stress was real. The adjustment held.

To reduce manual setup risk at large scale, we created 15 Group policy objects to facilitate the migration of file sharing to Azure Files. Automation took the place of manual configuration.

Post-migration remediation was performed in 6 counties, resulting in a predictable ticketing distribution: Outlook reconfiguration, gaps in delegated access, and re-enrollment of mobile devices. Triage took less time because the environment had been mapped out before migration.

The environment documentation handed to engineers by organizations is almost never complete.

The project plan is the place to start. Pre-migration scans are where you can find out exactly what you have to deal with.

#BitTitan #MigrationWiz #EmailMigration