Google Team Drives to Office 365 Groups Migration Guide

Overview:

1. Group migration with Cloudiway
2. Security
3. Performance
4. Group migration scope
   1. What can be migrated?
   2. Migration considerations
   3. Audience
5. Pre-migration configuration
   1. Before you start
   2. Migration requirements
6. Use the Cloudiway platform to migrate Team drives
   1. Create your Google Team Drives source connector
   2. Create your Office 365 target connector
   3. Import Team drives with the Get Groups / Teams command
   4. Add a Team drive manually to Cloudiway
   5. Import or create your user details
      1. Option 1: CSV import
      2. Option 2: Create a single user
   6. Preprocessing (recommended)
   7. Activate and monitor your migration
7. Troubleshooting

1. Group migration with Cloudiway

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:

1. You set up a migration account and tell the Cloudiway platform where to find your groups.
2. Cloudiway retrieves a list of Team drives that the migration account has access to.
3. You choose which Team drives to migrate and their target and activate migration.
4. Cloudiway creates the target object (Office 365 group).
5. Cloudiway creates the target content and adds members and permissions

2. Security

For more information about security, please refer to this article.

3. Performance

For more information about migration performance, please refer to this article.

4. Group migration scope

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:

• Documents
• Permissions (Owners and members and Reader, within the per-processing task)

4.2. Migration considerations

Some contents/settings from Google Team drives cannot be migrated in the current version:

• “Commenter” permissions. There is no equivalence on Office 365
• External Shared links. Currently not available in Google Team Drives.

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:

• Files (new and modified files will be migrated during a delta pass)
• Folders (only new folder will be migrated during a delta pass)

4.3. Audience

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 presales@cloudiway.com. This will ensure a fast, cost-effective and stress-free implementation.

5. Pre-migration configuration

5.1 Before you start

Before you start, you will need to ensure you have the details outlined in the following table.

5.2. Migration requirements

Pre-migration checklist

To ensure successful migration, we recommend that you follow the checklist.

