MICROSOFT TEAMS TO TEAMS
MIGRATION GUIDE
1. Introduction to Cross Tenant Microsoft Teams Migration
Cloudiway’s Cross Tenant Teams migration solution helps businesses perform technical migrations through a simple SaaS interface. As a result, Teams migrations require no additional software installation or overhead, and migrations can be performed securely and quickly.
This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.
The Cloudiway Platform allows migrating the Microsoft Teams and the Office 365 unified Groups between tenants.
What is migrated
Cross Tenant Microsoft Teams migration : What is migrated
You will find the list of what can be migrated on this page: Microsoft Teams Migration.
Performances & Security
Licenses
License Management
Cloudiway platform automatically assigns the licenses, for more details regarding the license management, check out this page.
Delta Passes
Delta Passes
Delta migration is a Cloudiway functionality that allows you to migrate incrementally. Changes are migrated during delta passes. Deletions are not propagated.
Support
Support
Although we provide support for our own products, we do not provide support for third-party products such as PowerShell or server administration of Microsoft products.
If you are concerned you might have any difficulty completing the steps for performing your Microsoft Teams to Teams migration, please consider a solution with our consulting team, contact us. This will ensure a fast, cost-effective, and stress-free implementation.
2. Prerequisites
The Cross Tenant Microsoft Teams Migration uses a mix of Graph APIs and CSOM calls. Therefore it requires to configure specific permissions at the source and at the target to execute Graph and CSOM calls.
2.1 Source Prerequisites
Create a source Microsoft 365 service account
First, we recommend to create an account dedicated to the migration, that can be deleted once the migration is completed.
- The migration account needs an Office 365 Teams License.
- For CSOM access, it must be SharePoint administrator.
- It must not be configured with multi-factored authentication (MFA) or SSO (ADFS).
- To perform the migration, the migration account needs to be an Owner and a Member of the Group/Team, in the source and in the target. If your source migration account is not Owner and Member of the Team, the migration engine will add it automatically.
2.2 Target Prerequisites
Create a target Office 365 service account
We recommend to create an account dedicated to the migration, that can be deleted once the migration is completed.
- The migration account needs an Office 365 Teams License.
- It must be SharePoint administrator.
- It must not be configured with multi-factored authentication (MFA) or SSO (ADFS).
Cloudiway automatically creates the team, therefore it doesn’t have to exist prior to the migration. If it already exists, it will be used and data appended to it.
Source Azure Active Directory Application
Graph APIs calls are performed through an Azure Active Directory Application which is granted specific permissions.
You can either create an Azure Active Directory Application manually or let the platform create one for you.
Please consult how to create the Azure Active Directory Application and associated permissions.
Target Azure Active Directory Application
Graph APIs calls are performed through an Azure Active Directory Application which is granted specific permissions.
You can either create an Azure Active Directory Application manually or let the platform create one for you.
Please consult how to create the Azure Active Directory Application and associated permissions.
2.3 Mapping Table
In Microsoft Teams, there are permissions and metadata (createdby, modifiedby, etc.) that contain email addresses. During the migration, these addresses must be converted into target accounts.
To achieve this, Cloudiway uses a mapping table to perform the conversion.
Important: the mapping table must be exhaustive, any missing email address will not be converted, and would end up with loss of file permissions and metadata. Cloudiway automatically populates this mapping table when source users are discovered by Get List functionality from Mail or File sections. However, make sure if the mapping table was populated automatically that you are not missing any email address.
3. Migration
Create the connectors for connecting to the source and the target .
Edit the Global Settings
Run a Discovery (GetList) or upload your list from a CSV file.
Configure the target location and Target Connectors.
Run an Audit to fully scope the scale of the migration, including how much data will need to be migrated. This step is optional.
Run a Pre-Processing to pre-create the target teams and channels and migrate the permissions.
Run the migration.
Close the Team
3.1 Create your Connectors
To facilitate the cross tenant Microsoft Teams migration, the Cloudiway platform needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors. You will need to set up a connector for each source tenant and each target tenant. Please refer to this page to configure your connectors.
For large projects, it’s possible to create multiple connectors that will be used in parallel. Please contact Cloudiway consulting services if you need to set up such configuration.
3.2 Migration Settings
Review the migration settings.
| Membership Migration | Enable the migration of team members |
| Conversation Migration | Enable the migration of channel Conversations, read more. |
| Planner Migration | Enable the migration of Planners |
| Mailbox Migration | Enable the migration of team mailboxes |
| Mentions Migration | Enable the migration of Mentions |
| Migration of TermStore | Enable the migration of TermStore, therefore you can safely leave it Off by default unless you have customized it. |
| Migration of Permissions | Enable the migration of Permissions (files permissions…) |
| Migration of Sharepoint | Enable the migration of SharePoint sites associated to the team |
| Keep in target | Keep files if already present at the target (existing files will not be overwritten) |
3.3 Discovery
To perform the Cross tenant Microsoft Teams migration, navigate to Sites > Group List
You have 3 different methods to fill the list:
Get List
The Get List entry under the MIGRATION menu connects to the source and retrieves the full list of teams and unified groups.
This is a useful tool which provides you with a complete picture of groups and teams to be migrated.
Select the connector you want to connect, click on GET.
Note: you can monitor the progress of this task in the Global Logs.
Once the job is completed, the list displays all the teams. Next, you need to assign a target connector to all the entries.
CSV Import
If you have a CSV file of all your teams, you can upload the file to Cloudiway.
Check this article for generating the CSV file correctly: https://help.cloudiway.com/article/how-to-fill-the-users-groups-csv-file/
Click MANAGE > Import. Select the CSV File, the Source, and Target Connectors, then click Upload.
Manual Creation
Many of our first-time customers create a single team for testing purposes.
Click on MANAGE, Create.
- Source Connectors Pool: Select the pool of connectors.
- Target Connectors Pool: Select the pool of connectors.
- Source Recipient Type: Select Microsoft Team or Unified Group.
- Target Recipient Type: Select Microsoft Team or Unified Group.
- Source Group Name: Enter the name of the team to migrate.
- Target Group Name: Enter the name of the team that you want to create (the name can be different).
- Source Group Email Address: Enter the email address of the team.
- Target Group Email Address: Enter the email address of the team as you want it to be created at the target.
- Source Group URL: Enter the relative URL of the SharePoint site of the team.
3.4 Target Location
Configure the Target Location.
If you want to mass assign a target connector to your objects in the list, you can select them and from the menu, click on MANAGE, then Assign Target.
In the same way, you can add a prefix to several entries at the same time
Add a Prefix to the Target?
You can add a Prefix to the Target Group Name and the Target Group Email Address.
In the Group List, check one or more objects that you want to add a prefix to. Go to MANAGE, then click Add Prefix.
Enter the Prefix in the pop-up and click SAVE.
3.5 Audit
The audit is optional and purely informative. It consumes the Cloudiway license. You do not have to run it, unless you wish to see how many Channels, files and folders you have in the source Microsoft Team.
This feature reports information about the Source team:
- Number of channels,
- Number of conversations in each channel,
- Number of files per channel,
- Number of members
To Audit a team, in Group List, select it and click on MIGRATION, Audit.
3.6 PreProcessing
The pre-processing tool creates the team at the target if it doesn’t already exist.
What does the pre-processing tool in detail?
At the source:
It uses the graph APIs (Client ID and Client Secret) and gives the owner role to the migration account defined in the source connector. This ensures that the migration account will have all the necessary permissions during the migration.
At the target:
It creates the Team (or unified Group) and the associated SharePoint modern site with the credential defined in the target connector.
- It uses the graph APIs (Client ID and Client Secret) and gives the owner role to the migration account defined in the target connector.
- It migrates membership and ownership.
- It creates the SharePoint libraries that may have been manually created.
To pre-process a team, in Group List, select it and click on MIGRATION, Pre-Processing.
The group or team is now ready to be migrated.
3.7 Migration
The 
icon indicates a private channel. Please see this article to learn more about how to migrate private channels.
Note on Migration: Cloudiway is leveraging Microsoft Teams Import Apis to maximize throughput.
This Microsoft article explains how it works : import-external-messages-to-teams
Cloudiway has integrated these apis. Checkout this article to see how it is implemented in the platform.
Before starting the Microsoft Teams to Teams migration, you must run the pre-processing (see step above) of the team.
To start the migration, in Group List, select it and click on MIGRATION, Start.
This will schedule the migration. The migration will start as soon as there is a free spot on the platform.
You can monitor your migration by clicking on the team in the list.
3.8 Close Team
When your migration is completed, run the Post Migration Task.
This will close the Team that has been created in import mode.
Note 1: Private channels cannot be created in Import mode. Therefore, if you are migrating to a private channel, you don’t have to run the Post Migration Task
Note that once it is closed, the import api cannot be used anymore. It means that if you start a delta pass after you have closed the team, the delta pass will work but the meta data will not be injected anymore into the messages.
4. Troubleshooting
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides, and downloads.
Please visit the knowledgebase here: https://help.cloudiway.com/
