WorkMail is shutting down.
Move to email you own.
AWS is retiring Amazon WorkMail — no new customers since April 30, 2026, and full shutdown on March 31, 2027. You liked having your email in AWS. MailPoppy keeps it there — but in an account you fully own, with no per-seat fee and no vendor who can switch it off.
Import your mailboxes over IMAP · Keep your folders and history
What's happening, and when
No new customers
Amazon WorkMail stopped accepting new sign-ups. Existing customers can keep using it — for now.
Full shutdown
Access to the WorkMail console and all resources ends. Emails, contacts and calendars become inaccessible.
Migrate out
AWS recommends moving to another solution. The earlier you start, the calmer the cut-over.
Dates per Amazon's WorkMail end-of-support announcement. After the shutdown, AWS has not announced any post-shutdown data recovery — so export or migrate your mail before March 31, 2027.
Keep what you liked. Drop what you didn't.
WorkMail's appeal was email inside AWS. Its problem turned out to be that it was someone else's product to discontinue. MailPoppy gives you the first without the second.
Still in AWS — but yours
The whole email service deploys into your own AWS account. Same cloud you already trust, except now you hold the keys and no vendor can retire it out from under you.
No per-seat fee
WorkMail billed per user. MailPoppy doesn't — you pay AWS usage directly, typically a few dollars a month for a whole domain, with unlimited mailboxes.
Private by architecture
No MailPoppy server sits in the path of your mail. We can't read it, scan it or hand it over — and because the engine is open source, you can verify that.
One-click in, one-click out
The desktop app deploys the entire backend for you and tears it all down just as easily. Your domain and data stay portable — no second lock-in.
The email-in-AWS idea, without the sunset
| Amazon WorkMail | MailPoppy | |
|---|---|---|
| Future | Shutting down March 31, 2027 | Yours to keep — no vendor sunset |
| Where it runs | AWS, managed by Amazon | Your own AWS account, owned by you |
| Pricing | Per user, per month | AWS usage — no per-seat fee |
| Who can read it | The provider | Only you |
| Leaving | Forced migration by 2027 | One-click teardown, anytime |
| Verifiable privacy | Closed | Open-source engine |
A few honest things to know
We'd rather you switch with clear eyes than be disappointed later. MailPoppy is the right move if email ownership is what you're after — but it isn't a like-for-like WorkMail clone:
- It's email-focused today — calendar and contacts aren't included.
- You read mail in MailPoppy's own webmail and iPhone/Android apps; standard Outlook/IMAP client support is on the roadmap, not shipped yet.
- A brand-new sending domain can land in spam for a week or two while reputation builds — that's normal and improves on its own.
- MailPoppy can't create your AWS account for you (AWS needs your own email and card), but the app guides every step.
Three steps to email you own
The desktop app walks you through each step. Most of the work is automated — and your credentials never leave your computer.
Deploy MailPoppy in your AWS
Install the desktop app, connect your AWS account once, and it builds the whole email backend in your account.
Recreate your mailboxes
Add your addresses on your domain in seconds, then import your existing WorkMail mail over IMAP — folders and history intact.
Cut over your domain
Point your domain's mail records to your new MailPoppy setup, and you're sending and receiving from infrastructure you own.
Full instructions, including the IMAP import details: Read the migration guide →
Questions, answered
Is AWS WorkMail really shutting down?
Yes. AWS has announced the end of support for Amazon WorkMail. New customers could no longer sign up after April 30, 2026, and after March 31, 2027 the WorkMail console and all WorkMail resources — including emails, contacts and calendars — become inaccessible. AWS recommends existing customers migrate to a third-party solution before then.
When do I need to migrate by?
Before March 31, 2027 — but sooner is safer. Migrations involving many mailboxes take time to plan, pilot and cut over, and leaving it until early 2027 risks a rushed move. Starting now means you switch on your own schedule, not under deadline pressure.
Why is MailPoppy a natural fit for WorkMail users?
You already chose to run your email inside AWS — that was the whole point of WorkMail. MailPoppy keeps that, but in an account you fully own and control: the entire email service is deployed into your own AWS, no vendor sits in the path of your mail, and there is no per-seat fee. It's the same 'email in AWS' idea, without the vendor who just walked away from it.
Can I bring my existing email and folders across?
Yes. MailPoppy imports your existing mailboxes over IMAP, preserving your folders and history, so you keep your mail when you switch. See the migration guide for the step-by-step.
Does MailPoppy include calendar and contacts like WorkMail did?
Not today — and we'd rather be upfront than surprise you. MailPoppy is focused on email: mailboxes on your domain, a webmail client, and native iPhone and Android apps. If calendar and contacts are essential to your team, factor that into your migration plan.
Can I keep using Outlook?
Today you read and send mail in MailPoppy's own webmail and mobile apps rather than a third-party desktop client. Standard IMAP/SMTP client support (so you could use Outlook or Apple Mail) is on the roadmap, not available yet — so if Outlook is a hard requirement right now, it's worth knowing before you switch.
What will it cost compared to WorkMail?
WorkMail charged per user, per month. MailPoppy has no per-seat fee — because the service runs in your own AWS account, you pay AWS directly for usage, which is typically a few dollars a month for a whole domain regardless of how many mailboxes you create. MailPoppy's own app pricing is coming soon.
Is my email private with MailPoppy?
Yes. Every message lives only inside your own AWS account — MailPoppy operates no servers that receive, store or read your mail. And the engine that runs it is open source, so that privacy is something you can verify, not just take on trust.
Don't wait for the shutdown.
Move your email to an account you own — same AWS, no per-seat bill, no vendor who can turn it off. Start on your own schedule, well before March 2027.
Open MailPoppy