This guide will cover frequently asked questions and troubleshooting processes related to Microsoft Teams to Microsoft Teams migrations for document versions and metadata. It is not intended to replace any part of the migration guide, which lays out the steps necessary to perform a Teams to Teams migration.
What are the metadata types supported?
- Single line of text.
- Choice.
- Single select.
- Multi-select Currency.
- Date and Time.
- Number.
- Person or Group (should be available at destination).
- Yes/No.
- URL/ Hyperlink.
- Picture.
- Location.
- Calculated.
What metadata types are not supported?
Any metadata referencing information from outside the document library (such as lists or other site-level data) is not migrated.
- External data.
- Managed metadata.
- Lookup.
- Retention policy tags/retention labels.
How many Document versions are supported?
By default, 3 versions, including the current version, will be migrated. However, migration of up to 25 versions (minor + major versions), including the current version, is supported. This can be configurable via the Advanced Options > Source/Destination tab.
How are versions migrated for multi-pass scenarios?
Refer to Versions & Metadata Migration for SharePoint & OneDrive for specific multi-pass scenarios.
SharePoint Provisioning
Please consider that SharePoint site creation occurs automatically within 24 hours of team creation.Other than documents, is the metadata for Teams and Conversations migrated?
No. Currently, only versions and metadata specific to documents are migrated.
I have existing Teams projects from before this feature is available. Can I migrate document versions and metadata for this existing project?
No, you cannot. We recommend creating a brand new Teams/Collaboration project to migrate this data if you have already started your migration in a previous project.