1. Deactivate MFA On Your Office365 Migration Account (guide: https://kb.cloudiway.com/article/deactivate-mfa-on-your-office365-migration-account/)
2. Prepare any mapping tables for users and groups in CSV format, ready to upload later on.
3. Ensure the source and target migration accounts have admin access to all site collections.
4. If you let the platform create the site collection, the migration account must be SharePoint administrator.

Migration account

On your G Suite tenant, you must create a new account and give it the following rights:

• Standard user
• Access on G Drive
• By default Tenant administrators can see all Team Drives but cannot migrate the files
• Therefore you must give the role organizer to the migration account on every Team Drives you want to migrate. (The platform can do it automatically for you, see below).

On your Office 365 target tenants, you must create a new account and give it the following rights:

• Global Admin tenant
• License to get access to OneDrive and SharePoint online

Grants access to Drive API for the Cloudiway service account

• Go to https://admin.google.com and log in with your Admin console credentials
• Click on Security, then Advanced settings (you might need to click on Show more to see this)
• Click on Manage API client access

• In the Client Name: paste 114818336788408865729
• Click on the One Or More API Scopes field and add the following scope:
• https://www.googleapis.com/auth/drive.readonly (However if you want to grant automatically the organizer permission on all team drives, you need to give https://www.googleapis.com/auth/drive)
• Click on the Authorize button.
• You can check that the scopes were successfully registered by looking for the names next to the client ID you paste.
• Now, navigate to Security > API Reference > API Access and ensure that ‘Enable API Access’ is checked.

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.

Microsoft Graph:

• Group.Read.All, Group.ReadWrite.Alls, User.Read.All, Directory. Read.All.
  • See https://docs.microsoft.com/en-us/graph/api/group-get?view=graph-rest-1.0
  • And https://docs.microsoft.com/en-us/graph/api/group-list-members?view=graph-rest-1.0
• Sites.ReadAll, Sites.ReadWrite.All, Sites.Manage.All, Sites.FullControl.All

SharePoint Graph: 

• Sites.FullControl.all 
• Sites.Manage.all 
• Sites.Read.all 
• Sites.ReadWrite.All

For CSOM access, the migration account must be SharePoint administrator.

The migration account must have a license and must have logged to his mailbox at least once.

6. Use the Cloudiway platform to migrate Team Drives

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.

1. Click on Group Migration in apps.cloudiway.com site, and then click on Sources.
2. Click on the + New option at the bottom of the screen and click on Office 365.
3. Type a meaningful name in Connector name and click on the Create button.
4. Enter the email of the account used to access the Team Drives.
   If you enter a tenant administrator email address, it will access by default all the team drives. If not, you have to give the migration account the permissions to all team drives you want to migrate.
   
5. Clik on the Save button at the bottom of the screen.

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.

1. From the Site & Group Migration , click on Targets.
2. Click on the + New option at the bottom of the screen and click on Office Group / Team.
3. Type a meaningful name in Connector name and click on the Create button.
4. Fill in the fields.
   

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.

1. Ensure you’re still in the Group Migration area of apps.cloudiway.com and go to Group List.
2. Click on the Migration menu at the bottom and select Get Groups / Teams to display the following dialog box:
3. Select your source from the dropdown list and click on the Get button.The tool will return a list of all team drives that the ‘migration’ user has been added to with full access. 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 target name and delete any team drives that don’t need to be migrated.

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.

1. Go to your Google Drive and Develop the Team Drives section. Search for your team drive and open it.
2. Take note of the URL of the team drive and the ID:
3. On the Cloudiway platform, go to the Group List of the Group Migration menu.
4. Click on Edit in the bottom left corner and select Create Single to display the following screen:
5. Fill in all details for the Team drive to be migrated, using the email address and URL from the Team drive details in step 3.
6. Click on the Create button.
   The new team drive will be added to the Group Migration / Group List screen.
7. Repeat steps 1 to 7 for any more Team drives you’d like to add manually.

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:

FirstName;LastName;SourceEmail;TargetEmail

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.

1. Ensure you’re still in the Group Migration area of apps.cloudiway.com and go to Mapping Users.
2. Click on User on the action bar and select Upload CSV.
   
3. If required, click on Download sample CSV and add your users to the CSV file using the sample headers (FirstName;LastName;SourceEmail;TargetEmail).
4. When you have a complete CSV file with the correct headers, click on the Upload button.
5. Locate your CSV file within your own file system, and double-click on it to select it. If the CSV file format is not correct, you will see an error message on your screen:
   
6. If you see any error messages, check your CSV file to ensure it has four columns each with a separator (including the last), and try uploading again.
7. Once the CSV file format is correct, you will see a confirmation message at the top of your screen:
8. Check your email for confirmation that all uploads have been completed: you can also refresh the Cloudiway platform to display your imported users.
9. If you wish to edit any user that’s been uploaded, click on the user from the user  list to display the editable list of fields.

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.

1. Go to the Mapping Tables area of the Group Migration menu.
2. Click on User on the action bar at the bottom of the screen and select Create Single to display the following screen:
3. Fill in all details for a new user:
   
4. Click on the Create button.
   The new user will be added to the Group Migration / Mapping Tables screen:
   
5. Repeat steps 1 to 4 for any more users you’d like to create.

6.6. Preprocessing

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:

1. Create the target recipient.
2. Migrate the membership (owners and members).

The Pre-processing task will do the following actions:

• Create the Group or Team: it will use the name you have defined in the field Target name as name and alias. The Email will build by using the alias and the technical domain name of your tenant.
• Read the permissions from the source Team drives.
• Add permission on to the Group or the Team
  • Full access on Team Drives will give you the owner permission on the Office 365 group
  • Editor on Team Drives will give you the member permission on the Office 365 group
  • Reader on Team Drives will give you the read permission on the site of the Office 365 group
  • Commentor on Team Drives are not migrated (no equivalence)

The Pre-Processing can terminate in two statuses:

• ERROR-PreProcessing: The task encounters an issue. Review the logs for this Team drive.
• NOT STARTED: The task is successful. You can start the migration for this Team drive.

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.

7. Troubleshooting

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.