What are the minimum requirements to migrate Teams? (4248339)

To migrate Teams successfully, there are several minimum requirements that must be met. Here is a summary of the key prerequisites:

• Admin Consents: Before starting the Teams migration, the following consents must be granted:

  If these consents are not granted or have expired, the "Discover Teams" action will be disabled.

  • Migration-Basic
  • Migration-MailboxMigration
  • Migration-SharePoint
  • Migration-Teams

• OneNote Initialization: The Tenant Administrator must open the OneNote application at least once in the target tenant to initialize it before granting consent for Teams migration. If this is not done, an error may occur.

• User Matching: Users must be matched or migrated before using the OnDemand Migration for Teams service.

• File Migration: Images, media files, and documents referenced in one-on-one or group chats stored in OneDrive for Business must be migrated using the OnDemand Migration for OneDrive service before migrating the chats.
• Team/M365 Group Mailbox Migration: Both the source and target Azure AD administrator accounts used to "Grant Consent" to the ODM Teams migration permission require ApplicationImpersonation rights.
• Membership Migration: Accounts joined to existing teams should be matched or migrated in the migration project.

Required Permissions:

• For Conversations: Read all channel messages, have full access to the Chat Service Aggregator and the Skype Teams Service, create chat and channel messages with anyone's identity and with any timestamp.
• For Private Chats: Read all chat messages, read and write user chat messages.
• For Groups and Teams Provisioning: Read and write directory data, read and write all groups.
• For Files and OneNote Items: Read and write all OneNote notebooks, read and write items in all site collections, view and modify notes for all users.
• For Groups and Teams Membership: Read all users' full profiles, read or write user region, add and remove members from all teams, add and remove members from all channels.

• Temporary Migration Manager Accounts:

• It is recommended to create or use source and target temporary Migration Manager accounts with the Global Administrator or Teams Administrator role and Application Impersonation role on the tenants. These accounts should have a Teams license and must be removed after the migration is completed for security reasons.

• Additional Considerations:

• Avoid adding/removing channels, especially private channels, before the migration as it may delay the process.
• Teams migration includes a configurable option to include/exclude SharePoint content migrations.
• Other content migration tools used simultaneously in the same tenant(s) can impact migration throughput.

• The migration sequence typically involves migrating planners, mailboxes, channels, SharePoint files, channel messages, channel tabs, and finally, Teams membership.

  Please ensure that all these requirements and steps are thoroughly reviewed and followed to avoid any issues during the migration process. For detailed guidance and updates, refer to the official migration documentation provided by the migration tool or service you are using.