If your last MigrationWiz pre-stage ends two days before cutover, you may be setting yourself up for an avoidable delta problem. MigrationWiz incremental passes produce the best cutover results when the final pre-stage completes as close to the maintenance window start as possible.

The reason is simple: every hour between the end of that last pre-stage and the beginning of the cutover pass creates more inbound mail for the cutover pass to handle before users can be live in the new tenant. In high-volume environments, that gap grows fast.

With a large user population, leaving a 48-hour window between the last pre-stage and cutover can easily add hours to the cutover pass, especially when multiple accounts have heavy inbound mail.

In the acquisition migrations I ran, the 30 day and older pass served as the final pre-stage before cutover. I timed its completion to land as close to the maintenance window as practical, which reduced the delta the cutover pass had to process and helped keep the maintenance window within the committed SLA.

How much time are you leaving between the completion of your last MigrationWiz pre-stage pass and the start of your cutover window?

#BitTitan #MigrationWiz