Step-by-Step Roadmap to Migrate Email to Microsoft 365 Without Downtime
A comprehensive step-by-step roadmap for IT leaders to migrate email to Microsoft 365 from legacy web hosting or email servers. Learn how to choose between Cutover, Staged, and IMAP batch migration, verify custom domains, update MX/SPF records, and prevent downtime or data loss during cutover.
Microsoft 365

Overview of Email Migration Methods to Microsoft 365
When planning to migrate email to Microsoft 365 from legacy hosting or an existing email server, understanding the available migration strategies is essential. According to technical documentation from SOFT365, organizations can choose between three primary migration paths: Cutover migration, Staged migration, and Hybrid migration. For standard Linux or cPanel web hosting environments, performing an IMAP batch migration through the Exchange Admin Center is the most widely adopted approach.
Cutover migration is best suited for smaller organizations (under 2,000 mailboxes) looking to move all users simultaneously. Staged migration applies to legacy on-premises Microsoft Exchange environments moved in batches over time. Meanwhile, IMAP batch migration allows administrators to synchronize mailbox data from the old hosting server to Microsoft Exchange Online in the background. Choosing the right path ensures continuous business operations and minimizes technical risks.
Auditing Legacy Infrastructure and Setting Up the Microsoft 365 Tenant
The first phase of the migration roadmap involves establishing your Microsoft 365 tenant and auditing existing assets. As outlined in Microsoft Learn documentation, administrators begin by creating an initial admin account (e.g., admin@domain.onmicrosoft.com) and selecting appropriate business subscriptions such as Microsoft 365 Business Standard or Business Premium. Subscriptions provide cloud services including Exchange Online, 1 TB of OneDrive storage per user, Teams collaboration, and core Office desktop apps.
Concurrently, the IT team must audit the legacy email hosting environment. Create a complete user inventory, evaluate mailbox sizes, identify distribution groups, and verify client protocols in use (IMAP vs. POP3). IT advisory insights from TND highlight that if users are connected via legacy POP3 and have downloaded emails to local machines while removing them from the server, those messages cannot be synced server-to-server. Identifying POP3 users early allows IT teams to schedule local PST exports.
Custom Domain Verification and User Provisioning
To enable users to send and receive messages using the company custom domain on Microsoft 365, IT admins must add and verify the domain within the Microsoft 365 Admin Center. Based on technical guidance from ITM Management, navigate to Settings > Domains, enter your business domain, and add the required TXT or CNAME verification record into your domain registrar's DNS management console.
Once ownership is verified, administrators provision user accounts in Microsoft 365 and assign product licenses. You can create users individually or bulk-import them using a CSV file. At this stage, user login IDs and primary addresses transition from the temporary onmicrosoft.com domain to your official domain name. Crucially, existing MX records should remain pointed to the old email host during this phase so normal mail flow continues uninterrupted.
Configuring Migration Endpoints and Launching IMAP Batches
With user accounts provisioned, the next step is establishing a connection between the Exchange Admin Center and the legacy email host. According to ITM Management, administrators navigate to Recipients > Migration in the Exchange Admin Center to create a new IMAP migration endpoint by entering the legacy server hostname (e.g., imap.yourdomain.com), port numbers, and security settings (SSL/TLS).
Next, prepare a structured CSV file listing all mailboxes to be migrated. The CSV file must use comma-separated formatting, include compulsory headers such as EmailAddress, UserName, and Password, and contain no more than 50,000 rows. Once the migration batch starts, Microsoft 365 copies historical emails in the background while users continue working on their existing email server without interruption.
Domain Cutover, MX Record Updates, and SPF Aggregation
After initial background data synchronization completes and reaches a Synced status, it is time to execute the domain cutover. Following recommended practices from Microsoft Learn and TND, administrators update DNS records at their domain registrar. The primary MX record must be repointed to Microsoft Exchange Online (formatted as domain-com.mail.protection.outlook.com) so all incoming emails route directly to Microsoft 365.
Additionally, TND emphasizes a critical DNS detail: if your company website remains on the old web hosting server and sends automated system notifications or order confirmations, you must retain the old host's IP address in your SPF record. Combine both senders into a unified SPF record (e.g., v=spf1 include:spf.protection.outlook.com ip4:OLD_HOST_IP ~all). Omitting the legacy host IP will cause transactional emails from your website to be flagged as spam.
Handling POP3 Archives and Final Incremental Sync
Due to global DNS propagation delays, some external mail servers may still deliver messages to the legacy host for 24 to 48 hours after updating the MX record. To capture these stray messages, keep the IMAP migration batch active and perform a final incremental sync (delta sync) to copy all residual emails over to Microsoft 365 before completing the batch.
For employees operating under legacy POP3 configurations, locally stored mail archives must be exported as .PST files from their local Outlook client and imported directly into their new Microsoft 365 mailbox. Combining automated IMAP server migration with targeted PST client imports ensures 100% data preservation across the entire enterprise.
Post-Migration Validation, User Enablement, and Decommissioning
A common mistake during email migration is canceling legacy hosting immediately after updating MX records. Technical experts at TND recommend keeping the old hosting active for at least one full month post-cutover. The minor cost of an extra month provides an essential safety net to verify data integrity and retrieve any forgotten server assets.
During the first month, IT teams should deploy Outlook and Teams across desktop and mobile devices, enforce mobile security policies via Microsoft Intune, and protect user credentials with Microsoft Entra ID. Perform end-to-end send/receive tests, review spam filters, and confirm calendar sharing functionality before decommissioning the old hosting service permanently.
Frequently asked questions
Contact TS68 today for expert assistance in migrating your enterprise email to Microsoft 365 efficiently, securely, and with zero operational downtime.
Sources
- Sản phẩm Microsoft 365 dành cho Doanh nghiệp: Ứng dụng dành cho Công việc
- Switch from Google Workspace to Microsoft 365 for business
- How do I move my email hosting from another ...
- Chuyển email từ Gmail hoặc hosting cũ sang Microsoft 365
- CÁCH CẤU HÌNH VÀ CHUYỂN EMAIL SANG MICROSOFT ...
- CÁC KIỂU CHUYỂN ĐỔI EMAIL SANG MICROSOFT 365
More articles

Cybersecurity Incident Response: Preparing People, Process, and Communication
A strategic guide to strengthening organizational cybersecurity incident response: defining response roles, establishing structured workflows, and securing backup communication channels.

Enterprise RAG Implementation: Connect AI to Existing Files and Data
A comprehensive guide to enterprise RAG implementation, connecting large language models with existing company files, workflows, and internal data securely.

Google Workspace Management for Business: Groups, Access and Calendars
Master Google Workspace management for business: learn how to configure email groups, mailbox delegation, context-aware access, and shared calendars securely.

SharePoint Permission Management: Building a Secure Internal Document Repository
Learn how to utilize SharePoint Online as a secure internal document repository, configure structured permissions, leverage metadata, and optimize B2B document workflows.

Automating Order, Invoice, and Debt Reconciliation for Vietnamese Businesses
Learn how automated order, e-invoice and debt reconciliation solutions help Vietnamese businesses save time and minimize accounting errors.
