This article outlines the workflow for migrating SharePoint Online to Google Shared Drives document libraries. Additional scenarios with known behavior and limitations are described at the end of this article.

First time?

If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices. If you have never performed a migration before, we suggest reading that before beginning the steps outlined in this guide.

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction. 

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migration projects.

Prerequisites

It is important to highlight the following prerequisites for a smooth migration project.

Licenses

This migration scenario uses the Shared Document license type. 

• Both licenses, Shared Document 50GB or Shared Document 100GB, can be utilized.
• Each license allows up to the maximum quantity of data it permits to be migrated per Document Library.
• If more than 100GB of data per Document Library is being migrated, purchase enough licenses to cover the total data being migrated. For example, if you have six Document Libraries and two have 200GB of embedded data, you must purchase eight licenses. 

This license migrates the following for this migration type:

• Documents
• Folders
• Permissions
• Major versions (up to 25)

Limitations

Consider the following limitations when performing this type of migration. We are aware of these issues and are working to find a resolution:

• App password usage, MFA/2FA, and ADFS are not supported for the migration admin account/service account being used by this endpoint.
• Please consider the following permission limitations for this migration scenario:
  • Document permissions are always migrated even when unchecking the Document Permissions checkbox during the configuration of the Full migration process. 
  • Full control permissions for folders are not migrated.
  • External permissions are not migrated for both files and folders.
  • Group permissions are not migrated for the SharePoint Online endpoint.
• The UMB license is not applicable to this migration. However, the UI currently presents an option to apply the UMB license. This is a known issue, and users must ensure they apply only the document-related license, not the UMB license.
• When migrating a file, the owner of it becomes an editor.
• Newly added permissions are not migrated during the second pass.
• Metadata information is not reflected in the UI after migration.
• Filtering by File name is not working as expected.
• File descriptions are not being migrated.

• MigrationWiz project line item setup currently does not support shared drive names with emojis (destination). 

  Tip

  We recommend renaming such shared drives (removing emojis) before setting up line items in the MigrationWiz project.

Membership Limits

Users in Google Groups can be added to a shared drive.

• Max 600 Combined users.
• Max total 50,000 individuals (users).

This is a Shared drive limitation in Google Drive. For more information, please review this article. 

File Sharing Limits

A given file within a shared drive can be directly shared with a maximum of 100 groups.

Folder Limits

A folder in a shared drive can support up to 30 levels of nested folders.

Format Conversions

In this migration type, MigrationWiz migrates some of the Microsoft files in the following ways:

• Microsoft Word (.docx) documents will be converted into Google Docs format.
• Microsoft Excel (.xlsx) documents will be converted to Google Sheets format.
• Microsoft PowerPoint (.pptx) documents will be converted to Google Slides format.

Migrated Items

Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.

Permissions Mapping

By default, MigrationWiz will map permission for users using the prefix of the User Principal Name (UPN) between the Source and Destination users.

If your source has multiple domains or the User Principal Name (UPN) is different, we strongly recommend using the UserMapping advanced option to ensure permissions are mapped correctly.

Prepare Source Environment

Prerequisites

Prepare the source environment by following the steps below:

1. Create the SharePoint site and make a note of the site URL where the document libraries are stored.
2. For migrating permission purposes, ensure all necessary users are set up in the destination Google Workspace.
3. Enable your application permissions.

Application Permissions for SharePoint

Continue configuring your destination environment by selecting one of these application permissions options and following the steps to enable permission levels at the source.

Prepare the Destination Environment

Prerequisites

Please meet the following prerequisites for the Shared Drive Membership permissions.

• Create a Google Shared Drive folder.
• Set up the Google service account and API scopes for Destination.
• Have at least 1 active member from the destination shared drive with a Manager role. Without this migration will not succeed.
• When your destination does not have an active member with a manager role, use the advanced option SetDestinationAdminAsSharedDriveManager=1. This advanced option allows MigrationWiz to use the Super Admin account required from the destination endpoint and set it as a manager for the destination shared drive.

Set up the Google Service Account and API Scopes

Step 1: Create a Google Project

1. Go to the Google Cloud Platform (GCP) Console and sign in as a super administrator. Choose one of the options below:
   • If you have not used the Google Cloud Platform Console before, agree to the Terms of Service and click Create Project.
   • If you have used Google Cloud Platform Console before, at the top of the screen next to your most recent project name, click Down to open your projects list. Then, click New Project.
