How to Set Up and Migrate Email to Zoho Mail

Moving business email needs more care than changing one DNS record. A safe Zoho Mail migration creates every account first, copies existing messages, tests a small group, changes mail delivery, and keeps the old service available for a final catch-up pass.

This guide explains how to migrate email to Zoho Mail without losing messages. It covers domain verification, users, IMAP migration, MX records, SPF, DKIM, DMARC, testing, and rollback.

Before You Start the Zoho Mail Migration

Choose the Zoho Mail plan and data centre that fit your business before adding users. Plans, storage, migration features, and client access can change by region, so check the current Zoho information instead of relying on an old “free forever” claim.

• List every mailbox, alias, group, shared address, forwarding rule, and catch-all.
• Record mailbox sizes, quotas, contacts, calendars, signatures, filters, and mobile or desktop clients.
• Export or back up important mail and groupware data.
• Confirm that you can edit the authoritative DNS zone.
• Lower the MX record TTL before the planned cutover when possible.
• Keep the old mail service paid and active throughout migration and rollback.
• Create a separate recovery administrator and enable multi-factor authentication.

IMAP normally moves email folders and message state. It does not automatically move every contact, calendar, rule, signature, or provider-specific feature. Zoho offers dedicated migrations for some providers, including Google Workspace and Microsoft 365, which may transfer more data.

1. Add Your Domain to Zoho Mail

Sign in to the Zoho Mail Admin Console, open Domains, and add the domain used after the @ sign in your email addresses. Check the spelling carefully. Pick the correct organization and regional data centre because the DNS values shown later can differ by region.

2. Verify Domain Ownership

Zoho supports TXT, CNAME, HTML, and one-click verification for selected DNS providers. TXT verification is a simple choice for most administrators:

1. In Zoho Admin Console, copy the unique TXT verification value for your domain.
2. Open the DNS service that controls the domain’s nameservers.
3. Add the TXT record at the host Zoho shows, usually the root domain.
4. Save it and wait for the record to become publicly visible.
5. Return to Zoho and select Verify TXT record.

Use the exact value generated for this domain. Do not copy a verification token from another tutorial or another domain. Domain verification proves ownership; it does not send incoming email to Zoho and should not interrupt the current service.

3. Create Users, Groups, and Aliases

Create all destination users before starting the migration. Then recreate aliases, groups, shared addresses, and required routing. Give each mailbox enough quota for its source data.

Start with three or four pilot users, as Zoho recommends. Include a small mailbox, a large mailbox, a user with nested folders, and an important business user. Send login instructions securely and require MFA.

4. Prepare the Old Mail Server

• Confirm the source IMAP hostname and use trusted TLS on port 993.
• Check whether IMAP access must be enabled.
• Use OAuth, an administrator migration method, or temporary app passwords where supported.
• Do not place mailbox passwords in an unprotected spreadsheet, ticket, or chat.
• Check source connection limits so the migration does not lock accounts or overload the server.

If you prefer a command-line transfer or need more control, our safe Imapsync migration guide explains protected credentials and repeat passes.

5. Add an IMAP Migration in Zoho

In Zoho Mail Admin Console, open Data Migration and create a migration. Choose the provider-specific option when it matches your source. Otherwise, choose IMAP and enter the source hostname, port 993, SSL, and a conservative connection limit.

Add or import the pilot accounts and map each source address to the correct Zoho user. Start the pilot, then review the account report for authentication failures, skipped messages, unsupported folders, message-size limits, and quota problems. Correct errors and rerun the affected accounts.

6. Run the First Migration Before Changing MX

Copy the bulk of the old email while incoming messages still reach the old provider. This reduces cutover pressure and gives users time to check their folders, dates, attachments, flags, and message counts.

Do not cancel the source service or delete old messages. Run the full group only after the pilot is accepted. Keep a record of every account’s source count, migrated count, errors, and user approval.

