Migrate Exchange to Office 365

Best method to migrate Exchange to Office 365

Native migration methods such as cutover and staged migrations provided by Microsoft can help organizations migrate Exchange Server mailboxes to Microsoft 365. However, these approaches often involve several limitations including extensive prerequisites, complex configurations, longer downtime, and potential risks of data loss or inconsistencies during the migration process. In comparison, the EdbMails Exchange to Office 365 migration tool provides a more reliable and efficient approach that overcomes these challenges. It enables secure and seamless migration of all mailbox attributes including emails, contacts, calendars, tasks, journals, appointments, and notes while maintaining complete data integrity throughout the migration.

EdbMails simplifies the migration of multiple user mailboxes, public folders, shared mailboxes, and archive mailboxes in a single operation, making it suitable for organizations with different migration requirements. Unlike native methods that often depend on complex PowerShell scripts and advanced technical knowledge, EdbMails provides an intuitive interface that makes the migration process straightforward and easy to manage. By using EdbMails, businesses and individuals can perform migrations with confidence, reduce potential risks, and achieve a smooth migration to Office 365 while taking full advantage of Office 365 features.

1. Exchange to Office 365 Migration Checklist

   The following checklists will help you migrate all your Exchange server data to Office365 smoothly.

   1. Plan for the migration:
      • Identify the scope of the migration, including the number of mailboxes,public folders, and other data that needs to be migrated.
      • Determine the size of the mailbox data and number of mailboxes to migrate.
      • Assess the current environment, including hardware, software, and networkconfigurations.
      • Prepare a complete inventory of items that you want to migrate.
      • Determine the migration schedule, including the timing and duration of themigration.
      • Identify any specific requirements or constraints that may affect themigration.
      • Communicate any changes to your end users and inform the stakeholders.
   2. Prepare the data for migration:
      • Clean up and archive any unnecessary data to reduce the amount of data thatneeds to be migrated.
      • Perform a test (pilot) migration to identify and resolve any issues beforethe full migration.
   3. Purchase and configure Office 365 licenses:
      • Purchase the necessary
      • Configure the Office 365 tenant, including creating and configuring users,mailboxes, public folders and other resources.
   4. Configure the domains and DNS records:
      • Prepare the domains and required Active Directory services on the target.
      • Update the DNS records to point to the Office 365 tenant, including MXrecords and Autodiscover.
      • Verify that the DNS changes have propagated and that email is flowing to theOffice 365 tenant.
   5. Perform Exchange to Office 365 migration with EdbMails:
      • EdbMails can help you with Exchange to Office 365 migration
      • Configure the migration settings and migrate mailboxes, Public folder andShared mailboxes.
      • Monitor the migration progress and verify the migrated items
   6. Test and validate the migration:
      • Test the migration by sending and receiving email and verifying that alldata has been migrated correctly.
      • Validate the migration by checking for any missing data or issues, andtroubleshoot as needed.
      • Perform a final backup of the Exchange server before decommissioning it.
   7. Post-migration tasks:
      • Update email client settings, such as Outlook, to point to the Office 365tenant.
      • Create new Outlook profiles and check if you are receiving mails correctly.
      • Update any custom scripts or applications that access the email data topoint to the Office 365 tenant.
      • Update any third-party services or integrations that access the email datato point to the Office 365 tenant.
      • Update the helpdesk and end-user documentation to reflect the new emailenvironment.
      • Train users on the new email environment and any new features orfunctionality provided by Office 365.
      • Decommission the source Exchange server if you no longer plan to use it(optional).
   8. Monitor and maintain:
      • Monitor the Office 365 environment for any issues or performance problems.
      • Maintain and update the Office 365 environment as needed.
      • Continuously review and improve security, backup, and disaster recoverystrategies.

