Identifying Bottlenecks - Identifying Bottlenecks - Alfresco - OnBase - Other - Hyland Migrate - Other/Hyland-Migrate/7.0/Hyland-Migrate/Usage/Migrations/Executing-a-Migration/Migration-Performance/Identifying-Bottlenecks - 7.0 - 7.0

Hyland Migrate

Platform
Other
Product
Hyland Migrate
Release
7.0
License
ft:lastPublication
2026-09-24T22:05:58.320000
ft:locale
en-US

You can identify bottlenecks in a migration process by analyzing the Processing Time Distribution metrics on the Hyland Migrate Dashboard.

Note: Migration can only run as fast as the slowest component.

The Processing Time Distribution graph provides the average amount of time that each migrated item spends in each part of the migration, such as Source, Mapping, and Target. The taller the bar in the graph, the slower that part of the migration is compared to the others.

In the following example, the Target is roughly 20 times slower than the Source, and the Mapping is so fast that it is not even visible in the graph. This indicates that to optimize overall migration speed, efforts should concentrate on improving the Target system's throughput.

The graph illustrating the processing time of the Source, Mapping, and Target, where the Target bar is much taller than the Source bar and the Mapping bar is invisible
Note: Additionally, system resources of the source and target systems can be monitored to identify bottlenecks.

Once a bottleneck has been identified, you can optimize the specific area where it has been identified. For more information on optimizing specific areas of the migration process, see Optimizing Performance.