Switching From Shortwave to Another AI Email Client

Shortwave is a Gmail client, not a mail store, so the reassuring part of how to switch from Shortwave to another email client is that your inbox is not really Shortwave's to move. Your messages, threads, labels and address live at Google, and any client you sign in with next sees the same server state Shortwave did. The mailbox is untouched by the leaving.

The uncomfortable part is that the layer above the mailbox is where most of the daily value sits. Bundle rules, saved AI instructions, custom AI-powered filters written in plain English, search history and any scheduled or pinned items live in Shortwave's systems, and none of them ride across to a new client on their own.

One disclosure so the recommendation later in the piece reads honestly: we build AI Emaily, which is one of the places Shortwave leavers land — especially when the trigger for leaving is adding an Outlook or IMAP account. This guide is about the mechanics of getting out cleanly, whichever client you land on next.

What actually moves when you leave Shortwave, and what doesn't#

The mailbox is not moving because Shortwave never held it. Google is the source of truth for the messages, the labels, the archive and the address, and every Gmail-capable client sees the same state on connect. That is why there is no mail-export step in this guide and no forwarding window to configure. If you have used Shortwave's unified-inbox workaround — pointing Yahoo, iCloud, Fastmail or Zoho at your Gmail via forwarding plus Send mail as — Gmail keeps the forwarding rule and the send-as identity too, because both live in Gmail settings rather than in Shortwave.

The Shortwave layer is where the real copy-out work is. It is the layer that made Shortwave feel like Shortwave rather than a generic Gmail client, and the moment the seat lapses, only Google's own bare surfaces remain.

Pre-migration checklist: what to save before you cancel#

Do all of this before you disconnect the account. Every item below is either impossible to recover after the seat ends, or dramatically harder if you wait until the workspace owner has deleted the team.

• Bundle rules: list every custom bundle you rely on, with a sentence describing what belongs in it. Shortwave has no bundle-export file — a screenshot of the bundle list is enough to rebuild the equivalent in another client's rule or label system.
• Custom AI filters (plain-English scripts): open each one, copy the natural-language rule text into a note, and save the intent alongside. Any client with an AI rule system can be pointed at the same intent; without the text you are rewriting from memory.
• Saved AI instructions and pinned prompts: paste them into your notes tool. Voice and writing preferences are re-usable across clients if you have the wording; without it, you rebuild by trial and error.
• Scheduled sends: open the outbox and either send now, cancel, or copy the body plus intended send time. Anything left in the queue when Shortwave loses your account never lands.
• Search history and saved searches: screenshot the searches you re-run often. The underlying mail is still in Gmail — you are saving the query strings, not the results.
• Team space: private comments on threads, assignments, and shared drafts belong to the workspace and vanish when the workspace is deleted. Copy any active comment thread into a shared doc before the owner shuts things down.
• Read receipts you have relied on: Shortwave's receipts are stored per account. Historical open data will not be visible from another client, so pull anything you need for a live deal now.
• Unified-inbox forwarding rules: if you routed Yahoo, iCloud, Fastmail or Zoho into Gmail via forwarding plus Send mail as, verify those rules in the source accounts' settings and in Gmail's Accounts and Import tab. They live outside Shortwave and will keep working, but this is the last cheap moment to audit them.

Steps: how to switch from Shortwave to another email client#

The order matters. Set up the new client and prove it works before you touch anything on the Shortwave side, so a mistake in step five does not leave you between two half-configured inboxes.

1. 1

   Pick the destination and confirm it covers your accounts

   If you were on Shortwave, at least one of your accounts is Gmail — that part is easy. Check the new client against every other account you plan to add. If you have been on Shortwave despite needing Outlook or Microsoft 365, that is the constraint the new client needs to solve, since Shortwave only supports Google sign-in and reaches other providers by forwarding into a Gmail account.

2. 2

   Sign in with Google (and any other provider) using OAuth

   Use Sign in with Google, Sign in with Microsoft, or the provider's OAuth flow where offered. It is what Google now recommends over app passwords, and it avoids re-doing the account setup later. Shortwave's own migration path is the same shape — connect the account, let it index.

