Switching From Superhuman Mail: What to Expect and How to Move

If you have already decided to leave Superhuman Mail, the operational question is smaller than it looks. Superhuman is a client on top of Gmail or Outlook, not a mail host. Your mail, your address and your archive belong to your provider, so no export file, no forwarding window and no MX record change stand between you and the new app.

What you do have to do is copy out everything Superhuman kept on its side of that line — snippets, splits, reminders, team comments, scheduled sends, signature — before the seat lapses. This post walks the sequence in order: what moves, the pre-switch audit, the steps, what breaks, the rollback, and how to run both clients in parallel so the switch never blocks a working day.

Full disclosure: we build AI Emaily, one of the clients people land on after Superhuman, and the destination named later in this post. The mechanics below apply whether you land with us, Shortwave, Mimestream, Apple Mail or plain Gmail — the audit is the same, and copying it out is what actually protects you.

What actually moves, and what does not#

The reassuring half first. Superhuman Mail authenticates to Google or Microsoft over OAuth and reads a mailbox those providers already hold. Its own help centre describes your inbox as stored on your machine rather than on Superhuman's servers, and cancelling a subscription is a disconnect from that OAuth grant — not a deletion of any mail.

The risky half sits above the mailbox. Anything that was Superhuman's product — the snippet library, split queries, Remind Me schedule, team comments, read statuses — never became part of the message or the mailbox. Once access ends, it is out of reach, and there is no export button that walks you out with all of it packaged.

The pre-migration checklist#

Do this in a single 30-minute sitting while Superhuman is still open and your subscription is still active. None of it is recoverable after access ends, and doing it under pressure on cancellation day is where people lose snippets they wrote years ago.

• Paste every snippet — private and any Team Snippets you own — into one document, including the shortcut name. Superhuman's help centre states snippets cannot be transferred between accounts, and it documents no bulk export as of August 2026.
• For each Split Inbox split, copy the underlying search query verbatim. A split is a saved query, so the string is the whole thing — it becomes a Gmail filter, an Outlook rule or a saved view in the new client.
• Open the Reminders view and list every pending Remind Me and auto follow-up, with its date and the recipient it chases. Decide which need to survive the switch and which can quietly expire.
• Scan the Send Later queue. Per message, decide: let it fire before cancellation, or reschedule it in Gmail or Outlook's own delayed-send tools. Anything left in Superhuman when the seat ends does not send from the new client.
• For any thread where the real decision lives in a team comment rather than in the message body, copy that context out. Comments were never delivered to external recipients and never became part of the mail, so Gmail does not have them.
• Copy your signature block — the HTML, not just how it looks — since Superhuman stores it in its own settings, not in Gmail's signature field.
• Note your read-status habits honestly. If you time follow-ups off whether the recipient opened the mail, confirm the destination client offers something equivalent before you commit.
• Screenshot your keyboard shortcut cheat sheet if you have customised bindings. You will want it as reference while you retrain in the new client.

The migration steps#

Once the audit is done, the actual switch is short. Neither Gmail nor Outlook needs to migrate anything — you are just adding a second OAuth grant to a mailbox that already exists.

1. 1

   Name the reason you are leaving

   Cost after the Grammarly acquisition, wanting the AI to do more than draft, needing IMAP or an Outlook.com account Superhuman does not cover, or a team consolidation. The reason picks the destination — and it is the honest answer to whether you should leave at all.

2. 2

   Run the pre-switch audit above

   Snippets, splits, reminders, scheduled sends, comments, signature. This is the one non-reversible part of the whole process, so it comes before every other step.

3. 3

   Connect the new client alongside Superhuman

   Add the same Gmail, Google Workspace or Microsoft 365 account in the new client using its normal OAuth or IMAP setup. Both clients hold the same mailbox at once — nothing duplicates, nothing moves, nothing is deleted.

4. 4

   Rebuild the layer, minimally

   Snippets become templates or reply blocks. Splits become filters, saved searches or views. Pending reminders become follow-up tasks in whatever the new client offers. Rebuild what you used last month, not every artifact you ever created — most of what accumulates never gets used again.

