How to Migrate Exchange Server 2019 to Microsoft 365 : Step-by-Step Guide

Understand About Exchange Server 2019 & Microsoft 365

Exchange Server 2019 is the on‑premises version from Microsoft. Moreover, Microsoft 365 mixes Exchange Online with cloud‑based productivity services. Moving mailboxes from Exchange Server 2019 to Microsoft 365 moves data storage to the cloud. This transition changes how organizations manage security, updates, and mailbox scaling.

I have seen that unlike versions of Exchange, Exchange 2019 does not support cutover migration. I have also seen that Exchange 2019 does not support staged migration, unlike Exchange 2003 & 2007. Hybrid migration remains the supported & recommended method for Exchange 2019 environments. This method connects on‑premises Exchange Server with Exchange Online during migration.

Migration Methods Available to Migrate Microsoft Exchange Server to Office 365

Before starting the migration, administrators should understand available migration options. Exchange Server 2019 supports hybrid migration as its primary supported pathway. Two hybrid configurations exist: full hybrid and minimal hybrid, also called express migration.

According to official Microsoft guidance, hybrid migration remains the recommended method to move Exchange Server mailboxes to Microsoft 365. Administrators can review complete details in the Microsoft documentation on using minimal hybrid to migrate Exchange mailboxes. This resource explains prerequisites, domain verification, and express migration steps in detail.

Step 1: Assess Your Current Exchange Environment

• Every successful migration begins with a thorough environment assessment.
• Administrators should review the total number of mailboxes requiring migration.
• It helps to document mailbox sizes, public folders, and distribution groups.
• Reviewing network bandwidth also ensures smoother data transfer during migration.
• Organizations should confirm their Exchange Server 2019 meets the latest cumulative update.
• This step reduces compatibility issues during the hybrid configuration process.
• Administrators should also verify Microsoft 365 tenant readiness before they proceed further.

Step 2: Verify Domain Ownership in Microsoft 365

Domain verification is required before starting any migration. I need to verify the on‑premises domain within the Microsoft 365 tenant. Administrators can complete verification through the Microsoft 365 admin center. This step makes sure each mailbox receives the correct email address format. Domain verification usually means adding a DNS TXT record for confirmation. Once Domain verification is complete, administrators can continue setting up the environment. If Domain verification is delayed, the overall migration timeline may stretch unnecessarily.

Step 3: Configure Microsoft Entra Connect for Directory Synchronization

Directory synchronization connects on-premises Active Directory with Microsoft Entra ID. This step keeps user accounts consistent between on-premises & cloud environments. Microsoft Entra Connect handles synchronization of usernames, passwords, & security groups. Proper synchronization prevents duplicate account creation during the migration process. Administrators should test synchronization before proceeding to the next configuration stage. This makes sure accurate user mapping throughout the hybrid migration journey.

Step 4: Run the Hybrid Configuration Wizard (HCW)

The Hybrid Configuration Wizard connects Exchange Server 2019 with Exchange Online. Administrators download & run the HCW from the Microsoft 365 admin center. The wizard configures mail flow, certificates, & federation trust automatically. It also establishes the secure connection required for hybrid mailbox migration. Administrators should choose between classic and modern hybrid topology during setup. Modern hybrid topology suits organizations planning a full move to the cloud. Classic hybrid topology suits organizations expecting a longer coexistence period.

Step 5: Create and Start a Migration Batch

Once the hybrid configuration completes, administrators can create a migration batch. A migration batch defines which mailboxes move during a specific session. Administrators can create batches through the Exchange admin center interface. Alternatively, PowerShell commands allow more granular control over migration batches. The following commands demonstrate a typical migration batch creation process.

Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com

New-MigrationBatch -Name "Batch1" -SourceEndpoint "HybridEndpoint" -TargetDeliveryDomain "yourdomain.mail.onmicrosoft.com" -CSVData ([System.IO.File]::ReadAllBytes("C:\MigrationList.csv"))

Start-MigrationBatch -Identity "Batch1"

This process begins the initial seeding of mailbox data to Microsoft 365. Administrators should monitor batch status throughout the migration process closely.

Step 6: Monitor Migration Progress

Migration monitoring ensures administrators catch errors before they affect users. The Exchange admin center displays batch status, including completed and pending items. Administrators can also use PowerShell to check detailed migration statistics. Regular monitoring helps identify mailboxes requiring additional attention during migration. Large mailboxes or public folders may take longer to complete synchronization. Patience during this stage supports a smoother overall migration outcome.

