Migrate Personal Gmail to Google Workspace Without Losing Mail

You have been running your business out of yourname@gmail.com for two years. The address is on business cards, in supplier portals, and in every client thread you have ever had. Now the team has grown, you have signed up for Google Workspace at yourname@yourdomain.com, and you need to move five years of mail history into the new mailbox without losing labels, search history, or the threading on conversations that started in 2021. This guide covers the three paths from personal Gmail to Workspace, when to use each, and the post-cutover steps that keep the old address as a safety net while everyone catches up.

Gmail and Workspace: same engine, different shell#

The mail back-end at Google is the same code whether you use it via @gmail.com or via Workspace at your own domain. What differs is the surrounding product:

• Storage: personal Gmail is 15 GB shared across Gmail, Drive, and Photos. Workspace Business Standard is 2 TB per user.
• Domain: personal is @gmail.com. Workspace uses your domain.
• Admin controls: Workspace has central management, audit logs, eDiscovery via Vault, and DLP rules.
• Support: Workspace gets human support; personal is forum-based.

Because the underlying engine is the same, migration is mechanically straightforward. The structural metadata (labels, threading, attachments) transfers intact. What changes is the identity of the mailbox.

Three migration paths, ranked#

Path 1: Gmail's "Check mail from other accounts". The destination Workspace mailbox can be configured to fetch mail from the personal Gmail via POP3. Suitable only for small mailboxes (under 5,000 messages) because POP3 is one-way, slow, and loses labels.

Path 2: IMAP-to-IMAP via a desktop client or migration tool. The cleanest approach for individuals. Connect both mailboxes via IMAP in a tool like Mailbox Taxi, Thunderbird with the ImportExportTools NG add-on, or a dedicated migration utility. Labels become folders become labels again on the destination — round-trip preserved.

Path 3: Workspace Data Migration Service (DMS). The right choice for batch moves of multiple users or for a single mailbox over 30 GB. DMS handles throttling, parallel users, and delta runs automatically.

For most one-person moves, Path 2 is what you want. For team-wide moves (everyone consolidating from personal Gmail to a shared Workspace tenant), use Path 3.

Pre-migration prep#

On the personal Gmail side:

1. Sign in to Gmail at gmail.com. Go to Settings → See all settings → Forwarding and POP/IMAP.
2. Enable IMAP. Set "When I mark a message in IMAP as deleted" to "Auto-Expunge off". This prevents accidental deletes during migration.
3. If you have 2FA enabled (you should), generate an app password at [myaccount.google.com/apppasswords]. Name it "Workspace Migration". Save the 16-character string.
4. Confirm your mailbox size: Storage at the bottom of the Gmail UI shows total used. If you are close to the 15 GB cap, archive or delete unwanted mail before migrating.
5. Export your filters: Settings → Filters and Blocked Addresses → Export. Save the XML file.

On the Workspace side:

1. Verify your domain in the Admin Console (TXT record on DNS).
2. Create the destination user at the desired email address.
3. Assign a licence. Business Standard (2 TB) is the right floor for anyone with more than 5 GB of mail.
4. Optionally, pre-create labels in the destination mailbox if you want a clean structure.

Path 2 in detail: IMAP-to-IMAP#

The most flexible approach. You connect both mailboxes via IMAP and copy mail across at the folder/label level.

1. Connect both accounts in a desktop tool

   Configure source: imap.gmail.com:993 SSL, username your @gmail.com address, password the app password from earlier. Configure destination: imap.gmail.com:993 SSL, username your Workspace address, password the destination's app password.

2. Map labels to labels

   Personal Gmail labels appear as IMAP folders. Workspace labels work the same way. Your migration tool copies folders across; Google does the IMAP-folder-to-label conversion automatically on the destination.

3. Migrate folders one at a time for a small mailbox or all at once for a larger one

   For mailboxes under 5 GB, do all folders at once. For larger mailboxes, do Inbox first (so you have working mail quickly), then [Gmail]/Sent Mail, then everything else.

4. Reimport filters

   In Workspace Gmail, go to Settings → Filters → Import filters → upload the XML you saved earlier. Review each filter — some may reference labels that have been renamed.

5. Set up forwarding from personal Gmail

   On the personal side, Settings → Forwarding → Add a forwarding address → enter your Workspace address. Confirm via the verification email. Choose "Keep Gmail's copy in the Inbox" so you have a fallback for the first 90 days.

Path 3 in detail: Data Migration Service#

For team-wide moves where multiple users are consolidating from personal Gmail into a single Workspace tenant.

1. In Workspace Admin Console, go to Account → Data Migration → Set up data migration.
2. Migration source: Gmail. Connection protocol: IMAP (or OAuth — IMAP with app passwords is more reliable for personal accounts).
3. Source server: imap.gmail.com. Port: 993. SSL: yes.
4. Role account: not applicable for personal Gmail. Each user provides their own credentials.
5. Add migration users by uploading a CSV with two columns: SourceAccount, DestinationAccount. For each row, you will also need the source app password — DMS prompts per user, or accepts a third column with the password (less secure but operationally faster for big batches).
6. Start the migration. DMS handles per-user throttling, retry, and delta runs.

