Skip to main content
WisMail

Migrate from Kerio Connect: Step by Step

This guide moves a mail domain from Kerio Connect (or any other IMAP server) to WisMail without downtime: you build the new server next to the old one, copy the data with standard protocols, test with a pilot group and only then switch MX. The marketing overview is Migrate from Kerio Connect; this page is the how-to.

Read this first. There is no automatic migration tool. We have not verified that WisMail can use a Kerio data directory or configuration file, so do not copy those onto a live server. The steps below use what WisMail ships (CSV user import, IMAP, POP3 download, CalDAV/CardDAV) plus general methods with third-party tools. We have not verified a step-by-step run against a Kerio server, so treat the first mailbox as a test. A Kerio license key does not work on WisMail; use a WisMail trial or license.

1. Inventory what you run today

Write down everything you must rebuild. This list is your checklist for the cut-over:

  • Domains and domain aliases, and which one is primary.
  • Users: login names, full names, quotas, who is disabled, who belongs to which group.
  • Aliases, mailing lists, groups, resources (rooms, equipment) and public folders.
  • Filter and message rules, spam and virus settings, allowed or blocked senders.
  • DNS records: A, MX, SPF, DKIM, DMARC, PTR, Autodiscover.
  • Certificates and the host name clients connect to.
  • Devices that sync (phones, Outlook, Apple Mail) and the number of enabled users, because your WisMail license counts users.

2. Build WisMail in parallel

  1. Install WisMail on a new Ubuntu server with its own host name, following Install a mail server on Ubuntu 24.04. Run the setup wizard and register the trial.
  2. Get a certificate (see Set up SSL/TLS with Let's Encrypt); clients should not see warnings during the pilot.
  3. Leave the old server running and do not change MX yet.
Web administration dashboard with server status

3. Prepare DNS

A day or two before the cut-over, lower the TTL of the MX record at your DNS provider so the switch takes effect quickly. Prepare the new SPF, DKIM and DMARC records as described in DNS for your mail server. WisMail signs outgoing mail with a per-domain DKIM key and shows the TXT record to publish in web administration. Publish it with the switch, not before, so you never have two conflicting SPF records.

4. Create domains and users

Create each domain in web administration, then create users. For more than a handful, use the CSV import.

  1. Go to Users, open the Import and Export menu and choose Import from a CSV File...; the dialog asks for the file and the domain to import into.
  2. Select your .csv file. It must be encoded in UTF-8 and the file name must end in .csv.
  3. Check the rows in the review dialog, choose a user template if you use one, and confirm.

The first line is a header. Only the Name column is required; separate columns with a comma or a semicolon:

Name,FullName,Password,Description,MailAddress,Groups
alice,Alice Nguyen,ChangeMe-2026!,Sales,[email protected],Sales
bob,Bob Tran,ChangeMe-2026!,Support,[email protected],Support

Passwords must meet the server's complexity rules. There is no password import from Kerio, so give users an initial password and ask them to change it, or use LDAP / Active Directory if your passwords already live in a directory. Then recreate aliases, mailing lists, groups, resources and public folders by hand; see Administer your mail server. Remember that enabled users cannot exceed your license.

Web administration: the Import Users dialog for a CSV file with the review step

5. Copy mail over IMAP

IMAP is a standard protocol, so a copy tool can read from the old server and write to the new one folder by folder. A common free tool is imapsync; it is third-party software, not part of WisMail. Run a dry run first, for one mailbox:

imapsync --host1 old-mail.example.com --user1 [email protected] --password1 'OLD-PASSWORD' --ssl1 \
         --host2 new-mail.example.com --user2 alice --password2 'NEW-PASSWORD' --ssl2 --dry

Check the folder list and message counts, then run it for real. The login name on the new server is the Name you created, so adjust --user2 if you use full addresses as login names. Notes:

  • You need each user's password on the old server, or an administrative way to read mailboxes that your old server documents.
  • Make sure each user's quota on WisMail is large enough: IMAP refuses to add messages beyond the quota.
  • Do several passes: a first pass for the bulk of old mail, and a last pass right before the MX switch for recent mail. The copy skips messages already present.
  • Prefer not to use a tool? Add both accounts to a mail client and drag folders across, or use the POP3 Download tab of Downloads & scheduling in web administration to pull a mailbox from the old server. POP3 only fetches the inbox, not your folder tree.

6. Move calendars and contacts

WisMail speaks CalDAV and CardDAV. Add the old account and the new account to one CalDAV/CardDAV client (for example Apple Calendar or Thunderbird) and copy events and contacts from one to the other, or export iCalendar (.ics) and vCard (.vcf) files from the old server and import them into the client while it is connected to the new account. Afterwards check recurring events, time zones and attendee lists. The webmail module has no file import, so the client does the upload. Read Using calendar, contacts, tasks and notes.

7. Reconnect devices

Phones and computers need a new account pointing at WisMail: ActiveSync or IMAP/SMTP on phones, Autodiscover/EWS or IMAP on Outlook and Apple Mail. See email on iPhone and Android and Outlook and Apple Mail. Send users these two guides, or schedule group sessions.

8. Pilot, then switch MX

  1. Move a pilot group first; ask them to send and receive, use their phones and use shared calendars for a few days.
  2. When ready, run the final IMAP pass, point MX at the new server and publish the new SPF, DKIM and DMARC records.
  3. Watch the queue and logs in web administration for a few days and tune the anti-spam settings. If your new server cannot send on port 25, use a relay (smarthost).
  4. Keep the old server, switched to read-only use, for a few weeks as a rollback.

9. Verify and go live

Kerio is a trademark of its respective owner; WisMail is not affiliated with Kerio or GFI.