How Team Migration works

This article explains what Teams migration does and how it works.

First, there is a discovery on the platform that discovers all the teams and groups.

Once the groups and teams are discovered, the Preprocessing task recreates all the Groups and Teams, creates the associated SharePoint sites and migrates the memberships (Owners and Members of the group).


Once done, the migration task will recreate the channels, migrate the files of the channels, the planners, the conversations and the associated mailbox.

Few tabs are migrated (planners). Other ones are currently in the roadmap and this article will be regularly updated.

What is migrated

  • Microsoft Team (Office 365 Group)
  • Private Channels
  • Logo
  • Description
  • Teams Settings
  • External Users Permissions
  • Owners
  • Members
  • O365 Group Emails
  • Teams Conversations (no message metadata such as user or data/time stamp)
  • Files
  • OneNotes
  • Channels
  • Tabs (Conversations, Files, Planner, OneNotes, Word, Excel, PowerPoint, PDF, Website)

PS: Only the following Team Settings are migrated:

What is not migrated

  • Channel settings
  • Personal chat. (Personal Chat is migrated with a Mail migration license).
  • Reactions on conversation messages.
  • Conversations attachments links (Pictures and files) are not migrated. The attached files will be migrated and will appear in the Files tab though.
  • Default Wikis
  • Non-default Wikis and Wiki tabs
  • Images and attachments in default Wikis.
  • Version history of files or items.
  • Apps
  • Bots
  • Activity History
  • Contacts. (Contacts are migrated with a Mail migration license)
  • Favourited Teams or channels
  • Call history
  • Team profile settings (notifications, theme, status)

Microsoft Planner

Each Team and Office 365 Group is created with a Microsoft Planner. Retrieving statistics for Planner usage is not possible.

What is migrated?

Cloudiway migration tool will migrate Planner content including:

  • Task Title
  • Buckets
  • Assignees
  • Progress
  • Start date and end date
  • Labels
  • Checklists
  • Description
  • Attachments (Links pointing to old SharePoint sites will not be translated)

What is not migrated?

  • Task ‘created by’ and ‘Date’ metadata (Microsoft Graph API limitation)
  • Task Comments (Microsoft Graph API limitation)
  • Conversations ‘Sent from’ and ‘Date’ metadata (Microsoft Graph API limitation)
  • Task Priority (Microsoft Graph API limitation)

This is what the conversations would look like:




Please beware that the chat messages are posted with a timestamp of the migration and will appear on the bottom of the message thread. Also, please note that if a message errors out and you restart the migration, that message will be pushed during a delta pass and will appear again on the bottom of the thread. (This will cause a chronological disorder in the messages). This is Microsoft Graph API limitation.

Additionally, please beware that the migration of messages is very sensitive to throttling. Depending on the throttling faced from the source or target tenant, Cloudiway suggests migrating the last few days of chat data for a better migration performance.

This is what the Planner Tasks would look like:



Note that the title, labels, bucket, progress, start date, due date, description, checklist, attachments, assignees are all migrated. The Comments, Created By and Completed By are not migrated (Graph API limitation).

Meet Cloudiway - A powerful and automated migration and coexistence platform. We support G Suite, Office 365, Zimbra, Lotus and lots more...
Register Now