2. Enter a project name and click Create.

If you cannot create a project here, the create projects permissions might be disabled for your tenant. To check this follow the steps below:

1. Navigate to the Google Admin Center
2. Click Apps > Additional Google Services
3. Select the Google Cloud Platform.

In the Google Cloud Platform settings, you will find an option that can be toggled to enable users to create projects. Make sure this setting is turned on to restore the ability to create projects.

Step 2: Enable APIs for the Service Account

1. From the Google Cloud Platform Console, click Menu > APIs & Services > Library.
2. Enable the following APIs by selecting the specific API and clicking Enable.
   Repeat for each API listed below for each endpoint:
   • Google Drive API
   • Admin SDK API

Step 3: Create the Customer Tenant Service Account

1. Navigate to Menu () > IAM & Admin > Service accounts from the Google Cloud Platform Console. 
2. Click + Create Service Account at the top middle of the screen and enter a name.
3. Click Create.
4. Assign the role of Owner to the new Service Account by selecting Owner from the Role dropdown menu.
5. Click Continue to move to the next step, then click the Done.
6. On the ‘Service accounts' page, click the vertical ellipsis “⋮” under the 'Actions’ column for the service account created above, and click on Manage Keys.
7. Click + Add Key.
8. Click Create New Key. Make sure that JSON is selected
9. Click Create.
   • Make sure that you download the key as a JSON file and make a note of the name and location of the file. This JSON file will be used when setting up the source endpoint in the migration project.
   • The JSON file must contain information in the following fields: “type”, “private key”, and “client email”. If these mandatory fields are empty, the file upload during the endpoint creation process will fail.

Step 4: Find your Unique ID

From the Google Cloud Platform Console:

1. Go to Menu > IAM & Admin > Service accounts.
2. Find the service account that was set up in Step 3: Create a Customer Tenant Account.
3. Find the Unique ID field for that service account by clicking the Column Display Options “|||” button in the upper right corner above Actions.
4. Select the Unique ID checkbox.
5. Click Ok.
6. Copy this unique ID number.
   
   • This is the Client ID number that will be used in a later step.
   • This Client ID should be considered as confidential as Administrator account passwords and handled securely.

Step 5: Setting the Scopes for the Migration

1. From the Google Cloud Platform Console, click Menu.
2. Navigate to Menu > Security > Access and data control > API controls > Manage Domain Wide Delegation.
   

   Important

   If you do not see the security icon on your admin console home page, you do not have the necessary rights on your account to make these changes. Request Super Administrator access from the customer to implement these changes. Google limits settings access and configuration to only G Suite Super Administrator accounts.

3. Click Add New.
4. In the Client Name field, paste the service account Unique ID copied above.
5. For OAuth scopes, enter the scopes listed below:
   https://www.googleapis.com/auth/drive,
https://www.googleapis.com/auth/admin.directory.group.readonly,
https://www.googleapis.com/auth/admin.directory.user.readonly,
https://www.googleapis.com/auth/admin.directory.domain.readonly
6. Click Authorize.

MigrationWiz Steps

Set up a Document Migration Project

1. Sign in to your MigrationWiz account.
2. Click Go To My Projects.
3. Click Create Project.
4. Click on Document Project to create a new project.
5. Enter a project name and select or create a Customer.
6. Click Next Step.
7. Select a Source and Destination endpoint from the endpoint dropdown menu. Otherwise, follow the steps below in the Endpoint section.
8. Click Save and Go to Summary.
9. Click Save Project.

Endpoints

The steps in this section outline how to create the endpoints in MigrationWiz. Consider only ten endpoints will be shown when selecting an existing endpoint. If you have more than ten, you may need to search.

Endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created with any unique spellings or capitalization you may have used.

You may either use existing endpoints or create new ones.

Add Line Items

There are three options for adding items. Choose which one you will use and follow the steps below. While Autodiscover Items is recommended, Bulk Add and Quick Add may also be used.

Capturing the Document Library Path for Line Items

For more information about how to correctly capture the SharePoint document path when using Quick Add please expand the dropdown below. Keep in mind that this information is also applicable to Advanced Options.

Advanced Options

Configure or edit your project's advanced options by going to the Edit Project dropdown and selecting Advanced Options.

The following advanced options may be useful for your migration. 

