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 document libraries, as documents are the only available data type for this scenario.
Before proceeding, ensure you have completed the steps in the Migration Guide to set up your migration project.
Important: When setting up your connections, you must add the SharePoint Admin URL. See How to find the SharePoint Admin Url.
1. Adding Entities to Your Batch
SharePoint Online allows you to create multiple document libraries within a single SharePoint site. The configuration of CloudM Migrate varies depending on whether you want to migrate all document libraries or just a specific set.
Migrating All Document Libraries (Default)
CloudM Migrate will check the destination for existing libraries. If a match is found, contents are merged. If not, a new library is created.
Example Configuration:
-
Source:
https://source.sharepoint.com/sites/SourceSite -
Destination:
https://destination.sharepoint.com/sites/DestinationSite
Batch Settings:
- Export Type: Team Site
-
Export Name:
https://source.sharepoint.com/sites/SourceSite - Import Type: Team Site
-
Import Name:
sites/DestinationSite -
Given Name:
Documents- Note: If your destination site is provisioned in a language other than English, enter the localized display name (e.g., 'Documentos', 'Dokumente', 'Documenten').
-
Family Name:
Destination Site Name
Note: This sets the display name of the destination site. You can leave this blank if the site already exists.
Migrating a Single Document Library
Use this configuration to migrate a specific document library (e.g., "Source Library") to a specific destination library.
Example Configuration:
-
Source Library:
Source Library -
Destination Library:
Destination Library
Batch Settings:
- Export Type: Team Site
-
Export Name:
https://source.sharepoint.com/sites/SourceSite - Import Type: Team Site
-
Import Name:
sites/DestinationSite -
Given Name:
Destination Library- ✅ Enter the exact display name of the destination library.
- ❌ Do not enter a URL or file path.
-
Document Path:
Source Library- The display name of the source library.
Further instructions on adding entities to your batch can be found here: Adding Items to a migration batch. Ensure the 'Migrate' checkbox is enabled for all entities you intend to include.
⚠️ Important Limitation
Migration Scope: CloudM Migrate operates at the Document Library level. It is not possible to specify or isolate a single folder within a library for migration. The configuration targets the entire library.
2. Configuration Settings
General Settings
Ensure all domain mappings are configured correctly. You can also apply date range filters here. General Settings Reference.
Source Settings
For a standard SharePoint site migration, modify the following:
- SharePoint Online > Default document library name: Modify to match the language used in your source tenant.
- SharePoint Online > Document sharing/permissions: Enable if you wish to migrate sharing permissions.
Destination Settings
- SharePoint Online > Migrate previous document versions: Enable to migrate historical versions. Note: This increases migration time.
- SharePoint Online > Maximum number of previous document versions: Select the limit (e.g., 5).
- SharePoint Online > Include document metadata: Enable to migrate text, boolean, number, and datetime fields.
- SharePoint Online > Provision sites: Enabled by default. Creates the destination site if it does not exist.
Destination Settings Reference
Advanced Settings
- Address Replacement: Highly recommended. Upload a CSV mapping source users/groups to destination equivalents to ensure permissions are migrated correctly. Address Replacements Reference.
3. The Migration Process
For a complete guide covering project planning, user communication, and checklists, please review our recommended strategy: