Before you start your migration, consider the following:
Before starting a migration, bear in mind that time consumed by the migration process depends on size on accounts involved. See the following migration speed test as an example:
| Number of migrated accounts | Duration |
|---|---|
| 1 account (1,5 GB, 50800 items, 75 folders) | 1 h 37 min. |
| 4 accounts (6 GB, 203177 items, 300 folders) | 4 h 13 min. |
Table 1. Migration speed test
Time consumed by migration shortens with increasing number of accounts migrated concurrently, since the migration runs in up to six threads at a time.
It is recommended to get the network and all users involved ready for outage of email services and for migration in low-load time. Migration can be also performed by batches of users, optimally these batches should be divisible by six.
The Kerio Exchange Migration Tool will not remove accounts on Exchange Server, but for security reasons it uses them only in the read only mode, so that it is possible to interrupt the migration process and keep using the Microsoft Exchange Server until migration of other users.
The scenario is likewise in Kerio MailServer. Migration does not remove the existing data or settings in Kerio MailServer. Migrated data will be added as extra data. For this reason, it is necessary to bear in mind possible duplication of data and try to avoid it.
Migration requires:
administration username and password for Microsoft Exchange Server.
username and password of the Kerio MailServer's primary administrator (i.e. the username and password set in the Initial Configuration Wizard).
For security reasons, user passwords cannot be migrated along with user accounts. However, there are some solutions available:
Data will be migrated after setting mapping of users from the Active Directory to Kerio MailServer. Passwords do not have to be changed in this case.
To learn more about mapping of user accounts, read chapter Mapping users from directory services in the Administrator's Guide.
Data can be migrated to the Kerio MailServer if empty (i.e. no user accounts have been created there yet). Migration includes creating accounts in Kerio MailServer and generating of new passwords which will be recorded in the Report log (for details, see section 5 Migration process logs).
Data will be migrated after mapping of user accounts from the Active Directory to Kerio MailServer. Passwords do not have to be changed either in this case.
To learn more about importing of user accounts and its configuration, read chapter Import Users in the Administrator's Guide.
Individual options will be focused in the following sections of this document. If you use Active Directory, it is recommended to use the option of user accounts mapping.
Problem description:
Microsoft Exchange Server 5.5 does not support UNICODE. Special characters (diacritics, etc.) in names of accounts, folders and email recipients will not be displayed correctly.
Solution:
The computer where Kerio Exchange Migration Tool would be installed, must include:
Windows in the corresponding localization,
Microsoft Outlook in the corresponding localization.
Another option is change of language from English to your native language for applications which do not support UNICODE. This can be done under .
Migration may come up against items which are saved in unsupported formats. Therefore, Kerio Exchange Migration Tool would not convert these items. In any of these cases, the item will be saved as an attachment in the MSG format in a new message with the subject of the original message. These attachments can then be opened in Microsoft Outlook.
All RTF email will be converted to plain text within the migration. Images included in RTF emails will be removed.