Switching From Spark Mail to Another Email Client: What Moves and What Doesn't

The reassuring part of how to switch from Spark Mail to another email client is that your mailbox is not really Spark's to move. Spark is a front end over Gmail, Outlook, iCloud, Yahoo or any IMAP account, and Readdle's privacy notes say email is mainly processed on your device. Leaving is an account re-connect, not a mailbox migration.

What is genuinely at risk sits above that line: Team Comments, shared drafts, link-shared threads, the send-later queue, meeting notes and AI summaries all live in Spark's systems. Some exports, most does not, and team data disappears the moment the team owner deletes the workspace.

One disclosure so the recommendation later reads honestly: we build AI Emaily, which is one place Spark refugees land. This guide is about the mechanics of moving.

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

The mailbox itself is not moving because Spark never held it. Your messages, folders, labels and address live with Google, Microsoft, Apple, Yahoo or your IMAP host, and the next client you sign in with sees exactly the same server state Spark did. That is why there is no export file to download for the mail and no forwarding window to set up.

The Spark layer is a different story. It is where team collaboration, scheduled sends, saved link-share URLs and AI outputs live, and only the Spark app can display them. Everything in the right column below has to be copied out by hand while the seat is still active.

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

Do this before you disconnect anything. Every item below is either impossible to recover after the seat ends, or dramatically harder if you wait for the team owner to delete the workspace first.

• Team Comments on live threads: paste the ones you still refer to into your team's real notes tool. Comments are not indexed by Gmail search and appear nowhere outside Spark.
• Shared drafts in flight: send, save or copy the body of any shared draft. They do not sync back to Gmail Drafts because they were never in Gmail Drafts.
• Send Later queue: open the Outbox and either send now, reschedule inside the new client, or copy the bodies out. Anything left in Spark's queue never lands if the account expires.
• Link-shared thread URLs: list the public links you have shared externally. They point at Readdle's servers and break when the link or account is deleted.
• Meeting notes and AI summaries: copy any that matter — Readdle keeps these until account deletion and only Spark renders them.
• Signatures, per account: copy the HTML for each connected address. A fresh client shows the provider default, not your Spark signature.
• Snoozes, priority senders and custom swipes: screenshot them. All three are Spark-side and will not carry over — plan to rebuild the ones you actually still use.

Steps: how to switch from Spark Mail to another email client#

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

1. 1

   Pick the destination and install it

   Choose the client, install it, and confirm it supports every account type you connect to Spark today — Gmail, Microsoft 365, iCloud, Yahoo and IMAP. If any of those is missing you will discover it now rather than mid-migration.

2. 2

   Add your accounts using Sign in with Google or Microsoft

   Prefer OAuth (Sign in with Google, Sign in with Microsoft) over IMAP with app passwords where the new client supports it. It is what Google now recommends and it avoids re-doing account settings later.

3. 3

   Let the initial sync finish before you judge anything

   Full-history sync over IMAP or the Gmail API can take hours on a large mailbox. Give it that time before deciding a label is missing or a folder tree looks wrong.

4. 4

   Rebuild the Spark-side settings you copied out

   Paste each signature back per account. Re-create the highest-value comments as saved notes, rewrite critical snoozes in the new client, and set up VIP or priority-sender equivalents. This is the boring hour, and it is unavoidable.

5. 5

   Warn anyone still using your Spark link-shares

   Message the external recipients of any shared-link threads and send them the content another way. Those URLs 404 the moment the account goes.

6. 6

   Run both clients for a week before you disconnect

   Two clients on one Gmail or Outlook mailbox is safe — the provider is the source of truth and either app writes back to it. Use the week to catch what you missed.

7. 7

   Disconnect Spark, then cancel

   In Spark, sign out of each account first, then delete the Spark account and cancel the subscription. Team owners: delete the team last — after every member has copied out what they need.

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

Most of what stops working after a Spark exit is the collaboration and scheduling 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 Spark never held the mail, rollback is short. Reinstall, sign back in with the same OAuth accounts and the mailbox reappears — messages, folders, threads, everything the provider stores. That part is essentially free.

The parts that are gone are the ones you did not copy out. Team Comments and shared drafts are irretrievable if the team was deleted. Queued Send Later items never sent. Public link-share URLs cannot be reissued at the same address. This is why the pre-migration checklist matters more than the migration itself.

Doing it without downtime#

There is no downtime because there is no cutover. Gmail, Outlook and iCloud can be signed in on multiple clients at once — the provider is authoritative and each client writes back to it, so Read/Unread, archive and label changes propagate between Spark and the new client while both are connected.

Run the two side-by-side for a week. Do real work in the new client, keep Spark installed as a fallback for the Spark-only surfaces (comments, shared drafts, saved link-shares). When nothing has forced you back to Spark for a full week, disconnect it. That is the whole cutover, and no message is ever in flight during it.

A faster place to land if collaboration is not the reason you're leaving#

If you are leaving Spark because you want an assistant that drafts and files rather than a client you drive by hand, we build AI Emaily. It sits over Gmail, Outlook and IMAP the same way Spark does, so the disconnect-and-reconnect above is the whole migration on our side too. The difference is what the layer does: an approve-before-send agent that drafts in a Personal Context brain you set (never scraped from your sent mail), a rules brain that files as you would, and an audit trail with undo on every action. There is a 7-day free trial on Pro or Autopilot, card on file, $0 if you cancel before day 7.

Honest concession: Spark's Team Comments — a private chat thread bolted onto any incoming email, inside the client — is a workflow we do not replicate. We ship shared inbox, delegation and assignment, which is a different shape. If your team's rhythm is chatting on threads without leaving the mail client, Spark is doing something for you that we would not replace like-for-like.