This article provides instructions on configuring a migration batch for migrating SharePoint Sites between Microsoft 365 tenants. The setup process outlined here focuses on migrating documents, this is the only available data type for this scenario. Each document library within the source SharePoint site can be migrated to a corresponding document library in the destination.
Before proceeding, ensure you have completed the steps in the Microsoft 365 to Microsoft 365 Migration Guide to set up your migration project and added users to your migration batch.
When setting up your source and destination connections, it is important that you add the SharePoint Admin URL.
SharePoint Online allows you to create multiple document libraries within a single SharePoint site. The configuration of CloudM will vary depending on whether you want to migrate all document libraries or just a specific set.
Note: It is not possible to migrate a specific folder within a SharePoint document library.
Adding Items to Migrate
Migrating All Document Libraries Within a SharePoint Site
When migrating all document libraries from one SharePoint site to another in Microsoft 365, CloudM Migrate will operate as follows:
- Library Name Match: CloudM Migrate will check if a library with the same name as the source library already exists at the destination. If a match is found, the folders and files within that library will be migrated.
- No Library Name Match: If no matching library name is found at the destination, a new library will be created with the same name as the source library, and the folders and files will be migrated into the newly created library.
Example:
-
Source:
https://source.sharepoint.com/sites/testsite -
Destination:
https://destination.sharepoint.com/sites/testsite
To migrate all document libraries from the source SharePoint site to the destination site, configure the migration settings as follows:
- Export Type: Team Site
-
Export Name:
https://source.sharepoint.com/sites/testsite - Import Type: Team Site
-
Import Name:
sites/testsite - Given Name: Documents
- Family Name: Test Site
Note: The "Family Name" is the display name of the destination SharePoint site. If the site already exists, you can leave the "Family Name" field blank.
Migrating a Single Document Library Within a SharePoint Site
When migrating a single document library to Microsoft 365, CloudM Migrate will perform the following checks:
- Library Name Match: The migration tool will check if a library with the same name as the source exists at the destination. If a match is found, the folders and files within that library will be migrated.
- No Library Name Match: If no matching library name is found at the destination, the migration will fail.
- Pre-Provisioning Required: If you are migrating a document library other than the default "Documents" library, you must pre-provision the destination site and document library.
Example:
-
Source Site:
https://source.sharepoint.com/sites/testsite -
Source Document Library:
TestLibrary -
Destination Site:
https://destination.sharepoint.com/sites/testsite
To migrate the specified document library from the source to the corresponding library at the destination, configure the migration settings as follows:
- Export Type: Team Site
-
Export Name:
https://source.sharepoint.com/sites/testsite - Import Type: Team Site
-
Import Name:
sites/testsite -
Given Name:
TestLibrary -
Document Path:
TestLibrary
Note: Since the destination site must already exist in this case, the "Family Name" field is not required.
For each entry, ensure you select the specific items you wish to migrate and enable the 'Migrate' option for all sites included in the migration process.
General Settings
In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.
You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.
Source Settings
For a standard SharePoint site to SharePoint site migration, it is recommended to keep most of the source settings at their default values. However, you will need to ensure you modify the below.
- SharePoint Online -> Default document library name: Modify this setting to match the language used in your source tenant.
- SharePoint Online -> Document sharing/permissions: Modify this setting depending on whether or not you would like the sharing permissions to be migrated or not.
Destination Settings
Depending on your migration plan, you may need to modify several settings in this section:
- SharePoint Online -> Migrate previous document versions: Enable this option to migrate previous major versions of documents in the migrating document libraries. Enabling this feature allows you to select the number of versions to migrate but will significantly increase migration run times.
- SharePoint Online -> Maximum number of previous document versions: Select the number of versions you plan to migrate.
- SharePoint Online -> Include document metadata: Enable this to migrate both standard and custom document metadata, including text, boolean, number, and datetime fields.
- SharePoint Online -> Provision sites: This option is enabled by default, leaving this enabled will result in Migrate creating any SharePoint sites at the destination that do not already exist. In order to create sub-sites, the parent site must be pre-provisioned.
Advanced Settings
For a straightforward SharePoint site to SharePoint site migration, most advanced settings can remain at their default values. However, consider the following:
-
Address Replacement: It is highly recommended to upload an address replacement CSV that maps source users, groups and aliases to their corresponding destination users, groups and aliases. This will help ensure permissions are migrated correctly. For more information, please refer to the Address Replacements article.
Migration Process
The migration process will vary depending on your project's specific approach. Generally, it is advisable to start with a bulk migration and perform delta migrations closer to the final migration cutover date.