SharePoint to SharePoint Migration Guide for GCC High/China Migrations

This is the complete workflow for the SharePoint 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.

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. (Flex Collaboration licenses cannot be used)

The Shared Document license applies to any document migration projects involving SharePoint or Google Shared Drives. This license type migrates up to 50GB of data per license.

This license migrates:

  • Documents

  • Folders

  • Permissions

  • Versions

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. 

Enable App-Based Authentication

Set up the app-based authentication in the Microsoft 365 tenant. BitTitan uses app-based authentication for SharePoint, OneDrive for Business, Microsoft 365 Groups (Documents) migrations, 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.

Important: This app must be added in both 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

Step 1:

Visit the following URL and sign in as the administrator user:

Do this for both Source and Destination tenants.

Step 2:

Authorize the App for both Source and Destination tenants.

Click on the Accept button.

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. Set up the app-based authentication in the Microsoft 365 tenant. The steps for this can be found under Prepare the Source. 
  5. 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.

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 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 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 from a GCC High US Government Tenant, add:

If migrating to a GCC High US Government 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