Teams to Teams Migrations - Document Versions and Metadata

MigrationWiz now supports migrating document metadata and versions for Teams to Teams projects. This may only be done if no document migration has occurred previously in the project.

This guide migrates documents, versions, and metadata from a SharePoint instance attached to a Teams instance. We suggest using the Teams to Teams migration guide for reference during this process and the SharePoint to SharePoint migration guide for reference.

Consider that Document Versions and Metadata are not supported for GCCH projects, for more information about this check the Migration Guide for GCCH Projects.


  1. Re-enable the Teams Application permissions here before starting the migration.

  2. Log in as a Global Admin at the destination tenant, then click Accept. Refer to the Application Permission guide for more information. 

  3. Create a brand new Collaboration project - these steps are outlined in the Teams to Teams migration guide linked above. 
  4. Choose the migration type Microsoft Teams (with Document Versions and Metadata).

    You can only migrate document versioning and metadata for Teams to Teams Migration projects by selecting this option (v3 connectors).

  5. Enable Azure storage. We recommend using a Microsoft-provided Azure storage solution for this migration.
  6. Purchase sufficient Collaboration licenses.
    • Migrating more versions creates larger documents, which may require more licenses.

MigrationWiz does not support creating Teams tenants outside the default geo location of the tenant.

Start Migration

Once the above prerequisites are met:

  1. Go to Start Migration.
  2. Select Documents. This is required to migrating metadata and versioning and cannot be skipped.
  3. Select Document Metadata, Document Versioning, or both. This cannot be done if documents have previously been migrated.


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. 

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. We recommend creating a brand new Teams/Collaboration project to migrate this data if you have already started your migration in a previous project. 

Was this article helpful?
1 out of 2 found this helpful