How to Move Emails From One Gmail Account to Another
Switching Gmail accounts — whether you're consolidating personal and work inboxes, handing off a project, or simply starting fresh — raises an immediate question: can you actually move emails between two Google accounts? The short answer is yes, but the method that works best depends on how many emails you're moving, what access you have to both accounts, and whether you need a one-time transfer or ongoing synchronization.
Why Moving Gmail Emails Isn't a One-Click Process
Gmail doesn't have a built-in "transfer emails to another account" button. Google accounts are designed as isolated environments, so migrating messages requires either routing them through a mail protocol, using Google's own tools for specific contexts, or exporting and re-importing data manually. Each approach has real tradeoffs in terms of effort, speed, and what gets preserved.
Method 1: Use Gmail's Built-In Forwarding (Best for Ongoing Emails)
If your goal is to redirect future incoming emails from Account A to Account B, Gmail's forwarding feature handles this cleanly.
Go to Settings → See all settings → Forwarding and POP/IMAP in Account A, then add Account B's address as a forwarding destination. Gmail will send a confirmation code to Account B to verify ownership.
What this does well: Every new email arriving at Account A automatically lands in Account B.
What it doesn't do: It won't move emails that already exist in Account A's inbox. Forwarding is prospective, not retroactive.
Method 2: Import via POP3 (Best for Pulling Existing Emails)
This is the most straightforward way to pull existing emails from one Gmail account into another without third-party tools.
In Account B (the destination), go to Settings → See all settings → Accounts and Import → Import mail and contacts. You'll enter Account A's Gmail address and password (or an app-specific password if two-factor authentication is enabled). Gmail will connect to Account A using POP3 and begin pulling messages over.
A few important details about this method:
- It imports emails into Account B's inbox, typically labeled with Account A's address
- POP3 pulls messages from the inbox — it may not capture every folder or label depending on Account A's POP3 settings
- The import can take anywhere from a few hours to a day or more for large mailboxes
- Attachments are preserved, but some metadata (like original labels) may not transfer exactly
To maximize what POP3 captures, check Account A's Settings → Forwarding and POP/IMAP and ensure POP is enabled for all mail, not just mail received after a certain date.
Method 3: Google Takeout + Re-Import (Best for Archives)
For users who want a complete, portable backup before migrating, Google Takeout lets you export your entire Gmail mailbox as an MBOX file.
- Go to takeout.google.com while signed into Account A
- Select only Gmail, then download the export
- The resulting
.mboxfile contains all your emails
Re-importing that MBOX into Account B isn't natively supported by Gmail's web interface. You'd need a desktop email client like Thunderbird with an MBOX import add-on, or a third-party migration tool. This approach suits archiving and offline access better than a seamless cloud-to-cloud move.
Method 4: Google Workspace Migration Tools (For Business or Admin Accounts)
If either account is a Google Workspace (formerly G Suite) account, admins have access to the Google Workspace Migration for Microsoft Exchange tool and other migration utilities that can move email in bulk with label and folder structure preserved. This is a more controlled, enterprise-grade path that individual consumer Gmail accounts don't have access to.
📋 For organizations moving an entire team's email history, these tools are significantly more capable than POP3 import — but they require admin-level access to the destination Workspace account.
What Gets Preserved — and What Doesn't
| Element | POP3 Import | Google Takeout | Forwarding |
|---|---|---|---|
| Message body | ✅ Yes | ✅ Yes | ✅ Yes |
| Attachments | ✅ Yes | ✅ Yes | ✅ Yes |
| Original labels/folders | ⚠️ Partial | ✅ Yes (in MBOX) | ❌ No |
| Read/unread status | ❌ Usually no | ✅ Yes | ✅ Yes |
| Future emails | ❌ No | ❌ No | ✅ Yes |
| Sent mail | ⚠️ Depends on POP settings | ✅ Yes | ❌ No |
Factors That Affect Which Method Works for You
Several variables shape which approach is practical:
Volume of email. A mailbox with 10,000+ messages will take much longer to import via POP3 and creates larger Takeout exports. For small inboxes, any method works reasonably fast.
Two-factor authentication. If Account A has 2FA enabled, POP3 import requires generating an app-specific password through Google's security settings rather than using your regular login credentials.
Account type. Consumer Gmail accounts have fewer migration tools than Workspace accounts. If one account is Workspace, admin tools open up additional options.
What you actually need to move. Sent mail, archived mail, spam, and drafts behave differently across methods. POP3 typically focuses on inbox and all-mail; Takeout is more comprehensive.
Whether both accounts remain active. If Account A is being deleted, timing matters — POP3 import needs Account A accessible throughout the process.
🔒 One security note worth keeping in mind: when setting up POP3 import, you're providing Account A's credentials to Google. Use an app-specific password rather than your primary password wherever possible, and revoke it after the import completes.
When Labels and Organization Matter Most
Gmail's label system doesn't map cleanly onto traditional folder structures. Emails in Account A that sit under custom labels will arrive in Account B's inbox without those labels intact when using POP3. If your workflow depends heavily on how emails are sorted and labeled, Takeout with a manual re-import into a desktop client may preserve more of that structure — though the re-import process is more involved.
How much that matters depends on whether you're archiving for reference or actively using those emails in a working inbox with the same organizational logic.