7. Change MX Records to Zoho Mail

When accounts exist and the first migration is complete, schedule a quiet cutover window. Open the domain’s DNS zone and use the exact MX hosts and priorities shown in your Zoho Admin Console. Zoho uses different data centres, so generic MX values copied from an old article may be wrong for your organization.

1. Confirm that all required users, groups, and aliases exist.
2. Take a screenshot or export of the working old DNS records.
3. Add Zoho’s regional MX records and remove conflicting old-provider MX records.
4. Preserve unrelated website, verification, and service records.
5. Check the public MX result from more than one network or DNS lookup.

DNS caches follow the previous TTL, so some senders may still deliver to the old server for a while. That is why the old mailboxes must remain available.

8. Configure SPF, DKIM, and DMARC

SPF

Publish the SPF value shown for your Zoho region. A domain should have one SPF TXT record. If another approved service also sends mail for the domain, merge its mechanism into the same record instead of publishing a second SPF record.

DKIM

In Zoho Admin Console, create a DKIM selector, publish its TXT record in DNS, verify it, and enable signing. Send a test message and inspect the headers to confirm DKIM passes.

DMARC

Configure SPF and DKIM first. A new DMARC rollout can begin with monitoring, such as p=none and an aggregate-report address you control. Review every legitimate sender, fix alignment, and then move gradually to quarantine or reject. A strict policy added before all senders are known can block real business email.

9. Run Final Catch-Up Passes

After MX changes, run the Zoho migration again for mail that reached the old server during DNS propagation. Repeat it after the old MX TTL has passed and source delivery becomes quiet. Check both old and new mailboxes before declaring the move complete.

10. Test the New Mail Service

• Send inbound messages from Gmail, Outlook, and another outside domain.
• Send outbound messages to external and internal users.
• Reply, forward, and test attachments.
• Check aliases, groups, shared addresses, and forwarding.
• Inspect headers for SPF, DKIM, and DMARC results.
• Check Spam and quarantine for missing tests.
• Test webmail, mobile apps, and approved IMAP/SMTP clients.
• Confirm old folders, recent mail, sent mail, and message counts.

Zoho Mail Migration Rollback Plan

If mail delivery fails during cutover, restore the saved old MX records while the source service is still active. Cached DNS means the change is not instant, so monitor both providers. Correct the Zoho accounts or DNS, repeat the migration, and try the cutover again. Do not remove the old service until users approve the result and your agreed rollback period ends.

Security Checks After Migration

• Require MFA for administrators and users.
• Keep at least two controlled recovery administrators.
• Use least privilege for delegated administrators.
• Revoke temporary app passwords and source migration access.
• Review login, audit, forwarding, and mail-delivery reports.
• Disable forgotten test accounts and protect backup exports.

Frequently Asked Questions

Is Zoho Mail free for a custom domain?

Plan availability and features vary by region and can change. Check Zoho’s current pricing page and confirm that your plan supports the storage, migration, mobile, IMAP, and administrative features you need.

Should I change MX before migrating email?

No. Add and verify the domain, create users, and run a pilot and initial migration first. Change MX during the planned cutover, then run catch-up passes.

Will there be downtime?

A well-planned migration can keep mail flowing, but senders may use old cached MX records for a period. Keep both services active, monitor both, and copy late messages.

Does IMAP migrate contacts and calendars?

Standard IMAP migration is mainly for email folders and messages. Use Zoho’s provider-specific migration or separate export and import steps for contacts, calendars, and other groupware data.

Conclusion

A safe Zoho Mail migration is a staged process: verify the domain, build the accounts, pilot and copy mail, change the regional DNS values, enable authentication, run catch-up passes, and test everything. Keeping the old provider available is what makes rollback and late-message recovery possible.

---

Reviewed and updated: August 2026. The workflow was checked against Zoho’s official guides for domain verification, migration planning, IMAP migration, DKIM, and DMARC.