Gmail Labels vs Outlook Folders: What Changes During Migration?

Why Labels and Folders are not the Same Thing

The confusion starts because both features look similar in the interface. On the left side of the screen, you see a list of names; you click one, and a set of emails appears. Under the hood, though, they work in opposite ways. A Gmail label is a tag. It is a piece of information attached to a message, and a single email can carry as many tags as you like. An invoice from a client might sit under "Finance," "2026," and "Client-Acme" all at once. There is still only one copy of that email. Gmail keeps every message in a single master store called All Mail, and each label is really just a saved view that filters that store. An Outlook folder is a container. A message physically lives inside one folder and one folder only. If you want the same invoice to appear in three places, you need three copies, one per folder. That is the core of it: Gmail describes a message with labels, while Outlook files a message into a location. Everything else about the migration follows from this single difference.

Gmail Labels vs Outlook Folders at a Glance

Regular User Labels Become Folders

Every label you created by hand turns into a folder with the same name. A label called "Projects" becomes a folder called "Projects," and the emails tagged with it show up inside. For the vast majority of your mail, this is the whole story, and the result feels natural the moment users open Outlook.

System Labels Map to Standard Outlook Folders

Gmail's built-in labels line up with the folders Outlook already expects. Inbox stays the Inbox. Sent Mail becomes Sent Items. Drafts stay Drafts. Trash maps to Deleted Items, and Spam lands in Junk Email. This mapping is handled for you, so users are not left hunting for their sent messages in an oddly named folder.

Nested Labels Keep their Hierarchy

Gmail lets you nest labels using a slash, so "Clients/Acme/Contracts" reads as a three-level structure. That hierarchy carries over into a matching nested folder tree in Outlook, with Contracts sitting inside Acme, inside Clients. You do not have to rebuild the tree by hand after the move.

Messages with more than one Label

This is the part that surprises people, and it is worth slowing down on. In Gmail, one email can wear several labels. In Outlook, that same email can only sit in one folder. So when a message tagged with "Finance" and "Client-Acme" arrives at the destination, it needs to appear under both folders to preserve the way you had it organized. The practical result is that a multi-labeled message shows up as a copy in each corresponding folder. This can be expected when the destination represents Gmail's multi-label organization as folders. The exact result depends on how the migration workflow maps Gmail labels to the target folder model. It also means the item count in Outlook can look slightly higher than the raw message count in Gmail, because a message with three labels is now filed in three places. Understanding this up front stops it from looking like something went wrong.

All Mail is Handled Separately for a Reason

All Mail is Gmail's master archive, and it contains every single message in the account, including everything that already sits under a label. If a migration copied All Mail as its own folder on top of every label folder, you would end up with a second full copy of the mailbox and a badly inflated size on the target. For that reason, All Mail is treated with care rather than copied blindly. EdbMails preserves your label-based structure while its duplicate-prevention logic keeps the same message from being written to the target twice. That is also why running incremental migration across several passes does not pile up duplicate emails, since each run only picks up what is new or changed.

Starred, Important, and Gmail categories

A few Gmail features have no direct folder equivalent, so they behave differently. Starred and Important are Gmail's own priority markers, and the inbox categories (Primary, Social, Promotions, Updates, Forums) are tabs that sort your inbox rather than real labels. These are display conveniences inside Gmail rather than storage locations, so they do not translate into standalone Outlook folders the way a user label does. Your actual messages still migrate in full; it is only these Gmail-specific views that do not have a matching container on the Outlook side.

Message Content and Metadata Stay Unchanged

It is easy to focus on the structural changes and assume the content itself is at risk. It is not. The message data comes across untouched. Read and unread status is preserved, so a folder full of unread mail still reads as unread after the move. Timestamps stay accurate, which keeps your mail sorting in the right order by date. Sender and recipient details, subject lines, and the message body all transfer as they were. Attachments stay bound to their original emails, so an invoice does not get separated from the message it arrived on. In short, the label-to-folder conversion changes how mail is organized, not what the mail contains.

If you want the full picture of every data type that moves across, including contacts, calendars, and tasks, the guide on migrating Google Workspace emails, contacts, and calendars covers it in detail.

What to Check Before You Migrate

A little planning around labels goes a long way toward a clean result. Take a look at how heavily your users rely on multi-label organization. Accounts where most messages carry a single label convert almost invisibly. Accounts where power users tag everything three or four ways will show more copies spread across folders, which is normal but worth explaining to those users in advance. Clean up before you move, not after. Old labels nobody uses, throwaway tags from years back, and abandoned sub-labels all become folders if you leave them in place. Trimming them in Gmail first gives you a tidier folder tree in Outlook. It is far easier to delete a label in Gmail than to reorganize a folder structure once it is sitting in a live Outlook mailbox. Set expectations about item counts. Because multi-labeled messages file into more than one folder, the total item count on the target can read higher than the source. Let your team know this ahead of time so it does not get mistaken for duplication or an error. If you hit anything unexpected during the run, the notes on how to fix Google Workspace migration issues and mistakes to avoid during Google Workspace migration are worth a read.

How EdbMails Converts Labels to Folders

EdbMails reads the label structure straight from the source Google Workspace account and rebuilds it as a folder hierarchy on the destination, whether that target is Microsoft 365, Exchange Server, or an IMAP-based platform. User labels become folders, system labels map to their Outlook counterparts, and nested labels keep their parent-child arrangement. Because the tool treats the mailbox as one connected dataset, folder structure, metadata, and message properties are preserved together rather than as separate pieces. Incremental migration lets you run the process more than once in the lead-up to cutover without stacking duplicates, and the per-mailbox migration report shows exactly what landed in each folder so you can verify the conversion before users switch over. The same behavior applies whether you are moving to Office 365, to Exchange Server, or exporting to Outlook PST.

Related migration guides

For organization-managed Google Workspace migration to Microsoft 365, use the Google Workspace to Microsoft 365 Migration Tool or the step-by-step Google Workspace migration guide. For personal Gmail/IMAP-based migration, use the Gmail to Office 365 migration guide.

Conclusion

The shift from Gmail labels to Outlook folders is really a shift in thinking, from tagging messages to filing them. Once you know that a label is a tag and a folder is a container, the rest follows: user labels become folders, nested labels keep their tree, system labels map to Outlook's standard set, and multi-labeled messages get filed in each folder they belonged to. The content of your mail, from read status to attachments, comes across unchanged. To see how this conversion runs end to end on your own mailboxes, start with the Google Workspace Migration Tool and review the automatic mailbox mapping step, which pairs each source account to the right destination before anything moves.