{"id":1610,"date":"2021-06-05T20:11:00","date_gmt":"2021-06-05T15:11:00","guid":{"rendered":"https:\/\/www.edopedia.com\/blog\/?p=1610"},"modified":"2022-02-26T01:41:32","modified_gmt":"2022-02-25T20:41:32","slug":"office-365-tenant-to-tenant-migration","status":"publish","type":"post","link":"https:\/\/www.edopedia.com\/blog\/office-365-tenant-to-tenant-migration\/","title":{"rendered":"Office 365 Tenant to Tenant Migration Done Right"},"content":{"rendered":"\n

When we first started adopting Office 365, the major concern was over our tenants being on a shared service. To ensure security, Office 365 and other cloud technology providers placed controls that keep tenants separate.<\/p>\n\n\n\n

However, those same controls cause challenges at the time of mergers, acquisitions, or divestiture.<\/p>\n\n\n\n

Today, I\u2019ll give you an overview of how to do o365 tenant to tenant migration<\/strong> the right way. For a more in-depth tutorial, you can also check out the o365 migration<\/a> guide.<\/p>\n\n\n\n

Generally, there are three phases of any tenant to tenant migration. These are mentioned below:<\/p>\n\n\n\n

  1. Pre-Migration Steps<\/li>
  2. Migration Day Activities<\/li>
  3. Post-Migration Steps<\/li><\/ol>\n\n\n\n

    Let\u2019s talk about each phase in a bit more detail.<\/p>\n\n\n\n

    \n\n\n\n

    1-       Pre-Migration Steps<\/h2>\n\n\n\n

    In this phase, you have to plan and set up everything ahead of the actual migration process. Usually, it’s better to finalize the planning at least 1 or 2 weeks before the migration to avoid any disruptions.<\/p>\n\n\n\n

    1. At first, you must ensure that your office 365 tenant to tenant migration tool is ready. In most cases, you\u2019ve to purchase its license.<\/li>
    2. Prepare the target tenant by creating extra room to accommodate mailboxes from the source tenant. You can either use Microsoft 365 admin center or Azure Active Directory consolidation.<\/li>
    3. Inform end-users about the impending o365 tenant to tenant migration<\/a><\/strong> process.<\/li>
    4. It’s time to perform the DNS verification. To do so, add the source tenant to the target tenant\u2019s o365 admin center and create the TXT records.<\/li>
    5. Migration tools usually require a CSV file containing all the email addresses that need to be migrated. So, you must generate one ahead of the scheduled date.<\/li>
    6. Update Mail Exchanger (MX) records to avoid disruption in the mail flow.<\/li>
    7. The last step is to disable the Azure Active Directory syncing. It can take up to one complete day, so plan it carefully.<\/li><\/ol>\n\n\n\n
      \n\n\n\n

      2-       Migration Day Activities<\/h2>\n\n\n\n

      As we\u2019ve planned most of the migration process early on, so there\u2019s not much to worry about now. On the migration day, you only need to perform four activities.<\/p>\n\n\n\n

      1. It\u2019s very important to stop any incoming emails from reaching the source tenant during the migration. It helps prevent any errors. You can even use a third-party service to queue incoming emails and receive them after the migration process ends.<\/li>
      2. In order to successfully perform the migration, it is required to remove the source tenant domain from Office 365. Some processes will even prevent you from doing that. So, you\u2019ve to manually stop them using the PowerShell command.<\/li>
      3. Let\u2019s say you\u2019ve added the source tenant domain to the target domain, now it\u2019s time to verify it. You can do that from the admin center of the target domain.<\/li>
      4. There are different ways to migrate office 365 to office 365. You must select the one depending on your Exchange Server and the number of o365 tenants. The most common methods are: