MS Teams Direct Migration mode

What is Direct Migration mode?

Direct Migration Mode allows you to migrate Microsoft Teams from the source Microsoft platform to the destination Microsoft platform and migrate Channels/Messages in the same migration pass. 

CloudM recommends making sure that all Microsoft Teams members are already migrated from the source platform to the destination platform. The user must exist in the destination to avoid scenarios where a Microsoft Team is created before the Team owner.

What is and is not migrated when using Direct Migration mode?

The following table shows what is and what is not migrated (as specified in this Microsoft article):


Group mailboxes will be migrated when mail is included in the MS Team migration, but it will be hidden by default. This means that it won't be accessible via Outlook in the Destination platform.

How to use MS Teams Direct Migration mode

The following process will allow you to migrate the Teams and Channels / Messages in a single migration pass, and the end user will see the Team and Channels / Messages in the Destination as soon as the process is finished:

  1. Set your Source platform to Microsoft 365 and configure as normal with the details of the platform you are going to migrate from and select Next to run a quick connection test to the Source.
    • You should not need to change any of the Advanced Settings at this point.
  2. On the Destination platform screen, again, set to Microsoft 365 and configure as normal with the details of the platform you are migrating to.
  3. In the Advanced Settings section of Source Platform (which can be expanded by selecting the down arrow on the Advanced Settings banner, under the Basic Configuration section), go to the Microsoft Teams / Groups subsection.
  4. Now, ensure that the Teams Direct Migration and Finalize Teams Direct Migration settings are BOTH enabled.
    • Setting only Teams Direct Migration to enabled will migrate the specified Microsoft Teams and Channels / Messages within, but they will not be visible to the end users in the Destination. It will appear in the Admin console view. Please view the Delta Migration scenario section below for an example where you may want to use this approach.
    • Setting only Finalize Teams Direct Migration will effectively cause nothing to be migrated across to the Destination. 
  5. Select Next to run a quick connection test.
  6. In the next section, Items to Migrate, add all the Microsoft Teams that you want to add from the Source, and ensure that the Migrate option is enabled for all. You should also ensure that the Mail, Calendar, Drive and Conversations checkboxes are ticked.
  7. Also in the Items to Migrate section, you should add all the users in your Source platform to the list but deselect the Migrate option. This means that the user will not migrate over to the destination again but their email name will be correctly converted from "" to "". Alternatively, you can use an Address Replacements file to pair up addresses.
    • All members of a Microsoft Team on the Source platform must exist in the Destination platform prior to this migration, as errors will be recorded otherwise.
  8. Now, select the Config Settings button to move to the next stage of the process.
  9. On the Config Settings screen, set the date ranges for the content that you want to migrate over to the Destination.
  10. Next, select Advanced Settings and go to Reporting.
  11. In the Reporting subsection, ensure that you set Record Document Mappings to enabled. This will record Drive mappings so that documents attached to messages will still be linked. You can also set the Include Document Mappings in Report setting to enabled if you want a CSV file report containing the recorded document mappings for migrated Drive items.
  12. Continue with your migration.
  13. Once the migration is complete, you should see the Microsoft Teams and all associated Channels / Messages (as well as any migrated users) migrated over to the Destination platform, and the Microsoft Teams should be visible to the end user.

Delta Migration scenario

As previously stated, the Direct Migration mode was designed to allow you to migrate the Team and content to the Destination with one migration pass.

However, you may not want to allow users on your destination to see Microsoft Teams prior to a go-live date, or you may be running a Delta migration approach where you migrate over a larger "bulk" of users and content and then mop up any additional users and content added between your bulk migration and go-live date in a "Delta" migration.

That is why we added the Finalize Teams Direct Migration setting. It acts as a confirmation that you want the Microsoft Team and content to be visible to the end user on the Destination.

To follow this approach:

  • In Migration Pass 1, follow the instructions in the section above except:
    • Teams Direct Migration is still set to enabled (True),
    • Finalize Teams Direct Migration is set to disabled (False).
  • In Migration Pass 2, follow the instructions in the section above, ensuring that:
    • Teams Direct Migration is still set to enabled (True),
    • Finalize Teams Direct Migration is set to enabled (True).

What is next?

Now that the Microsoft Team is created and Channels / Messages have been migrated over, you may need to run additional migration passes to migrate over some of the other Microsoft Teams content.

Please review the following article, where required.


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