5. 5

   Run both clients in parallel for at least one week

   Work in the new client, keep Superhuman open as the safety net. A week covers a Monday backlog and a Friday scramble; a weekend does not. If a Superhuman feature you thought was optional turns out to be load-bearing, this is when you discover it — while both clients still work.

6. 6

   Cancel, then revoke the OAuth grant

   Cancel the subscription in Superhuman's Subscription page. Then, separately, go to your Google Account security settings or your Microsoft account and remove Superhuman from the list of connected apps. Ending billing and revoking a mailbox connection are two distinct actions.

What breaks during the switch#

Almost all of the breakage sits in the Superhuman-side layer, not in the mailbox. This table is the full list of items that either need to be rebuilt manually or degrade the moment the seat ends — read it before you cancel, not after.

The rollback plan#

Rollback is the quiet advantage of any client that sits on your provider's mailbox — nothing you did in the new app touched a message, so reverting means resubscribing and reconnecting. As long as the audit was done and the parallel run was long enough, the risk of leaving is contained.

Where rollback is genuinely hard is in the Superhuman layer you did not copy out. Snippets you never pasted into a document are gone. Splits whose queries you never wrote down are gone. Everything else — messages, drafts, sent mail, calendar, contacts — sits with Google or Microsoft, unchanged.

If you decide the new client is not working, the sequence is short: resubscribe to Superhuman, reconnect the OAuth grant, and rebuild any snippets or splits you had saved locally. You will not get read-status history or team-comment threads back, but you never lost the mail.

The Grammarly acquisition and the Superhuman Suite rebrand do not change this. Superhuman Mail is still shipping as the client you left, and the same rollback path applies. Verify the current cancellation and re-subscription flow on Superhuman's own help centre — that surface changed hands and third-party guides age fast.

Doing it without downtime#

Because the mailbox never moves, downtime is a choice, not a constraint. The trick is running both clients on the same account for long enough to catch anything the audit missed.

• Connect the new client on the same mailbox first. Both OAuth grants coexist. No mail duplicates, no folder gets confused.
• Set the new client as the default handler for mailto links on your desktop and phone once you trust it — usually within two or three days of parallel use.
• Migrate one persona at a time if you run several mailboxes through Superhuman. Move your primary account first; add secondaries only after the first is stable.
• Rebuild only what you actually used last month. A snippet library grows like an attic; most of it is not load-bearing, and rebuilding all of it is what makes people give up on the switch.
• Warn any teammates before removing shared team access. Team Comments and Team Snippets end for everyone the moment an admin removes the seat, and quietly disappearing snippets nobody copied out is a preventable outage.
• Keep Superhuman as the fallback for a full seven days. If you are on an annual plan mid-term, the paid tail is free parallel-run time — cancel toward the end of the period, not the day you connect the new client.

Why AI Emaily, specifically, if you land with us#

We build AI Emaily, and this is the paragraph that names it — one place, at the end, where the reader has already worked through the switch. If you are leaving Superhuman because you want the assistant to do more than draft, and you keep at least some mail on Outlook, IMAP or a custom domain that Superhuman Mail does not open, we are one of the honest landing spots.

Three things distinguish us structurally, not by feature-list length. Authority is set per account: Manual is a plain fast client, Copilot triages, files and drafts while nothing sends without approval, and Autopilot is gated with an undo window and a per-action audit log. Provider coverage spans Gmail, Google Workspace, Microsoft 365, Outlook.com and standard IMAP in one inbox. Drafting voice comes from a user-set Personal Context brain plus per-client profiles — we do not train models on your mail, and model providers run under zero-retention terms.

We ship a 7-day free trial on Pro and Autopilot — card required, $0 if you cancel before day seven — with real downloadable desktop apps for Apple Silicon Macs and Windows, a native iOS app, and a PWA on Android. The limits, plainly: the Mac and Windows apps are an Electron shell around the web app rather than native binaries, so a native client like Mimestream beats us on memory footprint and OS-level integration; there is no Linux build, no Intel Mac build, and no watchOS app; and on raw keyboard throughput and shortcut depth, Superhuman is still ahead of us and we will not pretend otherwise.