Plan around 60 to 180 minutes per 10 GB. Run overnight for the bulk.

Sent items and the [Gmail] namespace#

One quirk of Gmail's IMAP: sent mail lives under [Gmail]/Sent Mail, not in a top-level Sent folder. Your migration tool must understand this namespace. If you see your sent items landing in a folder literally named [Gmail]/Sent Mail on the destination instead of being merged into the destination's Sent label, your tool is not handling Gmail-specific folder mapping. Switch tools or use DMS.

The same applies to:

• [Gmail]/All Mail — Gmail's archive
• [Gmail]/Drafts — drafts
• [Gmail]/Trash — trash (usually skip)
• [Gmail]/Spam — spam (always skip)

A well-behaved migration tool skips Spam and Trash by default and merges [Gmail]/Sent Mail into the destination Sent label.

Forwarding and Send-As setup#

After the migration, configure two things on the destination:

Send-As: In Workspace Gmail Settings → Accounts → Send mail as → Add another email address. Add your old @gmail.com address. Verify via the link sent to the old mailbox. Now you can reply from the new mailbox as if from the old address — useful while clients transition.

Forwarding from old mailbox: In personal Gmail Settings → Forwarding → forward to your Workspace address. This means any mail still being sent to the old address lands in the new mailbox. Keep this in place for 90 days minimum, six months ideally.

If you want to go further, set up a filter on the personal Gmail to also send an auto-reply that includes the new address ("This address is being retired. I've replied from yourname@yourdomain.com — please update your records.").

What does not move#

Be realistic about Gmail metadata that does not survive an IMAP transfer:

• Filters: handled separately via XML export/import.
• Vacation responder settings: recreate manually.
• Custom themes: recreate manually.
• Chat history: lives in a different product (Google Chat) and is not part of the mail migration.
• Contacts: export via Google Contacts → Export → vCard or CSV, then import on the destination.
• Calendars: export via Google Calendar → Settings → Import & export → Export, then import on the destination.

Plan to spend 30 to 60 minutes on these manual pieces.

DNS and identity#

Workspace requires SPF, DKIM, and DMARC for clean inbox delivery. Publish all three before users start sending from the new mailbox:

• SPF: v=spf1 include:_spf.google.com ~all
• DKIM: enable in Admin Console → Apps → Gmail → Authenticate email, then publish the generated TXT record.
• DMARC: start at v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com.

Without these, mail from the new address may land in spam at major receivers (Outlook, Yahoo, other Workspace tenants).

Where Mailbox Taxi fits#

For single-user moves from personal Gmail to Workspace, DMS is heavyweight. A desktop tool that speaks IMAP to both sides is faster, lets you control which labels move, and never uploads your credentials to a third-party cloud service.

Mailbox Taxi runs locally on Windows, Mac, or Linux. It speaks Gmail-aware IMAP (handles the [Gmail]/ namespace correctly), preserves labels as labels, and supports filtered migrations (date range, label subset, attachment size). It is the right tool for individual moves and for the messy outliers in a DMS-led batch.

If you eventually decide Microsoft 365 is a better fit than Workspace, the Gmail to Office 365 walkthrough covers that path, and Gmail to Outlook covers the desktop client side.

Common errors and fixes#

[ALERT] Web login required — Gmail flagged the IMAP session as suspicious. Sign in to the personal account via a browser from the same machine, then retry. The flag clears within 30 minutes.

Too many simultaneous connections — Gmail caps at 15 concurrent IMAP sessions per account. Reduce to one or two and resume.

AUTHENTICATIONFAILED — the app password is wrong, or 2FA is enabled and you are trying to use the account password directly. Generate a fresh app password and use it.

Folder UTF-7 conversion error — a label contains characters that IMAP UTF-7 cannot encode. Rename via the Gmail web UI before migrating.

Message too large for destination — only if a single message exceeds 50 MB, which is rare on personal Gmail. Export those messages as EML files separately.

The complete email migration guide has a broader error catalogue.

Post-cutover validation#

In the first week:

1. Item count: compare source label totals to destination label totals. Anything more than 1 percent variance deserves investigation.
2. Search test: search for an old email by sender and subject on both sides. The result count should match.
3. Calendar and contacts: confirm both imported correctly.
4. DNS: SPF, DKIM, DMARC passing — check with Google Postmaster Tools after a few sends.

After 90 days of stable Workspace use, you can stop forwarding from the personal Gmail. After 12 months, archive the personal mailbox. Keep it alive — do not delete — in case anything obscure was missed.

The pillar Google Workspace migration guide covers the broader program view, especially if you are running multiple users in parallel.