Migrate Zoho Mail to Fastmail (2026 Guide)

Zoho Mail to Fastmail is a migration most often driven by deliverability frustration — Zoho's outbound reputation has been spotty for some domains, and Fastmail's is consistently strong. The mechanics are clean because Zoho exposes proper IMAP and Fastmail accepts standard IMAP-to-IMAP imports. The complications are regional (Zoho's per-region IMAP hostnames), administrative (Zoho's per-user IMAP enable toggle that's off by default in some plans), and around the data that lives outside the mailbox (labels, streams, tasks, custom folder permissions). This guide walks through the full process with the Zoho-specific details that matter.

Zoho's data model#

Before you migrate, understand what Zoho organizes the mailbox into.

In the IMAP layer: INBOX, Sent, Drafts, Trash, Spam, Archive, and any user-created folders. Standard IMAP message metadata (flags, internal date, attachments) all migrates cleanly.

Outside IMAP — within Zoho Mail: Labels (separate from folders, applied additively), Tags, Reminders, Snooze metadata, and custom flag colors. None of these come across IMAP.

Outside IMAP and outside Zoho Mail: Zoho Streams (the activity/collaboration overlay), Zoho Tasks (separate app), Zoho Notes, Zoho Calendar, Zoho Contacts, Bookmarks, and any Zoho Workplace integrations. Each is a separate workstream if it matters.

For most migrations, the mail layer is the priority and the rest gets handled best-effort. If users heavily rely on Streams or Tasks, the migration becomes more complex — Fastmail doesn't have direct equivalents for these.

Pre-migration audit#

Inventory mailboxes#

From the Zoho Mail Admin console (mailadmin.zoho.com), export the list of users. Note:

• Mailbox size per user.
• Mailbox plan (Free, Mail Lite, Mail Premium, Workplace tier) — each has different IMAP enablement defaults.
• Aliases (in Admin console → Users → Aliases).
• Groups and distribution lists (Admin → Groups).
• Shared mailboxes (Admin → Shared Inboxes for Workplace tiers).

Each of these needs a corresponding setup on Fastmail.

Identify region#

Your Zoho account is hosted in one of several regions. The region determines IMAP server hostname:

• US: imap.zoho.com
• EU: imap.zoho.eu
• India: imap.zoho.in
• Australia: imap.zoho.com.au
• China: imap.zoho.com.cn
• UAE: imap.zoho.com.sa
• Saudi Arabia: imap.zoho.sa

If you don't know your region, log into Zoho Mail webmail and check the URL — mail.zoho.com is US, mail.zoho.eu is EU, etc. Use the matching IMAP hostname.

Document labels and shared resources#

Open Zoho Mail webmail as an admin user. Browse to a sample mailbox. Document:

• Labels in use (Labels section of the sidebar).
• Shared folder permissions if any users share folders.
• Outgoing filters and rules (Settings → Filters).
• Outgoing auto-reply configs (Settings → Out of Office).

None of this migrates automatically — plan to recreate on Fastmail or accept the loss.

Fastmail setup#

Create accounts#

Sign up at fastmail.com. The Business plan supports custom domains and centralized billing; Standard tier with 30 GB storage works for most users.

Create accounts matching the Zoho addresses. Use the same primary email — user@yourdomain.com on Zoho should be user@yourdomain.com on Fastmail.

Verify domain#

In Fastmail admin (Settings → Domains), add your domain. Add the TXT verification record at your DNS provider. Leave MX pointed at Zoho for now.

Generate Fastmail app passwords#

For each user: Fastmail account → Settings → Privacy & Security → App Passwords → New. Name it "Migration", set scope to "Mail (IMAP/SMTP)". Save the generated password securely — Fastmail shows it once.

For background on what app passwords do, our app password glossary entry covers the essentials.

Storage planning#

Zoho mailboxes are usually comparable in size to source, with no significant growth on Fastmail because both use folders rather than labels. Plan for 1.0–1.1× growth if some users use Zoho labels heavily and you choose to recreate them as folders on Fastmail.

Zoho-side prep#

Enable IMAP#

Per-user or globally:

• Per-user: Zoho Mail Settings (each user's settings, not admin) → Mail Accounts → POP/IMAP → Enable IMAP Access.
• Globally: mailadmin.zoho.com → Mail Settings → Mail Account Policies → enable IMAP for all users.

Globally is faster for organizations with many users.

Generate app passwords per user#

If 2FA is enabled (which it should be), each user generates an app password from accounts.zoho.com → Multi-Factor Authentication → Application-Specific Passwords. Name it "Migration".

If 2FA is disabled, the regular mailbox password works for IMAP. But enabling 2FA across your org before migration is good security practice, and it's the right time to do it because you're touching the auth flow anyway.

Lower DNS TTL#

24 hours before MX cutover, drop your MX record TTL to 300 seconds in whatever DNS provider hosts your domain.

Choosing your tool#

Fastmail's built-in importer#

Fastmail (Settings → Import) supports IMAP sources. Provide Zoho's IMAP host, port 993, your email address, and the app password. Fastmail's import servers will pull from Zoho.

Works well for: small organizations (under 10 users), single-user migrations, anyone who doesn't want to install software.

Limitations: one mailbox at a time (per Fastmail user account), no delta sync, error messages are sparse.

Desktop IMAP tool#

A local tool like Mailbox Taxi authenticates to both Zoho and Fastmail over IMAP and copies messages folder-by-folder. Desktop-first, with concurrency control and detailed per-message logging.

Wins for: multi-user organization migrations, parallel mailbox processing, audit trails, delta sync after MX cutover, custom folder mapping.

For background on IMAP itself, including how STARTTLS, UID, and SEARCH work in migration contexts, the IMAP protocol glossary is useful reading.

Hybrid#

Fastmail importer for bulk on small org, desktop tool for delta. Or for larger orgs, use the desktop tool for both bulk and delta.

Step-by-step#

1. Pilot two mailboxes

   Pick a light and a heavy mailbox. Run end-to-end. Validate:

   • Folder structure matches between Zoho and Fastmail.
   • Message counts per folder within 1%.
   • Sent items in Sent folder only (no duplicates from labels).
   • Custom folder names preserved correctly.
   • Non-English folder names (Devanagari for Indian users, Cyrillic, etc.) appear correctly on Fastmail.

   If the pilot reveals issues with folder mapping or label handling, fix the config before the bulk run.

2. Run the bulk pre-sync

   48 hours before MX cutover. Cap concurrency at 3–4 threads per mailbox. Zoho's per-mailbox connection limit is around 8, but practical safe concurrency is lower.

   If you're migrating 20+ mailboxes, stagger their start times by 10 minutes each to avoid hitting Zoho's per-IP limits. Aggressive parallelism triggers brief IP throttles that take 15–30 minutes to clear and can stall your entire migration.

   For a 25-user organization with 15 GB average mailbox sizes, expect 72–96 hours of bulk sync. Larger orgs scale linearly.

3. Set up forwarding from Zoho

   24 hours before MX cutover, set up forwarding on each Zoho mailbox to the matching Fastmail address. From Zoho Mail Settings → Forwarding → Add forwarding address. Verify the destination (Fastmail will receive a verification email).

   After verification, enable forwarding. From this moment, mail to Zoho is also copied to Fastmail. This gives you continuous coverage through MX cutover.

4. Cut MX to Fastmail

   At your cutover time, update MX records to Fastmail's published values:

   • Priority 10: in1-smtp.messagingengine.com
   • Priority 20: in2-smtp.messagingengine.com

   (Verify exact values in your Fastmail admin console.)

   Save. Verify propagation with dig MX yourdomain.com @8.8.8.8 and dig MX yourdomain.com @1.1.1.1. Send a test message from external accounts.

5. Run the delta sync

   48 hours after MX cutover, run a delta against each Zoho mailbox. With forwarding configured, the delta should be very small — most messages arrived via forwarder already. Without forwarding, expect a few percent of total volume.

   UID-based dedup means existing migrated messages won't duplicate. Verify by spot-checking message counts post-delta against pre-delta.

6. Import contacts and calendars

   Per-user from Zoho:

   • Contacts: contacts.zoho.com → Settings → Export → vCard. Import into Fastmail → Contacts → Import.
   • Calendar: calendar.zoho.com → Settings → Import & Export → Export → iCal. Import into Fastmail → Calendar → Import.

   Tasks and Notes don't have a direct Fastmail equivalent — accept the loss or keep Zoho as an archive.

7. Update SPF, DKIM, DMARC

   SPF: v=spf1 include:spf.messagingengine.com ~all. Remove include:zoho.com or any Zoho-specific include.

   DKIM: enable in Fastmail admin (Settings → Domains → DKIM) and copy the CNAME records into DNS at your registrar.

   DMARC: keep existing record if monitoring is in place; otherwise add v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com and monitor for a week before tightening.

8. Recreate filters and groups

   Zoho filters (Settings → Filters) need to be manually recreated as Fastmail Rules (Fastmail Settings → Rules). The configuration model is similar but the UI is different.

   Zoho Groups become Fastmail's group addresses (Settings → Domains → Aliases & Groups) — recreate membership manually.

   Distribution lists work similarly: in Fastmail, create a group with the appropriate member list.

9. Decommission Zoho

   After 30 days of clean operation, cancel the Zoho subscription. Don't rush — 30 days catches edge cases where users discover missing messages or need historical access.

   Before cancelling, export anything from Zoho's other apps (Tasks, Notes, etc.) that isn't part of the mail migration. Once the Zoho account is gone, those exports aren't available either.

Common failure modes#

AUTHENTICATIONFAILED with correct credentials#

Usually IMAP isn't enabled on the mailbox. Per-user setting in Zoho Mail Settings → Mail Accounts → POP/IMAP → Enable IMAP Access. If it's already on, the password may be wrong — verify by logging into webmail with the same credentials.

Too many simultaneous connections#

Zoho's connection cap is around 8 per mailbox and softer caps per IP. Drop concurrency. Wait 10–15 minutes for the throttle to clear. Stagger mailbox starts going forward.

Wrong region IMAP host#

If you're using imap.zoho.com but your account is EU-hosted, you'll see AUTHENTICATIONFAILED even with correct credentials. Verify region and use the matching IMAP host.

Folder names with non-ASCII characters#

Modern tools handle modified UTF-7 correctly for non-ASCII folder names. Older tools may produce garbled folder names on Fastmail. Verify in pilot.

Sent items appearing in multiple folders#

Zoho Sent should map to Fastmail Sent cleanly. If you see duplicates, your tool may be importing both the Sent folder and an "All Mail" pseudo-view. Most tools don't have this issue on Zoho (unlike Gmail), but spot-check.

Storage quota hit on Fastmail mid-migration#

If a user's mailbox exceeds the Fastmail plan storage during migration, the import halts. Upgrade the plan and resume. To avoid this, audit Zoho mailbox sizes before migration and pick the matching Fastmail tier.

Comparing alternatives#

For organizations weighing Gmail instead of Fastmail, the Zoho to Gmail walkthrough covers Google as the destination. For desktop-client-only users, Zoho to Outlook covers using Outlook as a client against either source or destination.

For the reverse direction (Fastmail to Gmail), see Fastmail to Gmail.

Validation#

Per-user:

• Folder count matches between Zoho and Fastmail.
• Message count per folder within 1%.
• Sent items present and ordered correctly.
• Non-ASCII folder names appear correctly.
• Mobile clients connect successfully.

Per-tenant:

• SPF includes Fastmail, excludes Zoho.
• DKIM signing outbound.
• DMARC reports arriving.
• All aliases recreated.
• All forwarders/groups recreated.
• Test mail flows from external Gmail, Outlook.com, and external accounts work correctly.

If validation passes, the migration is done. Wait 30 days. Then cancel Zoho.