Migrate Google Workspace to Zoho Mail Step by Step

You're moving off Google Workspace to Zoho Mail. The reasoning is usually cost: a 30-seat company spending $500/month on Workspace can run on Zoho Mail Premium for under $200. The mail has to come along, the calendars usually too, and the cutover has to be clean enough that users don't miss messages. This guide covers the source and destination prep, the IMAP migration mechanics, Zoho's quirks (label-to-folder conversion, storage limits, app password requirements), and the cutover sequencing.

Who actually does this migration#

Three patterns show up.

The first is cost-driven consolidation: a company that's been on Workspace for years is feeling the per-seat pricing and realizes most users only use Gmail and Calendar, not Drive or Meet. Zoho Mail with the basic suite covers their needs at a third of the cost.

The second is regional preference: organizations in India, the Middle East, or parts of Southeast Asia where Zoho has strong local support and data residency. Workspace works fine but Zoho's domestic presence wins.

The third is escape from Google's ecosystem: an org that has security or sovereignty concerns and wants its mail in a different jurisdiction. Zoho's data centers in the EU and India are part of the appeal.

In all three cases, the migration shape is the same: dozens to hundreds of Workspace mailboxes need to land in Zoho with their structure preserved, and the cutover needs to happen with minimal disruption.

What you keep and what you don't#

Mail, headers, attachments, dates, read/unread state, and folder/label structure carry over through IMAP migration. So does starred state, since IMAP exposes \Flagged on both sides.

Gmail labels become Zoho folders. A message with one label becomes a message in one folder. A message with multiple labels can become multiple copies, one per folder, unless your migration tool detects the duplicate and skips. This is the single biggest fidelity issue, and we'll cover handling it below.

Calendar, contacts, Drive, and Chat history do not move through mail migration. Calendar can be migrated separately via ICS export/import. Contacts via vCard. Drive needs a separate plan (Zoho WorkDrive, or just download everything as a Drive Takeout). Chat history is generally not migratable.

Filters, vacation responders, and forwarding rules do not move. Users will need to recreate these in Zoho. Document them in advance with a Takeout of each user's settings.

Aliases and groups: Workspace groups need to be recreated in Zoho. Aliases too. Plan this as a separate task during the migration window.

Setup, in sequence#

Provision Zoho destination#

Sign up for Zoho Mail with your custom domain. Verify domain ownership via DNS TXT record. Create users matching every Workspace user you'll migrate. Allocate storage tiers per user based on source mailbox size. If you have a user with 25 GB on Workspace, they need Mail Premium (50 GB) not Mail Lite (5 GB) on Zoho.

Confirm IMAP access in Zoho#

Zoho enables IMAP by default for paid plans. Verify under Admin Console → Settings → Mail Account → IMAP Access. The IMAP server is imap.zoho.com:993 SSL for personal accounts and the appropriate regional variant (imap.zoho.eu, imap.zoho.in) for EU and India tenants.

Generate Zoho app passwords#

Each destination user needs an app password for IMAP. Per user, sign into Zoho, go to My Account → Security → Application-Specific Passwords, and generate one. For larger estates, this is tedious; admins can disable two-factor temporarily and use regular passwords during the migration, then re-enable. Whichever way, capture credentials in a secure place.

Confirm IMAP and OAuth in Workspace#

In the Workspace Admin Console, ensure IMAP access is enabled in Apps → Google Workspace → Gmail → End User Access. For each user, you have two paths: generate per-user Google app passwords (requires 2-step verification to be enabled), or use OAuth2 if your migration tool supports it for Workspace sources.

For larger estates, OAuth2 is faster because you don't need 200 separate app password generations. Mailbox Taxi supports OAuth2 against Workspace as one of its source options.

Take a baseline#

Before any data moves, dump per-mailbox stats from Workspace. You can use the Gmail API, the Reports API, or the Admin Console exports. Save item counts and storage sizes per user. You'll compare against these to verify post-migration.

Migration approach#

Two paths exist for Workspace-to-Zoho.

Zoho's built-in IMAP migration wizard. Available in the Zoho Mail Admin Console under Mail Administration → Migration. Configure the source IMAP server (Gmail), enter per-user credentials in a CSV, start the migration. Works fine for under 50 users and mailboxes under 5 GB each. Less control over folder mapping and limited per-folder reporting.

A desktop IMAP migration tool. Runs on your workstation, connects to both sides over IMAP, gives per-folder visibility, handles label-to-folder collapse cleanly, and supports OAuth2 against Workspace. Better fit for larger estates and complex mailboxes.

For comprehensive source-side context, see the Workspace migration guide.

Step-by-step#

1. Test connectivity on both sides with a single mailbox

   Before bulk loading, verify one Workspace user connects via IMAP at imap.gmail.com:993 with their app password, and one Zoho user connects at the appropriate Zoho IMAP host with their app password. Use Thunderbird or any IMAP client. If either side fails, fix it before touching the migration tool.