Support Tab

Consider that each Support Option includes the "=" character. You can add blank fields by clicking the "+" button, and delete a field by clicking the trash can icon next to it.

• InitializationTimeout=8 This increases the initialization timeout window to eight hours. This value is in hours, up to a maximum of 100 hours. Values above 100 are in milliseconds. This is useful for large migrations. For example:​
  • InitializationTimeout=2 will increase the timeout to 2 hours.
• FolderMapping="^DestinationSharedDrive->DestinationSharedDrive/DestinationFolder" This advanced option modifies the target folder path to migrate the data to a specific folder in the destination shared drive. For more information, please review this article.
• UserMapping="abc_user1@source-domain->pqr_user5@destination-domain"
  

  Important

  For the UserMapping AO consider that on the left side of it is the current UPN of the User and the Source Endpoint, on the right side is the new UPN you want permissions mapped to in the Destination endpoint.

  • The User Mapping command requires one line per user. Click the + to add additional lines. Replace the UPN addresses in the example with the actual UPN addresses.
  • By default, we match users from the source to the destination based on the prefix in their User Principle Name (UPN). For example, if the user UPN is “name@domain.com”, we match the “name” portion.
  • We recommend using  UserMapping="name@source.com->full.name@destination.com" to set the new or correct name for each user when:
    •  Multiple people have the same prefix at the destination, for example, name@domain1.com and name@domain2.com.
    • The prefix of a particular user is changed in the destination, for example, name@source.com → name.full@destination.com.

Filtering Tab

Folder filtering excludes or includes specific source folders in the migration pass. For more information and examples about this topic, review the Folder Filtering and Mapping in MigrationWiz.

Source/Destination Tab

Set the number of versions to be migrated per project requirement and click Save.

• The minimum number of versions to migrate is 1, the maximum number is 25. 
• The default selection for the number of versions is 1. Please update this value as per your requirements.

Verify Credentials

You may verify the endpoint credentials and any items in the MigrationWiz project without migrating data or consuming any licenses.

1. Open the project containing the line items to validate.
2. Select the items to validate.
3. Click on the  Start button in your dashboard.
4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status column.

Run Migration

Trial

Trial migration is optional and does not require a migration license. Keep in mind that it migrates a very small amount of data to test that the project has been created properly. For more information, please refer to the MigrationWiz: the Migration Process article.

To run a trial migration, follow these steps:

1. ​Sign in to your MigrationWiz account.
2. Click on your migration project. If you have not created a project, create a project (following the steps laid out in the Create a Mailbox Migration Project below) and add a user to that project.
3. Select the user for whom you wish to perform the trial migration.
4. Click on ​ Start.
5. From the drop-down list, click on Trial Migration.
6. Click on Start Trial Migration.

Full

To initiate the migration of document libraries:

1. Open the project containing the items you wish to migrate.
2. Select the line items to migrate.
3. Click on the Start button in your dashboard.
4. Select Full Migration from the drop-down list.
5. Ensure that the Documents, Documents Permissions, and Versioning checkboxes are selected.
   
6. Click Start Migration.
7. Once complete, the results of the migration will be shown in the Status section.

Multi-pass Behavior

In the event of a multi-pass migration, MigrationWiz will pick up from where it stopped previously and not migrate files that were already migrated.

MigrationWiz will not migrate, nor overwrite, existing files at the destination which were unchanged from the first migration. However, if a source file has been modified after a migration pass, its destination file and its versions will be overwritten in a subsequent migration pass.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly. For more information review the Document Migrations article.

If problems persist contact Support.

Post-Migration Steps

1. Prevent users from inadvertently using the Source SharePoint libraries and decommissioning the Source SharePoint, libraries, or user accounts.
2. Delete all the Azure containers used for this migration. This will prevent incurring post-migration costs. Be careful to only delete the containers created for this migration.

Remove App Permissions

1. Remove the newly created user.
2. Remove the MigrationWiz Security Group.

To remove the app from the source or destination, perform the following steps:

1. Sign in to Microsoft Entra admin center.
2. Select Microsoft Entra ID.
3. Go to Identity > Applications > Enterprise applications, in the left bar of the window.
4. In the Manage section, select All Applications.
5. Search for the application permission you installed in the Prepare the Source Environment section, and select it.
6. Go to Manage > Properties, and select Delete from the properties bar.