SharePoint Online GCC High/China to SharePoint Online Migration Guide

This is the complete workflow for migrating from SharePoint Online GCC High/China to SharePoint Online. The source must be SharePoint Online for GCC High or China and the destination must be SharePoint Online. SharePoint On-Premise is not supported.

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 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 have created a guide on scoping, planning, and managing the migration process for you. If this is your first migration, we recommend carefully reading this guide.

Prerequisites

Licensing

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 using downloaded BitTitan software such as DeploymentPro.

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

Limitations

The following are some limitations for Google Sites to Microsoft 365 SharePoint Site migrations. Some of them are an inheritance from the APIs used as well as the capabilities of the current destination.

  • MigrationWiz only supports migrations to the SharePoint Team Site and Communication Site.
  • Permissions are not migrated by default when the site is created.
  • Files migrated from Google Shared Drive and Google Drive to SharePoint or OneDrive Sites, will not be linked to the original files.
  • MigrationWiz can only migrate a Google Site with a Public setting. It cannot migrate a Google Site with a Private setting.

  • Google Sites font type and size are not migrated to the Destination due to formatting in the SharePoint Site.

  • As SharePoint Sites do not support collapsible content, the collapsible content in Google Sites is migrated over as plain text.
  • As SharePoint Sites do not support embedded HTML webpages, the layout and content from Google Sites may be distorted.

  • Google Sites supports an unlimited depth of menu layers, while SharePoint only supports a menu depth of two layers. As such, menus in the third layer onwards are migrated to the same hierarchy as the second menu layer.

  • Google Sites supports up to four columns in a section, while SharePoint Sites only supports three columns in a section. As such, the fourth column is migrated as the first column in a new section below.

  • MigrationWiz migrates the Google Site in plain text format. No other format is supported for export.
  • Some errors may appear during the migration process, please see the list below:
    • “Error while creating image", this error usually indicates there was an issue while creating an image at the destination. Please ignore this error since testing indicates that the migration of all image files has been completed successfully without any issues when this error message appears.
    • "Your migration failed while checking destination credentials. Please verify the MigrationWIZ Full Control App or Delegate App is available at Azure portal", this is a false error. When an incorrect username or password is provided, the system prompts the message above. The appropriate message should be “Your migration failed while checking source or destination credentials. The administrator username or password seems to be invalid”.
  • 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.
  • GCC High/China document type migrations do not support migrating Versions and Metadata. 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 using MigrationWiz. 

We have provided a workaround for this issue

Preparing the Source Environment

Save Library Templates

This step is only required when applying templates from your Source libraries to your Destination libraries.

Steps for Enabling Delegated App Permissions

GCC High endpoints require using delegated permissions. The easiest approach is to use the global administrator account, set up at the time of tenant creation. However, you can create a new user account if you do not wish to use this global admin account during migration. This new account will then need to have a license assigned including SharePoint Online and be granted either Global Administrator permissions or SharePoint Administrator privileges.

Important

We strongly recommend you use an administrator account that is not one of the migrated users as it can cause issues with missing shared permissions.

Process

  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 source 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 https://login.microsoftonline.us) 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 UseApplicationPermissionAtSource=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.

Prepare Destination Environment

  1. 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 MigrationWiz Destination endpoint.
  2. Before beginning the migration project, create the structure of the document libraries and the current document libraries on the Destination SharePoint Online site. Refer to this Microsoft training video for more information on the steps of the Create your document library article.
  3. Optionally, you can apply Source library templates to your Destination library if you want to maintain the same look and feel.

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 used in step 4 that correspond with the endpoint to which the user belongs.

  8. Add the support option UseApplicationPermissionAtDestination=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.  

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. Select the appropriate workgroup from the left navigation pane and 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

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

When selecting an existing endpoint, consider that you can only see ten endpoints 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. 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.

Create Destination Endpoint

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Enter endpoint name.
  4. For the endpoint type, select SharePoint GCC/China.
  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

Adding the accounts (items) that will be migrated to the project, does not require the whole URL, just the library's name. The library field for both Source and Destination should contain the text at the end of the site URLs. This field is case-sensitive and may be different from the current name set for the Document Library. The examples below help explain this:

  • If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/sites/SiteName/Documents/", enter Documents as the document library name.
  • If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/sites/SiteName/Shared%Documents/", 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

The following sections describe the tabs available for Advanced Options in this migration.

Support Tab

Consider that each Support Option includes the "=" character and must be located in the Support Options section of the Support tab.

Add blank fields for new Support Options by clicking the "+" button. In case you want to delete a field click the trash can icon.

AO Support Tab.jpg

  • OneDriveProExportEnvironment=AzureUSGovernment If migrating from a GCC High US Government Tenant.
  • OneDriveProExportEnvironment=AzureChinaCloud If migrating from a China Tenant.

Performing 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

Decommission the Source SharePoint server, libraries, or user accounts to prevent users from inadvertently using the Source SharePoint libraries.

Remove the Authentication App

You can remove the Authentication App in Entra Center.

  1. Sign in to Microsoft Entra admin center.
  2. Select Microsoft Entra ID.
  3. Go to Identity > Applications > Enterprise applications, in the left bar of the window.
  4. In the Manage section, select All applications, look for the application permission you configured (MigrationWiz-SharePoint-Delegated or MigrationWiz-SharePoint-FullControl), and select it.
  5. Go to Manage > Properties, and select Delete from the properties bar.
Was this article helpful?
0 out of 0 found this helpful