Google Drive to OneDrive for Business Migration Guide

Introduction

This is the complete onboarding task flow for migrating folders and documents from Google Drive to OneDrive for Business.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

The Source must be a paid version of Google Drive. Free Google Drive accounts are not a supported Source.

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

The Destination must be OneDrive for Business, not the personal version of OneDrive.

Note: We no longer support migrations to or from GoDaddy hosted OneDrive.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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 migrations projects. For more information, visit Project Sharing in MigrationWiz. 

Prepare the Source Environment

1. Enable OAuthentication 2.0 within your Google admin portal, to grant MigrationWiz access to G Suite. Read the Enable access to G Suite using OAuth 2.0 article for more information.
   Notes:
   • If you are migrating from multiple domains, repeat these steps for each domain.
   • Make sure there are no spaces before or after the scope entry. This will cause the authorization to fail.
   • OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts, G Suite Legacy free accounts, or Google Apps Legacy free accounts. Unfortunately, migrating any Google Legacy free accounts is not supported.
2. Enable API Access. Log in to the Google Admin portal > Security > API Reference > and make sure the Enable API access box is checked. Read the Enable access to G Suite using OAuth 2.0 article for more information.
   Note: This extra step is mandatory when migrating from Google Drive.
3. Export mailboxes to CSV file(s). From the Google Admin portal > Click Users > Click ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Click Save.

Prepare the Destination Environment

1. Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. Read the How do I create an administrator account in Office 365, and then use this during migration? for more information.
   Important: The admin account must have a full license assigned to it, in order to be able to provision OneDrive for Business profiles for each user during the migration process. Read the Personal Site is not instantiated = PermissionsUserNotLicensed article for more information.
2. Assign an O365 license that contains OneDrive for Business to the admin account that will be used for migration.
   • If users have never used OneDrive before, MigrationWiz will provision OneDrive (SharePoint) profiles for each user being migrated, using the admin account credentials that are entered in the MSPComplete Destination endpoint. However, it does not create the user account; the user account needs to have already been created.
   • MigrationWiz cannot provision a OneDrive profile for blocked users. If a user is blocked, there will be a provisioning or access error.
3. Set up accounts on Office 365 and assign licenses. These can be created in several ways:
• Manually, one at a time.
• By bulk import, via CSV file. Read the Add several users at the same time to Office 365 article from Microsoft for more information.
  Note: You can use the CSV file that was created under Step 3 of the Prepare the Source Environment section of this guide.
• By PowerShell script. Read the Create user accounts with Office 365 PowerShell article from Microsoft for more information.
• By DirSync, AAD Sync or AAD connect. Read the How do I synchronize my Azure Active Directory objects to Office 365? article for more information.
• Important: If you are migrating permissions, the part of the usernames before the "@" sign on Office 365 must match the part of the username on Google Drive before the "@" sign, e.g., john.smith@domain1.com on Google Drive must follow the same format before the @ sign on Office 365, and so must also equal "john.smith" on Office 365. The domain name, however, can be different. Read the How are shared documents handled when migrating documents? article for more information.
4. Set up groups on Office 365. If permissions were assigned to groups on Google Drive, and you want these to be migrated, the group names on Office 365 must match the group names on Google Drive. Read the How are shared documents handled when migrating documents? article for more information.
5. Create the required Office 365 CNAME for your domain. Read the Create DNS records at Register365 for Office 365 article from Microsoft for more information.
6. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

MSPComplete Steps

1. Create the customer. Read the View, Add, and Edit Your Customers article for more information.
2. Create the Source and Destination endpoints. Read the View, Add, and Edit Customer Endpoints article for more information.
   • For the Source endpoint:
     • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Google Drive.
     •  Enter the Google admin account email address and domain name in the appropriate fields.
