Email server cutover checklist
A cutover goes smoothly when the order is right: prepare the new server, lower DNS TTLs, migrate every mailbox, then switch mail flow. Use this checklist to plan a move to SmarterMail from any server.
1. Plan (two to four weeks before)
- List every domain, mailbox, alias, mailing list and forwarding rule on the old server.
- List shared calendars and contacts, rooms and equipment, and public folders, and decide how each will work in SmarterMail.
- Note mailbox sizes, so you can estimate how long migration will take.
- Find every device and application that sends mail through the old server: scanners, printers, line-of-business apps and websites.
- Record your current DNS records (MX, SPF, DKIM, DMARC, Autodiscover, mail host names) and confirm you can edit them.
- Decide who runs Mailbox Migration: users for their own mailboxes, or an administrator, and how the administrator will sign in to each old mailbox.
- Choose the SmarterMail edition and add-ons: MAPI / EWS for native Outlook, Exchange ActiveSync for phones.
- Tell users what will change and when, and how to set up Outlook and phones afterward.
2. Prepare (a day or more before)
- Install SmarterMail on Windows Server, Linux or Docker. New perpetual licenses include free expert installation and configuration.
- Create domains, users, aliases and mailing lists, or connect Active Directory or LDAP (Enterprise).
- Install TLS certificates for your mail host names. SmarterMail can issue Let's Encrypt certificates per domain and host name.
- Open the firewall ports you need (see the table below).
- Generate DKIM keys for each domain in SmarterMail, ready to publish.
- Lower the TTL on MX, Autodiscover and mail host records to about 5 minutes, at least as long as the current TTL before cutover.
- Migrate one test mailbox and check mail, folders, calendars and contacts in webmail, Outlook and a phone.
3. Cut over
- Run Mailbox Migration for every mailbox. Users keep working on the old server while it runs.
- Switch MX records to the SmarterMail server once migration is complete.
- Update SPF to include SmarterMail's sending IP address, and publish DKIM records, then turn on DKIM signing in SmarterMail.
- Update Autodiscover records so Outlook and phones find SmarterMail.
- Test mail flow in both directions with an outside mailbox, and check headers for SPF, DKIM and DMARC passes.
- Reconnect clients: new Outlook profiles (removing any old connector), phones over Exchange ActiveSync, and IMAP clients.
- Move relaying devices and apps to SmarterMail by allowing their IP addresses or giving them SMTP credentials.
Switching MX first? You can point MX records to SmarterMail before migration finishes, but only after every mailbox has been created in SmarterMail. Mail sent to a mailbox that doesn't exist yet can be delayed or go missing.
4. Finish (the following days and weeks)
- Watch SmarterMail's delivery logs and queues for bounces or deferrals.
- Keep the old server running until DNS has fully switched, and check it for mail that arrived after migration finished; move anything you find.
- Review DMARC reports for unexpected failures.
- Raise DNS TTLs back to normal values.
- Confirm with users that nothing is missing, then decommission the old server and cancel its licenses.
DNS records to review
New to these records? The DNS and deliverability guide explains each one with examples.
| Record | Purpose | At cutover |
|---|---|---|
| MX | Where other servers deliver your mail | Point to the SmarterMail host name |
| A / AAAA | Mail, webmail and Autodiscover host names | Point to the SmarterMail server's IP addresses |
| SPF (TXT) | Which servers may send for your domain | Add SmarterMail's sending IP; remove the old server after decommissioning |
| DKIM (TXT) | Signs outgoing mail | Publish the key generated in SmarterMail, then enable signing |
| DMARC (TXT) | Policy and reporting for SPF and DKIM | Usually unchanged; watch reports after cutover |
| Autodiscover (CNAME or SRV) | Lets Outlook and phones find the server | Point to SmarterMail |
| PTR (reverse DNS) | Matches the sending IP to your mail host name | Set by the owner of the IP address if SmarterMail sends from a new IP |
Common ports
| Port | Used for |
|---|---|
| 25 | SMTP: mail from other servers - an alternative port can be configured |
| 587 and 465 | Mail submission from clients and devices |
| 993 and 995 | IMAP and POP over TLS |
| 443 | Webmail, MAPI, EWS, Exchange ActiveSync, CalDAV, CardDAV and Autodiscover |
Guides for your current server
Other servers
Kerio Connect, IceWarp, MailEnable, hMailServer, Zimbra and iRedMail.
All migration guidesFrequently asked questions
How far ahead should I lower DNS TTLs?
At least as long as the current TTL before cutover, and a day or more to be safe. If your MX record's TTL is 24 hours, lower it to about 5 minutes at least 24 hours before you switch.
Should I switch MX records before or after migrating mailboxes?
We recommend migrating first and switching MX records once migration is complete, so no mail is missed. You can switch MX first if you prefer, but only after every mailbox has been created in SmarterMail; switching before the new mailboxes are set up can delay mail or cause it to go missing.
Will users lose email during the cutover?
Not if every mailbox exists in SmarterMail before you switch MX records, and you keep the old server running until DNS has fully switched. Some sending servers cache old MX records, so mail can arrive at the old server for a while after the change; check for it and move anything that does.
How long should I keep the old server?
Until DNS has fully switched, every mailbox has migrated and users have confirmed nothing is missing. Many organizations keep the old server read-only for a few weeks before decommissioning it.
Do I need to change reverse DNS (PTR)?
If SmarterMail sends from a new IP address, ask the provider that owns the address to set a PTR record that matches your mail server's host name. Many receiving servers check it.
Does SmarterTools perform the cutover?
No. SmarterTools can install and configure SmarterMail and provides guides and guidance. Your team, or the IT partner you choose, performs the actual migration.
Start with a test mailbox
Install SmarterMail and migrate one mailbox before you plan the cutover.