Kerio Connect alternative: migrate to WisMail
WisMail is a self-hosted Kerio Connect alternative: build it in parallel, copy mail with standard protocols, test with a pilot group, then switch MX. This page is explicit about which steps are general methods and which parts we have not verified.
Why teams look at WisMail as a Kerio Connect replacement
- A self-hosted server: mail, calendars and contacts stay on your infrastructure.
- One edition with every feature, priced per user, as an annual subscription or a one-time purchase.
- The clients you already use: IMAP, ActiveSync for phones, EWS and Autodiscover for Outlook and Apple Mail, CalDAV and CardDAV.
- A free 30-day trial, so you can run both servers side by side with your real data.
- Webmail and web administration in Vietnamese, English, Chinese and Russian.
Features · Compared with Kerio Connect · Pricing
Check these gaps before you commit
- No XMPP chat, no clustering, no Outlook Connector, no BlackBerry support.
- No vendor-hosted management cloud, and no encryption of data at rest by the software itself.
- Backups are scheduled from web administration, but restore is manual; there is no restore command.
- Licence keys do not update themselves: after a renewal you download and install the new key.
What maps to what
| What you move | In WisMail | How you move it |
|---|---|---|
| Users and groups | Users and Groups in web administration | Import from a CSV file (Name, FullName, Password, Description, MailAddress, Groups) or sync from LDAP / Active Directory. Set new passwords; there is no password import. |
| IMAP, POP3 and SMTP mailboxes with quotas | Copy over IMAP with a copy tool, in several passes. POP3 download pulls the inbox only. | |
| Calendars and contacts | CalDAV and CardDAV, webmail | Copy between two accounts in one CalDAV/CardDAV client, or import .ics and .vcf files into the client. |
| Aliases, lists, resources, public folders | The same objects in web administration | Recreate by hand, then copy the content of shared folders over IMAP. |
| Phones and tablets | ActiveSync 2.5 to 16.1, with device list and remote wipe | Add a new account on each device. |
| Outlook and Apple Mail | EWS and Autodiscover, or IMAP and SMTP | Create a new profile or account; there is no Outlook Connector support. |
| Spam and virus settings | SpamAssassin with Bayes, greylisting, ClamAV, global rules | Configure again; settings are rebuilt, not imported. |
| Certificates | Let's Encrypt or your own certificate | Issue or import a certificate for the new host name. |
| License | A WisMail trial, then a WisMail key | Register the trial; buy a license for your number of users. |
The steps in short
1. Inventory what you run today
Write down domains, users and quotas, aliases, mailing lists, groups, public folders, filter rules, certificates, DNS records (MX, SPF, DKIM) and the mobile devices that sync. That is your rebuild list.
2. Build WisMail in parallel
Install WisMail on a new server following the install guide, run the wizard, register the trial and obtain a certificate. Leave the old server running; do not change MX yet.
3. Create domains and users
Create the domains, then the users: by hand, in bulk from a CSV file, or synced from LDAP / Active Directory if you use a directory. Recreate aliases, mailing lists and public folders.
4. Copy mail over IMAP
IMAP is a standard protocol, so it works between any two servers: copy each mailbox with an IMAP copy tool, or add both accounts to a mail client and drag folders across. Do several passes: a first one for old mail and a last one right before the MX switch for recent mail.
5. Move calendars and contacts
Add the old and new accounts to one CalDAV/CardDAV-capable application and copy events and contacts across, or export iCalendar (.ics) and vCard (.vcf) files and import them into the client while it is connected to the new account. Check recurring events and time zones afterwards.
6. Reconnect devices
Phones and computers need a new account (ActiveSync, IMAP/SMTP or CalDAV/CardDAV) pointing at the WisMail server. Plan instructions or group support sessions for users.
7. Switch MX and watch
Lower the MX TTL a day ahead, run the final mail copy, point MX at the new server, publish the new SPF, DKIM and DMARC, and watch queue and logs for a few days. Keep the old server for a while as a rollback.
Ready to do it?
The how-to guide has the CSV format, an IMAP copy example and the cut-over checklist.
Migrate from Kerio Connect Installation Download
Migration questions
Is there a Kerio Connect migration tool?
Can I run both servers in parallel?
Do users have to change passwords?
Will phones and Outlook keep working?
How long does a migration take?
Can I get help with the migration?
Kerio is a trademark of its respective owner. WisMail is an independent product, not affiliated with or endorsed by Kerio or GFI.
Try it on your own server for 30 days
Install the package, register the trial and test with real users and devices. No payment card needed.