Step 7: Complete the Migration Batch

• After initial synchronization finishes, administrators complete the migration batch.
• Completing the batch finalizes the mailbox move to Microsoft 365.
• At this stage, Outlook clients begin connecting to Exchange Online directly.
• Administrators should notify users about updated login screens or prompts.
• Testing mailbox access after completion confirms successful migration for each user.
• This step also updates mail routing to reflect the new destination.

Step 8: Migrate Exchange Public Folders to Microsoft 365

Public folders require a separate migration process within hybrid environments. Administrators should plan public folder migration after mailbox migration completes. Microsoft provides dedicated scripts for migrating public folder hierarchies and permissions. These scripts move public folder data while preserving existing folder structure. Administrators should test public folder access after migration finishes successfully. Proper planning avoids permission mismatches within migrated public folder environments.

Step 9: Update DNS and MX Records

• DNS updates redirect incoming mail flow toward Microsoft 365 servers.
• Administrators should update MX records once mailbox migration reaches completion.
• This change ensures new email messages route directly to Exchange Online.
• Updating DNS records should follow careful planning to avoid mail delivery delays.
• Administrators should verify mail flow after DNS propagation completes across the network.
• Testing inbound & outbound mail confirms proper configuration after this step.

Step 10: Decommission the On-Premises Exchange Server

Some organizations choose to keep hybrid connectivity for management purposes. Others decommission the On-premises Exchange Server to Office 365 (Microsoft 365) after migration completes fully. Microsoft recommends keeping at least one hybrid server for certain administrative tasks. Administrators should review official guidance before removing on-premises Exchange infrastructure. This step should only happen after confirming successful mailbox and folder migration. Proper decommissioning planning prevents unexpected mail flow disruptions afterward.

Migrate Exchange Server 2019 to Microsoft 365: Backing Up Mailbox Data Before Migration

Before starting migration, organizations often want an independent copy of mailbox data. Creating a backup protects against unexpected data loss during the transition. The Cigati Exchange Server to PST Backup Tool supports this preparation stage effectively. It backs up primary, shared, public folder, and archive mailboxes together. The tool preserves folder hierarchy, which matches the original mailbox structure. Administrators can filter backups by date range or specific item types. This flexibility helps teams create targeted backups before beginning hybrid migration. Having a local PST copy also supports compliance and audit requirements. Many administrators use this backup as a safeguard during large-scale migrations.

A Weekend Migration, Backed Up First

Common Challenges During Exchange 2019 to Microsoft 365 Migration

Organizations may encounter certain challenges while migrating Exchange Server 2019. Understanding these challenges in advance supports smoother migration planning & execution.

Best Practices for a Successful Migration

Following planning practices helps most companies have better results when moving their data. IT staff should always check how hybrid setups work in a place that isn't used for work first. Telling people when the move will happen helps them understand what's going on during the change. Doing the move at times when fewer people are using the system causes trouble for everyday work. Keeping records up to date during the process makes it easier to fix problems later. Also, checking the instructions from Microsoft makes sure everything is done the right way. IT staff can find advice in the Microsoft Learn article about choosing a move plan. This article gives help based on the email system and how fast the move needs to be.

Post-Migration Verification Checklist

After migration completes, administrators should verify several important elements.

• Confirm that all mailboxes appear correctly within the Microsoft 365 admin center.
• Test email flow between internal users and external recipients thoroughly.
• Verify that public folders display correct content and permissions accurately.
• Check that shared and archive mailboxes migrated without data loss.
• Confirm calendar items, contacts, and tasks transferred correctly for each user.
• Review mail flow logs to identify any delivery errors promptly.
• This checklist helps confirm a complete & accurate migration process.

Conclusion

Migrating Exchange Server 2019 to Microsoft 365 requires structured planning & execution. Hybrid migration remains the supported pathway for Exchange 2019 environments today. Following each step carefully reduces the likelihood of migration errors. From domain verification to public folder migration, every stage matters significantly. Backing up mailbox data beforehand adds an extra layer of protection. Tools like the Cigati Exchange Server to PST Backup Tool support this preparation well. With proper planning, organizations can complete migration smoothly and confidently. Reviewing official Microsoft documentation throughout the process ensures continued alignment with best practices.