Migrating to or from Google Shared Drives

CloudM Migrate supports the following migration scenarios for Shared Drives:

  • Migration from Shared Drives to One Drive
  • Migration from Shared Drives to Sharepoint Online
  • Migration from Shared Drives to Unified Groups
  • Migration from Shared Drives to Microsoft Teams
  • Migration from Shared Drives to Google Drive Users for different domains
  • Migration from Google Drive to Shared Drives within the same domain
  • Migration from Google Drive to Shared Drives for different domains
  • Migration from Shared Drives to Shared Drives for different domains
  • Migration from a file system to Shared Drives
  • Migration from Dropbox to Shared Drives
  • Migration from Box to Shared Drives
  • Migration from OneDrive for Business to Shared Drives
  • Migration from SharePoint to Shared Drives
  • Migration from Shared Drives to SharePoint

Requirements

  • External sharing or whitelisting of the destination domain(s) on the source is required. This is set three different ways: by the domain-wide Google Drive setting, by the shared drive setting (below the prior) and by the shared drives own settings. External (destination domain) users need to be able to be added to the source shared drives and access the files in order to perform the migration. 
    • Ensure that the "Allow people who aren't shared drive members to access files" setting is enabled

Potential error when either/both of the above are not complied with: "BadRequest[400]".

  • Your Google Workspace domain must have Shared Drives enabled. This is part of your contract with Google, so contact Google, or your reseller, if you do not have Shared Drives enabled.
  • Existing Shared Drives need to have at least one user with Manager permissions applied (if you use CloudM Migrate to create Shared Drives, however, the migration admin will become a Manager).
    • For more information on Shared Drive permissions, see here. In the Google Drive API, the "Manager" role may be referred to as an Organizer.
  • Managers must be an active user (not suspended and not a group) and have Drive enabled. 
  • Source Shared Drives must include at least one user (not group) that has 'Manager' permission set on the Shared Drive.

Migrating from Shared Drives

If you are migrating from a Shared Drive to another location, you should configure CloudM Migrate as follows:

  1. Ensure you have a license for migration from Shared Drives.  Contact your supplier or us for an updated license if required.
  2. Select Google Workspace as your source platform.
  3. In the users tab of CloudM Migrate, add a new item and make sure to select 'Shared Drive' as the export type.  Choose the appropriate import type depending on your destination platform.
  4. Specify the ID or name of the Shared Drive you are migrating from in the 'Export Name' field on the users tab. It is recommended to specify the ID.  If using the name and there are two Shared Drives with the same name, the migration will fail.
    • Please note that Shared Drive IDs are case sensitive. If the ID is entered incorrectly (e.g. using a lower case letter instead of a capital letter), CloudM Migrate will not be able to find the Shared Drive.
  5. Shared Drives are also added to the user list when using 'Get Users' to list users from the source system
  6. Configure your import user and type as appropriate for your destination platform.
  7. Run your migration.

Migrating to Shared Drives

*Destination Shared Drive settings are explained in detail here.

If migrating to a Shared Drive, the following configuration steps are required:

  1. Ensure you have a license for migration to Shared Drive. Contact your supplier or us for an updated license if required.
  2. Select Google Workspace as your destination platform and complete the Basic settings.
  3. On the Destination screen, open up the Advanced Settings section and navigate to the User section. You should enable the Create Users/Resources/Groups/Shared Drives setting so that any Shared Drives that aren't on the Destination are created as part of the process.
  4. When adding a new item, ensure 'Shared Drive' is selected for the 'Import Type' or when using 'Get items from source'. Select the row/s, right click and click 'Migrate as Shared Drive'
  5. In the users tab of CloudM Migrate, setup your source user as appropriate for your source platform. For all file-based platforms, you can specify a folder ID in 'Documents Path' from which to migrate from.  This can be used to limit the scope of the migration to a single folder. If you do this, the specified folder and all sub-folders will be migrated.
  6. Specify the name of the Shared Drive (to create a new Drive) or the ID of an existing Shared Drive in the 'Import Name' column.  This is used by CloudM Migrate to locate the Drive to migrate to.  If you specify a name, CloudM Migrate will try and find a Shared Drive with that name to use, or will create a new one. If you specify an ID, CloudM Migrate will use that ID.  If multiple Shared Drives exist with the same name, migration will fail and in this case you should specify an ID.
    • Please note that Shared Drive IDs are case sensitive. If the ID is entered incorrectly (e.g. using a lower case letter instead of a capital letter), CloudM Migrate will not be able to find the Shared Drive.
  7. Optionally, configure multiple Shared Drive Managers to speed up migrations. By default, CloudM Migrate will use all of the Managers of a Shared Drives to speed up migrations. However it is possible to configure CloudM Migrate to use extra organizers with the configuration setting: Destination Platform Migration Settings > Google Workspace > Advanced Settings > Shared Drive > Shared Drive Default Managers. If you add extra users in here, they will be added as Managers to the Shared Drive.
  8. Run your migration

You must specify the ID or name of the Shared Drive in Export Name when migrating from Shared Drives, and the ID or name of the Shared Drive in Import Name when migrating to Shared Drives. 

It is recommended to specify the ID of the Shared Drive rather than its name.  The name might not be unique within a domain and migration will fail if there are more than one Shared Drive with the same name.  Using the case sensitive ID removes any ambiguity.

Folders within Shared Drives

You may also migrate from a folder within a Shared Drive by specifying the ID of the folder in 'Documents Path'. To get the ID of a Shared Drive or folder look in the URL. eg.

  • https://drive.google.com/drive/folders/shareddriveid

In order to migrate to a folder within a Shared Drive, this is only possible by specifying a 'Top Level Folder' (Common Settings). This will create a new folder within the Shared Drive and migrate the data into it. It's not currently possible to specify an existing folder within a Shared Drive.

Shared Drive Migration Performance

To improve performance to Shared Drives, configure multiple Managers to perform the migration with the configuration setting: Destination Platform Migration Settings > Google Workspace > Advanced Settings > Shared Drive > Shared Drive Default Managers

Please note due to Google restrictions, Shared Drives are limited. Please refer to the Shared Drive Limits article on support.google.com for the most up to date information on these restrictions.

Was this article helpful?
1 out of 1 found this helpful