During BitTitan pre-stage, are changes being made to source tenant mail flow in a way that alters the content you are migrating?

Each BitTitan pre-stage pass migrates whatever mailbox content exists in the source tenant at the time that pass runs. If mail flow configuration shifts during pre-stage, what BitTitan migrates in later passes can change as well.

Examples of source tenant changes that can impact pre-stage results include: adding or modifying transport rules that delete, redirect, or alter messages; changing mailbox quotas in ways that trigger message deletion when storage limits are reached; purging Deleted Items as part of a mailbox cleanup effort; and enabling Litigation Hold changes that affect what appears in the standard mailbox view.

This is especially relevant in acquisition migrations, where the source tenant is often managed by the company being acquired, not by the acquiring IT organization. Source tenant admins can make changes during pre-stage that affect migration outcomes without the migration team realizing it.

To control this risk, establish a source tenant change freeze for mail flow configuration throughout the BitTitan pre-stage period. Any modifications to transport rules, mailbox quotas, or retention policies should be reviewed by the migration team before they are implemented.

Have you established a source tenant mail flow configuration change freeze for the duration of your BitTitan pre-stage period?

#BitTitan #MigrationWiz