If you are adding accounts to an active BitTitan migration project mid pre-stage and not revisiting the length of your cutover window, you are taking on schedule risk that is easy to miss until it is too late.

MigrationWiz projects allow you to add users after the project exists and even after pre-stage passes have begun. Operationally that is convenient, but it changes the timing math.

Users added after pre-stage is already underway do not benefit from the same runway as the original list. A mailbox added 10 days before cutover did not receive the 90-day, 60-day, and 30-day pre-stage passes the initial batch had. As a result, the cutover pass for that late-added account has far more data to move, which can extend the maintenance window.

The fix is to treat late additions as a separate acceleration effort. As soon as those accounts are added, run a full migration pass specifically for them, then run additional passes during the days leading up to cutover. The objective is to shrink the delta the cutover pass must handle so it more closely matches the delta size of the original batch.

Do you have a defined process for late user additions that accounts for their reduced pre-stage time instead of assuming they will behave like the original group?

#BitTitan #MigrationWiz