There's no specific migration throughput speed / performance data as this varies too greatly from Tenant to Tenant due to Microsoft.
The average throughput depends from tenant to tenant based on content type. For example lots of small files is slower then fewer of large files that add up to be the same size.
Also the time of the day the migration is running makes a difference. Microsoft will allow the throughput to be higher in evening and weekends without throttling.
It is recommended to select no more than 100 teams for the task to streamline the process. You can create several tasks that will be executed concurrently. Use search and filtering to quickly navigate through the list of teams
We would suggest migrating a pilot group and determine the speeds you get from the source to the target.
Only testing the migration of your own data (with its own unique makeup) on your own environment will provide accurate data for you.
Example:
Creating Collections
For Teams migrations, we recommend creating collections that contain up to 500GB of total content. This limit is based on the same dependency in SharePoint migrations. • --Teams file content migrations are processed by SharePoint content migration (ODMSP).
--The total content size migrated will be higher as permissions and metadata are migrated. The size will increase as the number of versions migrated increases.
--Select a mix of Teams sizes to total up to the target of 500GB.
Extremely large Teams (+250GB) should be placed in their own collection and/or migration task.
--In such a scenario, you can run migrations of two or more collections concurrently.
--You should expect that the extremely large Teams will take more than one day to migrate. It will also impact the total migration throughput.
