No. The source data cannot be manipulated in any way. CloudMigrator uses read-only processes on the source platform.
CloudMigrator has a built-in estimation tool which will estimate the amount of time it will take to complete your migration.
However, it is important to bear in mind that Google and Microsoft's cloud-based solutions have to provide a reliable service to most users, so they will often throttle migration data uploads which CloudMigrator cannot manipulate.
Although we provide an estimation tool, for larger migrations we still recommend that you get a feel for the duration by sizing your migration before it happens. "Sizing" a migration consists of*:
(a) Calculating the number of users and the total amount of data (in GBs) that need to be migrated, and
(b) Performing a test migration, ahead of time, and using the statistics generated to estimate your initial and delta migrations.
*Performing these sizing activities will not consume any additional licensing, so long as the same users are migrated during the real migration.
Yes. Emails will retain their SMTP email addresses or, in the case of legacy DNs, it will automatically convert them into SMTP email addresses on the destination.
CloudMigrator will provide a HTML report, saved locally or sent by email to specified email addresses, at the end of every migration. During a migration, estimations and time remaining are given on the "My Projects" pages, and configuration specific statistics are given.
CloudMigrator has a local migration history and an SQL Database as to avoid duplicates. These store the IDs of already migrated items so that CloudMigrator will never create duplicates.