Office 365 Mailbox to Office 365 Groups Migration Guide

Introduction

• This is the complete onboarding task flow for migrating mailboxes from one Office 365 tenant to another Office 365 tenant.
• Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
• This migration scenario is useful if you want to migrate data from individual mailboxes into shared Office 365 Groups.
• This migration scenario only supports migration of mail items into the Office 365 Groups.
• MigrationWiz now supports the capability to share migration projects across a Workgroup. Migration projects are no longer tied to individual accounts, they are tied to Workgroups. When Workgroup Administrators turn on the Project Sharing feature, all Agents besides those who are Inactive are able to view all migrations projects.  For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Environment

• Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
• Export the user list to a CSV file. This can be used when bulk-adding users to your MigrationWiz project later. You can copy and paste the user list into the Source Email column within your MigrationWiz project dashboard under Add > Bulk Add. Steps: From Office 365 admin portal > Users > Active Users > Export > Continue.

Prepare the Destination Environment

• Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
• Create the Office 365 Group, if it doesn't already exist. Office 365 Groups can be created by either of these options:
• Opening Outlook Web Access / Outlook On The Web. See the Microsoft support article "Create and navigate a group".
• Using PowerShell, using the New-UnifiedGroup command. Read the Microsoft support article "Use PowerShell to manage Office 365 Groups" for more information.
• Manage group membership:
  • Add members to the Group using the Office 365 admin center.
  • Add members to be the administrators of the Group.
  • Add the migration administrator account as a member of the Group.
  • Promote the migration administrator account to be the administrator of the Group.
• Follow the instructions in this Microsoft support article "Manage Group membership in the Office 365 admin center" to:

MSPComplete Steps

1. Create the customer. KB005421
2. Create the Source and Destination endpoints. KB005427
   • Click EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.
   • Click the Provide Credentials radio button, and enter the admin account credentials.
     
     Note: This should be a global admin account. If creating a separate admin account for the purpose of migration, refer to the Office 365 section in KB004725.
   • Click EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365 Groups.
   • Enter the URL of the group into the URL field.
   • Click the Provide Credentials radio button, and enter the admin account credentials.
     
     Note: This should be a global admin account. If creating a separate admin account for the purpose of migration, refer to the Office 365 section in KB004725.
• For the Source endpoint:
• For the Destination endpoint:
3. Purchase licenses. We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow you to perform multiple migrations of User mailboxes, documents, and personal archives, plus Google coexistence configuration, and allows the use of DeploymentPro to perform post-migration Outlook email profile configuration. Refer to these articles for more information:
   • How do I purchase licenses?
   • Apply User Migration Bundle licenses to the Customer's Users
   • Which migration license should I choose?
4. Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:
   • Via Group Policy Object (GPO).
     
     Note: This is the recommended methodology, because no end user interaction is required. ​KB005412 video
   • Via email. KB005411

DeploymentPro Steps

1. Launch DeploymentPro.
   1. Enter the Domain.
   2. Select the Destination endpoint.
   3. Check the Auto-populate box.
   4. In the Client Interface Configurations section, upload your company logo and add 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. Save and continue.
1. Go to All Products > Device Management, then click on DeploymentPro on the far left and follow the prompts to launch.
2. 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.
3. Configure the customer DeploymentPro module:
2. Activate the DeploymentPro module for users.
1. Either select all users (by putting a checkmark in the box to the left of the Primary Email column heading), or select the individual users (by putting a checkmark in the boxes to the left of the user email addresses).
   Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.
2. Click the Schedule Cutover button.
3. Schedule profile cutover date.
   • The DeploymentPro module will install on user devices immediately, and then run silently until this date.
   • The profile cutover date should be set to a date and time that is shortly after the MX record cutover.
• Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutover button.
  Notes:
4. On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

MigrationWiz Steps

1. Create the Mailbox Migration project. KB004380
2. Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
3. Set the Project Advanced Options. KB004834
   
   Note: Only mail items can migrate. The items can only be sent to the Group Inbox.
   • Under Filtering/Filter folders (RegEx) field, add ^(?!Inbox$)
     
     Note: This will migrate the Inbox > Inbox. Otherwise you can add the following folder mapping: FolderMapping="^.*$->Inbox". This will migrate all folders to the Inbox.
• The following option is the most valuable for this migration scenario:
4. Run Verify Credentials. KB004511
5. Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
6. MX Record Cutover. Change over MX records on the DNS providers' portal. Also include the AutoDiscover (CName) setting.
7. Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.
8. Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Select to migrate Mail only >Click Start Migration. KB004938
9. Run Retry Errors. KB004658
10. Look through the user list and click any red "failed migration" errors. Review information and act accordingly.
11. If problems persist, contact Support. KB004529
12. Show users how to access the Office 365 Group; they will appear in their Outlook, under Groups.
13. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626