Combine email accounts into one inbox: what you gain and lose

The phrase covers three operations that are nothing like each other. One shows several mailboxes in a single list and moves nothing. One redirects future mail into a different mailbox. One copies years of existing mail into a different provider. All three are described as combining accounts into one inbox, and only the first can be undone in an afternoon. Deciding which one is actually wanted is most of the work, because the irreversible option is the one search results tend to explain in most detail.

Three operations wearing one name

A unified view is a display change. A mail client signs into each account separately and offers a combined list on top of them, while every message stays in its own mailbox on its own server. Turn the view off and the accounts are untouched. Nothing about the accounts has changed, including the addresses people write to.

Forwarding is a redirection of future mail. Each provider is told to send new messages onward to one destination, and from then on that destination receives them. History stays where it was. The original mailbox continues to exist and, if configured that way, continues to keep its own copy.

Migration is a copy of the past. An import or migration tool reads the old mailbox and writes its contents into the new one, which is how a decade of archived mail ends up searchable in one place. This is the operation people mean when they say merge, and it is the one that takes hours, consumes storage, and cannot be cleanly reversed once the old account is closed.

The three can be combined, and often should be: a unified view for daily work, forwarding for an address that is being retired, migration only for an account that is genuinely going away.

What merges, and what stays behind

The part that surprises people is how much of an email account is not the messages.

The address stays. Merging inboxes does not merge addresses, and a message sent to the old address only arrives in the new mailbox while the forwarding rule survives. If the old account is closed, the address stops working, and everyone who has it in a contact list starts getting bounces.

Sending identity does not follow automatically. A forwarded message answered from the receiving account goes out with the receiving account's address. Both Gmail and desktop clients can send as an alternate address, but that has to be added and verified for each one, deliberately.

Filters, labels, and folders do not travel. These are the provider's own constructs, and Gmail's help is explicit that an import brings messages and not folders or labels. Whatever sorting had been built up over years has to be rebuilt in the destination.

Spam decisions are re-made. The original provider already judged each incoming message, and the destination judges it again, this time arriving via a forwarding server rather than directly from the sender. Some legitimate mail lands differently as a result.

Storage is shared in a way that matters. A Google account's quota covers Drive, Gmail, and Photos together, so importing a large archive into Gmail reduces the space available for files and photos in the same account.

Contacts and calendars are separate systems with their own migration paths. An inbox merge does nothing for either.

Two-step verification is its own item as well. Each account has its own second factor, its own backup codes, and its own recovery address, and merging the mail does not consolidate any of that. An account whose mail now arrives elsewhere is still an account that has to be signed into when a provider asks for re-verification, and the codes for it need to be somewhere findable.

The Gmail routes, and their expiry dates

Gmail offered the most convenient version of this for years, and it is being withdrawn on a published schedule:

Gmail will no longer support checking emails from third-party accounts through POP. The option to "Check mail from other accounts" will no longer be available in Gmail on your computer. Source: support.google.com

The same page gives the timeline. After the first quarter of 2026 the feature no longer accepts new users, and existing users can keep it until January 2027. Gmailify, which applied Gmail's spam protection and inbox categories to a third-party account, is being removed alongside it. Mail already synced stays in Gmail.

Two limits applied even before the withdrawal. The web feature accepted at most five added addresses, so it never scaled to a long list. And an Outlook account could not be added to Gmail on a computer at all, because Microsoft requires modern authentication from non-Microsoft clients.

Google names the replacements directly. Automatic forwarding, configured at the other provider, for new mail. The Gmail mobile app, which uses IMAP, for reading and sending from a third-party account on a phone or tablet. And import on the web, which remains available but is described as a one-time copy that does not sync continuously. That last distinction is the one to hold on to: import is a migration, not a merge that keeps running.

If a migration has to happen anyway

Sometimes the old provider is shutting down, a university address is expiring, or a company is closing an account, and the copy is not optional. Four steps make the difference between a clean move and a year of small surprises.

Keep the source account open for as long as possible, even after the copy finishes. It costs nothing while it exists and it is the only way to check anything that looks wrong afterwards.

