Every WorkMail Alternative, Compared

AWS WorkMail shuts down March 2027. We compared Google Workspace, Microsoft 365, Zoho, Fastmail, self-hosted, and inbox.camp — with honest pros, cons, and pricing for each.

The clock is ticking

AWS WorkMail shuts down March 31, 2027. No new organizations can be created after April 30, 2026. If you haven't started evaluating alternatives, now's the time.

I've spent the last six months building inbox.camp — a WorkMail replacement that runs on your own AWS. Along the way, I deeply researched every alternative on the market. Here's what I found, with honest pros and cons for each.

The quick comparison

ProviderPriceYour Data Lives OnIMAP/SMTPMigration Effort
Google Workspace$7.20/user/moGoogle's cloudYesMedium
Microsoft 365$6/user/moMicrosoft's cloudYesMedium
Zoho Mail$1–3/user/moZoho's cloudPaid tiers onlyMedium
Fastmail$5/user/moFastmail (US)YesLow
Self-hosted~$20–50/mo infraYour serverYesHigh
inbox.camp$4/user/moYour AWS accountYesLow (automated)

Google Workspace

The obvious choice — and exactly why you should think twice.

Google Workspace Business Starter costs $7.20/user/month and includes Gmail, Drive, Meet, Docs, and the rest of the suite. For teams already living in Google's ecosystem, it's compelling. For teams that just need email, you're paying for a productivity suite you won't use.

The good: Rock-solid infrastructure, excellent spam filtering, 15+ years of polish. Gmail's web interface is fast and familiar. Enterprise-grade security with 2FA, admin controls, and data loss prevention.

The not-so-good: Your email data leaves AWS entirely. Google controls your data residency, encryption keys, and pricing. They've raised prices before and will again. No "email only" tier — you're subsidizing Drive and Meet whether you want them or not.

Migration from WorkMail: Google provides a data migration tool that supports IMAP import. Expect a few hours for DNS cutover and a day or two for historical email sync. You'll need to reconfigure every user's email client.

Verdict: Choose Google if your team already lives in the Google ecosystem. Skip it if you chose WorkMail because you wanted infrastructure control. (We wrote a detailed cost comparison if you want the numbers.)

Microsoft 365

The enterprise default. If your company already runs Active Directory or uses Outlook heavily, this is the path of least resistance.

Microsoft 365 Business Basic costs $6/user/month and includes Exchange Online, OneDrive (1 TB), Teams, and web Office apps. Business Standard at $12.50/user adds desktop Office.

The good: Exchange is the gold standard for corporate email. Native Outlook integration is seamless. Teams + SharePoint + OneDrive is a strong bundle for larger orgs. Compliance tools — litigation hold, eDiscovery, DLP — are built in at higher tiers.

The not-so-good: Microsoft's licensing is infamously complex. The admin portal has layers upon layers. Your data moves to Microsoft's datacenters. And like Google, there's no email-only tier.

Migration from WorkMail: Microsoft offers IMAP migration tools and third-party services like BitTitan can automate the process. Budget $5–15/user for migration tooling, plus IT time for DNS and client reconfiguration.

Verdict: Choose Microsoft if you're already in the Microsoft ecosystem or need enterprise compliance features like eDiscovery. Skip it if you value simplicity or want to keep data on AWS.

Zoho Mail

The budget option that AWS actually recommends.

Zoho Mail starts at $1/user/month (Mail Lite) and goes up to $3/user/month (Mail Premium). AWS listed Zoho as one of their recommended alternatives when they announced the WorkMail shutdown.

The good: Affordable. Clean interface. Decent feature set including calendar, contacts, and tasks. Ad-free even on the free tier.

The not-so-good: Less mature than Google or Microsoft. Spam filtering isn't as sophisticated. IMAP is restricted on the cheapest tier. Smaller ecosystem means fewer integrations. Your data moves to Zoho's infrastructure.

Migration from WorkMail: Zoho has an email migration wizard that supports IMAP. It works, but isn't as polished as Google's or Microsoft's tooling. Manual DNS configuration required.

