Dashboards are essential for monitoring your migration performance, mailboxes, files, sites, groups migration statuses, and more from one place.
They are an important part of any migration project. They provide a visual overview of how your migration is progressing, allowing you to monitor each step in the process.
In this article, we explain the different statuses.
In the main menu of every product, there is a dashboard option:
Clicking on the dashboard, you can see the statistics for every migration.
If you need more detailed information about how your migration is progressing, you can access the “Details” tab. This will show you an explicit analysis for every job.
Dashboard Options, By Column
Mail Migration Dashboard
| ID | Id of the user on the platform |
| STATUS | Migration Status of the specific object |
| SOURCE EMAIL | User's source email |
| MAIL TOTAL | Counting the total emails read from the source |
| MAIL TOTAL TRASH | Counting the total amount of emails read from the source trash folder |
| MAIL SUCCESS | The total number of emails that have been migrated successfully |
| MAIL IGNORED | Counting the total amount of emails that have been ignored |
| MAIL FAILURE | The total amount of emails that didn’t migrate and are in error |
| MAIL DELTA | A calculation that contains mail total minus mail success, mail ignored, and mail failure |
| CALENDAR TOTAL | Counting the total calendars read from the source |
| CALENDAR SUCCESS | The total number of calendars that have been migrated successfully |
| CALENDAR IGNORED | Counting the total amount of calendars that have been ignored |
| CALENDAR FAILURE | The total amount of calendars that didn’t migrate and are in error |
| CALENDAR DELTA | A calculation that contains calendar total minus calendar success, calendar ignored, and calendar failure |
| CONTACT TOTAL | Counting the total contacts read from the source |
| CONTACT SUCCESS | The total number of contacts that have been migrated successfully |
| CONTACT IGNORED | Counting the total amount of contacts that have been ignored |
| CONTACT FAILURE | The total amount of contacts that didn’t migrate and are in error |
| CONTACT DELTA | A calculation that contains contact total minus contact success, contact ignored, and contact failure |
| TASK TOTAL | Counting the total tasks read from the source |
| TASK SUCCESS | The total number of tasks that have been migrated successfully |
| TASK FAILURE | The total amount of tasks that didn’t migrate and are in error |
| TASK DELTA | A calculation that contains tasks total minus tasks success, tasks ignored, and tasks failure |
| RULE TOTAL | Counting the total rules read from the source |
| RULE SUCCESS | The total number of rules that have been migrated successfully |
| RULE FAILURE | The total amount of rules that didn’t migrate and are in error |
| RULE DELTA | A calculation that contains rules total minus rules success, rules ignored, and rules failure |
| GLOBAL BYTES WRITTEN | Total bytes during all actions |
| BATCH NAME | The name of the batches that have been used |
| STARTED DATE | Starting day with the timestamp |
| CONCLUSION DATE | The date of completion of the migration, with the timestamp |
File Migration Dashboard
| ID | Id of the user on the platform |
| STATUS | Migration Status of the specific object |
| SOURCE | User's source email |
| TARGET | User's target email |
| FILE TOTAL | Counting the total files read from the source |
| FILE SUCCESS | The total number of files that have been migrated successfully |
| FILE IGNORED | Counting the total amount of files that have been ignored |
| FILE FAILURE | The total amount of files that didn’t migrate and are in error |
| FILE DELTA | A calculation that contains file total minus file success, file ignored, and file failure |
| FOLDER TOTAL | Counting the total folders read from the source |
| BATCH NAME | The name of the batches that have been used |
| STARTED DATE | Starting day with the timestamp |
| CONCLUSION DATE | The date of completion of the migration, with the timestamp |
Site Migration Dashboard
| ID | Id of the user on the platform |
| SOURCE SITE NAME | User's source site name |
| TOTAL LIBRARIES | Counting the total libraries read from the source |
| MIGRATED LIBRARIES | The total number of libraries that have been migrated successfully |
| ERROR LIBRARIES | The total amount of libraries that didn’t migrate and are in error |
| DELTA LIBRARIES | A calculation that contains the libraries total minus libraries migrated, and libraries error |
| TOTAL PAGES | Counting the total pages read from the source |
| MIGRATED PAGES | The total number of pages that have been migrated successfully |
| ERROR PAGES | The total amount of pages that didn’t migrate and are in error |
| DELTA PAGES | A calculation that contains the total pages minus pages migrated, and pages error |
| TOTAL FILES | Counting the total files read from the source |
| MIGRATED FILES | The total number of files that have been migrated successfully |
| IGNORED FILES | Counting the total amount of files that have been ignored |
| DELTA FILES | A calculation that contains the file total minus files migrated, and files ignored |
| BATCH NAME | The name of the batches that have been used |
| STARTED DATE | Starting day with the timestamp |
| CONCLUSION DATE | The date of completion of the migration, with the timestamp |
Group Migration Dashboard
| ID | Id of the user on the platform |
| SOURCE GROUP NAME | User's source groups name |
| TOTAL LIBRARIES | Counting the total libraries read from the source |
| MIGRATED LIBRARIES | The total number of libraries that have been migrated successfully |
| ERROR LIBRARIES | The total amount of libraries that didn’t migrate and are in error |
| DELTA LIBRARIES | A calculation that contains the libraries total minus libraries migrated, and libraries error |
| TOTAL FILES | Counting the total files read from the source |
| MIGRATED FILES | The total number of files that have been migrated successfully |
| ERROR FILES | The total amount of files that didn’t migrate and are in error |
| IGNORED FILES | Counting the total amount of files that have been ignored |
| DELTA FILES | A calculation that contains the file total minus files migrated, and files ignored |
| TOTAL CHANNELS | Counting the total channels read from the source |
| MIGRATED CHANNELS | The total number of channels that have been migrated successfully |
| ERROR CHANNELS | The total amount of channels that didn’t migrate and are in error |
| DELTA CHANNELS | A calculation that contains the channels total minus channels migrated, and channels error |
| TOTAL MESSAGES | Counting the total messages read from the source |
| MIGRATED MESSAGES | The total number of messages that have been migrated successfully |
| ERROR MESSAGES | The total amount of messages that didn’t migrate and are in error |
| DELTA MESSAGES | A calculation that contains the messages total minus messages migrated, and messages error |
| BATCH NAME | The name of the batches that have been used |
| STARTED DATE | Starting day with the timestamp |
| CONCLUSION DATE | The date of completion of the migration, with the timestamp |
Dashboard Migration Statuses Explained
Column “SUCCESS” / “MIGRATED”
The number of items migrated successfully after a pass. Always consider that this number can only increase through several delta passes and can’t decrease. Because of that, there are scenarios where this number can be greater than the column “TOTAL” number.
E.g. during the first migration, the option for migrating the trash folder is enabled and has been migrated 200 mails. In the second migration (delta pass), the option for migrating the trash folder has been disabled. The MAIL SUCCESS number will be 200 again, and the TOTAL MAIL number will be decreased based on the Trash folder emails that will not be migrated, so the DELTA MAIL number will be with a (-) sign.
Column “IGNORED”
The platform migrates emails, calendars, contacts, tasks, rules, etc. Depending on the scenario. For E.g. items that have been stored in a mail folder and are not classed as mail will not be migrated (for example, a calendar invitation object that is in the inbox or the trash). This explains why at the end of a migration, the total number of items migrated is not the total number of items in the source mailbox (In this scenario, however, the calendar appointment will be migrated correctly and will appear in the calendar view).
Also, the platform supports incremental passes and delta passes. When it detects a mail that has already been migrated, it will not push it a second time. The mechanism is based on the messagesID of the mail. Sometimes, you receive emails twice. The first time it is addressed to you, and the second time because it’s also sent to a group you are a member of. This is particularly the case if you send a message to a group you are a member of: The emails will be stored in your SentItems folder and will also appear in your inbox. During the migration, the platforms migrate the first mail, then it detects that the messageID has already been migrated and does not migrate for a second time.
Column “DELTA” for MAIL and FILE migration
It’s a simple calculation that subtracts the column “TOTAL” minus column “SUCCESS” + column “IGNORED” + column “FAILURE” (For MAIL, The column TOTAL TRASH is not included in the calculation). For several scenarios, this number could have a (-) sign. The (-) sign doesn’t mean that something didn’t migrate or lost, it means that the calculation has ended up on the (-) sign, see the previous example.
Column “DELTA” for SITES and GROUPS migration
It’s a simple calculation that subtracts the column “TOTAL” minus column “MIGRATED” + column “ERROR”. The column “IGNORED FILES” is included in the calculation only for “DELTA FILES”. For several scenarios, this number could have a (-) sign. The (-) sign doesn’t mean that something didn’t migrate or lost, it means that the calculation has ended up on the (-) sign.