BitTitan is conducting a limited preview for coexistence in Office 365 tenant migration scenarios where there is a change in domain name. Learn more about this new feature below or head over to the BitTitan Help Center for more information.
**Update: due to significant interest in this preview, we are unable to accommodate all requests at this time. Stay tuned for more updates regarding T2T coexistence in the near future. As always, happy migrating!
The need to move data between cloud environments and, more specifically Office 365 tenants, is an increasingly growing market and one that BitTitan wants to help automate. We frequently see this scenario arise during an acquisition or divestiture where businesses or individual units are being combined or separated. In fact, 2018 was the first year BitTitan saw cloud-to-cloud migration projects reach parity with on-prem-to-cloud moves – a trend we expect to continue in 2019.
BitTitan recently introduced an automated Office 365 tenant to tenant (T2T) migration solution, where the power of MigrationWiz helps reduce the time and effort needed to complete these complex migrations. But when IT is tasked with a T2T migration and a cutover is not feasible, migrations are done in batches or stages. This limits the impact to the end user during the migration while IT benefits from more flexibility in their project timeline.
These types of migrations generally require a feature called coexistence so that the users split between the Source and Destination can seamlessly communicate. This feature enables end users to be able to see users on the other side, including their free/busy calendar status and their contact details.
Our new migration path will allow for automatic user discovery in the Source tenant so that we can create and license those users in the Destination tenant. During the migration, we will allow for seamless mail coexistence as the stages of the migration progress. In addition to mail coexistence, we also enable seamless Free/Busy coexistence, so that the users don’t need to know who is migrated or not.
We take this one step further through the option to migrate Distribution Lists and Groups. After they are successfully migrated, they can be synchronized at any point in the migration to pick up the changes at the Source and update the Destination.
Configuring Coexistence in MigrationWiz
Using the same wizard as building a regular project, when you select endpoints that are Office 365 for Source and Destination, you will be presented a new option to enable tenant to tenant coexistence. Simple inputs of Source and Destination domains along with checkboxes for Distribution Lists and Groups help to feed the automation engine.
Once the automation takes over, Organizational Sharing and Individual Sharing are setup on the Source and Destination tenants. All the users in the source tenant are then automatically discovered and mail contacts with an external email address of the primary domain are created in the Destination tenant. This will allow for reverse free/busy look up from the Destination to the Source and enables mail-routing from the Destination back to the Source.
As soon as the automation is completed, the users are imported into the MigrationWiz project, where the User Migration Bundle can be applied. Mailboxes can be pre-staged and migrated; with the Outlook on the desktop being updated with DeploymentPro.
Currently, tenant to tenant coexistence is available only for projects in which there is a change in domain name and with the purchase of a User Migration Bundle license. To learn more about coexistence, read our migration guide covering this scenario in the BitTitan Knowledge Base or contact us today.
Stay tuned for more news on T2T coexistence next month!