OneDrive for Business to Google Drive Migration Guide

Welcome to the OneDrive for Business to Google Drive migration guide. This guide contains all the steps needed for your migration. Other useful resources and information are also linked or included.  

In OneDrive to Google Drive migrations, OneNote files will be created as a folder containing .onetoc2 and .one files. This is expected behavior.

MigrationWiz

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.

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. 

First migration?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.

Prerequisites

Please consider meeting the following prerequisites before starting your migration process.

Licensing

We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit MigrationWiz Licenses.

To use your license by following the next steps:

  1. Purchase Licenses.
  2. Create a Customer.
  3. Apply Licenses.
  4. Review Considerations.
Purchase Licenses Create a Customer Apply Licenses Considerations

Purchase licenses by following the steps below:

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose User Migration Bundle licenses.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

Limitations

Consider the following limitations for this type of migration.

  • Due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this migration type. 
  • We are not able to support migrations with two-factor or multifactor authentication. 

Migrated Items

Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.

What items are migrated?
  • Folders
  • Shared Folders
  • Permissions set at the individual folder or item level that have been granted to specific users/email addresses
  • Code Files
  • Documents
  • Images
  • Forms
  • Executables
  • Videos
  • Audio Files
  • Original metadata and BitTitan migration metadata (author, editor, created time, modified time, name, filesize, type, MigrationWizId, MigrationWizPermissionId)
  • Document attributes (Created by (person) and (time)
  • Modified by (person) and (time)
  • Versions & Metadata migrations only: Creation Date
What items are not migrated?
  • Non-Versions & Metadata migrations:
    • Creation date (Creation date gets changed to the "date of migration" date) 
    • Version History
  • Links giving access
  • Shared permissions for files/folders with symbols in name

Prepare the Source Environment

Please consider the following information when preparing your source environment.

  • Users being migrated need to be licensed to use OneDrive in the source tenant.
  • Users being migrated must not be blocked from signing into the source tenant.
  • Source OneDrives must not be set to read-only. This is initially for setup. Steps for setting up for read-only can be found under the Run Verify Credentials section later in the guide.

OneDrive Prerequisites

  • Create an admin account in Microsoft 365 for the migration, or use the global admin account for the tenant.
  • The easiest approach to follow is to use the global admin account. This was set up at the time of tenant creation. However, if you do not wish to use this global admin account during migration, then a new user account can be created instead. This will then need to be granted full access rights to each user.
  • The admin account must have a full license assigned to it, to provision OneDrive for Business profiles for each user during the migration process. 

Application Permissions for OneDrive

Continue configuring your destination environment by selecting one of these application permissions options and following the steps to enable permission levels at the destination.

Delegated Authentication App-Based Authentication

The easiest approach is to use the global admin account set up at the time of tenant creation. However, if you do not wish to use this global admin account during migration, then a new user account can be created instead. This user account needs to have a license assigned that includes OneDrive and be granted Site Collection Administrator privileges to OneDrive in the project.

  1. Create a user in Microsoft 365 and assign a license that includes SharePoint. For step-by-step instructions, see the Microsoft article Add users individually or in bulk to Office 365.
  2. Set the administration privileges. Grant one of the permission levels listed below to the user account to be user as the administrator for the endpoint in the project.
  3. Add the admin account, created in step 2, as a Site Collection Admin to the endpoint.

    Important

    The Global Admin or SharePoint Admin role does not automatically grant Site Collection Administrator rights to a SharePoint or OneDrive site.
  4. Go to MigrationWiz-SharePoint-Delegated and consent to the app access when prompted. Once you click on Accept, you will be redirected to the BitTitan login page. This is normal and the page can be closed.

Prepare the Destination Environment

Prerequisites

  • Subscription to Google Cloud Platform

  • Google Super Administrator account

  • Ability to set up a service account on the G Suite tenant

  • A service account must be set up before the MigrationWiz project is created

Create a Google Project

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

  2. Enter a project name and click Create.

If you are not able to create a project here, it may be that the ability to create projects has been disabled for your tenant. To check this, navigate to the Google Admin Center click on Apps > Additional Google Services, and select the Google Cloud Platform. Once there, you should see a setting that can be toggled to allow users to create projects.

Enable APIs for Service Account

  1. From the Google Cloud Platform Console, click Menu > APIs & Services > Library.

  2. Enable the following APIs by selecting the specific API and clicking Enable.
    Repeat for each API listed below:

    • Google Drive API

    • Admin SDK

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.

Create a Customer Tenant Service Account

  1. From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.

  2. Click Create Service Account and enter a name.

  3. Click Create.

  4. Assign the role of Owner to the new Service Account by selecting Owner from the Role drop-down menu.

  5. Click Done.

  6. You will now be returned to the "Service Accounts" page. 
  7. On the ‘Service accounts' page, click the vertical ellipsis under the 'Actions’ column for the service account created above.
  8. Click + Add Key.

  9. Click Create New Key.

  10. Make sure that JSON is selected as "Key Type."

  11. Click Create.

  12. Click Close.

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

Setting the Scopes for the Migration

From the Google Cloud Platform Console:

  1. Click Menu.
  2. Click IAM & Admin.
  3. Click Service Accounts.
  4. Find the service account. Previously set it up in the Create a Customer Tenant Account section above.
  5. Find and copy the service account's 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 Admin 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.

Classic Google UI New Google UI
  1. Go to the G Suite admin page at admin.google.com
  2. Click Security > Access and Data Controls > API Controls
  3. Under Domain-wide Delegation, click Manage domain-wide delegation.

Once the steps below are completed, you should now see your specific Unique ID and the associate scopes listed.

  1. In the Client ID field, paste the Unique ID copied above.
  2. In the OAuth scopes (comma-delimited) field, paste all scopes 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
    https://www.googleapis.com/auth/drive
  3. Click Authorize.

MigrationWiz Steps

Important 

During the migration process, users must avoid editing files at the destination. Otherwise, the edited file will be skipped. 

Attempting to modify a file at the destination and reattempting the migration will result in this error:
"Skipping item due to a user-modified item with the same name“.

For more information, please refer to the Troubleshooting section of the Google Drive Migrations FAQ page.

Create a Document Project

  1. Log in to MigrationWiz.
  2. Click the Go to My Projects button.
  3. Click the Create Project button.
  4. Select the Document project type. 
  5. Click Next Step.
  6. Enter a Project name and select a Customer.
  7. Click Next Step.
  8. Select endpoints or follow the steps below to create new endpoints. 

Endpoints

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints or create new ones.

Create a Source Endpoint

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select OneDrive for Business
  4. Leave the Provide Credentials option selected.
  5. Click Add Endpoint.

Create a Destination Endpoint

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select Google Drive (Own Service Account)
  4. Click Select File > Navigate to and select the JSON file that contains the Google Service Account key that was saved during the service account setup process.

  5. Enter the Google admin account email address and domain name in the appropriate fields. Please note that this admin email should match the end-user domain.

  6. Click Add Endpoint

Add Users

Add the user accounts that will be migrated to the project. MigrationWiz allows you to bulk import users into the system.

Important

For OneDrive endpoints, the email address must match the current User Principal Name of the user in the tenant

You may use Bulk Add, Quick Add, or add the accounts to the MSPComplete customer. 

Quick Add
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:
  • An email address
  • Login name
  • Password
  • Mailbox status
Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add.
  5. Follow the instructions on the page.

Advanced Options

Support Tab

  • InitializationTimeout=8 By setting up this AO, you increase the timeout initialization timeout window to 8 hours. 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.  
  • ShouldConvertToDestinationFormat=1 MigrationWiz converts the Microsoft file types (".doc", ".docx", ".ppt", ".pptx", ".xls", ".xlsx") into Google file types (Google Docs, Google Sheets, Google Slides), where possible. The file conversions do not happen by default.
  • UseGoogleAPIV2=1 This configuration avoids migrated items corruption and missing items issues. This is a default option.

Filtering Tab

  • Excluding OneNote Files

Please be aware that OneNote does not support versioning. To avoid creating duplicate content, it is crucial to migrate your OneNote files just once. Each subsequent migration attempt could result in new versions of your OneNote files being generated as separate new files.

To prevent this, we advise filtering out OneNote files during various stages of the migration process by adding one in the Advanced Options. Consider excluding OneNote files during the Trial Migration and Pre-Stage Migration. 

FilteringAO.png

We recommend you that only include them in the final Full Migration stage to ensure a smooth and efficient migration process. To ensure the successful migration of OneNote folders and files, particularly after initially excluding them, it is necessary to remove the one extension from the filtering tab in the Advanced Options.

Run Verify Credentials

  1. ​Sign in to your MigrationWiz account​.
  2. Open the Project containing items you wish to validate.
  3. Select the items you wish to validate.
  4. Click the Start button in your dashboard.
  5. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

To lock (set to ReadOnly) the OneDrive items before migration: 

  1. Make sure all OneDrive line items are not locked.

  2. Run Verify Credentials pass for all OneDrive line items. This will add the provided credentials as a site collection administrator for these items.

  3. You can now lock all the OneDrive line items.

  4. Run a full migration pass.

Notify Users

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 Source OneDrive accounts, because any modifications will not be included in the migration.

Run Migration

For small migrations, we suggest skipping the pre-stage pass and simply performing the full migration. However, for large migrations with more than five hundred users, we do recommend the pre-stage migration.

Pre-Stage pass

  1. Select the users you wish to migrate.
  2. Click the Start button from the top.
  3. Select Pre-Stage Migration.
  4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago.
  5. Click Start Migration.

Full pass

  1. Select the users.
  2. Click the Start button from the top.
  3. Select Full Migration.
  4. Click Start Migration.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

Otherwise, if you have any issues related to your migration, review the troubleshooting section of the Google Drive Migrations FAQ page. If you do not find any solutions or the problems persist contact Support.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.

Post Migration

To prevent users from inadvertently logging in and using their OneDrive for Business accounts, decommission the OneDrive for Business user accounts, or change their passwords.

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