Skip to content
Reference architecture · Illustrative scenario, fictional business

Email platform migration off Amazon WorkMail before support ends

A runbook to move 25 mailboxes from Amazon WorkMail to Microsoft 365 or Google Workspace before AWS ends WorkMail support on March 31, 2027: inventory, coexistence, cutover and rollback.

Illustrative scenario, fictional business. Kessler Roe Accounting is invented to show how I would run this migration; it is not a client.

Role
Migration lead
Industry
Accounting
Status
Design, not built for a client

Design targets

  • Mar 31, 2027DeadlineAWS ends WorkMail support
  • 25MailboxesMoved in one cutover window
  • 0Lost messagesItem counts compared per mailbox
  • One DNS changeRollbackUntil WorkMail is retired

Context and problem

Illustrative scenario, fictional business. Kessler Roe Accounting runs 25 mailboxes on Amazon WorkMail. AWS stopped accepting new WorkMail customers on April 30, 2026 and ends support on March 31, 2027; after that date the mailboxes, the console and their resources are no longer usable. The firm has to move, and tax season sits right before the deadline.

Constraints

  • A fixed date. The move has to be finished, with a margin, before March 31, 2027, and not in the middle of tax season.
  • Client correspondence is the business. No message can be lost, and clients must not notice the change.
  • Mail only, by default. The standard IMAP migration paths copy mail folders, not calendars or contacts, so those need their own step.

Architecture

Email platform migration off Amazon WorkMailFour phases: inventory, coexistence while mail is copied, MX cutover to the new suite, and a rollback window before WorkMail is retired. The deadline is AWS ending WorkMail support on March 31, 2027.RunbookMail deliveryIMAP copy1. InventoryMailboxes, aliases, DNS2. CoexistenceCopy mail, delta passes3. MX cutoverLow-TTL weekend window4. Rollback windowThen retire WorkMailAmazon WorkMailSupport ends Mar 31, 2027Microsoft 365 orGoogle WorkspaceLicensed mailboxes

How to read it. Read the top row as the timeline and the bottom row as where mail is delivered in each phase. MX records keep pointing at WorkMail until the cutover, the highlighted step. Until WorkMail is retired, the rollback path is a DNS change back.

Runbook

  1. Inventory. List every mailbox, alias, group and shared mailbox; record sizes and the largest messages; export the current DNS records, including MX, SPF, DKIM and DMARC.
  2. Coexistence. Create and license the new mailboxes, then copy mail over IMAP while WorkMail still receives everything. Microsoft 365 uses a migration endpoint and batch from a CSV; Google Workspace’s data migration service imports up to 100 IMAP users at a time and needs a super administrator. Run a delta pass before cutover.
  3. Cutover. Lower DNS TTLs two days ahead, switch MX and the authentication records in a weekend window, run a final delta pass, and check send and receive for every mailbox.
  4. Rollback window. Keep WorkMail running for two weeks after cutover. If something fails, pointing MX back is the rollback. Then export a final archive and retire WorkMail.

Decisions and trade-offs

  • Microsoft 365 or Google Workspace, decided by the firm’s tools. If the accountants live in Excel and Outlook, Microsoft 365; if they already use Google Drive and Sheets, Google Workspace. AWS itself recommends third-party hosted mail and names Kopano Cloud, Zoho Mail and Zoom Mail; either suite fits that guidance.
  • One weekend cutover, not a gradual move. At 25 mailboxes, a single window is simpler than running two systems for routing. Rejected: splitting users across both platforms, which complicates shared mailboxes and calendars.
  • Calendars and contacts as their own step. The IMAP paths do not carry them, so each user exports them and they are imported before cutover, checked by the user.

Governance and cost

  • Data handling: mail is copied directly between providers; the migration admin account is removed after retirement, and the final WorkMail export is kept under the firm’s retention policy.
  • Limits that shape the plan: the Microsoft 365 IMAP migration handles up to 500,000 items per mailbox and messages up to 35 MB. Larger items found in the inventory are moved by hand.
  • Cost: the new suite’s per-user license, an overlap month of both services, and the consultant’s time for inventory, cutover weekend and the rollback window.

Failure modes

What breaks How it is detected Fallback
Item counts differ after copy Per-mailbox count comparison Re-run the delta pass for that mailbox
Mail bounces after cutover Test sends from outside the domain Fix records, or point MX back to WorkMail
Authentication records missed DMARC reports, spam placement Restore SPF and DKIM from the inventory
User missing calendar items User checklist after cutover Re-import from the user’s export

Outcome

Design targets, not results: all 25 mailboxes moved before March 31, 2027 and outside tax season, zero lost messages confirmed by item counts, and a rollback that is one DNS change until WorkMail is retired.

What I would measure

  1. Completeness: item counts match for every mailbox before WorkMail is retired.
  2. Deliverability: no bounces and no spam placement in the first week after cutover.
  3. User impact: every user confirms mail, calendar and contacts in the post-cutover checklist.

What comes next

With the move done, a short security baseline on the new suite: multi-factor sign-in for every user and a review of mail forwarding rules.