Home » Categories » Kerio Connect » Server configuration » Export and migration
Icon Printer Icon Email      Icon Twitter Icon Digg Icon Stumbleupon Icon de.icio.us Icon FaceBook

Kerio IMAP Migration Tool


To migrate to Kerio Cloud, see Kerio Connect Migration Service.

To migrate from Microsoft Exchange Server, see Kerio Exchange Migration Tool.

Kerio IMAP Migration Tool (KIMT) is a free tool for migrating user accounts, email messages, and folders from your IMAP server to Kerio Connect:


Preparing for the migration

The duration of the migration depends on many factors, and may take some time. If possible, perform the migration during light usage hours.

It is important to note that the IMAP migration tool will not overwrite or remove existing data in the destination Kerio Connect mailbox. Therefore, you may run the migration tool on active Kerio Connect mailboxes, and the data will be merged. It is recommended to direct users and new email to the destination Kerio Connect server, so that users will not be changing data on the source IMAP server either during, or after the migration process.

CSV file with user accounts

Before the migration, prepare a CSV file with users and their passwords. This information is crucial for access to the source IMAP server. The CSV file must follow this pattern: user@domain.com;password;Full Name.

Public and archive folders

Public and archive folders cannot be migrated by the standard procedure. If you need to migrate these folders, move them to the mailbox of any user you will migrate. The folders will then be migrated as private folders

Before you start

  1. Install Kerio Connect and run it.

  2. Make sure the IMAP service in Kerio Connect runs on port 143.

  3. On a machine which can access both Kerio Connect and the source IMAP server, download and install the KIMT tool.

  4. We recommend to make sure the source IMAP server cannot accept new emails temporarily (otherwise migrated data will be inconsistent).

  5. If connection between the IMAP server and Kerio Connect goes through a firewall, open the following firewall ports:

    • TCP protocol on port 143

    • TCP/UDP protocol on port 44337

Migrating the data

The migration requires that both the source IMAP server and Kerio Connect are running.

  1. Run the KIMT tool and follow the wizard.

  2. Enter the hostname of the source IMAP server. We recommend to Use SSL connection for security reasons.

  3. Enter the hostname and admin credentials of Kerio Connect.

  4. Choose Accounts For Migration, load the CSV file and select users to migrate.

    The migration process may be time-consuming. We recommend to migrate data by parts (groups of users).

  5. Click Migrate.

  6. When the migration is finished, click the Report or Debug log links to see the migration result.


Once the migration is completed successfully, we recommend create new accounts/profiles in users' email clients. This will help them avoid data inconsistence.

If you interrupt the migration process, the KIMT saves only the completely migrated data of the user currently being migrated. Before you start the migration process again, we recommend to delete the partially migrated user in Kerio Connect (otherwise the data will be duplicated). See the migration Report log for details.

Migration process logs

Kerio IMAP Migration Tool generates various logs addressing the migration process. They are stored in the following locations:

  • MS Windows — %TEMP%\KimtLogs\MMDDYYYY_HHMMSS

  • Linux — ~/KimtLogs/MMDDYYYY_HHMMSS

  • Mac OS X — ~/Library/Logs/KimtLogs/MMDDYYYY_HHMMSS

Each start of the migration tool generates a new log.

Report log

After completion of each migration, read through this file to make sure that no errors occurred and that all user accounts have been migrated correctly.

Debug Log

Information provided in this log is useful especially for the software developers. Should any issue arise during the migration process, this log will help choose the right remedy in cooperation with Kerio Technologies technical support.

comments powered by Disqus