Introduction
This is the complete onboarding task flow for migrating folders and documents from Google Drive to Google Drive. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
The Source and Destination must both be paid versions of Google Drive. Free Google Drive accounts are not supported. The Source and Destination absolutely require a Google administrative account.
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".
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
- Enable OAuthentication 2.0 within your Google admin portal to grant MigrationWiz access to G Suite. This step will require a Google admin account. For guidance, see Enable access to G Suite using OAuth 2.0.
Notes: - 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, as they 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.
- 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.
- Enable API Access. Log in to Google Admin portal > Security > API Reference > checkmark the Enable API Access button.
Note: This extra step is mandatory when migrating from Google Drive. - Export mailboxes to CSV file(s). From Google Admin portal > Click Users > Click ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.
Prepare the Destination Environment
- Grant MigrationWiz OAuth2.0 access to authenticate to Google Drive. This step will require a Google admin account. For guidance, see Enable access to G Suite using OAuth 2.0.
- Add users to Google Drive. Instructions are located here.
MSPComplete Steps
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- For the Source endpoint:
- Click Endpoints > Add Endpoint, then enter endpoint name. For endpoint type, select Google Drive.
- Enter the Google admin account email address and domain name in the appropriate fields.
- Both the source and destination domains will need to be listed in the endpoint for the migration to be able to connect properly.
- For the Destination 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.
- Both the source and destination domains will need to be listed in the endpoint for the migration to be able to connect properly.
- For the Source endpoint:
MigrationWiz Steps
- Create the Document Migration project. Read the How do I create a new migration project? article for more information.
- Add the accounts (also referred to as "items") that will be migrated to the project.
Note: If 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. KB004842 - Set the Project Advanced Options. KB004834
InitializationTimeout=8- This increases the initialization timeout window to eight hours. KB005099DocumentBrowsingMode=ModerateFor more information, see How does Google Drive to Microsoft OneDrive with Moderate Mode work?ShouldConvertToDestinationFormat=1This command will keep migrated items in Google Format. For more information see How are format conversions handled from Google Drive to Microsoft OneDrive? And vice versa?SyncItems=1– This option allows changes in the documents on the source to be synced to the documents already migrated to the destination.
Important: The Sync Migration Pass should only be used in exceptional situations and only on the final Full migration pass. Running it more than once can result in multiple document versions being created in the destination if versioning is enabled. We recommend that versioning be turned off before migrating, as a best practice. See What do I need to know about the Sync Migration Pass? 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 detailed above.
- 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 the acquired company's G Suite Gmail) or Destination email address (if users have already been migrated to the acquiring company's G Suite Gmail).
- Customize notification email. Check the Customize "successful migration" email box. Add your own customization text and company name to this email.
Note: 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. KB004511
- Run an assessment to calculate the number of licenses required for your migration. KB005237
- Purchase User Migration Bundle licenses. Refer to these articles for more information:
- Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Source Google Drive accounts, because any modifications will not be included in the migration.
- 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.
- Full Migration strategy. For more information, see How do I start a migration?
- Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626
Post-Migration Steps
- 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.
Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion.
Comments
0 comments
Please sign in to leave a comment.