Moving Email Templates and Snippets to a New Client

You built a folder of go-to replies over years — the pricing-objection response, the password-reset instructions, the outreach follow-up that actually gets answered. Then you switch email clients, and none of it comes with you. Gmail's templates live on Google's servers. Superhuman's snippets live in Superhuman's own database. Classic Outlook's Quick Parts live in a template file on your hard drive.

None of these formats talk to each other, and none of them export as a portable file you can drag into a new app. That's not a bug — canned-response features were built as account settings, not as data you own in a transferable shape. Moving them takes a real, short project: find where each one is actually stored, decide which ones deserve to survive, and rebuild them — ideally as something more durable than frozen text.

What actually moves and what doesn't#

Start with where things live, because “export” means something different for every product on this list.

Frozen text vs. a drafting instruction#

There's a second decision hiding in this move, and it matters more than “copy the old text into the new box.” A canned response frozen at the sentence level goes stale — it still quotes last year's support hours, or links to a pricing page that moved. A drafting instruction describes what the reply should do, so it stays accurate longer.

The second version below survives the next time support hours change, because it describes the shape of the reply instead of freezing today's facts inside it. It's more work to write once, and less work every time after.

Pre-migration checklist#

Do this before you touch the new client's settings.

• List every template and snippet you've actually used in the last 90 days — not the ones you set up once and forgot
• Copy the raw text of each into one plain document, client by client, so nothing depends on a subscription you're about to cancel
• Note which ones include a variable — a name, a date, a ticket number — since syntax rarely matches between tools
• Flag anything with legal or compliance language, like a confidentiality footer or a refund-policy line, for a rewrite rather than a straight copy
• Check who else relies on a shared template — a team snippet in Superhuman or Outlook may belong to more than just you
• Note how each template currently renders — bold, bullets, an inline image — so you can tell later whether formatting broke in the move or was already inconsistent

Steps#

Once the checklist is done, the move itself is short.

1. 1

   Sort into two piles

   “Reuse as-is” versus “needs a rewrite.” Anything with a date, a price or a policy line in it belongs in the second pile regardless of how well it's worded.

2. 2

   Recreate the keepers first

   Use the new client's own feature — Gmail's Templates panel, Outlook's Quick Parts gallery, or a snippet manager's editor. Paste, then reformat; rich text from one product rarely survives a straight paste into another, so check the result in an actual draft, not just the editor preview.

3. 3

   Rewrite the rest as instructions

   Apply the frozen-text-vs-instruction split above. This is the slower half of the job, and the one that pays off the longest — a template that was already going stale in the old client will keep going stale in the new one if you copy it unchanged.

4. 4

   Test every variable

   Send yourself one message using each template that includes a placeholder. A silently broken {{first_name}} tag is worse than a snippet you had to type by hand.

5. 5

   Tell your team where things moved

   If a snippet was shared, a shared inbox or delegated account needs the new location pointed out — nobody finds a renamed folder on their own.

6. 6

   Retire the old copies last

   Don't delete anything in the old client until you've used its replacement in a real conversation, not a test one.

What breaks#

A few things don't survive the move no matter how carefully you do it.

Rollback plan#

Keep the old client installed and signed in for at least two weeks after the move. Deleting an account the day you finish is the single most common mistake in this process — if a rebuilt template turns out to be missing context, wrong, or worse than the original, you want the source text within reach, not gone.

Set a concrete bar before you call a rebuilt template done: it has to survive one real send to an actual recipient, not a test message to yourself. A rewritten instruction can read fine in isolation and still produce something you wouldn't have sent — that only shows up once someone else is reading it.

Keep the plain-text export from the checklist step permanently, even after the old client is gone. It costs nothing to store and it's the fastest way to recover a snippet nobody remembers writing.

Doing it without downtime#

You don't have to freeze all outbound email while you rebuild. Move the highest-volume templates first — the ones you send daily — and leave rarer ones in the old client until you get to them. A snippet you use twice a year can wait a month without costing you anything.

Run both clients side by side for the first week if the new one allows a second account. Send from the new templates when you remember to, fall back to the old ones when you don't, and let actual usage tell you which ones needed the rebuild most.

Where AI Emaily fits in#

Everything above is manual because canned responses were built as frozen text, not as instructions. AI Emaily's reply templates work differently: you set drafting guidance once — tone, structure, the boilerplate you always include — in a user-set Personal Context brain and per-client profiles, and the agent writes a fresh reply that follows it instead of pasting a stale paragraph. You still approve or edit before anything sends.

If pure snippet portability is genuinely the only thing you care about, a dedicated text expander like TextExpander is honestly the better fit for that one job — it lives outside any single mail client by design, which is exactly the property this guide has been chasing. AI Emaily solves the adjacent problem instead: reply templates live inside your account rather than inside whichever mailbox you've connected, so a future move between Gmail, Outlook and IMAP doesn't reset your drafting guidance, and each reply adapts to the message instead of repeating the same block. We build AI Emaily.