This guide is for Microsoft 365 Group to Microsoft 365 Group Mailbox (Conversations) migrations and is meant to work in conjunction with the SharePoint to SharePoint Migration Guide (Including Microsoft 365 Groups) if group file migration is also required.
There are some tools and resources that will make the migration easier.
MigrationWiz
MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.
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.
First migration?
While this guide includes all the steps required, migrations are complex projects that require a lot of planning ahead of time. We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.
Prerequisites
Please consider the following information to perform a smooth migration.
Licensing
We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit MigrationWiz Licenses.
To use your license by following the next steps:
- Purchase Licenses.
- Create a Customer.
- Apply Licenses.
- Review Considerations.
Purchase licenses by following the steps below:
- Sign in to your BitTitan account.
- In the top navigation bar, click Purchase.
- Click the Select button and choose User Migration Bundle licenses.
- Enter the number of licenses you want to purchase. Click Buy Now.
- Enter a Billing address if applicable.
- Click Next.
- Review the Order Summary and enter a payment method.
- Click Place Your Order.
Create Customer on MSPComplete by performing these steps:
- Click the Add button in the top navigation bar
- Click the Add Customer button on the All Customers page
- Select the appropriate workgroup in the left navigation pane and click All Customers.
- Click Add Customer.
- Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
- Click Save.
- Repeat steps 1 through 4 for each customer you want to add.
Perform these steps on MSPComplete:
- Select the correct workgroup on the top of the left navigation pane.
Important
This is the workgroup which the customer and migration projects were created under. Your account must be part of the workgroup if the project was not created under your account. - Click Customers on the left navigation pane.
- Click the customer that employs the user to whom you want to use the User Migration Bundle license.
- Click the Users tab at the top of the page.
- Apply the license to the users by checking the box to the left of their emails.
- Click the Apply User Migration Bundle License button at the top of the page.
Tip
We recommend adding users to the Customer page with the vanity domain. Then apply the User Migration Bundle Licenses, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration. - Click Confirm if at least one unassigned User Migration Bundle license is available for each selected user.
Important
If there are no User Migration Bundle licenses currently available to be assigned and your role in the workgroup is Manager or higher, the form that appears provides all the necessary information and will walk you through the steps of purchasing User Migration Bundle licenses.
Licenses are released once payment has been received:
- Licenses are available immediately upon payment if you purchase via credit card.
- If you purchase via wire transfer (100+ licenses), the licenses will be available once payment is received and accepted.
- We do not accept purchase orders because of processing overhead.
In both cases, you will be notified by email that payment has been accepted and licenses are available in your account upon notification.
For more information on licensing, including coupon redemption and other licensing types, see our Licensing FAQ.
Limitations
- We are not able to support migrations with two-factor or multifactor authentication.
- App password usage, MFA/2FA, and ADFS are not supported for the migration admin account/service account being used by this endpoint.
- The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.
Migrated Items
Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.
- Inbox
- Primary Calendar
- Safe Sender/Block Lists
- In-line images in Tasks
- Notebooks
- For Groups documents: anything not in a document library (See SharePoint)
Important
- Some group conversations might not be nested at the Destination.
- The group OneNote notebook is not migrated.
- We are not able to support migration endpoints that use admin accounts with two-factor or multifactor authentication enabled.
- Only the Inbox and Calendar folders are migrated for this migration scenario. Folder filters will need to be added to your project. The folder filters are covered in the steps for adding advanced options in this guide.
Prepare the Source Environment
- Create an administrator account in Microsoft 365 to be used for the migration, or use the global admin account for the tenant.
- Add the migration administrator account as an owner and a member of the source group.
- Make note of the owners and members of the group. You will need this information later when replicating the membership of the Source group at the Destination group.
Modern Authentication Requirements
The steps listed in the Obtain Client and Tenant ID Settings for Mailbox and Exchange Online Migrations section of the Authentication Methods Migrations KB apply to both the source and destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in mailbox, archive mailbox, and public folder projects. Use a Global Administrator for the configuration steps.
Please review the documentation before preparing the destination.
Prepare the Destination Environment
- Create an administrator account in Microsoft 365 to be used for the migration, or use the global admin account for the tenant.
- Create the Office 365 Group, if it doesn't already exist.
- Add the migration administrator account as an owner and a member of the destination group.
- Add other owners and members to the group to replicate the membership of the Source group.
Modern Authentication Requirements
The steps listed in the Obtain Client and Tenant ID Settings for Mailbox and Exchange Online Migrations section of the Authentication Methods Migrations KB apply to both the source and destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in mailbox, archive mailbox, and public folder projects. Use a Global Administrator for the configuration steps.
Please review the documentation before preparing the destination.
MigrationWiz Steps
Create a Mailbox Migration project
- Click the Go to My Projects button.
- Click the Create Project button.
- Select Mailbox Project for the type of project to create.
- Click Next Step.
- Enter a Project name and select a Customer.
- Click Next Step.
Endpoints
Endpoints are created through MigrationWiz. If you select an existing endpoint from the dropdown, it will only show ten endpoints. If you have more than ten, you may need to search it.
Consider that endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.
Create your Endpoints
Please review the following tabs to create your destination and source endpoints.
Create your source endpoint by following the next steps:
- Click New.
- Name the endpoint.
- Select type Microsoft 365 groups.
- For the URL field, enter the tenant's SharePoint top-level site URL.
- Enter the admin account credentials.
- Click Add.
- Complete the Application (client) ID, the Directory (tenant) ID fields, and the Region of Destination Tenant, otherwise, you cannot save your project.
Create your destination endpoint by following the next steps:
- Click New.
-
Enter a name in the Endpoint Name field.
-
Select Microsoft 365 Groups from the Endpoint Type drop-down menu.
-
Enter the SharePoint top-level domain URL. Although the SharePoint URL would not be used in the Google Groups to Microsoft 365 Groups migration, we recommend it as a good practice and for future development.
-
Enter the administrator credentials, Administrator username, and password.
- Click Add to save your destination endpoint.
-
Complete the Application (client) ID, the Directory (tenant) ID fields, and the Region of Destination Tenant, otherwise, you cannot save your project.
Application (client) ID, Directory (tenant) ID, and Client Secret
For Microsoft 365 Mailbox and Archive migrations, MigrationWiz adds the Application (client) ID, Directory (tenant) ID, and Client Secret fields.
While the Application (client) ID and the Directory (tenant) ID are mandatory, the Client Secret field is not. It will depend on the permissions of the user account that performs the migration. Please review the following information before the creation of your M365 endpoints.
-
The client secret value is not mandatory if you use delegated permissions. Please leave the Client Secret field empty.
-
The client secret value is mandatory if you use the Application Impersonation using API Permissions approach.
- If you already have an admin account with the Impersonation role enabled (not using the Application Impersonation using API Permissions approach) the client secret value is not mandatory. Please leave the Client Secret field empty.
For more information about how to get the Application (client) ID and Directory (tenant) ID values from the Application Registration, please review step 3 of this article.
Region of Destination Tenant
MigrationWiz displays a dropdown to select the Preferred Region of the Tenant at the destination endpoint. This value updates the Preferred Region of the Destination Tenant field in the project's Advanced Options, and vice versa. You will notice that both values are always the same.
The Region of Destination Tenant feature optimizes the migration performance and speed when choosing the region closest to the destination tenant.
Tip
You can find the region of your destination tenant directly in the Microsoft Entra admin center by going to Identity > Overview > Properties, and using the Country or region or the Data location.
For more information on this topic, review this article.
Warning
If you do not complete this field you will not be able to save your project and the “This field cannot be left blank.” error will appear.Endpoint Validation
Once the information has been provided for both, the source and destination endpoint, and the customer selects Save and Go to Summary, MigrationWiz performs an endpoint validation check.
This validation tests the administrator credentials entered into the project and the Modern Authentication setup only. If there is an issue, the screen redirects to the endpoint and provides an error message or flyout that can be selected for more information regarding the error.
Common Errors when Configuring Your Endpoint
For more information, review the AADSTS700016, AADSTS90002, and ADDSTS50126 issues on the Common Errors Using Modern Authentication page.
Add Items
Add the Source and Destination group email addresses. This may be done in several ways, depending on the size of the project.
Small Migrations
For small migrations, it is easy to add users one at a time using Quick Add.
Larger Migrations
For larger migrations, we recommend either using the Bulk Add option.
- An email address
- Login name
- Password
- Mailbox status
Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.
MigrationWiz allows you to bulk import mailboxes into the system.
To import one or more mailboxes:
- Sign in to your MigrationWiz account.
- Select the Project for which you want to perform the bulk import.
- Click Add.
- Click Bulk Add.
- Follow the instructions on the page.
Advanced Options
Navigate to Support Options in your MigrationWiz dashboard and add the following.
Support Tab
Optional Settings
- RecipientMapping="@old-domain.com->@new-domain.com" Replace "old-domain.com" and "new-domain.com" with your actual domain names. This performs a find-and-replace that updates email addresses from one domain name to another. Use this support option when migrating mailboxes from an old domain name to a new domain name. If the email address of the users stays the same after the cut-over, this option is not needed.
Filter Tab
- Under Filter Folders: ^(?!Inbox$). This RegEx expression migrates the Inbox, but not its subfolders. To migrate both the Inbox folder and Calendars folder, use instead the RegEx expression ^(?!Inbox$|Calendar$). These filters are used to prevent failures, as Groups should only contain an Inbox folder, and possibly a Calendar. No other folders are supported. This expression must be in the source language, such as ^(?!Boîte de réception$) for French.
Source/Destination Tab
"Use Impersonation to authenticate" must NOT be checked in the advanced options for the source or destination the migration will fail.
Run Verify Credentials
- Open the Project containing items to validate.
- Select the items to validate.
- Click the Start button in your dashboard.
- Select Verify Credentials from the drop-down list.
Once complete, the results of the verification will be shown in the Status section.
Run Migration
Notify users
Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration and let them know what to expect for their Outlook profile reconfiguration. Samples and screenshots can be found in our DeploymentPro documentation if you are utilizing that tool.
Full pass
Important
Under the Select what to migrate section, ensure that only Mail is selected before starting the migration. You may also select calendars.
- Select the users.
- Click the Start button from the top.
- Select Full Migration.
- Click Start Migration.
Run Retry Errors
Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
If problems persist, contact Support.
Request Statistics
Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.