NM: Why are migrations so slow? (B297931)

NM: Why are migrations so slow?

NM: Why are migrations so slow?

Slow performance is usually caused by running the migration on a WAN. It does not matter how fast the WAN is, it is still a WAN, and the extra HOPS will slow down a migration.  

We recommend the Domino server and migration workers be on the same network segment as the Exchange server (1 Hop).

There are other factors that cause slow migrations that are not related to our product. This has to do with the migration workstation, anti-virus software, Domino & Exchange servers, workstation QoS, etc.  
Test network through put.
Check Notes setup and connections (Trace Connection test)
Test where the bottleneck is within each segment.
Check the response time between Outlook and Exchange (Cloud).

Confirm there's no proxy server between the end points
Confirm a firewall is not interfering with the migration
Check the Throttling policy Get-ThrottlingPolicy | Format-List.
Confirm the RCAMaxBurst and RCARechageRate are set to "Unlimited"

Find the bottleneck by performing the following tests:
1. Migrate from a local Notes database to local .PST file - If the migration is slow, then there is an issue with Migrator for Notes or the migration workstation. Check health of the machine (CPU, RAM, Disk i/o, etc)
2. Migrate from Local Notes NSF to Exchange - - If slow, then there is a problem with the connection to Exchange/Exchange Online tenant
3. Migrate from Domino to local .PST - If slow, then there is a problem with the connection between the Domino server and the migration workers

Additional articles related to migration throughput

Office 365 (M365) Migration Throughput Statement

Migration Throughput Statement

Antivirus software on the migration workstation