The following site templates are supported for site collection discovery and migration:
- Modern Office 365 group site (Group#0). Some limitations are applicable
- Modern team site – no Office 365 group (STS#3)
- Modern communication site (SITEPAGEPUBLISHING#0)
- Classic team site (STS#0, SPSMSITEHOST#0)
- Classic project site (PROJECTSITE#0)
- Community site (COMMUNITY#0)
- Document Center (BDR#0)
- Enterprise Wiki (ENTERWIKI#0). Some limitations are applicable.
- Publishing Portal (BLANKINTERNET#0, BLANKINTERNET#2, CMSPUBLISHING#0). Some limitations are applicable.
Migration of site collections based on other templates is not supported. Sub-sites based on unsupported templates will be skipped.
|
|
IMPORTANT:
- The Group or Team site based on the Group#0 must already exist on the target before the migration is allowed to be performed.
- The Group or Team sites cannot be set to be cleared before migration.
|
- Checked out status for files in document libraries is not migrated.
- Currently checked out documents are not migrated. The last checked in version of the document is migrated. If the file has never been checked, no version of the file is migrated.
- Reputation Settings for Community site migration are not supported
- Reporting of offensive content setting for Community sites is not supported
- Private views and personal sites are not migrated.
- Maximum number of items that can be migrated in a single list or library is 1 million
- Classic web parts in classic wiki pages are not migrated. This may affect the home pages of older classic team sites (STS#0) where the home.aspx page is built on a Wiki page.
- Assigned translators in Language settings for Communication site are not migrated
- Comments on modern site pages are not migrated
- Migration from an education tenant to another education tenant is not supported for education templates.
- Migration of verified web parts is a best effort. A warning event will be posted for any site pages where an issue occurred while migrating web parts. The warning event will identify the web part and possible cause of the problem. Please review the identified web parts on the site pages and correct as needed.
- The migration of some look and feel settings require that running of custom scripts be allowed on the site. See https://docs.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script for more information on allowing custom scripts.
- OnDemand Migration for SharePoint migrates the content starting with the root site and then proceeds to any sub-sites. As a result:
- Links to SharePoint lists, libraries and sub-sites that have not been migrated to the target will not be added to the Quick Launch menu.
- Navigation links and links in web parts to SharePoint content in sub-sites cannot be updated if the linked sub-site has not been migrated.
- Migration of the Master Page Gallery is not supported because active master pages cannot be updated or overwritten during the migration. Custom master pages should be manually added to the Master Page Gallery in the target tenant and set as the new master page.
- Some Pages library files like Home.aspx, About.aspx and PageNotFoundError.aspx, and the Welcome Page setting cannot be migrated if the sites are built with the following features or templates. You must manually move these files and reconfigure the Welcome page setting if necessary.
- The SharePoint Server Publishing Infrastructure site collection feature is activated in the source.
- The site is based on the Wiki site template.
- The site is based on Publishing Portal templates.
- Managed navigation is based on term sets. The term set setting for Managed Navigation for the Publishing Portal is not migrated. The term set is set to the default on the target. You must manually update the term set setting in the target tenant if the selected term set setting in the source is no longer the default.
- There could be duplication in navigation links because links are managed from the site UI and from a Publishing Portal specific Navigation site setting.
See the Considerations for details on re-migration behavior or if the target site or sub-site exists before the migration is started.
Your target tenant might already host SharePoint top-level sites (site collections) or sub-sites created before the migration. See the table below to see the migration action that will be used depending on the existing site properties and the selected migration options.
| Yes |
Yes |
No |
Merge, all supported properties will be overwritten using source settings |
| Yes |
Yes |
Yes |
Create and migrate |
| Yes |
No |
Yes/No |
Skip and report |
| No |
- |
- |
Create and migrate |
Merging and Re-Migration considerations
- Sub-sites based on unsupported site templates are skipped
- System settings including site columns, content types etc. from the source will overwrite settings that were changed on the target.
- New site structure including list item and docs that only exist on the target remains unchanged.
- If a new list item with the same name is added on both source and target, the source item will be migrated and added as a separate item (i.e. target will have two items with identical names).
- If a new document with the same name is added on both the source and target, the migration of the source item will be skipped, and the warning that the item already exists on the target is reported. Document libraries only allow one document per name.
- For previously migrated list items and docs (same name and ID):
- Updates on source will be migrated to the target
- Updates to target will be overwritten by re-migrated source item or document
- System libraries like Site Pages are always cleared before a re-migration. Any new files added only to the target will be deleted from the target as part of the re-migration.
Currently, only the latest versions of documents and list items are migrated. In case of re-migration, please consider the following:
- The migrated document is always replaced, document version remains unchanged.
- The list item is always replaced and list item version remains unchanged, unless Create a new version each time you edit an item in the list list versioning setting is enabled. If this setting is enabled, the remigrated list item will be added as new version.
Language considerations
When SharePoint groups in a site are migrated from a source to a target tenant with different default site languages, the group names may not match. In that case, the source groups are migrated to the target tenant with the original names from the source.
For Team sites (sites associated with the Microsoft 365 Groups and Teams) the migration of some members in the default SharePoint group may fail because the reference to the M365 group cannot be matched due to the different languages on the source and target. The resulting warning event is benign because equivalent permissions to the SharePoint group on the source will be created during the Teams or Microsoft 365 group provisioning by the Teams migration service.
Using this intuitive interface you can:
- Keep track of your location within project and quickly return to the main project dashboard using breadcrumbs on the top of the pane
- View list of discovered site collection with last information, completed workflows, site collection information, and last events related to the site collection
- Quickly navigate to the event lists
- Quickly navigate to the tasks list
- Create discovery tasks, matching tasks, and site collection migration tasks
- Export feature data into comma-separated file and use this file for manual mapping
- Temporarily remove sites from migration project
- Search site collection
- Filter site collection by workflow, or by matching state
- Delete site collection