Set up forwarding before starting the import, not after. Forwarding catches mail that arrives during the copy, which is otherwise the one window where messages can genuinely be missed.

Add and verify the old address as a sending address in the destination before announcing the change. Replies then go out with the address the recipient recognises, which buys time to update contacts at a normal pace instead of all at once.

Label the imported mail as a block. Gmail's import offers to label incoming messages, and a single label applied to the whole archive keeps the old mailbox distinguishable inside the new one. That one step restores most of the search precision a merge otherwise costs, because a search can be narrowed back to the source account whenever it matters.

None of this makes the copy reversible. It makes the consequences visible and bounded, which is the realistic goal.

The three routes compared

Route	Moves existing mail	Keeps the old address working	Keeps each account's filters	Reversible
Unified view in a mail client	No	Yes	Yes	Yes, immediately
Forwarding new mail	No	Yes, while the rule exists	No, the destination's rules apply	Yes, by disabling the rule
One-time import or migration	Yes	Only if the account stays open	No	No, not cleanly
App windows per account	No	Yes	Yes	Yes, immediately

Read down the last column. The routes that can be undone in a minute are the ones that changed a display rather than the data, and they are also the ones that preserve the four things listed in the previous section. That is not a coincidence. Convenience in this area is bought almost entirely by discarding separation, so the question worth asking is how much separation the accounts were carrying in the first place.

The costs that do not show up until later

Search noise is the first. A combined mailbox of four accounts makes every search return four accounts' worth of results, and the searches that used to be precise because the mailbox was narrow stop being precise. For anyone who finds things by searching rather than by filing, this is a real loss of speed.

The reply accident is the second, and it is the one with an external witness. Once mail from a client address arrives in a personal mailbox, every reply is one distracted moment away from going out with the wrong name attached.

The handover problem is the third. An address that belongs to a role, such as enquiries or billing, may one day need to be handed to somebody else. That is straightforward while it is a mailbox of its own and very awkward once its history is interleaved with somebody's personal mail.

Storage is the fourth, and the most mechanical. Because a Google account's quota is shared between Gmail, Drive, and Photos, importing a large archive can push an account towards a paid tier for reasons that have nothing to do with the work.

The fifth is quieter. Organisations frequently need to show that a work mailbox is separate from personal correspondence, and a merged inbox makes that claim impossible to support. Where a mailbox belongs to an employer or holds client material, the separation is a requirement rather than a preference.

When a unified view is the right answer

For most people who type this search, a unified view is what they actually wanted. The Mail app included with macOS holds accounts from iCloud, Gmail, Exchange, work, school, and other providers in one location, keeps each account's own sending address, and offers an All Inboxes view for a single pass. Nothing is copied, nothing is redirected, and switching the view off restores the previous arrangement exactly. It also sorts incoming mail into Primary, Transactions, Updates, and Promotions, which cuts the volume the combined list has to carry.

Thunderbird does the same job, is open source, and runs on macOS as well as Windows and Linux.

The one thing a client cannot do is reproduce the provider's interface. Gmail's labels, filter editor, search operators, and snooze behaviour belong to the Gmail website, and a client offers its own equivalents over IMAP instead. That is why a client suits someone running several different providers better than it suits someone running several Gmail accounts.

When staying separate is the requirement

Where the accounts exist because roles are separate, the goal is not to combine them but to stop paying for the switching. A browser built around app windows gives each service its own window and its own cookie container, so several accounts of the same provider stay signed in at once and none of them can see the others. No mail moves, the addresses keep working, each account keeps its own filters, and replies are composed inside the account that received the message.

The trade is memory and one more running application, since each web app stays loaded. Which services are covered is listed under supported apps, the isolation model is described under workspaces, and the free and paid tiers are set out on the pricing page.

What to change first

Write down which of the three operations is actually wanted, and treat migration as a last resort reserved for an account that is being closed. If the accounts are staying open, start with a unified view in a mail client for a week, and if the provider interfaces turn out to be the thing you cannot give up, keep them and change the container instead, which is what SpaceDeck is for.