Office 365 to Office 365 Migration Guide - While Changing the Domain Name – with Coexistence

Introduction

This is the complete onboarding task flow for migrating mailboxes from one Office 365 tenant to another Office 365 tenant while using coexistence.

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

This guide is only valid if the domain name is changing at the Destination. If the domain name is staying the same, read the Office 365 to Office 365 - While Keeping the Same Domain Name migration guide.

The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. This is an Agent which includes modules for HealthCheck for Office 365 and DeploymentPro. Deploying DMA to end users is a prerequisite if you will be using HealthCheck for Office 365 and/or DeploymentPro. The steps for HealthCheck for Office 365 have been omitted from this guide because your end users are already using Office 365.

DeploymentPro can be used to configure the user Outlook profiles on the destination.

Important note: Unfortunately, due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this specific migration type.  However, you can still migrate to or from GoDaddy using this guide instead: Office 365 to Office 365 Migration Guide - While Changing the Domain Name.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. 

Prerequisites

• Important: Azure Active Directory Connect (ADFS, AADConnect, AADSync, ADSync, etc.) cannot be used to do anything with the destination user accounts until after the migration project is fully completed.
• At this time, we are not able to support tenants that have enhanced security set up.  
• User Migration Bundle licenses are required for this migration.
• Only specific Office 365 licenses are supported for this migration.  The supported types are listed in the Migration Setup drop-down menu.
  • Only one Office 365 license type can be used per project.
  • The Office 365 license types cannot be changed once the project has been set up.
• The administrator account on the destination must use the onmicrosoft domain and not the vanity domain.
• The administrator accounts on both the source and the destination must have an Office 365 license applied and be set up with a mailbox before the migration project is created.
• The migration can be completed in batches; however, all the users need to be in the same project.
• Once a project is set up, you can use the Rediscover Items option in the Manage Tenant to Tenant menu to add/remove users from the project.  
  Note: The users must be removed or added to the Source environment before the Rediscover is used.
• Cloud accounts are created on the destination. 
  Note: User passwords will be created as part of the DeploymentPro Profile Configuration.

Prepare the Source Environment

1. Create a Global Administrator account in Office 365 to be used for migration or use the Global Administrator account for the tenant. Read the How do I create an administrator account in Office 365? article for more information. 

Prepare the Destination Environment

1. Create a Global Administrator account in Office 365 to be used for migration or use the Global Administrator account for the tenant. Read the How do I create an administrator account in Office 365?  article for more information.
   Important: The destination tenant Administrator account needs to be able to access MSOnline, so the account must use the .onmicrosoft.com domain to ensure the correct access levels.
2. Prepare the tenant to send and receive large mail items. Read the How do I migrate large mail items to Office 365? article for more information.

MSPComplete Steps

1. Create the customer. Read View, Add, and Edit Your Customers for more information.
2. Create the Source and Destination endpoints. Read View, Add, and Edit Customer Endpoints for more information.
   • For the Source endpoint:
     • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.
     • Click the Provide Credentials radio button and enter the administrator account credentials.
       Note: The administrator needs to be a Global Administrator account. Read the How do I create an administrator account in Office 365, and then use this during migration? article for more information.
   • For the Destination endpoint:
     • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.
     • Click the Provide Credentials radio button and enter the administrator account credentials.
       Note: The administrator needs to be a Global Administrator account and be on the onmicrosoft domain. Read the How do I create an administrator account in Office 365, and then use this during migration? article for more information.
3. Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:
   • How do I purchase licenses?
   • Migration License Types
   • Apply User Migration Bundle licenses to the Customer's Users 
     
     

DeploymentPro Steps

Read the DeploymentPro Guide for detailed steps on configuring a DeploymentPro project.

1. Deploy DMA by email to all the users in the project.  For more information see How do I deploy the Device Management Agent through email?
   Note: DMA must be deployed to users before any migration of their mailbox.  
2. Launch DeploymentPro:
   • Go to All Products > Device Management.
   • Select a customer from the list by clicking on the customer name.
     Note: The status column will show Enabled when a customer account has had DMA deployed to users.
   • Click DeploymentPro in the column on the left.
3. Configure the DeploymentPro module:
   • Enter the Destination Domain Name.
   • Select the Destination endpoint. 
4. In the Personalized DeploymentPro Interface section, upload your company logo and add any supporting text.
   Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
5. Click Save and Continue.
6. Select the users to be scheduled and click Run Module.  Schedule for your planned cutover date and time.
   Note: Users can be scheduled individually, or by selecting several at a time.  All selected users will be scheduled to run at the same time.  

MigrationWiz Steps

1. Create a Mailbox Migration project. Read the Office 365 Tenant to Tenant Coexistence Setup Guide for more information on the specific steps for setting up this type of migration.
   Note: Once a project is set up, you cannot add more users or make changes to the configuration; other than advanced options. If you want to add users to the organization, please add them to the source before creating the project or add them manually to the destination.
2. MigrationWiz will automatically start to configure the Office 365 tenants for the project.  This process may take up to 1 hour per 1000 users.
3. Users will be added to the project automatically from the Source endpoint.
4. MigrationWiz creates the users on the destination as mail-enabled contacts.  For more information see What happens during a Tenant to Tenant Migration with Coexistence Project Setup.
5. The migration project can be completed in batches, but all the users need to be in the same project.  When ready to run a batch of users, select the users to be migrated in that batch.
6. Run a Pre-Stage migration. This step converts the mail-enabled contact on the destination to a user account, applies the selected license to the user, and initiates the mailbox creation process.  A mail forward is then set up from the destination to the source mailbox.
   Note: Mailbox creation can take up to 24 hours. Once the mailbox is available, the migration will proceed.  If the migration has not started to move data after 24 hours, contact Support.  See How do I get support for your products? for more information.
7. When the time arrives to cut over the batch of users, select the users and run a Full Migration.  This sets up a mail forward on the source and removes the forward from the destination mailbox.
   Important: After the users have successfully completed, the Source Mailbox for those users will need to be converted to a mail-enabled contact pointing to the destination mailbox.
8. When all users have been migrated successfully, change over MX records on the DNS provider's portal. Also, include the Autodiscover (CName) setting.
9. Run Retry Errors. Read How do I retry failed items? for more information.
10. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
11. If problems persist, contact Support. Read How do I get support for your products? for more information.
12. If not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.
13. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read How do I request statistics for my migration project? for more information.