This guide outlines how to migrate file data to or from the Document Library associated with a Microsoft Communication Site using CloudM Migrate.
Overview
While Microsoft Communication Sites are often used for internal broadcasting and do not function like a standard Microsoft Team (which includes chat and channel infrastructure), they are fundamentally SharePoint entities. Therefore, to migrate data associated with these sites, you must treat them as Team Sites within CloudM Migrate.
Note: This process specifically migrates File data stored in the site's Document Library. It does not migrate site pages, web parts, navigation settings, or other aspects of the site.
Configuration Requirements
To successfully migrate to or from a Communication Site, use the following configuration settings:
1. Using a Communication Site as a Source
When extracting data from a Microsoft Communication Site, configure your migration item as follows:
- Batch Type: Team Sites
- Export Type: Team Site
- Export Name: The full URL of the site.
- Example:
https://yourtenant.sharepoint.com/sites/CommunicationSiteName - Example:
https://yourtenant.sharepoint.com/teams/CommunicationSiteName
- Example:
2. Using a Communication Site as a Destination
When migrating data into a Microsoft Communication Site, configure your migration item as follows:
- Batch Type: Dependent on your source platform (e.g., Google Workspace: Shared Drives).
- Import Type: Team Site
- Import Name: The relative short path of the site.
- Example:
sites/CommunicationSiteNameorteams/CommunicationSiteName
- Example:
- Given Name:
Documents- Note: This field is mandatory and must be set exactly to "Documents" to target the default Document Library.
- Note: If your destination site is provisioned in a language other than English, enter the localized display name (e.g., 'Documentos', 'Dokumente', 'Documenten').
Key Technical Considerations
- SharePoint vs. Teams: Even if the URL contains
/teams/, a Communication Site is still handled as a SharePoint entity. It will not work if added to a "Microsoft Teams" batch type in CloudM Migrate because it lacks the underlying Microsoft 365 Group/Teams architecture. - Document Library Verification: Data is migrated to the primary Document Library. Ensure the library exists on the destination site before starting the migration.