Google Team Drives can be migrated as part of your entire migration plan or as an independent project, depending on your business needs. You can choose to migrate each Team drives to an Office 365 group.
By default, the Cloudiway platform migrates a Team drives to an Office 365 group. An Office 365 group is used to communicate, collaborate, and schedule events from within a user’s inbox, in an area dedicated to groups.
You can override the default on a per-group basis with the Cloudiway group migration platform. As a result, you can achieve total flexibility during a Google Team Drives migration to Office 365.
The path to migration is straightforward. In five steps and with very little setup, your Google Team Drives will be migrated to your intended target. The steps are:
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?
The group migration product supports the migration from a Google Team Drive to a unified group only. The migration tool will migrate:
4.2. Migration considerations
Some contents/settings from Google Team drives cannot be migrated in the current version:
To perform the migration, you will need to create a migration account, give access to your Drive API for the Cloudiway Service Account in G Suite and a new Office 365 Admin in the target tenant, and manually give it full permission to each source Team drives that you wish to migrate. It’s therefore important that you notice that any Team drives cannot be migrated unless this new user is granted full access on Team drives.
Delta passes can be used with group migration to ensure all batch migrations are completed. The Cloudiway platform uses the id of the source Team drive as the unique ID during migration. This ensures a Team drive is only migrated once. The delta pass includes the following kind of items:
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 firstname.lastname@example.org. 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|
|Our extensive knowledge base is always accessible, with videos, troubleshooting tools, samples and more.||https://kb.cloudiway.com|
|Office 365 account with global admin rights||Account with admin role that bypasses SSO and is able to authenticate using username/password credentials, preferably with the format: email@example.com. 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.|
|G Suite service account (Cloudiway)||You will need to grant permissions on your Drive API for the Cloudiway service account.||Client id: 114818336788408865729|
|G Suite migration account||You need to create account (or use an existing one) for the migration. You will need to grants full access (for this account) on each Team drives you want to migrate.||We recommend you create a migration account especially for migration. After all migrations are complete, simply delete this account. We provide steps below to help you set up an account if you don’t already have one.|
5.2. Migration requirements
To ensure successful migration, we recommend that you follow the checklist.
On your G Suite tenant, you must create a new account and give it the following rights:
On your Office 365 target tenants, you must create a new account and give it the following rights:
Grants access to Drive API for the Cloudiway service account
Permissions in Office 365
Our Group Migration product come with a pre-processing task, that is able to create the Office 365 groups and teams in your target tenant. To achieve that, migration uses a mix of Graph Apis and CSOM calls.
Graph APIS require application permissions on groups, users and sites.
For CSOM access, the migration account must be SharePoint administrator.
6.1. Create your Google Team Drives source connector
For Cloudiway to migrate your Team drives, it 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 you wish to migrate and each target tenant. Follow the steps below to configure a Google Team Drive source connector.
6.2. Create your Office 365 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 target connector.
Name of the tenant: enter the name of your tenant (ie cloudiwaylab), not cloudiwaylab.com or cloudiwaylab.sharepoint.com
Filling this field automatically fills the URL field.
Server Region: Most of the time, keep the default value “Worldwide” except if you have a China, German or US Governmental tenant.
Domain Name: Enter the name of your primary domain.
Migration User: A sharePoint administrator account ( for permissions to run CSOM calls).
User Password: The password of the migration user. This is stored encrypted in EAS 256.
Client ID / Client Secret: Graph API client ID and secrets with permissions to access, groups, users and sites.
See this article for creating the application : https://kb.cloudiway.com/article/azure-apps-registration/
6.3. Import Team drives with the Get Groups / Teams command
The Cloudiway platform provides a tool called Get Groups / Teams which returns a list of all your Team drives that have in your source tenant.
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 of team drives 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 team drive, either re-run the Get Groups /Teams command (which will add newly-available Team drives to the existing list) or add a team drive manually using the steps below.
6.4. Add a Team drive manually to Cloudiway
You can manually add the details of a Team drive to your list on the Cloudiway platform. Due to the lengthy URLs, we recommend you only use this option if it’s impossible to rerun the Get Groups / Teams command.
You might wish to test migration on a test Team drive you’ve set up especially for that purpose. In this case, adding the Team drive manually might be preferable to using Get Groups.
6.5. Import or create a mapping table of user and group details
In order to migrate access rights for the list of users who have acces to your Team Drives, a mapping table of users must be defined. A list of users is used as a mapping table as it defines who has access to the different Team Drives.
If you have already migrated mail via Cloudiway, your users will already be available on the Mapping Users menu of Cloudiway’s group migration. If not, you can upload a user list via CSV, or manually add each user on the Cloudiway platform.
You can add a user to the mapping table without assigning a migration license. Each user will, however, need to be assigned a license type — Standard or No License (used for adding users to your mapping table regardless of migration plans).
6.5.1. Option 1: CSV import
If you have a CSV file of all your users, you can upload the file to Cloudiway. The file must have the following fields in the header row:
A sample CSV file is available for download during the steps outlined below. If you perform more than one upload, any user data already uploaded will not be overwritten by following uploads. Therefore, duplicates can occur.
6.5.2. Option 2: Create a single user or group
Many of our first-time customers create a single user for testing purposes. This provides a means of watching the migration process without affecting all users. Single users can also be created for migrations affecting just a few users.
The Pre-Processing task will help you to prepare the target recipient before you start your migration.
After you run the “Get Groups / Teams” action, you will be able to update your Team drives in the list. Once it’s done, you can launch the Pre-Processing. This task will perform two main actions in your Office 365 target:
The Pre-processing task will do the following actions:
The Pre-Processing can terminate in two statuses:
6.7. 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 Team drive first to check that your configuration produces the outcome you expect.
To start your migration, select the Team Drive(s) or batch you wish to migrate and click on the Start button on the Migration menu at the bottom. Your batch will be scheduled and will begin as soon as resources are available. By default, a hundred migrations can be run concurrently.
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides and downloads.
Please visit the entire knowledge base 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.