Throttling allows you to modify the volume of migration throughput in order to accommodate network bandwidth on either the Source or Destination systems. In some cases, you may need to limit throughput, while in other cases you may be able to increase throughput.
The links below provide additional instructions and guidance.
Exchange Server has very low throttling policy limits. We recommend disabling the throttling limits during the migration. Click through for instructions on this process.
Google has strict throttling limits. If these limits are reached, it could result in the account being locked out for 24 hours, which may negatively impact your migration plan.
Important: During migrations, MigrationWiz connects to Google (G Suite) endpoints using OAuth 2.0. This allows administrators to grant access to MigrationWiz at an organization level, rather than requiring each individual user to grant MigrationWiz access to their inbox. We have also noticed that Google may be a bit more relaxed about enforcing the data transfer limits than are found here: G Suite Bandwidth Limits.
G Suite uses throttling both when retrieving and pushing data. Throttling limits are different for retrieving data vs. pushing data.
Also, G Suite imposes a hard limit of one (1) item per second when migrating to G Suite. MigrationWiz adjusts migration throughput accordingly, but remains subject to those limits.
Instructions on setting the throttling limits to avoid issues during migration.
Commands and instructions to increase your allowed connections.
As mentioned in the article, How long does a migration take, it can be difficult to accurately predict how long a migration will take, due to several factors, such as system load, bandwidth, average item size, and Source or Destination bottlenecks.
However, this link contains a rough breakdown of what speeds you can expect. Note: this is by no means an SLA, but just an example based on a very large sample of migration speeds experienced by our Partners.