SharePoint Online to SharePoint Online Migration Guide for GCC High/China Migrations

This is the complete workflow for the SharePoint Online to SharePoint Migration Strategy Guide for GCC High/China. 

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

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

IMPORTANT: Migrating Versions and Metadata from the source is not supported for GCC High/China document type migrations. Due to versioning enabled in the destination, storage usage in SharePoint/OneDrive may be increased when migrating with permissions.

Document Properties Limitation

Microsoft Word document properties in Content Controls are not retained at the destination after migration. References to custom metadata values within a document appear broken after being migrated to the destination document library. This is a Microsoft limitation and can be replicated by copying a basic document to a new document library within the same tenant without the use of MigrationWiz. 

We have provided a workaround for this issue


This migration requires an appropriate number of Shared Document Licenses or Flex Collaboration licenses.

The Shared Document license applies to any document migration projects involving SharePoint or Google Shared Drives. This license type migrates up to 50GB or 100 GB of data per license. Flex Collaboration licenses are good for up to 100 GB per license.

This license migrates the following for this migration type:

  • Documents

  • Folders

  • Permissions

This license does not support the use of downloaded BitTitan software such as DeploymentPro.

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

​​Licenses are released once payment has been received:

  • If you purchase via credit card, licenses will be available immediately upon payment.

  • If you purchase via wire transfer (100+ licenses), licenses will be available once payment has been received and accepted.

  • We do not accept purchase orders, because of processing overhead.

In both cases, you will be notified by email that payment has been accepted and licenses will be available in your account upon notification.

For more information on licensing, including coupon redemption and other licensing types, see our Licensing FAQ.

Preparing the Source

Save library templates. This step is only required if you want to apply templates from your Source libraries onto your Destination libraries. 


BitTitan uses app-based authentication for commercial SharePoint, OneDrive for Business, Microsoft 365 Groups (Documents), and Teams endpoints. 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. Using this option, including steps for uninstalling, can be found outlined here: App based authentication using Application Permissions for SharePoint and OneDrive Migrations

Steps for enabling app-based authentication permissions

  1. Ensure you are signed in as a Global Admin.
  2. Go to MigrationWiz-SharePoint-FullControl 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.

  3. Create a new security group named MigrationWiz in the Office 365 Admin Portal. (The name of the security group must be an exact match)

  4. Create a new user that is not having data migrated in the project. This account does not require any administrator roles to be assigned. (If you already have an existing user, that should be fine) This user must have a SharePoint/OneDrive license applied.

  5. Add the new (or existing) user to the previously created security group as a Member (Adding as an Owner will not work here).

  6. Create MigrationWiz project.

  7. When creating the source and destination endpoints, enter the user credentials for the user in step 4 that corresponds with the endpoint the user belongs.

  8. Add the support option UseApplicationPermission=1 to the advanced options of the MigrationWiz project under Support Options.

Steps to remove these permissions are provided below in the Post-Migration section.  

Prepare Destination Environment

    1. Create a SharePoint Online administrator or Site Collection administrator account to be used for migration, or use the global admin account for the tenant. More information about these can be found here.
    2. Create SharePoint site libraries and schema. Make a note of the site URL where the document libraries are stored. This will be entered when creating your MSPComplete Destination endpoint.
    3. Create the structure of the document libraries, and also create the actual document libraries on the Destination SharePoint Online site, before beginning the migration project. Refer to this Microsoft training video for more information on the steps: Create your document library.
    4. Optional: Apply the Source library templates to your Destination libraries. This step is only required if you want to maintain the same look, feel, and design of your Source libraries on your Destination.

Steps for enabling delegated app permissions

GCC High endpoints require using delegated permissions. 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.


    1. Create a user in Microsoft 365 and assign a license that includes SharePoint Online. For step by step instructions, see the Microsoft article Add users and assign licenses at the same time.
    2. Grant the new user Global Administrator permissions or SharePoint Administrator rights in Microsoft 365.
    3. Grant Site Collection Administrator privileges to the target SharePoint sites in the destination that are being migrated in the project. 
    4. Ensure that the administrator account is not set to use MFA, 2FA or app password.
    5. Go to MigrationWiz-SharePoint-Delegated for GCC High tenants (This will install the app via login at 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.
    6. Add the support option UseApplicationPermissionAtDestination=0 to the advanced options of the MigrationWiz project under Support Options.

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.

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. 

MigrationWiz Steps

Create a Document Project

Document migrations will maintain the folder hierarchy from the source to the destination.

  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 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. Enter endpoint name
  4. For the endpoint type, select SharePoint.
  5. Enter the Site Collection URL for the top-level SharePoint document library, i.e., the site URL displayed in the SharePoint Admin Center.
  6. Enter the administrator username and password in the fields. This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.
  7. Click Add Endpoint

To create a new destination endpoint:

    1. Click Endpoints
    2. Click Add Endpoint 
    3. Enter endpoint name
    4. For the endpoint type, select SharePoint.
    5. Enter the Site Collection URL for the top-level SharePoint document library, i.e., the site URL displayed in the SharePoint Admin Center.
    6. Enter the administrator username and password in the fields. This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.
    7. Click Add Endpoint

Add Users

Add the accounts (items) that will be migrated to the project. This does not require the whole URL, just the name of the library. The name that needs to be entered under the library field for both Source and Destination will be the text that is at the end of the site URLs. This field is case-sensitive and may be different than the actual name that has been set for the Document Library. The examples below help explain this:

If the document library is named "Documents" and the URL is listed as "", enter Documents as the document library name.

If your document library is named "Documents" but the URL says "", then the name of the document library that needs to be entered is Shared Documents.

‘/' characters are not supported in the destination library name. Attempting to migrate any destination library with a '/' character will result in a migration failure.

Advanced Options

Add the following to the Support Options: UseAsynchronousMetadataRead=1

    • This is not supported when using On-Premises SharePoint as the source. This is required for SharePoint Online and requires the administrator account to be a Site Administrator or better.


This is required for the application permission to function at the source.

  • If migrating to a GCC High US Government Tenant, add:

  • If migrating to a China Tenant, add:

Run the 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.

Post Migration

To prevent users from inadvertently using the Source SharePoint libraries, decommission the Source SharePoint server, libraries, or user accounts.

Remove the Authentication App

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>
Was this article helpful?
1 out of 5 found this helpful