Skip to content
Koltrix
FeaturesPricingCompareCustomersDocsBlog
Sign inStart 7-day free trialOpen app
Guides

Migrating Email Away From Zoho Mail, Step by Step

How to move a domain's mail off Zoho Mail without losing messages: export options, recreating aliases and groups, DNS changes, and checking every integration.

Koltrix Team5 min read
Stone arch bridge spanning a rocky river gorge
Photo by Adrien CÉSARD on Unsplash
On this page(10 sections)
  1. Before you start: what's in your Zoho org
  2. Step 1: Inventory every sender
  3. Step 2: Decide what happens to existing mail
  4. Step 3: Rebuild the address map on the new provider
  5. Step 4: Publish the new provider's authentication records
  6. Step 5: Switch MX
  7. Step 6: Reconnect integrations
  8. Step 7: Clean up
  9. Fair warning about what you might miss
  10. Key takeaways

Zoho Mail is a solid, inexpensive mail host, and plenty of teams that leave it do so for reasons unrelated to Zoho itself: a merger, a new requirement, or a wish to put mailboxes and product email in one place. Whatever the reason, the move goes smoothly if you treat it as a sequence rather than a single DNS change.

This guide walks through that sequence. Zoho's admin console changes over time and differs slightly by data center region, so confirm exact menu paths in Zoho's own documentation as you go.

Before you start: what's in your Zoho org

Zoho Mail organizations tend to accumulate more than mailboxes. Open the admin console and write down:

  • Users and their mailboxes, including anyone who left but whose mailbox was kept.
  • Aliases on each user. Zoho lets you add several email aliases per user, and they're easy to forget.
  • Groups, which work as shared addresses and distribution lists. Note each group's members and whether it accepts mail from outside the organization.
  • Domain aliases, if you receive mail on more than one domain.
  • Mail forwarding and filters set up by users that people rely on without thinking about.
  • Other Zoho apps your team uses: CRM, Desk, Books. Some of these send mail or integrate with Zoho Mail, and leaving the mail service may affect them.

That last point matters. Zoho's strength is its suite, and if your CRM or help desk is Zoho too, check how each one sends and receives mail before you change anything. You may decide to keep some Zoho apps and move only the mailboxes.

Step 1: Inventory every sender

List every system that sends mail as your domain, not just Zoho. Look at your SPF record, read DMARC aggregate reports if you have them, and check the settings of your invoicing, CRM, forms and support tools. Our post on inventorying everything that sends as your domain has a template.

Step 2: Decide what happens to existing mail

Your options:

  1. Import into the new provider, if it offers an importer that can connect to Zoho over IMAP or read exported files.
  2. Export and archive. Zoho Mail provides ways for users and admins to export mailbox data; check the current options for your plan.
  3. Keep the Zoho account read-only for a period, then export before cancelling.

Zoho supports IMAP, which means a desktop client such as Thunderbird can also download a full copy of a mailbox to local storage. It's slower than an admin export, but it works for small teams and gives you a file-based archive.

If you're moving to Koltrix, note that there's no mailbox importer in v1; pulling mail across over IMAP is planned for the release after launch. So plan on exporting and archiving, or keeping Zoho readable for a while.

Step 3: Rebuild the address map on the new provider

Create an address map before you create anything. One row per address:

Address Type in Zoho Type at destination Delivers to Notes
ana@ User mailbox Mailbox Ana Has alias accounts@
accounts@ Alias of ana@ Alias or shared mailbox Ana, later finance hire Consider making it shared
support@ Group (3 members) Shared mailbox Ana, Ben, Chen Accepts external mail
team@ Group (all staff) Group or alias Everyone Internal only

The "type at destination" column is a chance to clean up. Groups used as customer-facing addresses often work better as shared mailboxes, where everyone sees the same thread and can tell who replied. Aliases that everyone on a team needs probably should be shared too.

Then create every mailbox, alias and shared address on the new provider.

Step 4: Publish the new provider's authentication records

While Zoho is still receiving mail:

  • Verify your domain on the new provider.
  • Add the new provider's DKIM record. It will use its own selector, so it doesn't conflict with Zoho's DKIM record.
  • Update SPF to authorize both. Zoho's SPF include depends on your data center region (for example zoho.com or zoho.eu). Keep it alongside the new provider's mechanism during the transition, and stay under SPF's ten-lookup limit.
  • Check DMARC is published, at least at p=none with reports going somewhere you read.

Send test mail from the new provider to a few external accounts and inspect the authentication results.

Step 5: Switch MX

  1. Lower the MX TTL to around 300 seconds at least a day ahead.
  2. Replace Zoho's MX records with the new provider's. Zoho's MX hostnames also depend on region.
  3. Keep Zoho mailboxes active; some senders will deliver to Zoho until cached DNS expires.
  4. Check both systems for a day or two. Use an MX lookup to confirm what the world sees.

The cut-over steps mirror our Google Workspace DNS checklist closely, and that post explains why the order matters.

Step 6: Reconnect integrations

Anything that authenticated against Zoho's SMTP servers will break when you remove those mailboxes. Typical culprits:

  • Website contact forms using a Zoho mailbox's SMTP credentials.
  • Printers and scanners that email documents.
  • Accounting or CRM tools configured to send through Zoho.
  • Mail clients on phones and laptops with saved Zoho accounts.

Repoint each to the new provider's SMTP relay or API, or to the provider each tool recommends, and send a test from every one.

Step 7: Clean up

  • Remove Zoho's SPF include once no mail goes out through Zoho
  • Remove Zoho's DKIM record after sending through Zoho has stopped
  • Remove Zoho's domain verification record if no other Zoho app needs it
  • Confirm each address in your map receives external mail
  • Export remaining mailboxes and test that the archive opens
  • Downgrade or cancel the Zoho Mail subscription, keeping any Zoho apps you still use
  • Raise the MX TTL back to normal

Fair warning about what you might miss

People leaving Zoho sometimes underestimate what they got for the price: IMAP, POP and ActiveSync support for every client, a choice of hosting regions, and a suite that covers a lot of back-office work. If those matter to you, make sure the destination covers them. Our Koltrix vs Zoho Mail comparison is explicit about where Zoho is the better choice.

Key takeaways

  • Inventory users, aliases, groups and other Zoho apps before planning the move.
  • Build an address map and use it to clean up groups that should be shared mailboxes.
  • Export or archive mail first; confirm whether your destination can import it.
  • Run both providers in parallel with dual SPF and separate DKIM, then switch MX on a quiet day.
  • Reconnect every integration that used Zoho SMTP credentials, then remove Zoho's DNS records last.

Start with Koltrix

Your domain, one inbox, and an API that sends.

A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.

Start your 7-day free trialOpen KoltrixRead the docs
SharePost on XLinkedIn

Keep reading

More in Guides →