Cloudiway’s 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.
For more information about security, please refer to this article.
For more information about migration performance, please refer to this article.
4.1 What can be migrated?
When migrating Teams between Office 365 tenants, the following site items can be migrated:
4.2. Migration limitations
MetaData on conversations are not migrated (Sender, DateTime of the chat message).
Wiki pages are not mapped with the Wiki Tab.
Delta migration is a Cloudiway functionality that allows you to migrate incrementally. Changes are migrated during delta passes. Deletions are not propagated.
This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.
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 these steps, please consider a solution with our consulting team, contactable via email@example.com. This will ensure a fast, cost-effective and stress-free implementation.
5.1 Before you start
Before you start, you will need to ensure you have the details outlined in the following table.
|Cloudiway login||Stores details and provides communication between the systems you already use.||https://apps.cloudiway.com|
|Knowledge base access||Our extensive knowledge base is always accessible, with videos, troubleshooting tools, samples and more.||https://kb.cloudiway.com|
admin role for
|Account with admin role that bypasses SSO and is able to authenticate using username/password credentials, preferably with the format:
Used for migration of permissions only.
|We recommend you create an account with admin access, especially for migration.
After all, migrations are complete, simply delete this admin account.
5.2. Pre-migration checklist
To ensure a successful migration, we recommend that you follow the checklist.
5.3. Security Pre-requisites
Migration uses a mix of Graph Apis and CSOM calls.
Graph APIS permissions requires application permissions on groups, users and sites.
For CSOM access, the migration account must be SharePoint administrator.
6.1. Create your source connector
To facilitate the Teams migration, the Cloudiway platform needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors, which are configured on apps.cloudiway.com. You will need to set up a connector for each source tenant and each target tenant. Follow the steps below to configure a source connector.
6.2. Create your target connector
With the source connector now configured on the Cloudiway platform, it’s time to create and configure the target connector. Follow the steps below to configure an Office 365 Group / Team target connector.
6.3. Discover Teams
The Cloudiway platform provides a tool called Get Groups / Teams which returns a list of all groups and teams from the domain you added to the source connector. This is a useful tool which provides you with a complete picture of groups and teams to be migrated.
You should therefore run this tool prior to group/teams.
The tool will schedule a call to your domain to return a list of all visible Groups and sites for migration.
Once the Get Groups / Teams tool has completed, it will return a list of all groups and teams discovered via the source connector’s credentials. The list will appear in the Group List area of the Cloudiway platform.
From this list, you can check what is due to be migrated prior to migration, edit the group definitions, assign licenses and delete any group or team that don’t need to be migrated. These actions are explained in the following sections.
You can also download the results in CSV format for your own records or to make editing changes, and then upload the updated CSV file to the Cloudiway platform as your final list to be migrated.
Note: you cannot add new entries to the CSV file: they must exist on the Cloudiway platform already. If you need to add a new group or team, either re-run the Get Sites (which will add newly-available sites to the existing list) or add a group or team manually using the steps in section 6.6.
6.4. Add target connector
From the group list, select the groups and teams of your choice and click on Manage / Assign Targets.
Select your target from the dropdown list and click on the Assign button.
6.5. Assign licenses
In the same way you assigned the targets, now assign the licenses.
From the group list, select the groups and teams of your choice and click on Manage / Assign Licenses.
You can manually edit the details of the group or team.
For this, click on the line to edit it.
6.6. Manually create an entry in the list
Due to the possibility of typos, we recommend you only use this option if it’s impossible to rerun the Get Groups command.
6.7. Import or create a mapping table of users and group details
In order to migrate permissions and metadata (createdby, modifiedby, etc…), a mapping table of users must be defined.
A list of mail users is used as mapping tables as it defines who has access to the different sites. It is also used to migrate metadata for files and folders.
You can upload a user or group list via CSV, use Cloudiway’s automated Import Users tool, or manually add each user on the Cloudiway platform.
6.7.1. Option 1: CSV import
If you have a CSV file of all your site users and another one for groups, you can upload the files to Cloudiway. The files must have the following fields in the header row:
User CSV: FirstName;LastName;SourceEmail;TargetEmail
Group CSV: Name;SourceEmail;TargetEmail
If you perform more than one upload, any CSV data already uploaded will not be overwritten by the following uploads. Therefore, duplicates can occur. Sample CSV files are available to download during the steps below.
6.7.2. Option 2: Create a single user or group
Many of our first-time customers create a single user and/or group for testing purposes. This provides a means of watching the migration process without affecting all users. Single users and groups can also be created for migrations affecting just a few users.
Cloudiway provides a preprocessing tool that will set automatically all the required permissions at the source and at the target and provision the groups and teams at the target.
What does the preprocessing tool?
At the source:
At the target:
At the end of the preprocessing, the status of the migration is set to “Not Started”. The group or team is now ready to be migrated.
How to run the preprocessing?
With this level of detail about pages and contents, you can verify any troublesome items unlikely to be migrated prior to starting migration. You should also use the audit to cross-check any missing items from the audit that are present on your source site.
6.9. Activate and monitor your migration
Now that you have performed all the pre-migration steps within your tenants and within Cloudiway, you’re ready to migrate. We recommend you run a test migration on a single site first to check that your configuration produces the outcome you expect.
To start your migration, select the Group or Team you wish to migrate and click on the Start button. Your batch will be scheduled and will begin as soon as resources are available.
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides, and downloads.
Please visit the entire knowledgebase here (where you can search for keywords or read through topics): http://kb.cloudiway.com/
The knowledge base also contains information on how you can ask for further support, should you require it.