This is the complete onboarding task flow for migrating folders and documents from Google Drive to Microsoft SharePoint Online. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
This is a one-to-many migration path. This means that data that belongs to one user will be migrated into a shared document library. This is a rare business case, because individual data would then be accessible by multiple people. This migration scenario is free and requires no MigrationWiz licenses.
If performing a Google Drive to OneDrive for Business migration, refer to the Google Drive to OneDrive for Business Migration Guide. This is the most common migration scenario for Google Drive migrations.
Permissions are supported from Google Drive to SharePoint Online. 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. firstname.lastname@example.org 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 How are shared documents handled when migrating documents? for more information.
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".
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
- Enable OAuthentication 2.0 within your Google admin portal, to grant MigrationWiz access to G Suite. For guidance, refer to the Enable access to G Suite using OAuth 2.0 article.
- If you are migrating from multiple domains, repeat the 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 Google Legacy free accounts is not supported.
- Enable API Access. Log in to the Google Admin portal > Security > API Reference > checkmark the Enable API Access button.
- This extra step is mandatory when migrating from Google Drive.
- Export mailboxes to CSV file(s). From the Google Admin portal > Click Users > Click ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.
Prepare the Destination Environment
- Create a SharePoint Online administrator or Site Collection administrator account to be used for migration, or use the global admin account for the tenant. Read the Manage administrators for a site collection article from Microsoft for more information.
- Create a SharePoint site.
Note: Make a note of the site URL where the document libraries will be stored. This will be entered when creating your MSPComplete Destination endpoint.
- Before beginning the migration project, create the structure of the document libraries, and also create the actual document libraries on the Destination SharePoint Online site.
Note: Refer to the Training: Introduction to document libraries video from Microsoft for more information.
- Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.
- Create the customer. Read the View, Add, and Edit Your Customers article for more information.
- 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 SharePoint.
- Enter the URL for the top level SharePoint document library.
- Enter the administrator username and password in the fields.
Note: This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.
- Create the Document Migration project. Read the How do I create a new migration project?article for more information.
- Add the accounts (items) that will be migrated to the project. Read the How do I add items to my migration project? article for more information.
- Click Add and enter the email address of each Google Drive user for Source, and the corresponding document library name at the Destination that the Source documents will be migrated into.
- If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/Documents/", enter Documents as the document library name.
- If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/Shared Documents/", the name of the document library that needs to be entered is Shared Documents.
Note: ‘/' characters are not supported in the destination library name. Attempting to migrate any destination library with a '/' character will result in a migration failure.
- 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.
- RenameConflictingFiles=1- This automatically renames the files that have the same name. It will rename the files to their original file names, followed by a unique identifier hash so it does not interfere with the original name and search. Read the How do I migrate multiple files with the same name into OneDrive? article for more information.
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 above.
- Run Verify Credentials. Read the How do I verify credentials? article for more information.
- Notify users that a migration is occurring. Send email to all users letting them know 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.
- Perform the migration. Read the How do I start a migration? for more information.
Important: Deselect permissions before migrating. If permissions are left checked, this will result in errors during your migration, because permissions cannot be migrated for this scenario.
- 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.
To prevent users from inadvertently logging in and using their Google Drive accounts, decommission the Google Drive user accounts, or change their passwords.
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.