# WorkMail migration checklist

Prepared by Folio Inbox — 4 September 2026. Free to copy, adapt and share.
This checklist works with any destination; Folio is not affiliated with AWS.

AWS ends Amazon WorkMail support on 31 March 2027. After that date the service
will no longer be usable. Finish and verify your move before then.
Source: https://docs.aws.amazon.com/workmail/latest/adminguide/workmail-end-of-support.html

## Before you choose

- [ ] List all domains, addresses, aliases, folders and people needing access.
- [ ] List calendars, contacts, shared resources, distribution groups and client requirements.
- [ ] Choose a provider that supports those requirements. AWS names Kopano Cloud,
      Zoho Mail and Zoom Mail; other providers may fit your situation.
- [ ] Save an independent backup and verify you can open it. Follow AWS's mailbox
      export guidance linked from the notice above; plan calendar/contact handling
      separately. Do not assume an IMAP mail import transfers all your data.
- [ ] Record current DNS values and TTLs. List every service sending for your domain.

## Prove the destination before changing mail routing

- [ ] Connect one test mailbox through the destination's authenticated importer.
      Never put mailbox passwords in this checklist or send them to a marketer.
- [ ] Compare old and recent messages, sent mail, folders and attachments.
- [ ] Handle contacts, calendars and other non-mail data through a supported path.
- [ ] Set up the new domain's sender authentication using the provider's exact values.
      Keep a single SPF policy and a single DMARC policy per DNS name. Preserve other
      legitimate senders; do not blindly replace an existing policy or tighten it
      during migration without checking alignment.
- [ ] Test sending before changing MX where the destination supports it.

## Cut over and verify

- [ ] Schedule the move and a rollback window while WorkMail is still operational.
- [ ] Lower MX TTL in advance. Wait at least the OLD TTL before relying on the new TTL.
- [ ] Follow the new provider's MX cutover instructions only after the mailbox and
      required addresses are ready to receive. Keep the old DNS values for rollback.
- [ ] Keep WorkMail active during propagation. Check both inboxes: senders may still
      use cached records. Multiple MX records do not mean every message is copied
      to both providers, and no checklist can guarantee zero downtime.
- [ ] Reconcile messages arriving during the overlap. Re-run an import only after
      confirming how the destination handles duplicates and folders.
- [ ] Test external incoming mail and replies from each address. Check the From
      address and sender authentication, not just whether the message arrived.
- [ ] Verify the final copy and independent backup before retiring WorkMail.
      A migration copy is not automatically a compliance archive.

## When Folio fits

Folio Inbox is one inbox for one person managing several business domains.
It imports WorkMail mail over IMAP, not WorkMail calendars or contacts. It does
not replace staff mailboxes, shared team access or Exchange/ActiveSync groupware.

Preview one domain and your first 100 sends with no card. Paid monthly plans:
Solo $3.50 (3 domains / 1,000 sends), Studio $15 (10 / 6,000), Holding Co. $39
(unlimited domains / 30,000 sends). Annual billing is also available; confirm
current terms at https://folioinbox.com/pricing before purchasing.

Read the guide and check your fit:
https://folioinbox.com/migrate/aws-workmail?utm_source=checklist&utm_medium=download&utm_campaign=workmail-switch-2026#switch-kit

Not leaving WorkMail, but managing several businesses?
https://folioinbox.com/for/portfolio-entrepreneurs?utm_source=checklist&utm_medium=download&utm_campaign=portfolio-operator-2026