Switching from Zoho Mail to Microsoft Outlook / Exchange – Receiving Emails Using the Same Email Address

Hi @Elizabeth Pureza 

Here's the guide for moving email receiving from Zoho Mail to Microsoft 365 / Exchange Online, while keeping the same email addresses and avoiding mail loss. 

1.Add & verify your domain in Microsoft 365 

Add your domain in Microsoft 365 Admin Center > Settings > Domains and verify ownership using a TXT record.  

You can read more at: Add a custom domain to Microsoft 365 - Microsoft 365 admin | Microsoft Learn. 

2.Create mailboxes in Microsoft 365 before switching MX: 

-Create user accounts with the same email addresses.

-Assign Microsoft 365 licenses that include Exchange Online.  

-Confirm mailboxes are active and accessible in Outlook / Outlook Web.  

3.Migrate existing mail from Zoho 

Changing MX records only redirects new incoming mail to Microsoft 365. It does not automatically transfer existing messages from Zoho. If you need to preserve old mail, migrate the mailbox content first: 

-Use IMAP migration to copy existing messages into Microsoft 365 

-Keep the migration running while Zoho remains active 

-During this period, new mail will continue to arrive in Zoho until the MX records are updated 

4.Lower DNS TTL before cutover 

-At your DNS provider, reduce the TTL of current MX records (for example to 300 seconds / 5 minutes) about 24 hours before migration 

5.Change MX records to Microsoft 365 

-Remove Zoho MX records and replace with the Microsoft 365 MX record (e.g., yourdomain-com.mail.protection.outlook.com). This routes all new mail to Exchange Online. 

6.Update related mail DNS records  

-SPF (TXT): 

During Zoho coexistence: v=spf1 include:spf.protection.outlook.com include:zohomail.com ~all

After Zoho is fully retired: v=spf1 include:spf.protection.outlook.com -all

-Autodiscover (CNAME): autodiscover > autodiscover.outlook.com (Used for Outlook client configuration only; not mail routing.)

-DKIM: Enable in Microsoft 365 Defender and publish DKIM CNAME records. DKIM does not affect inbound mail delivery, it only signs outbound messages.  

-DMARC (recommended): v=DMARC1; p=none; rua=mailto:dmarc(at)yourdomain.com  

-References: 

• Connect your domain by adding DNS records - Microsoft 365 admin | Microsoft Learn 
• Use DMARC to validate email, setup steps - Microsoft Defender for Office 365 | Microsoft Learn 
• How to use DKIM for email in your custom domain - Microsoft Defender for Office 365 | Microsoft Lea… 

7. Keep Zoho Mail active temporarily 

-Keep Zoho Mail active for several days (often 48–72 hours minimum) because DNS propagation may take time, and some senders may still use cached MX records. This ensures late-arriving mail is not lost 

8.Validate mail flow  

-Send test emails from external accounts (e.g., Gmail, Outlook.com)  

-Confirm delivery in Exchange Admin Center > Message Trace  

I hope this information is helpful. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".          

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.   

Below is a high‑level, Microsoft‑aligned way to move inbound mail from Zoho to Exchange Online while keeping the same email address.

1. Prepare Microsoft 365 and verify the domain

• Add the domain (for example, contoso.com) in the Microsoft 365 admin center.
• Use the TXT verification record provided by Microsoft 365 at the DNS host (where the domain’s DNS is managed).
• Ensure the TXT record is copied exactly, including the MS= prefix, and that changes are saved at the DNS host.
• Wait for DNS to propagate, then complete domain verification in Microsoft 365.

If verification fails, typical causes are:

• The TXT value is not exact (missing MS= or extra characters).
• The DNS zone file was not saved/published.
• DNS propagation delay (can take up to a few hours).

See: “Can't verify your domain?” in the referenced article.

2. Configure mailboxes in Exchange Online

• Create user mailboxes in Exchange Online for every email address that will receive mail at the domain before changing MX records.
• This ensures that when MX is switched, Microsoft 365 has a mailbox ready for each address.

3. Plan DNS cutover and reduce TTL (optional but recommended) To minimize disruption when switching from Zoho MX to Microsoft 365 MX:

• At the DNS host, locate the existing MX records that point to Zoho.
• Reduce the TTL on those MX records to 3,600 seconds (1 hour) or less, at least several hours (ideally a day or more) before the final cutover.
• If there are multiple MX records, set the TTL on each to 3,600 seconds or less.

This causes external mail systems to refresh the MX information more frequently, reducing the time they continue to send to Zoho after the switch.

4. Switch MX to Microsoft 365 / Exchange Online Once:

• The domain is verified in Microsoft 365, and
• All required mailboxes exist in Exchange Online,

then update MX records:

• In the Microsoft 365 admin center, go to Settings > Domains, select the domain, and follow the domains wizard to obtain the required MX record for Exchange Online.
• At the DNS host, replace the Zoho MX records with the Microsoft 365 MX record provided by the wizard.
• Remove or lower the priority of Zoho MX records so that only the Microsoft 365 MX record (or records required by Microsoft) is active.

Microsoft guidance for MX change:

• Email systems use MX records to locate the email system.
• During migration, MX points to the old system (Zoho); after migration, it must point to Microsoft 365 so new mail is delivered to Exchange Online.
• It can take up to 72 hours for all external systems to recognize the new MX record.

5. Handle propagation and avoid mail loss

• During the 0–72 hour propagation window, some senders may still deliver to Zoho based on cached MX data.
• Lowering TTL in advance reduces this period, but does not eliminate it.
• To avoid loss:
  • Keep the Zoho service active until at least 72 hours after the MX change.
  • During this time, periodically check Zoho mailboxes for any straggler messages and forward them to the corresponding Exchange Online mailboxes.

Microsoft notes:

• Until the MX record is changed, email continues to be routed to the old system.
• After MX is changed, there can still be a delay before all senders use the new route.
• Even if TTL is not lowered, delayed messages will still eventually arrive at the new system once senders refresh MX.

6. Finalize and retire Zoho After at least 72 hours with no new mail arriving at Zoho:

• Confirm that all new mail is arriving in Exchange Online.
• Optionally increase MX TTL back to a longer value (for example, several hours) for stability.
• When confident that no senders are using Zoho anymore and all needed historical data has been migrated, Zoho mail services can be safely decommissioned.

Key best practices

• Verify the domain and create all required mailboxes in Microsoft 365 before changing MX.
• Lower MX TTL to 3,600 seconds or less before cutover to reduce delay.
• Change MX to Microsoft 365 only after preparation is complete.
• Keep Zoho active for at least 72 hours after MX cutover to catch any late‑arriving mail.
• Expect that full global MX propagation can take up to 72 hours.

References:

• Find and fix issues after adding your domain or DNS records
• Migrate email to Exchange Online using the Exchange cutover method
• Perform a staged migration of email in Exchange Online
• What you need to know about a cutover email migration in Exchange Online
• Use Minimal Hybrid to quickly migrate Exchange mailboxes to Microsoft 365 or Office 365
• Migrate other types of IMAP mailboxes to Microsoft 365 or Office 365