Hyper Migration takes too long to complete (4236010)

Hyper Migration takes too long to complete.

**Hyper Migration = Migrations where the source is Dropbox, FileShare, Box, OneDrive, Google Drives, or Google Shared Drives.

Switch to Asynchronous Mode, going to Help Tab > Profile Manager > General > Azure Migration Mode:

• When in Asynchronous mode, the job is reported as finished when all packages created from the source are uploaded to Azure, and added to the import queue. The job completion is not an indication that all content is copied to the target library. The log viewer in Asynchronous mode will display the status of items during the package creation and upload to Azure Pipeline. This option is recommended when a speedier migration is important.
  

• To view the actual status of the item when the azure batches are processed there is an option of ‘Refresh Logs’ from the Azure turbo window to check statuses at the end of the work day, therefore allowing you to manually refresh azure logs and synchronize them with essential's post-migration logs, or use Azure Logs Refresh Policy for Hyper Mode jobs.
  

• When in Synchronous mode, the job is reported as finished when all packages created from the source are uploaded to Azure, and all azure batch processing statuses are returned as complete. However, the job progress will take longer in this mode, but when it has finished it is an indication that all content is copied to the target library. The log viewer in Synchronous mode will display the status of items during package creation and the migrated content on the target.

Note:  The next job created in a Hyper migration will start once the previous job operation along with logs update is complete. Therefore it is considered a slower process versus Asynchronous mode and recommended as the option when there is a need to monitor individual migrations before starting a new migration.