Get Started With SharePoint Migration From SharePoint On-Premise To Online Using ShareGate

Overview

In this article, we will learn how we can start the migration from source site collection to the destination site collection. Then, we will talk about "Incremental Delta Sync" for the migration and at last, will talk about common migration errors and their resolution.


If you didn’t visit my previous articles of this series, please do visit using the following URLs.

So now, let’s get started!


Start Migration on On-Premise Site Collection to Online

  • Please make sure all the documents/files are checked in before performing the migration.

  • Sharegate should be installed on On-premise environment so that it will be able to connect to the On-premise farm.

  1. Your team should have the farm administrative and site collection administrator user account through which they can perform the migration.

  2. For destination, you should have Global Administrator/SharePoint Online Administrator account.

  • Open Sharegate and go to the Migration tab.

  • Click on “Copy Structure” in “Migration” tab from the left navigation panel.

  1. Note: “Copy structure” will migrate Sites, List and Libraries, User and Groups, Managed Metadata, etc.

  2. Copy Content” will migrate only the content of the Lists/Libraries.

  • Enter the source site collection URL with “Full Control” permissions to the user account credentials and click on the “Connect” button. Next, select source root site and click the “Next” button.

  • After connecting to the source, enter target URL with “Full Control” permissions to user account credentials and click the “Connect” button. Next, select the destination root site and click “Next”.

  1. Note: I recommend connecting On-Premise/Online site collections using SharePoint Online Administrative permission user account for migration.

  • In “Copy Structure” tab, select site collection and click on “Mappings”.


  • In the Mappings window, we can map unsolved sources, such as Users and Groups, Site Templates, and Permission Levels. Note We map a user because the source site users or groups may not be available in the target site collection; so, it will assign the missing users’ content to the mapped user in a target site co