This article provides instructions on configuring a migration batch for migrating Shared Drives from Google Workspace to SharePoint site document libraries in Microsoft 365. The setup process outlined here focuses on migrating files.
Before proceeding, ensure you have completed the steps in the Google Workspace to Microsoft 365 Migration Guide to set up your migration project and added a Shared Drives migration batch.
Adding Items to Migrate
When migrating from a Shared Drive to SharePoint sites, there are two available options:
-
Migrating to a New SharePoint Site: If the SharePoint site does not yet exist, the CloudM Migrate can automatically provision the site and migrate data into the default "Documents" document library.
-
Migrating to an Existing SharePoint Document Library: If the target document library does not exist, it must be provisioned ahead of time.
When preparing to migrate Shared Drives to corresponding SharePoint site document libraries, follow the format below:
Example:
-
Source Shared Drive ID:
0AJdUYx8YE1ihUk9PVA -
Destination SharePoint Site URL:
https://destination.sharepoint.com/sites/testsite
- Export Type: Shared Drive
-
Export Name:
0AJdUYx8YE1ihUk9PVA - Import Type: Team Site
-
Import Name:
sites/testsite - Given Name: Destination Document Library name. If the site and document library is not pre-provisioned, this should be set to "Documents".
- Family Name: Display name of destination SharePoint site.
- Documents Path: ID of the folder at the source you wish to migrate from. This is optional, leave blank if you want to migrate from the root of the shared drive.
- Documents Destination Path: Name of the folder you wish to migrate to at the destination.
For each Shared Drive entry, you can only migrate drive items. Make sure the drive option and the 'Migrate' option is enabled for all shared drives included in the migration.
General Settings
In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.
You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.
Source Settings
For a standard Shared Drive to SharePoint site migration, it is recommended to keep most of the source settings at their default values. Detailed information about each setting can be found in the article linked below:
Google Workspace - Source Settings
Destination Settings
For a standard Shared Drive to SharePoint site migration, most settings can be left at their default values. However, you may want to consider the following options:
-
SharePoint Online -> Migrate previous document versions: Enable this option to migrate previous major versions of documents in the migrating document libraries. Enabling this feature allows you to select the number of versions to migrate but will significantly increase migration run times.
-
SharePoint Online -> Maximum number of previous document versions: Select the number of versions you plan to migrate.
-
SharePoint Online -> Provision Sites: Enable this option if you want the migration tool to automatically provision SharePoint Sites at the destination.
Depending on your specific migration scenario, you may need to adjust additional settings. The article below provides a detailed overview of all available destination settings for Microsoft 365:
Microsoft 365 - Destination Settings
Advanced Settings
For a straightforward Shared Drive to SharePoint site migration, most advanced settings can remain at their default values. However, consider the following:
-
Address Replacement: It is highly recommended to upload an address replacement CSV that maps source resources, users and groups to their corresponding destination items. For more information, please refer to the Address Replacements article.
Additional settings are outlined here: Advanced Settings
Migration Process
The migration process will vary depending on your project's specific approach. Generally, it is advisable to start with a bulk migration and perform delta migrations closer to the final migration cutover date.