2. Configure the migration tool

   Open Mailbox Taxi. Add Workspace as the source: either OAuth2 (preferred for many users) or per-user IMAP credentials. Add Zoho as the destination: per-user IMAP credentials. Load the user-mapping CSV that pairs each source user with their destination user.

3. Handle Gmail's label-to-folder collapse

   This is the critical step. In Gmail, a single message can have multiple labels. In Zoho, folders are exclusive. Configure the migration tool to either: (a) place a multi-labeled message into the most specific label's folder and drop the others, or (b) place a single copy and apply Zoho's flagging where available. Option (a) is cleaner; option (b) preserves more information but is harder to verify. Document the choice.

4. Map system folders explicitly

   Gmail's system folders are All Mail, Sent, Drafts, Spam, Trash, Important, Starred. Zoho's are Inbox, Sent, Drafts, Spam, Trash, Outbox. Map Sent → Sent, Drafts → Drafts, Trash → Trash, Spam → Spam, and exclude All Mail (it's a Gmail concept, not a real folder). Exclude Important and Starred if they're not labels you actually use; otherwise treat them as labels.

5. Run a pilot with 3 to 5 mailboxes

   Pick a mix: one small, one medium, one with deep label hierarchy, one with heavy use of multi-labeled messages. Migrate them all the way through. Verify in Zoho: dates correct, attachments open, folder structure matches Gmail labels, no unexpected duplicates from the label collapse. Adjust config and rerun the pilot until clean.

6. Run the full migration in waves

   Break users into waves of 20 to 50. Start each wave off-hours. Mailbox Taxi will use 2 to 4 connections per mailbox; Zoho's per-IP cap means you don't want more than 4 concurrent mailboxes per workstation. For estates over 100 mailboxes, consider running on multiple workstations to parallelize.

7. Verify each wave against baseline

   After each wave, compare per-mailbox message counts in Zoho against your baseline Workspace numbers. Account for the label-to-folder collapse: if a Gmail mailbox had 50,000 messages with average 1.3 labels each, you might see 50,000 messages in Zoho after deduplication, or 65,000 if you preserved every label as a separate copy. Decide which model you used and verify accordingly.

8. Cutover MX records

   After all waves complete, flip MX records to Zoho. Lower TTLs to 300 seconds 48 hours in advance. On cutover day, change MX and wait for propagation. Senders will start hitting Zoho within minutes for fast resolvers and within hours for the slowest.

9. Run a final delta

   After MX cutover, run a delta migration to catch mail that arrived at Workspace during the cutover window. Mailbox Taxi will only fetch new messages, so this delta runs quickly. Do this within 24 hours of MX cutover.

Zoho's throttle behavior#

Specifics for setting expectations.

Zoho limits concurrent IMAP connections per user to about 4 to 5. From a single IP across multiple users, the cap is around 20 simultaneous connections.

Append throughput tops out around 5 to 10 messages per second per mailbox. Faster than Yahoo, slower than Gmail.

Per-message size limit is around 30 MB. Larger messages fail with Message too large for destination. Most Gmail mailboxes have a handful of these; expect to handle them manually.

Idle timeout is around 20 minutes. Connections that sit idle longer get dropped. A good migration tool keeps them alive with periodic activity.

After cutover#

The work after MX flip.

Send users their reconfiguration guide. Specific steps: reconfigure phone mail apps with the new IMAP/SMTP details for Zoho. Recreate filters and signatures. Update bookmarks pointing at mail.google.com.

Forward Workspace mail to Zoho for 30 days. In Gmail per-user settings, configure forwarding to the Zoho address. This catches anything that lands at Workspace despite MX changes.

Keep Workspace licensed for 60 days. Don't cancel the subscription immediately after cutover. Old contacts, services with stale MX records, and any forgotten internal integrations will surface during the first month or two. The licensed Workspace serves as your forwarding origin and emergency fallback.

Archive Workspace before final shutdown. Use Google Takeout per user to export their full Gmail to MBOX before deleting the account. Store these on cold backup. Users will request old emails months later.

If you're considering going back to Gmail later, see the Zoho to Gmail walkthrough. If Office 365 was on your shortlist, Workspace to Office 365 covers that path. For general IMAP-to-Gmail patterns that apply here, the IMAP to Gmail guide is useful background. And the complete email migration guide covers project sequencing.

Common errors#

AUTHENTICATIONFAILED from Gmail: app password missing, or 2-step verification not enabled (Gmail requires it before app passwords work). Or you're using OAuth and the migration tool doesn't have the right scopes.

AUTHENTICATIONFAILED from Zoho: app password missing, or you used the regular Zoho password instead.

Quota exceeded on Zoho: destination storage tier is too small. Upgrade the user's tier and resume.

Too many simultaneous connections on Zoho: lower concurrency to 3 to 4 per mailbox.

Message too large for destination on Zoho: message exceeds 30 MB. Save the attachment separately and either drop the message or re-import without the attachment.

Folder UTF-7 conversion error: a Gmail label has characters Zoho's IMAP doesn't accept. Rename the label in Gmail before re-running the migration of that user.