Switching From Thunderbird to a Modern Email Client

Thunderbird is one of the longest-running desktop email clients still in active development, and if you have been on it for a decade you have accumulated more than you think: local mbox archives, per-account message filters, a saved-search list, an address book, a mail signature file, half a dozen extensions and a preferences file with hundreds of tweaks. None of that moves automatically when you install a new client. This guide is the honest version of how to switch — what carries across for free, what you have to carry across yourself, and what quietly does not survive the trip.

The reader we assume here is a Thunderbird power user who wants a more modern inbox — AI triage, a real mobile app, a maintained calendar, or a design from this decade — and who is not willing to lose their local folders or their filter set to get it. If that is you, work top to bottom. The step that matters most is not the migration; it is the backup.

What actually moves, and what does not#

Before you plan a migration, sort your Thunderbird data into two piles: server-side and profile-side. Server-side data lives on your mail provider (Gmail, Outlook, Fastmail, your own IMAP host) and follows you the instant you add the account to any other IMAP-capable client. Profile-side data lives only in your Thunderbird profile folder on disk, and if you do not move it deliberately it is gone the moment you uninstall.

The profile folder is the one thing to know the location of before you touch anything else. On Windows it is at `%APPDATA%\Thunderbird\Profiles\<random>.default-release\`; on macOS at `~/Library/Thunderbird/Profiles/<random>.default-release/`; on Linux at `~/.thunderbird/<random>.default-release/`. Everything below lives inside that folder.

• Moves for free (server-side): IMAP mail, sent items, drafts, server-side folder tree, and — for Gmail — labels (mapped to IMAP folders). Re-add the account in the new client and it comes back on its own.
• You have to move it (profile-side): Local Folders (`Mail/Local Folders/` — mbox files with a matching `.msf` index), account-level archives, message filters (`msgFilterRules.dat`), address book (`abook.sqlite` on Thunderbird 102+, `abook.mab` on older builds), tags/labels (encoded in `prefs.js` as `mailnews.tags.*`), saved searches (virtual folders in `virtualFolders.dat`), signatures, and any per-message flags stored only client-side.
• Does not survive in any client (Thunderbird-only): extensions and their data, per-account column layouts, message-view custom columns, quick-filter presets, and any keyboard-shortcut customisation. These are Thunderbird constructs and every other client rebuilds the equivalent in its own way.

The pre-migration checklist#

Do this list in order, in a quiet hour, before you install the new client. Every item exists because a real Thunderbird user has lost that specific thing during a rushed switch.

1. 1

   Copy the whole profile folder somewhere safe

   Close Thunderbird first — the profile is not safe to copy while it is open. Then copy the entire `<random>.default-release/` folder to an external drive or a cloud sync folder. This one archive is your rollback: if anything goes wrong at any later step, you reinstall Thunderbird, point it at the copied profile, and you are back where you started.

2. 2

   Audit your IMAP accounts and remember the passwords

   Open Account Settings and note the incoming/outgoing server, port, SSL, username and — critically — whether each account is OAuth (Gmail, Outlook) or password-based. Thunderbird stores passwords encrypted in `logins.json` + `key4.db`; they do not export to another client. For app-password accounts, know where in your password manager the credential lives before you uninstall.

3. 3

   Export your message filters as a reference

   For each account, filters live in `msgFilterRules.dat` inside `Mail/<server>/` or `ImapMail/<server>/`. Copy those files aside, and — this is the one that pays off — open Tools → Message Filters, take a screenshot of every rule, and paste the list into a text file. No other client reads Thunderbird's filter format, so you will be rebuilding them from that screenshot.

4. 4

   Export your address book

   Right-click each address book in the address book window and Export as either LDIF or vCard. vCard imports cleanly into every modern client; LDIF is a fallback for anything that only speaks it. Do this even if the address book feels small — one lost customer contact is one too many.

5. 5

   Consolidate Local Folders before you copy

   If you have moved mail into Local Folders over the years — an offline archive, a personal inbox, project folders — compact each folder in Thunderbird (right-click → Compact) so the mbox file no longer holds deleted-but-not-purged messages. Uncompacted mbox files can be 3–5× the size of the mail they actually contain.

The migration steps#

The order here matters. Add accounts first while Thunderbird is still installed and can serve as a fallback; move local archives second; rebuild filters last, in the new client, where you can see what actually needs rebuilding.

1. 1

   Install the new client and add your first IMAP account only

   Do not add every account at once. Pick the account you use most, add it, and wait for the full initial sync — this can take from minutes to hours depending on mailbox size and provider throttling. Gmail in particular rate-limits initial sync; a 50,000-message mailbox is normal to see finish overnight, not in ten minutes.

2. 2

   Verify the folder tree, then add the rest

   Once the first account has finished, walk the folder tree side by side with Thunderbird. Confirm the message counts match for a few folders (Inbox, Sent, and one deep sub-folder are the useful spot-checks). Only when that account is clean should you add the second, third and fourth.

3. 3

   Import Local Folders as mbox, or upload them as an IMAP folder

   There are two clean paths. Path A (mbox import): if the new client supports mbox import — eM Client, Apple Mail, and Thunderbird itself all do — point it at your Local Folders directory and import each mbox file as a folder. Path B (IMAP upload): create a folder called `Archive-Local` on your IMAP server, drag the messages from Thunderbird's Local Folders into it, wait for sync, then remove Thunderbird. This second path is slower but leaves the archive on the server, which is where it wants to live if you ever change client again.

4. 4

   Import contacts from the LDIF or vCard export

   Every modern client accepts vCard. Import the file you exported earlier and spot-check ten contacts, especially any with photos or custom fields — those are the ones that tend to translate imperfectly.

5. 5

   Rebuild filters in the new client's native rule format

   Open the screenshot of your Thunderbird filter list and rebuild the rules one at a time in the new client. This is manual work — plan on 30–60 seconds per rule — but it is also a good pruning pass. Most Thunderbird users find that a third of their old filters were for mailing lists they no longer subscribe to.

6. 6

   Recreate saved searches / virtual folders

   Thunderbird's saved searches (`virtualFolders.dat`) do not translate to other clients' saved-search formats. Most modern clients call these Smart Folders (Apple Mail), Search Folders (eM Client), Views (Missive) or filtered views. Recreate the queries by hand.

What breaks when you leave Thunderbird#

This is the table to read before you commit. Every row is a real thing a Thunderbird user has to make a decision about; the point of leaving is worth what you give up on some of them, and not worth it on others. Look at your own row before you install anything.

Two rows deserve extra attention. Tags are the one Thunderbird construct that consistently surprises people, because they feel like Gmail labels but they are not — they are per-client colour keywords Thunderbird writes to a message header, and only Thunderbird reads them back as colours. If your workflow depends on tag colours, replan it around IMAP folders (which survive) before you switch.

OpenPGP is the row that quietly loses people years of mail. Thunderbird ships with its own OpenPGP store separate from the OS keychain, and if you do not export the secret key before uninstalling, you cannot decrypt any previously encrypted message in the new client — even after you re-import your public key. Do this step even if you are only "trying out" a new client.

A rollback plan that actually works#

Every migration guide tells you to back up. Almost none tell you what rolling back actually looks like when you are three days in and the new client is not working out. Here is the version that assumes you already made the profile copy from step 1 of the checklist.

1. 1

   Stop the new client and disconnect its accounts

   Sign the new client out of every mail account, so it stops syncing changes to the server. Do not delete anything server-side — just detach.

2. 2

   Reinstall Thunderbird from the current release

   Do not try to restore Thunderbird from a version you no longer remember. Install the current release from mozilla.org/thunderbird; a new profile will be created automatically, which you are about to overwrite.

3. 3

   Point Thunderbird at your copied profile

   Close Thunderbird, then open the Profile Manager (`thunderbird -P` on Windows/Linux, `/Applications/Thunderbird.app/Contents/MacOS/thunderbird-bin -P` on macOS). Create a new profile, name it, and set its directory to a copy of the profile folder you saved in the checklist. Never point Thunderbird at the original backup — always work on a copy, so you still have the untouched backup if this step corrupts something.

4. 4

   Reconnect one account, verify, then the rest

   Open Thunderbird, enter passwords/OAuth for the first account, wait for it to reconcile with the server, and check a few folders. Only then reconnect the others. If anything looks wrong, you still have the original untouched profile backup.

Migrating without downtime#

You do not have to pick a day, uninstall Thunderbird and hope the new client is ready by end of business. IMAP is designed to let two clients read the same mailbox at once, which means the safe migration is a parallel-run, not a cutover.

Run both clients side by side for one to two weeks. Add every account to the new client, but leave Thunderbird installed and connected. Read and reply in whichever feels natural for the task in front of you, and use that period to discover the things you cannot know from a checklist — how the new keyboard shortcuts feel, whether the search finds what you need, whether notifications behave. Because both clients are talking to the same IMAP server, a message you archive in one appears archived in the other within seconds.

The one caveat is filters. If you rebuild filters in the new client and Thunderbird still has its old ones running, both will fire on incoming mail and you can end up double-filing or double-labelling. Pick a moment — often the end of the first parallel week — when you disable Thunderbird's filters (Tools → Message Filters → uncheck the account) and let the new client's filters run alone. This is a much smaller change than switching client, and it is the change that lets you commit without losing anything.

When the two weeks are up and you have not opened Thunderbird for three days without noticing, that is the signal. Compact the profile one last time for the archive, keep the profile copy on your backup drive, and uninstall.

Where AI Emaily fits, and where it does not#

The Thunderbird reader has several honest destinations: staying on Thunderbird, moving to eM Client or Mailbird on Windows, Apple Mail on macOS, or a modern AI-triaged client like ours. We build AI Emaily, and the case for it is narrow and specific: it is a full mail client for Gmail, Outlook and IMAP that adds a triage agent with approve-before-send, an audit log and rules you actually see. If you have been using Thunderbird because the modern web clients felt shallow, we are aimed at that reader.

The concession: **Thunderbird is still the better answer if your workflow depends on a fully local, offline-first mail archive on Linux.** We ship no Linux desktop app, our offline is partial by design (read and draft, not a complete local archive), and our Mac build is Apple Silicon only. If those matter, stay on Thunderbird — you can see the [AI Emaily pricing](/pricing) and the trial terms whenever you decide otherwise, but the honest answer for that shape of user is not us.