The following description addresses the procedure of starting of the migration tool especially on Windows. However, you can follow the guidelines even if you run it on Mac OS X or Linux.
Windows: | Run Kerio IMAP Migration Tool, for instance from . |
Mac OS X: | Double-click on the KIMT icon or drag it to Applications. |
Linux: | Unpack thee TGZ file including the Kerio IMAP Migration Tool application and run the program. |
Table 1. Installation on individual operating systems
Do not start the migration tool if it is already running.
The migration tool is a wizard which will ask for IP address or DNS name of the source IMAP server and login information for Kerio MailServer (you will need to log in with the name and password of the primary administrator).
Note: The migration tool will not affect accounts on the source server, but for security reasons it uses them just in the read-only mode, so that it is possible to interrupt the migration process and keep using the original server until migration of other users. Also, migration does not remove the existing data or settings in Kerio MailServer. Migrated data will be added as extra data. Therefore, beware of possible data duplication (data gets duplicated if one account is migrated twice).
Once you are connected to both servers, use the Load and Select Users users to load the CSV file with users and select user accounts to be migrated (see figure 3 User selection dialog).
button in theThe migration process may be time-consuming. Therefore, for time-saving reasons it is recommended to migrate data by parts (see section 2 Before you start).
At the start of migration, the Migration Status window (see figure 4 Dialog displaying status of migration of particular mailboxes) is opened, showing the current status of the migration progress.
If the migration process is interrupted (finished without being completed) deliberately, the following results take effect:
Data of users whose migration has been completed will be saved in Kerio MailServer.
In case of users whose migration was just being in progress in the time of the interruption, only part of the data (data having been migrated completely at the moment) is migrated. If the user is migrated again, the data already migrated gets duplicate. For this reason, it is recommended to remove the partly migrated users in the Kerio MailServer's administration interface before executing another migration. To find out which users were involved in an interrupted migration, see the migration report (for details, see section 5 Migration process logs).
Users in the status that indicates they have not been migrated yet do not have accounts created in Kerio MailServer and they can therefore be migrated within one of the following batches.
When the migration is completed, the Migration Result page is opened (see figure 5 Migration result dialog). This page sums up information about the migration which has just been completed.
To get migration process details and reports of possible errors, click on the Report link.
Once a migration is completed successfully, it is recommended to create new accounts in users' email clients (or profiles, if supported by the applications). This will help you avoid data inconsistence on the client sides. Details on how to set for example profiles in MS Outlook or a new account in MS Entourage, refer to Kerio MailServer 6, User's Guide.