This articles outlines the complete task flow for migrating folders and documents from Google Drive to OneDrive for Business. This migration requires an Azure subscription, which maximizes migration speed and bypasses throttling.

First time?

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.

Limitations

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 migrations with two-factor or multifactor authentication. 

The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.

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.

OneDrive migrations

Consider the following behaviors and tips for OneDrive migrations.

• OneDrive data may not be accessible for a few days after migration, due to OneDrive's crawling and indexing process. We suggest having your users log in immediately after migration but warn them that their data may not be available immediately. For this reason, it may be best to complete the migration on a Friday so the indexing can happen over the weekend.
• If you are migrating to a Microsoft 365 Small Business Tenant account, the processes will be very similar to the above. However, you will not be able to use admin credentials for your Destination endpoint and will instead be using end-user credentials.
• This endpoint does not support the User's personal site provisioning. If App-Based Authentication is in use at the Destination, the AO DestPersonalSiteIsProvisioned=1 must be used. Refer to Advanced Option.
• Due to versioning, storage usage in OneDrive may be increased when migrating with permissions.
• Due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this migration type.
• Changing the domain after the migration process will not automatically update the previously migrated destination file. Once data is migrated from one domain to another, any subsequent changes or modifications made to the original source data or the domain will not automatically reflect in the destination file.

Set up the Azure Environment

If using Microsoft-provided Azure storage, you can skip this section.

1. Estimate Azure storage costs. This step is optional but is useful in providing the customer with upfront storage costs ahead of time.
2. Buy an Azure subscription or use the free one-month trial (this option is only viable if you are performing a very small migration).
3. Create an Azure storage account. You will need to set up a STORAGE (General Purpose v2) account rather than a storage blob. Take note of the storage account name and the primary access key. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Microsoft 365 tenant. You do not need to create any Azure containers for this migration.
1. Log in to http://portal.azure.com/
2. Goto the Storage account you have created for Migration purpose
3. Click Access Keys for the access keys need to be entered when creating the Destination endpoint. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Office 365 tenant. 
4. Take note of the Storage Account Name and the Primary Access Key as follows:
5. -accesskey – This is the Storage account name for the Blob – example “accountname”
6. -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”

Prepare the Source

The Google Drive (Own Service Account) connector launched in 2020 and requires the set up of a Google Service account. This significantly reduces the likelihood of the migration being throttled. This is the option we recommend for all Google Drive migrations. Follow the steps below under under OAuth2 Requirements for Google Drive (Own Service Account) to set up your environment for this endpoint.

All accounts being migrated must be in Active status in the tenant. Users that are set to a status of Inactive will not be able to fully migrate and will fail in the project.

Prepare the Destination Environment

Create an administrator account in Microsoft 365 to be used for 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, in order to be able to provision OneDrive for Business profiles for each user during the migration process. If you encounter the error "Personal Site is not instantiated = PermissionsUserNotLicensed", this means that the OneDrive collection for a user does not exist and the administrator account used for the migration does not have a full license assigned. To resolve this issue, assign a license to the administrator account, and resubmit the migration.

Create an Administrator Account for Delegated Administration rights

The easiest approach to follow is to use the global administrator account that 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 new account will then need to have a license assigned that includes OneDrive for Business and be granted either Global Administrator permissions or SharePoint Administrator privileges.

Important: We strongly recommend that you use an administrator account that isn’t one of the users being migrated, as it can cause issues with missing shared permissions.

Process:

1. Create a user in Microsoft 365 and assign a license that includes OneDrive for Business. For step by step instructions, see the Microsoft article Add users individually or in bulk to Office 365.
2. Grant the new user Global Administrator permissions or SharePoint Administrator rights in Microsoft 365.
3. Ensure that the administrator account is set to use Basic authentication rather than Multi-Factor authentication.

After you perform these steps, the specified user will be visible in the Microsoft 365 administrator center. Full provisioning of the user account can take up to 24 hours.

Using App-based Authentication

BitTitan uses app-based authentication for SharePoint, OneDrive for Business, Microsoft 365 Groups (Documents), and Teams migrations. This provides greater security and reduces the potential of Microsoft throttling. It replaces the previous Microsoft 365 authentication, which has been subject to increased throttling by Microsoft. This app-based authentication method is specific for Microsoft 365 tenants.

If you elected to use app-based authentication, perform the following steps:

Add the App to the tenant

Steps to enable permission level at the destination:

1. Go to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted.
2. Create new Security Group named “MigrationWiz” on the Microsoft 365 Admin Portal.
3. Create new user.
4. Add new user to previously created security group as a member.
5. Create MigrationWiz project.
6. When creating the endpoints, enter the new user credentials.

Assign Licenses

Assign an Office 365 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 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.

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. 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.
  Important: If you are migrating permissions, the part of the usernames before the "@" sign on Microsoft 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 Microsoft 365, and so must also equal "john.smith" on Microsoft 365. The domain name, however, can be different. For more information see: Set up groups on Microsoft 365. If permissions were assigned to groups on Google Drive, and you want these to be migrated, the group names on Microsoft 365 must match the group names on Google Drive.  Create the required Microsoft 365 CNAME for your domain. Read the Create DNS records at Register365 for Office 365 article from Microsoft for more information. Set up the app-based authentication in the Microsoft 365 tenant. 

Post Migration Steps

To remove the BitTitan Enterprise app, perform the following steps:

1. Launch PowerShell.
2. Connect PowerShell to Microsoft 365.
3. Enter the command:

   Connect-AzureAD

4. Enter the admin credential in the prompt.
5. Enter the command:

   Get-AzureADServicePrincipal -SearchString Migration

6. Look for the ObjectId of the app you want to remove and enter the following command: Remove-AzureADServicePrincipal -objectId <the object id>

MSPC Steps

Licensing

Licenses are required to run a migration project in MigrationWiz. To obtain license pricing information, or to purchase licenses, click the Purchase button in the top of your MSPComplete or MigrationWiz dashboard.

Payment: We accept credit cards, and wire transfer in certain situations.  

• When purchasing with a credit card, payment is immediately processed during checkout. If successful, licenses are granted to your account instantly.
• Wire transfers are available for purchases of 100 or more licenses. If you are purchasing at least 100 licenses, you will be presented an option to purchase via wire transfer during checkout. A wire transfer checkout will generate an invoice with wiring information for your accounts payable department and bank. Once the funds are received by our system, the licenses are granted to your account immediately. 

For this project type it is recommended to use our User Migration Bundle licenses. 

To purchase licenses:

1. 1. 1. Sign in to your BitTitan account. 
      2. In the top navigation bar, click Purchase.
      3. Click the Select button and choose the license type you need.
      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.

These licenses enable you to perform multiple migrations of documents and in-place archives.

User Migration Bundle Licenses have unlimited data available per license. User Migration Bundle Licenses are applied to the customer's users, for whom you'll be performing migrations, and are valid for one year.

Read the Licensing FAQ article for more information.