Answer first: Changing MX does not move old Zoho Mail. Historical mail leaves Zoho only if you copy it with IMAP (when the plan allows it), an admin ZIP/PST export, folder EML export, or a desktop client talking to both sides. New inbound mail leaves Zoho only after ArawaMail receiving is active and MX points at ArawaMail. There is no documented ArawaMail import wizard.
A familiar failure: someone “switched DNS,” then support@ still fills a Zoho tab for two days because TTL has not expired — and the old archive never moved at all.
What this cutover is (and is not)
This is a provider-specific runbook for Zoho Mail organization accounts. Product-fit lives on the ArawaMail vs Zoho Mail page. Google cutover lives in How to Move Business Email Off Google Workspace.
- Zoho Mail is not Zoho ZeptoMail. Transactional sending may already use a separate product and a separate SPF/DKIM setup.
- ArawaMail does not document a one-click mailbox import. Docs mention “imports” only as data removed if you delete a mailbox.
- Calendars, tasks, Streams, WorkDrive, and other Zoho Workplace apps do not follow MX.
How we checked this
On 12 September 2026 we re-read ArawaMail onboarding docs (Cloudflare zone, receiving before sending, email accounts, mailbox folders) and public Zoho help on IMAP hosts, export, and Free-plan protocol limits. Zoho still documents migration into Zoho more thoroughly than export out. Treat regional hosts and Free IMAP availability as account-specific: open Settings → Mail Accounts and read the servers printed for that user.
Before you touch MX
1. Inventory Zoho
- Domains and whether they are primary or alias domains.
- Users, aliases, groups, and forwarding rules.
- Any ZeptoMail or other sender already authenticating the same domain.
- Whether each mailbox can use IMAP. Forever Free and some data-center Free plans are web-and-app only: Zoho staff have stated IMAP/POP/ActiveSync are paid-plan features for many Free orgs.
2. Prepare ArawaMail without cutting traffic
- Add the domain and confirm an exact-match active Cloudflare zone. See How to Connect a Cloudflare Domain to ArawaMail and ArawaMail DNS Records.
- Do not confirm MX replacement until mailboxes exist.
- Create matching accounts and role addresses (info@, support@). Test sign-in.
- Map Zoho aliases and groups to real ArawaMail accounts, plus addressing, shared-inbox patterns, or a catch-all (exact mailbox → catch-all → discard).
- Note forwarding limits: destinations must verify within 24 hours; Free 1 / Pro 5 / Business 10 destinations; forwarded copies count toward transactional allowance.
How to copy historical Zoho mail
Pick the path your plan allows. IMAP is fastest when it is enabled. Export is the fallback when it is not.
| Method | Use when | Watch-outs |
|---|---|---|
| IMAP sync (paid / entitled accounts) | IMAP is on for the user | US paid often uses imappro.zoho.com:993; many Free/personal US accounts use imap.zoho.com:993; EU/IN use imap.zoho.eu / imap.zoho.in. SMTP is commonly 465 (SSL) or 587 (STARTTLS). Confirm the host printed in the account. |
| Admin ZIP / PST export | IMAP is blocked or mailboxes are large | Admin console can export user mail as ZIP; PST is commonly a paid-plan option. Downloads usually expire after about 30 days. Spam and Trash are excluded unless you include them. |
| User folder EML export | One folder or a mailbox without IMAP | Settings → Import/Export Emails (or Trident Mail → Export). EML or PST depending on the client. Files age out after about 30 days. |
| Desktop client on both sides | You can attach Zoho IMAP and ArawaMail IMAP | Do not publish placeholder ArawaMail hostnames. Use the hosts shown in ArawaMail Connect Device after receiving is active. See IMAP vs POP3. |
ArawaMail mailbox storage on public pricing is 1 / 10 / 50 GB (Free / Pro / Business). Inbox and sent stay until deleted, subject to that cap. Transactional API records are separate (45 / 60 / 90 days).
During cutover
- Lower MX TTL well before the change window. Snapshot current MX, SPF, DKIM, and DMARC.
- Activate ArawaMail receiving only when you are ready for new inbound mail to leave Zoho. Sending requires receiving first.
- Enable sending (DKIM CNAMEs and custom MAIL FROM on Cloudflare). Send a test from a real From address people can reply to.
- Keep Zoho seats live through the TTL window. Late mail will still hit old MX until caches expire.
- Run a final copy of anything that landed in Zoho after the first archive.
What will not land in ArawaMail
- Zoho Calendar, tasks, notes, Streams, WorkDrive, CRM bindings.
- ZeptoMail templates, suppression lists, and bounce webhooks — re-point those senders separately.
- Spam older than Zoho’s export rules, and ArawaMail spam (excluded from search and inbound webhooks, deleted after 30 days).
After: when to cancel Zoho
Cancel seats only after all of these stay true for a full TTL cycle:
- New inbound arrives in ArawaMail mailboxes, not Zoho.
- Outbound from people and from the app authenticates (aligned SPF/DKIM/DMARC).
- Aliases and forwarding match the old directory.
- A final historical copy finished.
Disabling an ArawaMail mailbox blocks IMAP/SMTP/MCP without deleting data. Permanent delete has no recovery window — do not “clean up” until you are sure.
Compare plans on ArawaMail pricing if storage or forwarding destinations will grow with the import.
FAQ
Will switching MX move my old Zoho mail?
No. MX only changes where new messages are delivered. Copy history first.
What if my Zoho Free plan has no IMAP?
Use admin ZIP/PST or user EML export, then import through a desktop client into ArawaMail after receiving is active. Do not promise an IMAP copy on Forever Free.
Which IMAP host should I use?
Use the host printed in Zoho Settings for that account. Typical patterns: imap.zoho.com or imappro.zoho.com on port 993; regional imap.zoho.eu / imap.zoho.in. SMTP 465 or 587.
Can I keep Zoho alive during DNS cache?
Yes — you should. Leave Zoho licensed until caches die and the final copy is done.
When is it safe to delete the Zoho organization?
After inbound, outbound, aliases, and any leftover ZeptoMail or app senders are stable on the new stack — not on the day you click “activate receiving.”