Migrate Zoho Mail to Gmail: IMAP Walkthrough for Real Cutovers

Zoho Mail is a thoughtful, deeply-featured business mail product that quietly wins comparison shoot-outs on price. Most teams that adopt it stay for years. The teams that leave usually do so because the rest of the business has standardised on Google Workspace, and the per-user economics of running two mail systems no longer make sense. Moving the mailbox from Zoho to Gmail is one of the cleaner migrations in this category because both sides speak modern IMAP and both honour INTERNALDATE on APPEND. The challenges are operational rather than protocol-level: Zoho's IMAP requires explicit enabling per user, two-factor accounts need app-specific passwords, and Gmail's label model does not map perfectly onto Zoho's tags. None of these are show-stoppers. They just require knowing what to expect before you start. This guide covers a single-user mailbox cutover with notes on how the same shape scales to a small team. It is written for the technical owner doing the move, not for an end user who has never opened an IMAP setting.

What you need on hand#

Zoho's IMAP server is reliable but it requires that the IMAP protocol be enabled for the specific user. This is a per-user toggle, not an org-wide one. The default state depends on which Zoho plan the org is on. For Zoho Workplace plans (Standard and above) IMAP is enabled by default; for the free Lite plan it is restricted. Check before you start. If your org disabled IMAP at the Control Panel level for security reasons, you need a temporary exception for the migration.

You will also need:

• The full Zoho Mail address.
• A Zoho app-specific password if two-factor authentication is enabled. Generate at accounts.zoho.com > Security > App Passwords.
• A Gmail account with enough storage. Personal Gmail caps at 15 GB across mail, Drive, and Photos by default.
• For Google Workspace destinations, a domain that is either already verified in the tenant or that you can verify before the cutover.
• A workstation that will not sleep for the duration. Plan on 60 to 120 minutes per 10 GB on Zoho's side.

If you are doing this for someone else, get explicit permission before generating an app password. Treat the app password like any other credential and revoke it as soon as the migration is verified.

Connection settings#

• Zoho IMAP host: imap.zoho.com
• Zoho IMAP port: 993 with SSL/TLS
• Zoho username: full email address
• Zoho password: account password, or app-specific password if 2FA is on
• Gmail IMAP host: imap.gmail.com
• Gmail IMAP port: 993 with SSL/TLS
• Gmail credential: account password (with app password if 2FA on) or OAuth

If the source is a Zoho data centre other than the global one (Zoho operates separate clusters in the EU, India, Australia, and elsewhere), the IMAP hostname will be region-specific: imap.zoho.eu, imap.zoho.in, imap.zoho.com.au. Check the Zoho Mail web URL the user signs in to and match the IMAP host accordingly. Connecting to the wrong region with the right credentials produces AUTHENTICATIONFAILED and looks identical to a wrong password.

Steps#

1. Inventory the Zoho mailbox

   Sign in to Zoho Mail at the user's regional URL. Walk the folder tree on the left. Note approximate sizes, message counts for the big folders, and any folders you do not want to migrate (most teams have an old Backups folder that has not been touched in five years and does not need to come along).

   Check whether the user has any Zoho tags applied at scale. Tags are Zoho-specific metadata that do not transfer over IMAP. If your taxonomy depends heavily on tags, plan to recreate the most important ones as Gmail labels after the migration. Take a screenshot of the tag list as a reference.

   Empty Trash unless you have a retention requirement to keep it. Spam should usually be skipped during the migration, not migrated, but if you have a Spam folder you want to keep, copy a few example messages to a custom folder first so they survive the move.

2. Enable IMAP and generate an app password

   In Zoho Mail, go to Settings > Mail Accounts > Configure IMAP. Confirm IMAP Access is set to Enable. If two-factor authentication is enabled on the account, switch to the Zoho Accounts page at accounts.zoho.com, open Security > App Passwords, and create a new password labelled Migration. Copy the password immediately. Zoho only shows it once.

   Region matters for app passwords

   If the user is in the Zoho EU or India cluster, generate the app password from the regional accounts URL (accounts.zoho.eu, for example), not the global one. Credentials issued in the wrong region will fail authentication even with the right hostname.

3. Prepare the Gmail destination

   For personal Gmail: in Gmail settings, open Forwarding and POP/IMAP and confirm IMAP is enabled. Check storage in Google One; if you are close to the 15 GB cap, prune or upgrade before starting.

   For Google Workspace: confirm the user has an active mailbox, IMAP is allowed in the admin console under Apps > Google Workspace > Gmail > End User Access, and 2-Step Verification or OAuth is configured. The Workspace approach generally uses OAuth on the destination side for reliability.

   Decide on a label prefix. Zoho/ is the common choice. It groups all imported folders together in the Gmail label list and avoids collisions with existing Gmail labels named Inbox or Archive.