3. 3

   Let the initial sync finish before judging anything

   Full-history sync over the Gmail API can take hours on a large mailbox, and semantic search or AI features often index in a separate pass afterwards. Give it that time before deciding a label is missing or search is worse.

4. 4

   Rebuild the layer you copied out

   Recreate the top few bundles as labels, rules or the new client's smart categories. Point AI filters at the same natural-language intents. Paste saved AI instructions into the new client's voice or context settings. This is the boring hour, and it is unavoidable.

5. 5

   Warn anyone relying on Shortwave-only surfaces

   If your team used private comments or assignments inside Shortwave, tell them the workflow is changing before you disconnect. If external recipients depended on Shortwave's read receipts as part of a deal cadence, expect that signal to end.

6. 6

   Run both clients on the same Gmail for a week

   Two clients on one Gmail mailbox is safe — Google is authoritative and either app writes back to it, so read/unread, archive and label changes propagate between Shortwave and the new client in near real time. Use the week to catch the settings you forgot.

7. 7

   Disconnect Shortwave, then cancel

   In Shortwave, sign out of each account. Then open your Google Account, go to Security, then Third-party apps with account access (or Data and privacy, then Apps you have connected), find Shortwave and revoke access. That is what actually invalidates the OAuth token on Google's side. Cancel the subscription last. Workspace owners: delete the workspace only after every member has copied what they need.

What breaks in the move, and how to replace it#

Most of what stops working after a Shortwave exit is the intelligence layer, not the email. The table below is a copy-out job list — go through it row by row before you disconnect.

Rollback plan: what to do if the new client isn't right#

Because Shortwave never held the mail, rollback to Shortwave is short. Reinstall, sign back in with the same Google account and the mailbox reappears — messages, threads and labels intact. The parts that are gone are the ones you did not copy out: any scheduled sends that failed to land during the gap, any workspace data that was deleted with the team, any read-receipt history from mail sent through the new client.

This is why the pre-migration checklist matters more than the migration itself. The mailbox always rolls back for free; the layer you built on top of it does not.

Doing it without downtime#

There is no downtime because there is no cutover. Gmail can be signed in on Shortwave and a new client simultaneously — Google is authoritative and each client writes back to it, so read/unread, archive and label changes propagate between them within seconds of the underlying sync. No message is ever in flight during the switch.

Run the two side-by-side for a week. Do real work in the new client. Keep Shortwave installed as a fallback for the Shortwave-only surfaces — bundle behaviour, custom AI filters, saved instructions, search history. When nothing has forced you back to Shortwave for a full week, revoke the OAuth token in Google and cancel the subscription. That is the whole cutover.

If the reason you're leaving is that Shortwave is Gmail-only#

The most common trigger for this switch is adding a mailbox Shortwave cannot cover natively. Per Shortwave's own docs, sign-in requires a Gmail or Google Workspace account; Microsoft 365 and Exchange are not supported, and Yahoo, iCloud, Fastmail and Zoho are reachable only by forwarding into your Gmail with Send mail as configured. If your work has moved to Outlook, or you are consolidating a personal iCloud and a work Google account into one triage view, the forwarding workaround stops being enough.

That is the situation we built AI Emaily for. It connects to Gmail, Microsoft 365 and Outlook.com, and IMAP providers directly, so the two mailboxes sit in one inbox with the same triage rules over both. On top of the unified inbox there is an approve-before-send agent that drafts and files, a Personal Context brain you set for voice and preferences (not scraped from your sent mail), and an audit trail with undo on every action. Try it on a 7-day free trial of Pro or Autopilot — card on file, $0 if you cancel before day 7. We build AI Emaily.

Honest concession: Shortwave has built harder on Gmail-native semantic search than we have, and the team came out of Google. If you live entirely in Gmail and your workflow is finding threads inside a long archive rather than triaging across providers, Shortwave's search is a genuine reason to stay. Where a Shortwave user usually leaves is not search — it is the moment the second mailbox arrives.