Migrating business email to Zoho Mail is a structured process — not a simple click-and-go. Done correctly, your team experiences minimal downtime and zero data loss. Done incorrectly, email can go missing during the cutover window or route to the wrong server for days.
This guide covers the complete migration process from any email platform — cPanel hosting, Google Workspace, Microsoft 365, Rediffmail or on-premises servers — to Zoho Mail in India.
Before You Start — Pre-Migration Checklist
Before touching any DNS records, complete this checklist:
- Create a Zoho Mail account and select your plan (Free, Mail Lite, or Mail Premium)
- Add and verify your domain in Zoho Mail admin
- List all mailboxes to be migrated (names and current passwords)
- Export a backup of all current email (as .PST, .MBOX or via IMAP backup tool)
- Identify any email aliases, distribution lists and forwarding rules in your current setup
- Note the TTL value of your current MX records (lower it to 300 seconds 24–48 hours before cutover)
- Communicate the maintenance window to your team
Lowering the MX record TTL to 300 seconds (5 minutes) 24–48 hours before cutover is critical — it ensures DNS changes propagate quickly when you switch, minimising the window where email could route to the old server.
Step 1 — Create Zoho Mail Account and Add Your Domain
- Sign up at mail.zoho.in (for India data centre) or mail.zoho.com
- Choose your plan — Free Forever, Mail Lite or Mail Premium
- Navigate to Admin Console → Domains → Add Domain
- Enter your domain name (e.g. yourcompany.com)
- Zoho will provide a TXT verification record — add this to your DNS provider
DNS TXT record for domain verification:
Type: TXT
Host: @ (or your domain root)
Value: zoho-verification=xxxxxxxxxxxx (Zoho provides this)
TTL: 300
Wait for DNS propagation (typically 10–30 minutes, up to a few hours depending on your DNS provider) and click Verify in Zoho Admin.
Step 2 — Create All User Accounts
Before switching MX records, create all user mailboxes in Zoho Mail:
- Go to Admin Console → User Management → Add User
- Create each user with their display name and email address
- Set temporary passwords — users will be prompted to change on first login
- Create any email aliases (e.g. info@, support@, sales@)
- Set up distribution groups and shared mailboxes
It is important to create all accounts before the MX cutover so that email arriving after the switch has a valid destination.
Step 3 — Configure MX Records (The Cutover)
This is the step that redirects all incoming email from your old provider to Zoho Mail. Do this during a low-traffic period — early morning or weekend.
Remove your current MX records from your DNS provider, then add Zoho's MX records:
For zoho.in (India data centre — recommended for Indian businesses):
| Type | Host | Value | Priority |
|---|---|---|---|
| MX | @ | mx.zoho.in | 10 |
| MX | @ | mx2.zoho.in | 20 |
| MX | @ | mx3.zoho.in | 50 |
For zoho.com (Global data centre):
| Type | Host | Value | Priority |
|---|---|---|---|
| MX | @ | mx.zoho.com | 10 |
| MX | @ | mx2.zoho.com | 20 |
| MX | @ | mx3.zoho.com | 50 |
After adding MX records, set TTL to 300 seconds. DNS propagation typically completes within 15–60 minutes when TTL was pre-lowered.
Verify MX records are live using an online MX lookup tool before proceeding.
Step 4 — Set Up SPF Record
The SPF record tells receiving mail servers that Zoho is authorised to send email on behalf of your domain. Without SPF, outgoing email from Zoho Mail may be flagged as spam.
Remove any existing SPF record for your domain, then add:
For zoho.in (India data centre):
Type: TXT
Host: @
Value: v=spf1 include:zoho.in ~all
TTL: 3600
For zoho.com (Global):
Type: TXT
Host: @
Value: v=spf1 include:zoho.com ~all
TTL: 3600
Important: If you send email from other services (e.g. a CRM, bulk email tool, or website contact form), include those services in the same SPF record:
v=spf1 include:zoho.in include:sendgrid.net ~all
Only one SPF record is allowed per domain. If you have multiple sources, combine them into a single record.
Step 5 — Configure DKIM
DKIM adds a cryptographic signature to every outgoing email, allowing recipients to verify it genuinely came from your domain.
- In Zoho Mail Admin Console, go to Email Authentication → DKIM
- Click Add Selector — Zoho will generate a public key
- Add the DKIM TXT record to your DNS:
Type: TXT
Host: zoho._domainkey (or the selector name Zoho provides)
Value: v=DKIM1; k=rsa; p=MIGfMA0GCSq... (Zoho provides the full value)
TTL: 3600
- Return to Zoho Admin and click Verify DKIM once DNS has propagated
- Enable DKIM signing for your domain
Step 6 — Migrate Historical Email Data
Switching MX records means new email arrives in Zoho Mail from that point forward. But your old email — weeks or months of inbox history — still sits on the old server. You need to migrate it.
Option A — IMAP Migration (recommended for most setups)
Zoho Mail includes a built-in email migration tool that connects to your old server via IMAP and pulls all historical data across.
- Go to Admin Console → Migration Assistant
- Select your source (cPanel/Generic IMAP, Google Workspace, Microsoft 365, etc.)
- Enter the IMAP server details and credentials for each user
- Zoho will begin migrating all folders, including Inbox, Sent, Drafts and custom folders
- Migration runs in the background — users can start using Zoho Mail immediately
Migration time depends on mailbox size: a 5 GB mailbox typically migrates in 1–3 hours. A 20 GB mailbox can take 6–12 hours. Large organisations should migrate users in batches.
Option B — PST / MBOX Import
For Microsoft 365 or Outlook users, export mailboxes as .PST files and import them via Zoho Mail's import tool. For cPanel or Linux-based servers, .MBOX format is common.
Option C — Managed Migration (Cloudfy handles everything)
As an authorised Zoho Mail partner in India, Cloudfy Systems manages the complete migration process — IMAP configuration, data transfer monitoring, error handling and post-migration verification. Contact us at +91 97600 50555 if you prefer not to handle this yourself.
Step 7 — Configure Email Clients
After migration, every user needs to reconfigure their email client (Outlook, Thunderbird, Apple Mail, mobile devices) to connect to Zoho Mail.
Zoho Mail IMAP Settings (for zoho.in):
| Setting | Value |
|---|---|
| Incoming server | imap.zoho.in |
| Incoming port | 993 (SSL) |
| Outgoing server | smtp.zoho.in |
| Outgoing port | 465 (SSL) or 587 (TLS) |
| Username | Full email address |
| Authentication | Password or App-specific password |
For mobile devices (Android / iOS): Use the Zoho Mail app for the best experience, or configure via ActiveSync using mail.zoho.in as the server address.
Step 8 — Post-Migration Verification
Once migration is complete, verify the following before communicating that the switch is done:
- Send a test email from an external address and confirm it arrives in Zoho Mail
- Send a test email from Zoho Mail to an external address and confirm delivery
- Check that all historical email folders are present and accessible
- Verify that email aliases and distribution lists are routing correctly
- Run an MX lookup to confirm old MX records are fully removed
- Check email headers on a received message to confirm DKIM signing is active
- Verify SPF by checking a received email's authentication headers
Common Migration Issues and Solutions
Email still arriving at old server: DNS hasn't propagated fully. Wait for TTL to expire and check again. If TTL was not pre-lowered, this can take up to 48 hours.
Outgoing email landing in spam: SPF or DKIM is not yet configured or hasn't propagated. Verify both records using an online DNS checker before sending bulk emails.
IMAP migration stuck or slow: Large mailboxes take time. Check Zoho Admin for migration status and error logs. If source server has rate limiting, migration may pause and resume automatically.
Missing email during cutover window: Email sent between your old server going offline and Zoho's MX records going live may queue at the sending server and redeliver automatically. Always keep the old server accessible for 48–72 hours post-cutover.
Frequently Asked Questions
How long does migration to Zoho Mail take?
Basic setup — domain verification, MX records, SPF and DKIM — takes 24–48 hours. Email data migration depends on mailbox size: a 5 GB mailbox migrates in 1–3 hours, larger mailboxes take longer. Full migration for a 10-user team with moderate mailbox sizes typically completes within one business day.
Will email be lost during the Zoho Mail migration?
No — if the migration is done correctly. The key steps that prevent email loss are: keeping the old server active during the transition period, pre-lowering MX TTL to ensure fast DNS propagation, and running IMAP migration to bring historical data across. Cloudfy Systems follows this process for all managed migrations.
Can I migrate from Google Workspace to Zoho Mail?
Yes. Zoho Mail's migration assistant supports Google Workspace as a source via IMAP. Cloudfy Systems handles migrations from Google Workspace, Microsoft 365, cPanel, Rediffmail, on-premises Exchange and any IMAP-compatible server.
Do I need to inform my contacts about the migration?
No. Your email address stays the same — only the underlying infrastructure changes. Contacts sending to you will not notice any difference after the MX records propagate.
What happens to email during DNS propagation?
During propagation (typically 15–60 minutes when TTL is pre-lowered), some email may route to the old server and some to Zoho Mail. As long as the old server remains active and accepts email during this window, all messages will be delivered correctly — either directly in Zoho or forwarded from the old server.