4. Run a small dry run

   Pick a folder with 50 to 200 messages. Anything other than Inbox is fine; the goal is to validate the pipeline, not stress-test it. Configure the migration tool to migrate only that folder. Run it.

   Open Gmail and verify:

   • The folder appears as a label under the prefix you chose.
   • Dates are the original dates from Zoho, not today.
   • Read and unread states match.
   • Attachments open. Test a PDF and an image.
   • Subjects with non-ASCII characters render correctly.

   If the dry run looks wrong, fix the configuration before committing to the full job. Most issues show up here: a date-handling bug, a tool that decompresses MIME parts and re-encodes them differently, a folder name with embedded slashes that confuses Gmail's label parser.

5. Run the full migration

   Start the full sync at a quiet time. Zoho's IMAP server handles 4 to 8 parallel connections comfortably; the bottleneck is almost always Gmail's APPEND rate limit. Most tools default to two streams for safety.

   Keep the workstation awake. Disable lid-close sleep. Plug it in. Most migrations of this kind run 4 to 8 hours for a typical 20 to 40 GB business mailbox.

   You may see occasional Gmail throttle responses with messages like Too many simultaneous connections or Lookup failed - server is busy. The migration tool should back off and retry. If you see repeated OAuth2 token expired errors, the tool's token refresh logic is failing; restart the tool with a fresh token.

6. Verify and cut over

   After completion, search Gmail for known difficult items:

   • A PDF from at least two years ago.
   • A thread with accented characters in the subject.
   • A flagged Zoho message — flags do not transfer perfectly, but you can confirm the message body is present.
   • A Calendar invite — note that the calendar attachment carries, but the actual calendar event does not transfer over IMAP.

   Compare folder counts. They will be within a few percent of the Zoho counts.

   For DNS cutover, if you are moving the domain itself to Google Workspace, change MX records only after the IMAP migration is verified. New mail arriving at Google before the history has finished landing will mix into the migrated folders and confuse the conversation view. For personal use, set Zoho to forward to the new Gmail address under Settings > Mail Forwarding.

Gotchas worth remembering#

Gmail conversation threading reorders the apparent order of messages in the All Mail view. Even with INTERNALDATE preserved, Gmail groups messages that share the same Message-ID base or References header into a single thread, and the thread's timestamp is the latest message. This is not data loss — every message is still there with its original date — but it looks different in the Gmail UI than it did in Zoho. Users who are used to Zoho's strict per-folder timeline find this disorienting. Warn them.

Zoho's IMAP folder hierarchy uses / as the delimiter, while older IMAP servers used .. Modern migration tools handle both cleanly, but if you wrote your own script, double-check that subfolders like Projects/Acme end up as labels nested under Projects in Gmail rather than as a single flat label named Projects/Acme.

If you are running this against the Zoho EU cluster and seeing intermittent STARTTLS handshake failed errors, the issue is usually a network proxy intercepting TLS. The fix is to bypass the proxy for IMAP traffic or to run the migration from a network that does not do TLS inspection. Zoho's TLS configuration is current and modern; the failures almost always come from middleboxes downstream.

Errors you are likely to see#

• AUTHENTICATIONFAILED — wrong password, wrong region, or 2FA enabled without an app password.
• Too many simultaneous connections — Gmail throttling on the destination. Reduce parallel streams.
• OAuth2 token expired — tool's token refresh has failed. Restart with a fresh token.
• STARTTLS handshake failed — TLS interception in the network path. Bypass the proxy.
• Message too large for destination — Gmail rejects messages above about 50 MB. Rare from Zoho, but possible for old internal threads with several large attachments.

Communication and DNS#

For a domain migration (Zoho Workplace to Google Workspace), the DNS cutover sequence matters. Do not change MX records before the IMAP migration is finished. Plan a maintenance window. Lower the TTL on the existing MX records 24 hours before the cutover so the change propagates quickly. Migrate the history first, then change MX, then verify new mail is arriving in Google.

For personal use where you keep the Zoho address running, set up forwarding from Zoho to Gmail and a Send Mail As alias in Gmail so replies go out from the Zoho address. This is the same pattern used in the Gmail to Zoho migration, just reversed.

For users moving away from Zoho to a Microsoft destination, the Zoho to Office 365 walkthrough and Zoho to Outlook.com guide cover the same source side. The broader complete email migration guide puts these provider pairs in context with a checklist that works across any combination. For other IMAP sources moving to Gmail, the IMAP to Gmail reference is the place to start.

When something goes wrong#

If the migration tool crashes or the workstation reboots, restart and let it resume. IMAP migrations are append-only, so a restart never causes data loss; the worst case is a few duplicates that you can clean up afterwards. Most tools detect duplicates by Message-ID hash and skip them automatically.

If Gmail starts rejecting batches with quota errors, you have hit the per-day APPEND limit. Pause for a few hours and continue. The limit resets on a rolling window.

If you discover after the cutover that an important folder did not transfer, you can re-run the migration targeting only that folder. Provided the source is still live and the credentials still work, the tool will skip duplicates and pick up anything missing.