BitTitan: Perform tenant-to-tenant Microsoft 365 During Mergers and Acquisitions
Assess and plan the strategy for migration Evaluate your M&A situation to determine the domain consolidation strategy. Also, consider user count and workloads. Establish a schedule and identify all the stakeholders involved in migration.
Create a communication plan with users. Develop a strategy of T-minus communications, working backwards starting from the migration day and providing updates on a regular basis (normally three days prior to cutover). Inform users about expected access changes and the post-migration action they’ll have to take.
Prepare the destination Microsoft 365 environment Create user accounts in the destination tenant using PowerShell scripts, CSV bulk import, or manual entry. Also, ensure that all data is clean, ready for migration. Prepare the Microsoft 365 environment at the destination. Create user account in the tenant using PowerShell scripts and/or directory synchronization. Assign licenses to the Azure AD/Entra ID and integrate it.
Create the BitTitan MigrationWiz project Log in to MigrationWiz. Create a new tenant-to-tenant project. Then configure the source-to-destination endpoints, using the appropriate API information and credentials.
Configure domain-mapping and mail routing. Map the origin domain to the destination, configure mail routing correctly, and install connectors to maintain the email flow during coexistence, if necessary during a phased transition.
Add users, then select workloads. Select the users that you wish to migrate. Migrate according to this recommended order: Start with mailboxes by migrating Exchange Online, then files and collaboration by migrating OneDrive and SharePoint, and finally Teams.
Execute a pre-stage data migration run Run the migration pre-stage to perform the initial data transfer. Test the process. This allows for you to verify the data integrity before final cutover without affecting users.
Perform MX Record Cutover Change DNS records to point Microsoft 365. Update Autodiscover CNAME setting. Schedule this work during non-working time as it could cause temporary mail delivery delay.
Validate the migration and correct any errors. Check the migration logs for failed items. Verify user access within the destination tenant. And troubleshoot all data transfer problems before declaring the migration completed.
Deploy Outlook settings after migration Use BitTitan DeploymentPro, to configure Outlook profiles automatically on user devices. Or provide guidance for manually setting up profiles if automation isn’t used.
Complete post migration cleanup and user handoff. Once validation is complete, decommission the source tenant, remove vanity sites from the source and provide any remaining issues or queries to the end-user.
Leave a Reply