Verdict: Choose Zoho if budget is the primary concern and you don't need tight integration with other tools. Skip it if you need enterprise polish or want data on your own infrastructure.

Fastmail

The privacy-focused indie alternative.

Fastmail costs $5/user/month (Standard) or $3/user for the basic tier. Australian company, strong reputation for privacy and standards compliance.

The good: Fast, clean interface. Excellent IMAP and JMAP support. Strong privacy stance — no ad tracking, no data mining. Good calendar and contacts. Custom domain support with solid documentation.

The not-so-good: No enterprise compliance features (eDiscovery, litigation hold, DLP). Limited admin controls compared to Google/Microsoft. Data lives on Fastmail's servers in the US. Smaller company — some enterprise teams see that as a risk.

Migration from WorkMail: Fastmail supports IMAP import with good documentation. Straightforward but manual. DNS docs are clear.

Verdict: Choose Fastmail if you want a clean, fast email experience and care about privacy. Great for small teams who don't need enterprise features. Skip it if your data needs to stay on your infrastructure.

Self-hosted (Mailu, Mail-in-a-Box, Stalwart)

The DIY route. Full control, full responsibility.

Open-source email servers like Mailu, Mail-in-a-Box, and Stalwart let you run your own mail infrastructure. You can deploy them on an EC2 instance in your AWS account, keeping everything on your own servers.

The good: Complete control. No per-user fees — just infrastructure costs. Your data stays exactly where you put it. Open source means you can audit the code.

The not-so-good: You're responsible for everything — security patches, spam filtering, deliverability, backups, monitoring, SSL certificates, IP reputation. Email is one of the hardest services to self-host reliably. Major providers are increasingly hostile to small mail servers. You will spend hours debugging why Gmail is rejecting your emails.

Migration from WorkMail: Entirely manual. IMAP sync your mail, reconfigure DNS, set up users, configure authentication records, warm up your IP. Budget days, not hours.

Verdict: Choose self-hosted if you have dedicated sysadmin time and strong opinions about infrastructure. Skip it if your team doesn't have the expertise or patience to maintain a mail server. Most teams that try self-hosting eventually migrate to a managed solution.

inbox.camp

Full disclosure: I'm building this one. But here's the honest case.

inbox.camp costs $4/user/month and runs entirely on your AWS account. We deploy via a CloudFormation stack, use your SES for sending/receiving, your S3 for storage, and your Route 53 for DNS. We provide the web UI, IMAP/SMTP access, user management, and auto-configuration.

The good: Your email data never leaves your AWS account. Same price WorkMail was. Auto-detects your WorkMail organizations and migrates users, domains, and DNS in under 10 minutes. Full IMAP/SMTP — use any email client. Revoke access instantly by deleting the IAM role.

The not-so-good: We're launching Summer 2026 — not available yet. No productivity suite (no Drive, no Docs, no Teams). Requires an AWS account. We're a small company — if that makes you nervous, Google and Microsoft aren't going anywhere.

Migration from WorkMail: Automated. Connect your AWS account, we detect your WorkMail setup, import users, and cut over DNS. Under 10 minutes. (See our step-by-step migration guide.)

Verdict: Choose inbox.camp if you want to keep email on AWS without the complexity of self-hosting. Join the waitlist — we're launching well ahead of the March 2027 deadline.

So which one should you pick?

It depends on what matters most:

  • Already using Google or Microsoft tools daily? Stay in that ecosystem. The integration is worth the premium.
  • Budget is the top priority? Zoho at $1–3/user is hard to beat on price alone.
  • Want the cleanest email experience? Fastmail punches above its weight.
  • Have sysadmin chops and strong opinions? Self-hosted gives you total control — and total responsibility.
  • Chose AWS for a reason and want to stay? That's exactly why we're building inbox.camp.

Whatever you choose, don't wait until February 2027. Email migrations take longer than you think, and the April 2026 cutoff for new WorkMail organizations means your options are already narrowing.

Get on the inbox.camp waitlist and stay on AWS.