2. Exchange to Office 365 Migration Planning

   • Step 1: Decide on a suitable Exchange to Microsoft 365 migration type

     The first step is to plan the Exchange mailbox migration to Office 365.Depending on your source and target environments, the following migration pathsare available.

     Migration Requirement	Ideal migration approach	Migration flow
     You want to move all of your email, calendar, and contacts fromExchange to Office 365 at once.	Exchange cutover migration	Set up your target Office 365 tenant and migrate everything tothe cloud all at once. Suitable for large-scale mailboxmigrations
     You prefer to transfer mailboxes from Exchange Server to Office365 in smaller batches or on weekends.	Staged Exchange migration	Migrate your mailboxes and mail data in stages, transferring themost recent data first, followed by the others.
     You want to retain your on-premises Exchange server and prefermoving to Office 365 gradually	Hybrid migration	Move mailboxes to Office 365 in a Hybrid deployment of Exchangeand Office 365.

      Use the Microsoft 365 mail migration advisor to determine which migration method is best for you.

   • Step 2: Install cumulative updates (CU) on the Exchange server

     Ensure that you have the latest updates installed on the source Exchange.

     1. Install CU for Exchange server 2010
     2. Install CU for Exchange server 2013
     3. Install CU for Exchange server 2016
     4. Install CU for Exchange server 2019
   • Step 3: Consider the network and bandwidth requirements
     1. Network requirements
        1. Network Setup: Understand the networking roadmap for Microsoft 365. It involves planning, deploying andmanaging your network.
        2. Internet Connectivity: A stable and reliable internetconnection is required for migration of Exchange to Office 365. Theinternet connection should have sufficient bandwidth to handle thedata transfer and should be free from congestion.
        3. Firewall and Port Configuration: Review and configure the firewall and port configurations to allow for the necessary data transfer to the Office 365 tenant.
        4. DNS Configuration: Review the DNS records and configure themto point to the Office 365 tenant, including MX records andAutodiscover. This task ensures that email is properly routed to theOffice 365 tenant after the migration.
        5. Network Latency: Consider the Network Latency to ensure aseamless data transfer. If the Network Latency is high, it may slowdown the migration process. See how Microsoft365 networking is different.
        6. Office 365 Throttling: Microsoft limits the number ofconcurrent mailbox transfers to ensure service availability.Consider the Office365 throttling policies when you migrate large mailboxes.
        7. Network Security: Review the network security to ensure thatthe data transfer is secure. This includes configuring any necessaryencryption, authentication, and access controls.
        8. Network Load Balancing: Consider the Network LoadBalancing to ensure that the data transfer is balancedacross multiple networks and to avoid any bottlenecks.
     2. Bandwidth requirements

        Bandwidth requirements for Exchange to Office 365 migration can varydepending on several factors, such as the number of mailboxes, theamount of data to be migrated, and the migration method used. Use toolslike Microsoft Remote Connectivity Analyzer and connectivity test tool to test your existing network.

        1. Number of mailboxes: The number of mailboxes beingmigrated influences the overall bandwidth requirements. The moremailboxes you plan to migrate, the more bandwidth you will need. See bandwidth requirements for Office 365 migration.
        2. Mailbox Size: The size of the mailboxes beingmigrated also influences the overall bandwidth requirements. Largermailboxes will require more bandwidth to migrate.
        3. Migration Type: The type of migration you use alsoaffects the bandwidth requirements. For example, a cutovermigration, where all mailboxes are migrated at once, requires morebandwidth than a staged migration, where mailboxes are migrated insmaller groups.
        4. Migration schedule: The schedule of the migrationalso influences the bandwidth requirements. For example, migratingduring off-hours or over a weekend when network traffic is typicallylower, reduces the overall bandwidth requirements.
        5. Network infrastructure:. A network with higherbandwidth capacity can handle more data during the migration.
        6. Network Latency: Network Latency between the sourceand destination servers is also a factor to consider during themigration. If the Network Latency is high then a higher bandwidth isrequired.

       See best practices for network planning and improving migration performance.

   • Step 4: Select a suitable Microsoft 365 license plan that fits your needs

     Microsoft 365 is available as a cloud-based subscription service and offers avariety of licensing options, each tailored to a specific user needs. It isrecommended that you thoroughly evaluate the Office 365 business plans and Office 365 enterprise plans todetermine which one best meets the needs of your organization. You can also signup for a 30-day free trial of Office 365 to test out the various plans beforemaking a final decision.

   • Step 5: Set up your target Office 365 Tenant for the migration
     1. Create an Office 365 Tenant: Plan for the Tenantimplementation and deploy the tenant. See the tenant roadmap for Office 365.
     2. Sign in to the Microsoft 365 admin center: Microsoft 365 admin center (https://admin.microsoft.com/) and sign in with your global administrator credentials.
     3. Customize the Tenant settings:After the tenant is set up, configure and customize the settingssuch as email domains, language, and time zone to suit your organization'sneeds.
     4. Configure Azure AD Connect: Azure AD Connect is used tosynchronize your on-premises Active Directory with Azure AD. This step isnecessary if you want to retain your on-premises in a Hybrid environment andto enable single sign-on (SSO) for your users.
     5. Configure email clients and apps: If you want to installOffice 365 apps and Outlook, see system requirements for Microsoft 365 and Office configuration support matrix. Because Office 365 is a cloud based solution, it is also important to learn where your Microsoft 365 customer data is stored.
     6. Set up Office 365 services: Besides email, you may want toset up additional services such as SharePoint, OneDrive and Teams.
     7. Establish data retention policies: With Office 365, youhave the ability to retain data in accordance with compliance and legalrequirements. Set up data retention policies to meet your organization's compliance needs, and if necessary configure retention policies for specific mailboxes or groups ofusers
   • Step 6: Add and verify the custom domain on Office 365

     If you have a custom email domain from your hosting provider to which you wantto migrate and receive emails, you must add and verify the domain on Office 365.This will enable you to use your own domain name (such as example.com) for youremail addresses and other Office 365 services.

      To set up your custom domain, follow these steps:

     1. Verify that you own the domain by adding a TXT record to your DNS configuration.
     2. Add a new domain to your Office 365 tenant. You can use an existing domain that you own or purchase a new one. The domain is used to access your Office 365 services. 
     3. Update your DNS records to point to Office 365. This step is required to ensure that your email is delivered tothe correct mailbox. You can also update the MX records after you complete the migration.
   • Step 7: Create mailboxes and set up mail-enabled Public folders

     Before you migrate to Office 365, ensure that you create mailboxes for users in your organization and assign suitable licenses to them. EdbMails automatically creates mailboxes on target Office 365 servers

     1. Add users and assign licenses to Office 365 users
     2. Add several users at the same time to Office 365
     3. Assign Microsoft365 licenses to user accounts

     If you want to migrate Exchange public folders to Office 365 , then create and configure Public folders and make them mail enabled on Office 365.

     1. Create Office 365 Public folder and assign permissions to admin user If you are migrating to Office 365 archive mailboxes ensure to enable In-Place Archives on Office 365 server
     2. Steps to enable In-Place Archive mailboxes in Office 365 server
   • Step 8: Set impersonation rights for the admin user on the source server

     If you are using the global admin account to connect your source Exchangeserver, ensure to set the impersonation rights.

       Steps to set impersonation rights in Exchange 2019, 2016, 2013, 2010

      Steps to set impersonation rights in Exchange 2007

   • Step 9: Verify the mailbox of the admin account

     Check to see if the admin account that has been assigned management roles has avalid and non-hidden mailbox on the Exchange server. See how to configure user mailbox properties for the users from the Exchange admin center (EAC).

   • Step 10: Configure Office 365 to send and receive large messages

     Increase the message size limit on Office 365 to 150 MB. This option enables you to bypass message size limitations during the migration.

3. Steps to Migrate Exchange to Office 365

   1. Step 1: Download EdbMails Exchange to Office 365 migration tool

      • Download and install theEdbMails application on your computer.

        

      • See the detailed list of EdbMails system requirements for Exchange to Office 365 migration.
      • Open the EdbMails application on your computer.
      • Enter your registered email ID and password, then click ‘Login’. If you haven’t created an account yet, select ‘Start Your Free Trial’ to continue with the trial version.
        Note: The trial version provides access to all key features and supports migration of up to 30 items per folder. For unlimited migration, purchase an Exchange Migration license from the official EdbMails website.

         Click here to check the Exchange Migration pricing details.

        After purchasing the license, close the application and launch it again. Then log in with the same email ID and password used during the purchase to complete the license activation.

        

      • Select ‘Live Exchange Migration’.

        

      • Select 'Live Exchange to Office 365 Migration'

        

      • You can use the default job name or click 'New Job' to modify the job name

        

   2. Step 2: Connect to source Exchange server

      • To establish a new connection with the source Exchange server, click ‘Add New Connection’. To reconnect using a previous connection, select it from the list and click ‘Connect to Existing’ to continue.

        

      • Select the required connection options and click the ‘Next’ button.

          Different options to connect to Exchange server in EdbMails

        

      • Enter the source Exchange server details, including the IP address (Domain name), Exchange version, username, and password.
      • Click the ‘Login’ button to proceed.

        

      • After signing in to your target Office 365 server, choose the method to load the mailboxes.
        • EdbMails can automatically load the mailboxes, simplifying the setup. Due to Microsoft API limitations, the automatic method displays only up to 100 mailboxes at a time.
        • For larger environments or when you need to include specific mailboxes, select the ‘Load Mailboxes using .CSV file’ option. This method allows manual selection and gives you complete control over the process.
      • Select ‘Load Mailboxes Automatically’ and click ‘Next’ to proceed.

        

      • Choose the specific mailboxes/folders from the source Exchange server for the migration process.

        

   3. Step 3: Connect to target Office 365 server

      • Click ‘Add New Connection’ to set up a fresh connection to the target Office 365. If you've connected before, choose it from the list and click ‘Connect to Existing’ to continue.

        

      • Select the required options to establish a connection with your target Office 365 server
      • Then click the ‘Next’ button to proceed with the migration setup.

        

      • Ensure you have a Global Admin account with an active mailbox to enable Auto Registration of the EdbMails application in your Entra ID (Azure Active Directory).
      • For the Manual Registration method, you can use either a Global Admin account or a user account that has full access permissions.
      • Select ‘Auto Registration’ to connect to Office 365 and click the ‘Login’ button to continue.

        

      • Authenticate on Microsoft sign-in page.

        

      • Select one of the methods to load the mailboxes.
      • You can either select ‘load Mailboxes Automatically’ or load the mailboxes using a CSV file and click ‘Next’ to continue.

        

   4. Step 4: Map source and target mailboxes

      • Choose the required mailbox mapping option

        

      • EdbMails automatically creates mailboxes on your target Office 365 server and assigns the necessary licenses.

         Learn more about automatic mailbox creation in the target Office 365 server.

        

   5. Step 5: Start Exchange to Office 365 migration

      • Click the 'Start Migration’ button to initiate the migration process.

        

      • Track migration progress in progress bar. After migration completion, EdbMails prompts to review the migration status. Click the ‘View Logs’ button to check the migration report. Log in to the target server and verify the migrated items.

        

      • You can verify the list of migrated folders and mailbox items with EdbMails text-based migration log report.
      • Login to your target Office 365 server and verify the migrated items.

4. Exchange to Office 365 Post Migration Tasks

   • Step 1: Update MX records to route to Office 365.

     It’s necessary to update MX records to route email to the new server. Furthermore, setting up the Autodiscover record is essential for ensuring that migrated mailboxes can connect seamlessly with mail clients, such as Outlook.

   • Step 2: Set up a new Outlook profile for users in the new domain

     If users encounter issues connecting Outlook to Office 365 mailboxes,manually configure their Outlook profiles in the new domain.

   • Step 3: Uninstall and decommission the source Exchange server

     The following points provide an overview of the steps to decommissionon-premise Exchange server.

     • Verify that all mailboxes have been successfully migrated toOffice 365.
     • Check the status in the Exchange admin center or with thePowerShell Get-MailboxStatistics cmdlet.
     • Make sure that all Outlook clients are configured to connect to Office 365. You can use the Test-OutlookWebServices cmdlet to check the connectivity of Outlook clients.
     • Disable all mail flow on the Exchange server by removing theReceive Connector or disabling the SMTP service.
     • Ensure that all public folders have been migrated to Office 365.You can use the Get-PublicFolder cmdlet to check the status of public folders.
     • Uninstall the Exchange server software from the Control Panel.
     • Remove any remaining Exchange-related hardware or virtualmachines.
     • Verify that no mailboxes or public folders remain on theExchange server.
     • Finally, remove the server from the Active Directory and DNS.
     • Once you verify that everything is working fine, you candecommission your on-premises server.
       1. Steps todecommission Exchange 2013
       2. Steps todecommission Exchange 2010
       3. Modify orRemove Exchange 2010
       4. RemoveExchange 2007 organization
       5. UninstallExchange Server 2003
       6. DecommissionExchange server in a Hybrid deployment

5. Troubleshooting guide for Exchange to Office 365 Migration

     See the troubleshooting solutions for Exchange and Office365 migration. For more information related to EdbMails Exchange migration,see frequently asked questions.