• For the Destination endpoint:
  • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select OneDrive for Business.
  • Enter the administrator username and password, for the admin account that was set up under step 1 of the Prepare the Destination Environment section of this guide.
    Important: The domain name of the admin account must match the domain name of the user accounts that will be added to the project in MigrationWiz. Otherwise, the OneDrive for Business profiles cannot be created during migration, and permissions will not be migrated. For example, do not add the admin account with the onmicrosoft.com domain name if the users will be entered with a vanity domain name.
3. Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:
   • How do I purchase licenses?
   • Migration License Types
   • Apply User Migration Bundle licenses to the Customer's Users 

MigrationWiz Steps

1. Create the Document Migration project. Read the How do I set up a migration project? article for more information.
2. Add the accounts (also referred to as "items") that will be migrated to the project.
   Note: If you are using the Bulk Add option, only the Source and Destination columns need to be filled in. You can use the CSV file that was created under Step 3 of the Prepare the Source Environment section of this guide. Read the How do I add items to my migration project? article for more information.
3. Set the Project Advanced Options. Read the What project Advanced Options are available? article for more information. 
   • Under Support/Support Options add:
     • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. Read the Cannot get folders from My Drive article for more information.
     • IncreasePathLengthLimit=1 - Use this Advanced Option in MigrationWiz to enable the use of 400 characters for the file path name. Read the What would I use the Advanced Option IncreasePathLengthLimit=1 for? article for more information.
     • RemoveExistingPermissionsWhenUnspecified=1 Read the What is the Advanced support option RemoveExistingPermissionsWhenUnspecified=1, and when should it be used? article for more information.
     • ShrinkFoldersMaxLength=200 (optional, but recommended) Read the How do I auto shrink the folder path when migrating to OneDrive for Business or SharePoint Online? article for more information.
     • DocumentBrowsingMode=Moderate (optional, but recommended) Read the How does Google Drive to Microsoft OneDrive for Business with Moderate Mode work? article for more information.
     • RenameConflictingFiles=1 (optional, but recommended). Read the Error: Cannot create 'filename' because another file exists with the same name article for more information.
     • If the migration project is a long-term project, it may be necessary to add an additional Advanced Option for use during the final migration pass to verify the contents of previously migrated items. For more information on this setting, see MigrationWiz - SyncItems Migration Option.
       Note: There 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 detailed above.
     • MapPermissionEmailByPairsInProject=1Permissions generally cannot be migrated unless the prefix of the mail address is the same in the source and the destination. However, choosing Support Option MapPermissionEmailByPairsInProject=1 will allow permissions to be migrated without identical mail addresses.
   • Set the Advanced Option to send a notification to end users after the migration pass completes. Notifications are not mandatory.
   • Notifications > Send successful migration and notification to: > Source email address (if users are still using G Suite Gmail) or Destination email address (if users are already using Office 365).
   • • Customize notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
       Note: Notifications are not mandatory for a successful migration.  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.
4. Run Verify Credentials. Read the How do I verify credentials? article for more information.
5. Run an assessment to calculate the number of licenses required for your migration. Read the How does the MigrationWiz Assessment tool work? article for more information.
6. 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.
7. Perform the migration, using one of the following strategies:
   • Full Migration strategy. For more information, see How do I start a migration?
     • For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.
   • Pre-Stage Migration Strategy:
     • Pre-Stage pass. For more information, see How do I start a migration?
     • Full (Delta) pass. For more information, see How do I start a migration?
     • For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.
8. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article for more information.

Post-Migration Steps

1. To prevent users from inadvertently logging in and using their Google Drive accounts, decommission the Google Drive user accounts, or change their passwords.
2. Notify users once the migration has completed.
   Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion. Assist them with setting up access to their OneDrive for Business accounts, and setting up their synchronization settings.
3. Provide training on OneDrive for Business.

Note: Some users may encounter error "XXX does not have solid file content" when migrating using encryption. This indicates that the user has 0 byte files in their Google Drive. As OneDrive does not allow uploading of empty files, it triggers this error during migration. 

To resolve, navigate to your Advanced Options and enter SkipNoContentError=1 under the appropriate section. This will treat the error as a warning instead of an error and simply skip those files.