MicrosoftMicrosoftWhile good to see as a starting point, it's not an option for me until there is the ability to pre-sync data and then control finalization of the sync and cutover. Setting a "not before date" is inadequate. Particularly when dealing with large mailboxes, communicating that at some point any time after xx-xx-xxxx the mailbox will cutover is not feasible option.
MicrosoftThank you for considering our product. For mailboxes, the sync will begin when the migration is submitted. At this time, admins also provide a "Complete After Date". The Complete After Date will be the earliest that users will feel an impact of the migration: mailboxes will cut over, OneDrives will move, and Teams data will move.
The amount of time required for sync is based on the total amount of content that is moving. We recommend customers submit migrations to allow for up to two weeks of syncing given average migration batch sizes.
This product provides two ways to be more precise on the actual cutover timing: 1) customers can view when the mailboxes have synced (the Exchange Mailbox status for the user will be "synced"), and 2) the Complete After Date can be updated.
In the case of a large mailbox migration, customers can do the following: 1) submit the batch with ample time for syncing, say 2 weeks in advance of target migration cutover date, 2) provide a Complete After Date with the intended cutover date or a date further in the future, 3) monitor the batch for the synced state of all mailboxes, and 4) update the Complete After Date once mailboxes have all synced to the precise date and time that cutover is acceptable.
Please let us know what other questions or concerns you have!
