Large BitTitan programs tend to run more smoothly when users move in planned waves instead of one event. Smaller groups across multiple maintenance windows limit how many people each cutover affects and keep hypercare from becoming unmanageable.

Common wave criteria:

• Geography. Move everyone in an office together so local IT support can align coverage.
• Business unit. Cut over self-contained departments together to reduce disruption from cross-team dependencies.
• Mailbox size. Start with smaller mailboxes to confirm configuration and establish migration velocity before committing larger ones.

The tradeoff is coexistence. While some users are in the destination tenant and others remain in the source, cross-tenant meeting and calendar dependencies surface. Without coexistence federation, users who have cut over can’t see free/busy details for users still in the source tenant. Wave order should reflect which groups have the most cross-team meeting dependencies.

What are your wave criteria, and have you checked the coexistence impact between waves?

#BitTitan #MigrationWiz