OneDrive for Business to OneDrive GCC/China Migration Guide

This guide is for migrations from OneDrive for Business to OneDrive GCC/China. The source must be OneDrive for Business and the destination must be OneDrive GCC/China - not the personal OneDrive version, which uses Azure. GCC/China OneDrive migrations do not utilize Azure.

If you are migrating to an Office 365 Small Business Tenant account, the process will be very similar. However, you will not be able to use admin credentials for your Destination endpoint, and will, instead, be using end-user credentials.

Due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this migration type.

OneDrive Migrations

Note that 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 for a short period. For this reason, it may be best to complete the migration on a Friday so the indexing can happen over the weekend.

Due to versioning, storage usage in OneDrive may be increased when migrating with permissions.

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.

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. 

We are not able to support migrations with two-factor or multifactor authentication. 

Preparing the Source

Prerequisites

Unlock the OneDrive source account or manually add migrationwiz@domainname.onmicrosoft.com as a site collection admin to the OneDrive account.

Authentication

There are two authentication options to choose from when setting up the source environment:

  • App-based authentication, which is more secure and avoids throttling

or

  • Delegated admin rights

Create an administrator account using Delegated administrator 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 will then need be granted Site Collection Administrator privileges and assigned a license that includes OneDrive for Business.

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 Office 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. Set the administrator privileges. Grant one of the permission levels listed below. 
    • Global Administrator. Microsoft has instructions to set these permissions here: Assign admin roles.
    • Site Collection Administrator. For specific permissions and project settings to be used with a Site Collection Administrator, see MigrationWiz Permission Requirements.

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

Export Users

Export the list of OneDrive for Business user accounts to a CSV file. This can be used when adding users on the Destination, and when adding the users to the project in MigrationWiz. 

Set up the app-based authentication in both Office 365 tenants

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

Important: If you opt to use app-based authentication, this app must be added in both .microsoftonline.com tenants (Source and Destination) to reduce the throttling and failures due to Microsoft throttling policy changes.

If this app is not added on both tenants, MigrationWiz will attempt to create a temporary substitute app in the tenants to be used for authentication. We do not recommend relying on this substitute app creation, as this behavior will only be a temporary transitional behavior within MigrationWiz. To avoid potential interruptions or failures in migrations, it is strongly recommended to set the app up in the tenants.

Add the App to the tenant

These are the steps to enable permission level at the source only. This authentication process gives you control over who is entitled to use the source.

  1. Ensure you are signed in as a Global Admin.
  2. Go to either MigrationWiz-SharePoint-ReadOnly or to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted.
  3. Create a new Security Group named “MigrationWiz” on the Office 365 Admin Portal. 
  4. Create new user.
  5. Add new user to previously created security group as a member.
  6. Create MigrationWiz project.
  7. When creating the endpoints, enter the new user credentials.
  8. Add support option UseApplicationPermission=1 

Prepare the Destination Environment

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

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. Ensure you are signed in as a Global Admin.
  2. Go to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted.
  3. Create new Security Group named “MigrationWiz” on the Office 365 Admin Portal.
  4. Create new user.
  5. Add new user to previously created security group as a member.
  6. Create MigrationWiz project.
  7. When creating the endpoints, enter the new user credentials.

MSPComplete Steps

Create Customer

  1. Click the Add button in the top navigation bar.
  2. Click the Add Customer button on the All Customers page.
  3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
  4. Click Add Customer.
  5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
  6. Click Save.
  7. Repeat steps 1 through 4 for each customer you want to add. 

Purchase licenses

We recommend that you purchase the User Migration Bundle license for this migration scenario. 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. For questions on licensing, visit MigrationWiz Licenses

To purchase licenses

  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.

Apply licenses

  1. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
  2. On the left navigation pane, click Customers.
  3. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
  4. Click the Users tab at the top of the page.
  5. Check the box to the left of the email for the user(s) to whom you want to apply a license.
  6. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
  7. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm.

MigrationWiz Steps

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.

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. 

To create a new source endpoint

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select OneDrive for Business
  4. Select migration type OneDrive for Business.

  5. Leave the Provide Credentials option selected.
  6. Click Add Endpoint

To create a new destination endpoint

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select OneDrive for Business
  4. Select migration type OneDrive for Business (GCC or China migrations).

  5. Enter the administrator username and password in the proper fields. 
  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.

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

Bulk Add

To import one or more accounts:

  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.

Quick Add

This option allows you to add items o​ne at a time. You need to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.

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 prior to 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 email to all users telling them the time and date of the migration.

Advanced & Support Options

Add the following options in the Advanced Options and Support Options tabs (if needed). 

  • Add UseApplicationPermissionAtSource=1
    • This is required for the application permission to function at the source.
  • For non-standard URL endpoints, add OneDriveProExportAdminUrl=<non standard URL> and OneDriveProImportAdminUrl=<non standard URL>. (Replace "<non standard URL>" with your custom URL.) 
  • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. This is especially useful for large migrations.
  • IncreasePathLengthLimit=1 - Use this Advanced Option in MigrationWiz to enable the use of 400 characters for the file path name. OneDrive limits characters in file path names, which can cause errors when migrating folder structures.
    • BitTitan has no limitations to the number of folders per migration. Any folder limits will be set by Microsoft.
    • 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.
  • If migrating from a GCC High US Government Tenant, add:
    OneDriveProExportEnvironment=AzureUSGovernment

    If migrating to a GCC High US Government Tenant, add:
    OneDriveProImportEnvironment=AzureUSGovernment

  • If App Based Authentication is in use at the Destination, add DestPersonalSiteIsProvisioned=1

Set the Advanced Option to send a notification to end users after the migration pass completes. (This is optional.) To set up the notification:

  1. Click Notifications.
  2. Click Send successful migration and notification to:
  3. Select Source email address (if users are still using the original source Microsoft 365 tenant) or Destination email address (if users are already using the Destination Microsoft 365 tenant).

Customize notification email:

  1. Checkmark the Customize "successful migration" email option.
  2. Add your own customization text and company name to this email.
  3. 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.

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, contact Support.

Map Permission Email by Pairs

In scenarios where usernames change during a migration, you will need to run the following command to ensure permissions map to the new username:

Option Command: MapPermissionEmailByPairsInProject=1

Environment(s): OneDrive/Google Drive (Destination)

Migration Type(s): OneDrive/Google Drive as destination only.

Important: Permissions 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.

Description: When OneDrive/Google Drive is the destination, this option can be used to map permissions by pairs in the project. user@domain.com to firstinitial.lastname@domain.com.

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 fifty users, we do recommend the pre-stage migration.

Recent changes to the Dropbox APIs prevent us from adding watermarks on files in the Destination Dropbox accounts. Therefore, if you perform a partial migration, reset the items in MigrationWiz, and then perform the migration again, you will end up with duplicate files at the Destination. If you must rerun the migration, we recommend that you first delete all files already migrated to the Destination Dropbox accounts.

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.

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

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