This is the complete onboarding task flow for migrating folders and documents from Google Drive to Google Drive.
This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. 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 scenario.
Some item types are not migrated. Click the bar below to expand the full list of what item types are and are not migrated. We are constantly working to create a better migration experience for you, so these items may change.
MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. 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.
Items and folders in "Shared with Me" will not be migrated. Only items in "My Drive" will be migrated. To migrate "Shared with Me" items, they must be added to "My Drive".
We are not able to support the use of Admin accounts that use two-factor or multifactor authentication.
- Folders you have shared
- G Suite native files (except Google Forms)
- Code Files
- Audio Files
- Templates (files that the template had been applied to are migrated)
- Creation Date (Creation date gets changed to the "date of migration" date)
- Scripts/Macros (Scripts are not converted to macros when going to documents)
- Document History
- File/Folder permissions
- Items/folders in "Shared with Me”. These folders must be added to the user’s “My Drive” and the advanced option “DocumentBrowsingMode=FullCopy” must be enabled.
- Shortcuts (Migrated in Google Drive to Google Drive scenarios only.)
- Google Shared Drives (also known as Team Drives) are not supported
This is largely because Shared Drives use a different root folder than Google Drive does. Shared Drives also follow different organization, sharing, and ownership models, so the same methods used to migrate Google Drive will not work to migrate Shared Drives.
- Personal / Free Google Drive is not supported
- File/folder shortcuts
Step 1: Source & Destination Preparation
Prepare the Source Environment
Source Endpoint: Google Drive (Own Service Account) Endpoint
This endpoint requires your tenant service account to be set up and Google APIs be enabled. Follow the steps below to set up your environment for this endpoint.
Subscription to Google Cloud Platform.
Google Super Administrator account.
Ability to set up a service account on the G Suite tenant.
Service account must be set up before the MigrationWiz project is created.
1: Create a Google Project:
Go to the Google Cloud Platform (GCP) Console and sign in as a super administrator. Choose one of the options below:
If you haven't 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.
Enter a project name and click Create.
- When the new project creation completes, at the top of the screen next to current project name, click Down icon and select the newly created project name from the list.
2: Enable APIs for Service Account
From the Google Cloud Platform Console, click Menu > APIs & Services > Library.
Enable the following APIs by selecting the specific API and clicking Enable.
Repeat for each API listed below:
Google Drive API
Make sure that the respective services are enabled within the Google tenant. You can control services for your users using the instructions on this page: Control who can access G Suite and Google Services.
3: Create Customer Tenant Service Account
From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.
Click + Create Service Account at the top middle of the screen and enter a name.
Assign the role of Owner to the new Service Account by selecting Owner from the Role drop down menu.
Click Continue to move to the next step, then click the Done button.
- You will now be returned to the "Service Accounts" page.
- On ‘Service accounts' page, click vertical ellipsis under 'Actions’ column for the service account created above.
Click Create key.
- Make sure that JSON is selected as "Key Type."
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 migration endpoint in the Mailbox 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 endpoint creation will fail.
4: Setting the Scopes for the Migration
From the Google Cloud Platform Console:
- Click Menu.
- Click IAM & Admin.
- Click Service Accounts.
- Find the service account that was set up in Step 3: Create Customer Tenant Account.
- Find and copy the service accounts Unique ID number. This is the Client ID number that will be used in a later step.
- This field often needs to be added to the view. Click on the Column display options button and add a checkmark to Unique ID, then click OK.
- This Client ID should be considered similar to Administrator account passwords and handled securely.
- You will now have one of two options, depending on if the Google UI has been updated in your tenant.
- Go to the G Suite admin page at admin.google.com
- Click Security.
- Click API Controls.
- Under Domain wide Delegation, click Manage domain-wide delegation.
- Go to the G Suite admin page at admin.google.com
- Click Security.
- Click Advanced Settings.
- Under ‘Domain-wide delegation’, click Manage domain-wide delegation.
- On the Manage domain-wide delegation page, click Add new.
Once these steps are complete:
- In the Client ID field, paste the Unique ID copied above.
- In the OAuth scopes (comma-delimited) field, paste all scopes listed below:
- For source endpoint:
https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive.readonly
- Click Authorize.
You should now see your specific Unique ID and the associate scopes listed.
Prepare the Destination Environment
Google Drive (Own Service Account) Endpoint
Follow the same steps as listed above, but use the following OAuth scopes as listed below:
For destination endpoint (must include read-write scopes):
https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive.readonly,
Step 2: Set up MigrationWiz
Create New Project
To create a new migration project:
- Click the Go To My Projects button.
- Click the Create Project button.
- Under Project Type, select Document Project. Document projects are used to migrate document drives from one cloud storage to another. Document migrations will maintain the folder hierarchy from the source to the destination.
- Enter a Project name and select a Customer. If you have not already added the customer into MSPComplete, you will need to click New to create the Customer.
- Click Next Step.
- Select the JSON file created in the steps above and enter the Super Admin username and password for the source then select the source endpoint from the Endpoint dropdown list, or create a new source Google Drive (Own Service Account) endpoint.
- Click Next Step.
- Select the JSON file created in the steps above and enter the Super Admin username and password for the destination then select the destination Google Drive endpoint from the Endpoint dropdown list, or create a new Google Drive endpoint.
- Click Save and Go to Summary.
- Click the Save Project button.
Add the accounts (also referred to as "items") that will be migrated to the project. There are several ways to do this.
MigrationWiz allows you to bulk import mailboxes into the system.
To import one or more mailboxes:
- Sign in to your MigrationWiz account.
- Select the Project for which you want to perform the bulk import.
- Click Add.
- Click Bulk Add.
- Follow the instructions on the page.
The Autodiscover process within MigrationWiz can be used to discover items from the Source environment, so that they can be imported into your projects.
There are few requirements in order for this to work:
- The Source has to be Exchange 2007 or later, or Office 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
- The endpoint on the Source needs to use admin credentials.
- For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
- The admin mailbox must be listed in the public Global Address List (GAL).
- The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.
One additional item to note here is that there is not a way to restrict the IP addresses that the connection will come from. This means that the steps outlined in our IP Lockdown guide will not apply here. If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using on of the other available options.
Autodiscover of items will not work while using Modern Authentication
Autodiscovery exposes the following items:
- For mailbox migration, autodiscovery will list all mailboxes at the Source.
Steps to Run Autodiscover
Navigate to the project you want to import users into.
Ensure that you have created an endpoint for the source project.
Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.
Once discovered, click on the Import button, to import the items into your MigrationWiz project.
Set Advanced Options
Set the Project Advanced Options. These are customization options which help MigrationWiz perform within specific environments.
Under Support/Support Options add:
InitializationTimeout=8- This increases the initialization timeout window to eight hours.
RemoveExistingPermissionsWhenUnspecified=1There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.
DocumentBrowsingMode=FullCopy. This option migrates all accessible content for a user, along with associated permissions.
Set the Advanced Option to send a notification to end users after the migration pass completes:
- Notifications > Send successful migration and notification to: > Source email address (if users are still using G suite Gmail) or Destination email address (if users have already migrated from the G Suite gmail platform).
- Customize the notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
- Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-stage migration strategy, only set this up prior to the final Full (Delta) pass.
Run Verify Credentials
You may verify the credentials of items in MigrationWiz without migrating data or consuming any licenses.
- Open the Project containing items you wish to validate.
- Select the items you wish to validate.
- Click the Start button in your dashboard.
- Select Verify Credentials from the drop-down list.
Once complete, the results of the verification will be shown in the Status section.
Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Google Drive accounts, because any modifications will not be included in the migration.
Step 3: Run Migration
Perform the migration, using one of the following strategies. More information on each strategy is included in the Migration Planning and Strategy Guide linked in the beginning of this guide.
- Full Migration strategy. For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration, and requires licenses. This migration selection will migrate all identified and supported items.
- Pre-Stage Migration Strategy: This strategy includes a Pre-Stage pass and a Full (Delta) pass. This migration selection will migrate all identified and supported items before the selected date. This migration option requires a license of the appropriate type.
Additional Migration Types
Trial - Free migration pass. This migration selection is used to test the migration server. It will migrate up to 10 items per folder or up to 5 MB of data per mailbox. A full migration with a license will pick up where the trial left off.
Verify Credentials - Free migration pass. This migration selection will test to make sure that the credentials being used for migration are correct and will allow a successful connection. No data is migrated.
Retry Errors - Free migration pass. Once a Full or Pre-Stage migration has completed successfully, Retry Errors can be run to retry only failed items.
For large migration projects that are more than 50 users, we recommend a Pre-Stage Migration strategy. This is a multiple-pass migration.
Once you have chosen your migration strategy:
Click on the name of the Project you want to run.
- Select one or more items to migrate by checking the box next to the item name. If you want to select all the items, click the checkbox to the left of Source Email.
- Click on the Start button and select the type of migration to run.
- If you want to delay your migration, then select the checkbox marked "Automatically start the migration at", and enter the date and time to have the migration start. To start a migration immediately, you do not need to select the scheduling option.
- Click Start Migration.
Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.
Shortcuts are a new type of file introduced in Google Drive. A shortcut is a link referencing another file or folder. When you open a shortcut, you are accessing (opening) the file referenced by the shortcut. Downloading a shortcut will download the file the shortcut points to. Shortcut titles are visible to everyone with access to the folder or drive the shortcut is in; however, they may only open it if they have permissions to the original file.
Migrating shortcuts is not required. If you do not wish to migrate shortcuts in your Google Drive to Google Drive migration, simply skip this section. This migration type is only available for Google Drive to Google Drive migrations and will not function in any other scenario.
Shortcuts cannot be migrated if the target document and its permissions are not already available at the destination. All relevant documents and permissions must be migrated before attempting to migrate shortcuts. If the destination target folder is not shared with the owner of the shortcut, the shortcut (within the shared folder) will not be migrated.
After all relevant documents and permissions have been migrated, you will run another migration pass. This will migrate only Shortcut files. After successful completion of this migration run, shortcut files will be available at the destination for the relevant documents.
- To prevent users from inadvertently logging in and using their Google Drive accounts on the acquired company's G Suite platform, decommission the Google Drive user accounts, or change their passwords.
- Notify users once the migration has completed.
- If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion.