Tenant to Tenant Migration for AAD, EXO and OD4B Services Only: 1-Week Implementation

Occasionally, a customer needs a migration inside the Microsoft 365 cloud platform. For example, if one company acquires another company and both are using Microsoft 365, there may be many reasons to start merging. 

Our objective is to provide planning, design, and migration of email service from one Microsoft 365 tenant to another. 

While the domain is transferring from the source tenant to the new tenant, incoming mail will not be received for about 24 hours. This is due to domain name binding features in Exchange Online. To avoid the loss of emails during the transfer period, you can consider the optional MX Spooler Service.

IT Partner responsibilities Export resources (mailbox-enabled users, contacts, groups, etc.) from the source tenant Import resources to the destination tenant via AD Connect or CSV import Do pre-stage migration (only emails and email folders older than 30 days) Proxy services setup, which allows for receiving all incoming emails during a domain transfer Final mailbox migration with calendars, contacts, rules, and other data Change records in domain zones to accommodate migration needs Client responsibilities Provide a dedicated point of contact responsible for working with IT Partner Coordinate any outside vendor resources and schedules Configure all network equipment, such as load balancers, routers, firewalls, and switches If Microsoft Outlook or other desktop email clients are used to connect to Microsoft 365, deploy email software on client workstations Perform changes to internal and external DNS, as required Assist with identification of high-risk users (top executives and VIP users, users with 50 GB mailboxes or larger and/or 30 GB deleted folders or larger) Recreate new Outlook profile on all client workstations, if desktop Outlook version is used Inform users about upcoming changes and provide the necessary information Additional cost items not provided by the project Informing users about upcoming changes Customer team training (could be added as an additional service) Migration of corporate documents to SharePoint Online (could be added as an additional service) Desktop software settings Upon completion of the project, we will provide a project closeout report. This document will indicate the final project status, including acceptance criteria matching, outstanding issues, and the final budget. If you require more extensive documentation, it can be provided for an additional fee. 

Prerequisites You must have global admin level access to the source Microsoft 365 tenant You must have global admin level access to the destination Microsoft 365 tenant, with Exchange Online licenses available You must have access to your email domain DNS zone Plan The plan may vary depending on your needs.

Kickoff meeting Pre-migration source system health check Creating users or configuring AD Connect tool Email migration start Verification of email migration Changing MX record to new Microsoft 365 tenant Final email migration Post-migration tasks Success criteria Users can access Exchange Online on their desktop PCs, mobile phones, and tablets from any place, any time Old Microsoft 365 tenant successfully migrated to new Microsoft 365 tenant and accessible by all users All necessary Transport rules are created and working Mail can be sent and received using Exchange Online Exchange Online Protection is configured and working No incoming message loss during the migration process