There are multiple options how a mailbox move job can be created; you can add it as a new job from the Email archive’s Jobs page, or you can create a mailbox mover job directly from the address book, with selecting the “Move mailbox” option from the desired mailbox’s context menu. On the screenshot below can be seen, how a mailbox move job is created for mailbox “edit.balazsy@tech-arrow.com” directly from the address book.

With clicking on the “Move mailbox” option in the mailbox’s context menu, the Select mailbox to move dialog will automatically open. The desired source mailbox will be already preselected in this dialog. The new mailbox mover job will be created with the name of the selected mailbox. By default, the job will be able to run on any available node.

In the Select mailbox to move dialog the administrator may set the following:

A. The source mailbox, of which archived data should be moved: if the job has been created from the address book, the source mailbox will be preselected; if the job has been created from the jobs page, the source mailbox has to be configured manually.

B. The target mailbox; in special cases the source mailbox archive data may be moved to a target mailbox archive. To achieve this, check the “Move to different mailbox” option on the target side and specify a new target mailbox. If you would not like to move the source mailbox archive data to a target mailbox archive, select the source mailbox on the target side, too (by default it is configured like this).

                                                              Screenshot A                                                                                       Screenshot B: Source mailbox archive selected on the target side.

C. The source database and storage: by default the already associated database and storage of the source mailbox are set here. The source mailbox statistics (email count, folder count) can be seen in the source column.

D. The target database and storage: the user may select here the target destinations, where the archive data of the source mailbox should be moved. On Screenshot D we have selected Ex-employees’ DB and Ex-employees’ storage. The target mailbox statistics (email count, folder count) can be seen in the target column as well.

Screenshot C: Associated DB and store.                                                                                       Screenshot D: Target DB and store.

E. An across tenant move is also supported:

You have some configuration options based on what the behavior of the Mailbox move job will be a bit different.
If you :

Select DIFFERENT databases but the same store, then the records will be moved (copied and then deleted) from the source database into the new target one, but the binary will be kept in the same store

Select same databases but DIFFERENT store, then the records in the database will be updated only with the new storeID. The source storage data will be copied into the new storage and the old files will be removed from the source store if the source store supports deletion. Deletion is actually supported in Disk store and HybridStore. If the store does not supports deletion, then the binary will be kept in the source store

Select DIFFERENT database and DIFFERENT store, then the combination of the above will happen, so the database records and binaries will be moved.

Move into different mailbox, then the original mailbox record will also be deleted from the database if all entries were successfully moved.

When configuring a Mailbox move job the administrator is also required to set the running time of the job, notification settings and the resource settings on the job’s configuration page:

✓ Scheduling settings: the administrator may select a scheduler from the dropdown list, which will determine, when the moving process will run. By this plugin type it is recommended to set one time scheduler, or to start the job manually. For more information how to set up schedulers please refer to section Schedules.

✓ Notification settings: if you want to use notification emails to be informed about potential failures of the mailbox move process, then select a) in which cases such notifications need to be sent, b) who will be the recipient of such emails. It is recommended to set here Errors or warning occur option (or to check the job events on the monitoring page).

✓ Resource settings. Set the value, which will determine how many items will be processed simultaneously by the mailbox move job.

Option “consolidate” on the job’s configuration page: Consolidation option is the fastest way of how to correct your mistake, if you have archived the same mailbox into multiple databases. By clicking the consolidate button the system will find all mailboxes which are in two or more databases and will list them on the Mailbox selection page. The target database/target store are the already assigned ones based on the View address book. So, once you have the list, you just select one or more mailboxes and click OK.

If this dialog is empty, it means that all your metadata are in one database only, there is nothing to correct.

How to check if the mailbox move was finished successfully?
The user may check on the monitoring page, if the mailbox move job successfully moved the selected mailbox archive to the desired database/storage. To check this, navigate to the email archive jobs’ page on the ribbon (Email Archive tab ⇒ Archive ⇒ Jobs). Open the context menu of the mailbox move job, and click on “Show last logs”. This will redirect the user to the monitoring page, where the last run of the selected job will be preselected, and the correspondent job events can be viewed.