How to Migrate Zoho Mail to Exchange Online (100 Users)
Question details
An organization needs configuration and migration guidance to move 100 user mailboxes from Zoho Mail across two domains to Microsoft Exchange Online.

- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- Enterprise email platform migration from Zoho Mail to Microsoft 365 / Exchange Online.
- Observed behavior
- Requires step-by-step guidance on setting up the migration endpoints, creating the migration batch, and successfully transitioning the 100 targeted user mailboxes.
Ensure you have global administrator access to your Microsoft 365 tenant and administrative access to your Zoho Mail domains before starting the migration.
Perform an IMAP Migration via Exchange Admin Center
The standard and most reliable method to migrate from Zoho Mail to Exchange Online is utilizing Microsoft's built-in IMAP mailbox migration process.
IMAP migration allows you to transfer emails from a source email provider (like Zoho) directly into Exchange Online. This process transfers email messages and folders, but does not include contacts or calendars.
Add and verify your domains in the Microsoft 365 admin center. Create the 100 user accounts and assign them Exchange Online licenses so the destination mailboxes exist.
Ensure that IMAP access is enabled for all the Zoho mailboxes you plan to migrate. If users have Two-Factor Authentication (TFA) enabled, you must generate Application-Specific Passwords for each account.
In the Exchange Admin Center, navigate to Migration. Add a new migration endpoint and select IMAP. Enter Zoho's IMAP server details (imappro.zoho.com) and configure the connection settings.
Create a CSV file mapping the source mailboxes to the destination mailboxes. The file must contain three columns: EmailAddress (Microsoft 365 address), UserName (Zoho email address), and Password (Zoho password or App Password).
Upload your CSV file in the Exchange Admin Center to create a migration batch. It is highly recommended to run a pilot migration with 2-3 mailboxes first to verify the configuration before migrating the remaining users.
Once the mailboxes have successfully synced, update your domain's MX records to point to Microsoft 365 to route new incoming emails to Exchange Online. Finally, complete the migration batch.

Equip Your Migrated Users with WPS Office
While you transition your organization's email to Exchange Online, providing your users with a powerful, lightweight, and cost-effective productivity suite is crucial. WPS Office serves as a fantastic alternative to heavy Microsoft Office subscriptions, ensuring seamless workflow continuity and document handling.
- 1. Download the Enterprise Installer: Visit the official WPS Office website to download the lightweight installation package for your team.
- 2. Deploy Across Devices: Run the installer on your organization's machines. Its low resource requirement makes deployment incredibly fast.
- 3. Open and Edit Native Office Files: Users can immediately open and collaborate on existing .docx, .xlsx, and .pptx files seamlessly.

Frequently Asked Questions
Can I migrate only 100 out of my 300 Zoho users?
Yes. With the IMAP migration process, you specify exactly which mailboxes to migrate by including only those 100 specific users in your migration CSV file. The remaining users will stay on Zoho.
Will IMAP migration transfer my users' Zoho contacts and calendars?
No. The IMAP protocol only synchronizes email messages and folder structures. Users will need to manually export their contacts and calendars from Zoho and import them into Microsoft 365.
How do I handle email routing if my organization uses both Zoho and Exchange Online?
If you are splitting users between Zoho and Exchange (co-existence), you must set up email forwarding or connector rules so that users on Exchange Online can successfully route internal emails to the users still residing on Zoho Mail.
Why is my IMAP migration batch failing authentication?
Authentication failures are typically caused by incorrect passwords in the CSV file, Zoho's IMAP access being disabled for the specific user, or the user having Two-Factor Authentication enabled without providing an App-Specific Password in the CSV.




