Google Team Drives to Office 365 Migration Guide

Follow the steps below for Google Team Drives to Office 365 (Microsoft Teams / SharePoint) Migration. If you wish to use this new version, please contact us.

Overview:

  1. Introduction
  2. Prerequisites
  3. Create Your Connectors
  4. Google Team Drives Migration Settings
    1. Group List
    2. Specify Your Destination
    3. Mapping Table
    4. Global Settings
    5. Audit
    6. Pre-Processing
    7. Migration
  5. Troubleshooting

1. Introduction

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 migrate your Google Team Drives to Microsoft Teams or to SharePoint sites.

1.1. Performance & Security

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

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

1.2. License Management

Cloudiway platform automatically assigns the licenses, for more details regarding the license management, check out this page.

1.3. Delta Passes

Delta migration is a Cloudiway functionality that allows you to migrate incrementally. Changes are migrated during delta passes. Deletions are not propagated.

1.4. Support

Although we provide support for our own products, we do not provide support for third-party products such as PowerShell nor SharePoint administration.

If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contact us. This will ensure a fast, cost-effective, and stress-free implementation.

2. Prerequisites

2.1. How it works

The product uses the Google Drive APIs to read the source and a mix of Graph APIs and CSOM calls to push the data to the target.

Migration from G Suite requires to set up an OAuth authentication with appropriate permissions.

Some contents/settings from Google Team Drives can’t be migrated in the current version:

  • “Commenter” permissions. There is no equivalence in Office 365.
  • External Shared links.

2.2. Mapping Table

In Google Drive, 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 the loss of permissions and metadata.

Prepare your mapping table for users and groups/teams in CSV format, ready to upload later on.

2.3. Source Prerequisites

To perform the migration, you will need to create a G Suite migration account, give access to your Drive API (Google feeds). The migration account must have 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.

If you give sufficient permissions to the Cloudiway service account (Google feeds), the platform can add the permissions to the Team Drives for you.

Read more: G Suite Connector Configuration.

2.4. Target Prerequisites

We recommend creating an Office 365 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).
  • Legacy Authentication must be turned on.

Cloudiway automatically creates the team or Sharepoint site, therefore they don’t have to exist prior to the migration. If they already exist, it will be used and data appended to it.

2.5. 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 our How To Create Azure Apps Registration page to create the Azure Active Directory Application and associated permissions.

3. Create Your Connectors

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. 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.

4. Google Team Drives Migration Settings

Note: to test the migration, you can use a Trial License, please consult this article to assign a Trial License.

4.1. Group List

To perform the migration, navigate to Sites > Group List

Sites Migration

Use the Get List option to fill the list of Team Drives to migrate:

Migration GetList

This will connect to Google Team Drives and retrieve all available teams.

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 list is retrieved, you need to assign a target connector to the entries.

Select the entries, click on MANAGE, then Assign Target.

Google Team Drives to Office 365 Assign Target Migration

Select the connector, click on Assign.

Add a team drive manually

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 run Get List.

  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 MANAGE then Create
  5. Fill in all details for the team drive to be migrated
  6. Click on the OK button.

4.2. Specify Your Destination

The product gives you the flexibility to migrate to a large choice of targets and gives you the possibility to reorganize your data. You can migrate your Team Drives:

  • To different team channels
  • To different channels within a team
  • To different SharePoint sites
  • To different libraries within a SharePoint site
  • To different folders within a SharePoint library

Migration to SharePoint Sites:

Google Team Drives to Office 365 Modern Site

Enter the URL of the site.

Enter the optional Library Name: leave empty to migrate to the default document library of the site.

Enter the optional Folder Name (within the library).

Migration to Teams:

Google Team Drives to Teams

Enter the team name and email address.

Enter the optional Channel Name, leave empty to migrate to the default general channel of the team.

4.3. Mapping Table

Mapping Table

Click on Mapping Table.

You can upload a User or Group list via CSV (use IMPORT) or CREATE your entries manually.

A template of CSV file is available on the platform when you click on IMPORT.

FirstName;LastName;SourceEmail;TargetEmail;DisplayName;EntryType;

  • User example: test;user1;test@source.com;test@target.com;test user;0
  • Group example: ;;testgroupe@source.com;testgroup@target.com;testgroup;1

EntryType: enter 0 for user, 1 for group.

FirstName and LastName: Leave blank for group.

4.4. Global Settings

At this point, you are ready to migrate.

Most of the settings below are not used for Google Team Drives migration, you can leave the default values:

Teams Migration Global Settings

Membership MigrationEnable the migration of team members
Conversation MigrationEnable the migration of channel Conversations
Planner MigrationEnable the migration of Planners
Mailbox MigrationEnable the migration of team mailboxes
Mentions MigrationEnable the migration of Mentions
Migration of TermStoreEnable the migration of TermStore, therefore you can safely leave it Off by default unless you have customized it.
Migration of PermissionsEnable the migration of Permissions (files permissions...)
Migration of SharepointEnable the migration of SharePoint sites associated to the team
Keep in targetKeep files if already present at the target (existing files will not be overwritten)

4.5. Audit

This feature reports information about the Source Team Drives:

  • Number of files

To Audit a team drive, in Group List, select it and click on MIGRATIONAudit.

Team Drives Audit

4.6. Pre-Processing

The pre-processing tool creates the site or team at the target if it doesn’t already exist.

What does the pre-processing tool do in detail?

At the target:

      • It creates the team and channels.
      • It creates the SharePoint sites and libraries.
      • 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.

To pre-process a team, in Group List, select it and click on MIGRATIONPre-Processing.

The group or team is now ready to be migrated.

4.7. Migration

Before starting the migration, you must run the pre-processing (see step above) of the team drive.

To start the migration, in Group List, select it and click on MIGRATIONStart.

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.

Microsoft Teams Migration Logs

5. 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/

 

Cloud Migration Cloudiway
Want to try?
BOOK A DEMO
Cloud Migration Questions
Any questions?
Contact