After connecting to your source and target email service, the next step is to list the mailboxes you want to migrate. This is done in the Mailboxes tab.
|
Note: If you haven’t already done so, set up the mailbox accounts in the target email service. On Demand Migration for Email does not create target mailboxes during a migration. Also, you cannot add mailboxes until you have successfully connected to your source and target email service. |
You can add the mailboxes you want to migrate manually, or in the case of a large migration, you can import a TSV file which lists each mailbox. If you selected the option Use end-user credentials when connecting to either the source or target email service, you must specify the passwords for each mailbox.
Be aware that if you import TSV file, this will overwrite any mailboxes that have already been added, whether manually or through a previously imported TSV file.
Supported mailbox types
This table lists mailbox types migrated by On Demand Migration for Email.
G Suite |
|
|
|
|
Exchange 2007/2010/2013/2016/2019 |
|
|
*Migration from Exchange 2010, 2013, 2016, and 2019 |
|
Microsoft 365 |
|
|
|
|
Sun ONE/iPlanet |
|
|
|
|
Zimbra |
|
|
|
|
IMAP |
|
|
|
|
POP/Hotmail |
|
|
|
|
Resource mailboxes for Exchange and Microsoft 365 are used for reserving and coordinating rooms and equipment.
Dealing with large mailboxes
Mailboxes that added to a migration plan are migrated in parallel as described in Connecting to Email Services. However, contents of each individual mailbox are migrated subsequently, item by item. That may cause decreased migration performance for large mailboxes.
To make the migration faster for a large mailbox, you can split the mailbox's contents into several parts by time when message is created or received and then migrate each part in a separate migration plan.
To do that, take the following steps:
- Approximately estimate the time period of messages within the mailbox by finding the oldest message and the newest.
- Split the estimated time period into several shorter time intervals. Note that each time interval must have a one-day overlap with the neighbor time intervals to avoid data loss.
- For each time interval create a separate migration plan. Note that each migration plan should use its own pair of source and target administrative accounts.
- Add the mailbox to all of these migration plans.
- On the Options page of each migration plan under Date Range select Choose Date Range and specify the corresponding time interval.
|
Important: In case of migration to Microsoft 365, it is not recommended to have more than 4 migration plans processing the same mailbox in parallel due to Microsoft 365 throttling limitations. Otherwise, the The server cannot service this request right now. Try again later. Waiting 5.00 minutes before resuming errors may repeatedly occur decreasing an overall migration speed. |