What you need to know about Exchange 2013 and Office 365

Microsoft announced the end of support for Exchange Server 2013. This means that Microsoft is no longer supporting security updates, non-security hotfixes, or online technical content updates for Exchange Server 2013. It’s very crucial to understand that the end of support doesn’t render the server inoperable. Nevertheless, the absence of security updates after this deadline implies an increased vulnerability to potential security threats and other operation issues.

In light of this development, extending considerations beyond the Exchange server is imperative. This includes taking into account the status of other Microsoft products such as SharePoint Server 2013, Project, Lync server, and the Office 2013 client. Planning an upgrade for these components is equally vital to ensure a comprehensive and secure information technology infrastructure. Organizations are encouraged to adopt a proactive stance, preparing for the impending end of support by strategizing a seamless migration to newer, supported versions of these Microsoft products. This strategic approach helps maintain system integrity, safeguard against potential vulnerabilities, and ensure continued operational resilience in the evolving landscape of technology and security standards.

Suppose your organization plans to use Exchange Server 2013 after the end of the support date. In that case, upgrading to a newer version of Exchange Server or Exchange Online is highly recommended, which is part of the Office 365 suite. Upgrading to Exchange Online can help you take advantage of the new features and functionality, as well as ensure that the messaging and collaboration platform is secure and up-to-date.

Compared to Exchange Server 2013, Office 365 offers several advantages including the convenience of a cloud-based service, scalability, automatic updates, a comprehensive suite of productivity tools, and a more cost-effective pricing model. Before you decide on the migration, weigh the pros and cons and compare the Microsoft 365 plans based on your requirements and the current setup is best.

In this guide, we describe the pre-migration activities, the different migration paths from Exchange 2013 to Office 365, and the post-migration activities.

Is migrating from Exchange 2013 required?

You should migrate from Exchange 2013 depends on several factors:

1. End of Support: Since Exchange Server 2013 has reached its end of support, continuing to use it may pose security risks as Microsoft will no longer provide updates, including security patches.
2. Security Concerns: Without regular security updates, the system becomes more vulnerable to threats. Migrating to a supported platform can ensure a more secure environment for your email and communication systems.
3. Feature Updates: Newer versions of Exchange, such as Exchange Server 2016 or Microsoft 365, offer improved features, performance enhancements, and compatibility with the latest technologies. Migrating could provide access to these benefits.
4. Compliance Requirements: Industry or organizational policies may require the use of supported and up-to-date software, and migrating to a current version can help meet these standards.
5. Integration Opportunities: If your organization is adopting new technologies or cloud-based solutions, migrating to a more recent version of Exchange or a cloud-based email platform like Microsoft 365 could offer better integration possibilities.

Methods to migrate from Exchange 2013 to Microsoft 365

Various methods are at your disposal for migrating mailboxes to Exchange Online.

• Hybrid migration
• Cut-over migration
• Express migration
• Manual method
• Third-party tool

Hybrid migration: A hybrid migration involves setting up an environment with both on-premises Exchange servers and Exchange Online, facilitated through the Hybrid Configuration Wizard. The process includes migrating data from local mailboxes to cloud-based mailboxes. Although this approach offers flexibility in staging the migration, it adds complexity to your IT infrastructure. In essence, mailbox management occurs on-premises, with all changes synchronized to the cloud through Azure AD Connect. The complexity of hybrid environments might not be entirely clear to most individuals.

Cut-over migration: Cutover Migration is a method that migrates all data in a single, comprehensive transfer. This technique quickly migrates data with minimal effort, making it particularly recommended for small and medium-sized organizations. Given that such organizations typically have smaller data volumes, the entire migration process usually takes just a few days. To minimize potential downtimes, organizations can schedule the Exchange migration over weekends.

Cutover migration is well-suited for Exchange environments using versions 2003, 2007, 2010, or 2013, and when the total number of mailboxes is less than 2,000.

Express migration: Express migration, also known as minimal Hybrid, is a quick migration method that excludes directory synchronization. This approach streamlines the migration process, prioritizing speed. It is suitable for organizations seeking a quick migration to Exchange Online without the need for ongoing synchronization between on-premises Exchange and the cloud. While efficient, it is essential to consider the impact on user management processes, as user accounts and attributes are managed independently in both environments. Express migration is best suited for straightforward migration goals but may not be ideal for complex scenarios requiring continuous synchronization.

Manual methods: This method requires replicating the organizational structure in the cloud and utilizing Exchange 2013 migration to Office 365 through the use of PST files for data migration. The process involves exporting PST files from the source server, a task that can be simplified with PowerShell. However, it is crucial to acknowledge the inherent complexities and fragility associated with PST files, including the potential for various points of failure. Consequently, while this approach may be viable for organizations with a limited number of mailboxes and robust backups in place, it is generally not recommended due to its inherent challenges.

Third-party tool: For a more streamlined Exchange 2013 to Office 365 migration, third-party tools provide a practical solution, particularly for organizations managing a significant number of mailboxes. Make use of the EdbMails Exchange migration tool that utilizes different methods to enhance the efficiency of the migration process and that can aid in the migration from Exchange 2013 to Office 365.

What is the best way to migrate Exchange 2013 to 365?

EdbMails Exchange server migration software can help you perform Exchange 2013 to Office 365 migration without requiring technical expertise. By using EdbMails, you can migrate selected or entire mailboxes, contacts, notes, tasks, folders, attachments, emails, archives, and shared mailboxes from the source to the target. It simplifies the operation and enables you to complete the migration without affecting the users.

Furthermore, it supports secure modern authentication for Office 365 migration and maintains complete data consistency between the source and target servers. You can use EdbMails to migrate on-premises Exchange to Office 365, Hosted Exchange to Office 365, from one Exchange server to another, between two different forests and domains, and so on.

1. Exchange 2019 to Office 365 Migration Checklist

   Migrating from Exchange 2019 to Office 365 can be a complex process, but with proper planning and execution, it can be completed smoothly. Here is a comprehensive checklist that can help you plan and execute your migration

   1. Preparing your Exchange 2019 environment
      • Assess your current Exchange environment: This step includes gathering information about your current Exchange infrastructure, such as the number of mailboxes, their sizes, the number of public folders, and the number of Distribution Groups and others.
      • Plan your migration: Based on the information gathered, plan the migration process, including the number of mailboxes to be migrated, the migration schedule, and the migration method to be used.
      • Consider mailbox requirements: Take into account specific requirements for certain mailboxes or groups of users, or any permissions that need to be migrated.
      • Plan what you want to migrate: Identify the type of your current migration environment and determine whether you want to move everything at once or in stages.
      • Backup your Exchange 2019 mailboxes: It is highly recommended to take a copy of your Exchange 2019 mailboxes and email data before you start the migration.
   2. Performing the pre migration tasks
      • Create an Office 365 tenant: If you haven't already done so, sign up for Office 365 and create a tenant. This will be the destination for your Exchange migration.
      • Set up Azure AD Connect: Azure AD Connect is used to synchronize your on-premises Active Directory with Azure AD. This step is necessary to enable single sign-on (SSO) for your users.
      • Prepare your on-premises Exchange environment: Make sure that your on-premises Exchange environment is properly configured and updated. This preparation ensures that your Exchange servers meet the necessary system requirements and that they are running the latest updates and service packs.
      • Create a test environment: It's a good idea to set up a test environment to test the migration process before attempting it on your production environment. This will help you identify and resolve any issues that may arise during the migration.
   3. Migration with EdbMails Exchange migration
      • Perform a test Exchange 2019 migration to 365: You can choose among cutover, staged or hybrid migration. This approach allows you to test the migration process before migrating the rest of the mailboxes.
      • Migrate Public Folders: Public folder migration is simplified with EdbMails because you do not require any PowerShell scripts.
      • Synchronize your on-premises Active Directory with Azure AD: This step ensures that any changes made to your on-premises Active Directory since the last synchronization are propagated to Azure AD.
   4. Post-migration Tasks
      • Test the migration: Test the migration by logging in as a test user and accessing their mailbox, calendar, and other data. Make sure that everything is migrated and you are able to access the data.
      • Perform any necessary cleanup: Once the migration is complete, perform a cleanup such as removing the on-premises Exchange servers and decommissioning any other hardware that's no longer needed.
      • Update your documentation: Update your documentation to reflect the changes made during the migration. This includes updating your inventory of hardware and software and your network diagrams.
      • Update user training: Inform and give training if necessary to the users, how to use the new Office 365 features and functionalities.

2. Exchange 2019 to Office 365 Migration Prerequisites

   • Step 1: Decide on the Exchange to Office 365 migration path

     The first step is to carefully evaluate how you want to migrate Exchange 2019 to Office 365 and select the one that best suits the organization's needs. A thorough assessment of the existing Exchange environment helps you in making an informed decision. The migration path chosen should align with the specific requirements of your source and target environments.

     Current environment and migration requirement	Ideal migration approach	Migration flow
     You are looking to migrate your email, calendar, contacts and all mail data from Exchange Server 2019 to Exchange Online in a single operation	Exchange cutover migration to Office 365	With this method, you can migrate all of your email data at once to Office 365 and is suited for a large number of mailboxes.
     You prefer to move all of your mailboxes from Exchange Server 2019 in smaller increments or during the weekends.	Staged Exchange migration	In this approach, you migrate your mailboxes and mail data in stages, starting with the most recent data and then proceeding to the rest.
     You prefer to switch to Office 365 gradually rather than moving all at once due to certain on-premises requirements.	Hybrid migration	With this method, you can migrate from Exchange 2019 to Office 365 in a hybrid deployment.

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

   • Step 2: Evaluate the bandwidth and network requirements

     When migrating from Exchange 2019 to Office 365, it's important to take into account the bandwidth and network requirements of the migration operation. The amount of bandwidth and network resources required depends on the number of mailboxes being migrated, the size of the mailboxes, and the migration method being used.

     1. Internet bandwidth: The migration requires a reliable and fast internet connection to transfer the data from the on-premises Exchange environment to Office 365. See bandwidth requirements for Office 365 migration.
     2. Connectivity: It's also important to ensure that you have a stable connection between the Exchange environment and Office 365. See networking roadmap for Office 365.
     3. Network latency: The network latency between the on-premises Exchange environment and Office 365 should be as low as possible. A latency of less than 150 ms is recommended. See how Microsoft 365 networking is different.
     4. Firewall configuration: Make sure that your firewall is configured to allow traffic to and from Office 365 which includes ports that are used for Exchange and Azure AD Connect. See the list of worldwide endpoints for Office 365.
     5. Testing your network connection: With tools like Microsoft Remote Connectivity Analyzer and Microsoft 365 network connectivity test tool, you can test your existing network.

      See best practices for network planning and improving migration performance.

     Note: If you have already configured your Office 365 tenant, you can directly skip to Step 6 in this section.

   • Step 3: Choose a Microsoft 365 license option that suits your requirements

     Microsoft 365 is available as a cloud-based subscription service or as a one-time purchase of a perpetual license. Office 365 has different licensing plans each suited to different user requirements.

     It is recommended to thoroughly evaluate the Office 365 business plans and Office 365 enterprise plans to determine which one aligns with your organization's requirements. Alternatively, you can also sign up for a 30-day free trial of Office 365 and test the various plans before making a final decision.

   • Step 4: Set up and prepare the target Office 365 tenant

     Setting up the target Office 365 for the migration involves creating the tenant and configuring it to receive the migrated data from Exchange 2019.

     1. Create an Office 365 tenant: Plan for the tenant creation and deployment. See the tenant roadmap for Office 365.
     2. Sign in to the Microsoft 365 admin center: Go to the 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, you can configure and customize the settings such as email domains, language, and time zone to suit your organization's needs.
     4. Configure Azure AD Connect: Azure AD Connect is used to synchronize your on-premises Active Directory with Azure AD. This step is necessary if you want to retain your on-premises in a Hybrid environment and to enable single sign-on (SSO) for your users.
     5. Configure email clients and apps: If you want to install Office 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 to set up additional services such as SharePoint, OneDrive and Teams.
     7. Establish data retention policies: With Office 365, you have the ability to retain data in accordance with compliance and legal requirements. Set up data retention policies to meet your organization's compliance needs, and if necessary configure retention policies for specific mailboxes or groups of users
   • Step 5: Add and verify the custom domain on Office 365

     If you have a custom email domain from your hosting provider to which you want to 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 your email 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 to the correct mailbox.
   • Step 6: Create mailboxes and 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.

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

     If you want to migrate Public folders from Exchange 2019, ensure that you create and configure Public folders and make them mail enabled on Office 365.

     1. Create Office 365 Public folder and assign mailbox user
     2. Enable In-Place Archive mailboxes in Office 365
   • Step 7: Set the impersonation role on the source to the admin user

     Ensure that you set the following permissions to the admin account on the source and target server and that the mailboxes you migrate are not hidden from the address lists.

     1. On the source
        1. ApplicationImpersonation
        2. View-Only Configuration - Run the cmdlet New-ManagementRoleAssignment using the Exchange Management Shell to assign the View-Only Configuration role to the admin.
     2. On the target
        1. ApplicationImpersonation

     Setting impersonation rights in Office 365 is a simple process that can be done quickly using the Admin Center. Assign the Organization Management role group to the admin user in Exchange online. It is an elevated permission that is required to migrate Public folders.

   • Step 8: Verify the mailbox of the admin account

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

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

      Follow the steps to increase the message size on Office 365 to 150MB.

3. Exchange 2019 to Office 365 Migration using EdbMails

   The following methods can help you perform Exchange 2019 to Office 365 migration with EdbMails Exchange migration.

   1. Direct migration from Exchange 2019 to Office 365
   2. Hybrid Exchange 2019 migration to Office 365
   3. Migrate Exchange 2019 to Exchange online with EDB file
   4. Import 2019 mailboxes to O365 by using PST files

   Method 1: Direct Exchange 2019 to Office 365 migration

   • Step 1: Install EdbMails migration software for Exchange server
     • Download EdbMails and install the application on any computer that is connected to the source and target environment. You can also perform the migration operation by installing EdbMails on a Windows computer.
     • Launch the application and click 'Login' or 'Start Your Free Trial'.
     • Select the migration method as 'Live Exchange migration'.

      See the detailed list of EdbMails system requirements for Exchange migration.

     

     

     Note: If the standard folders, such as Inbox, Calendar, and Contacts, on your source Exchange server mailboxes are in a different language, follow these instructions to properly migrate them to the corresponding system folders on the target server.

     For example, if your source Inbox folder is named 'Boîte de réception' in French, migrating it directly to the destination server will not automatically map it to the 'Inbox' folder on the target server. In order to ensure that the folder is mapped correctly, you must change the regional settings on Office 365 to match the language of the folder in the source mailbox.

   • Step 2: Sign in to Exchange 2019 as a Global Admin user

     In the source Exchange connection window, select 'Connect using Global Admin User'. You have several options of connecting to your Exchange server. For example, you can load the mailboxes using a CSV file, connect to a specific user or even connect to a Hosted Exchange. See the different Exchange server connection methods supported by EdbMails.

      With EdbMails, you can transfer mailboxes, public folders, and migrate In-Place Archive to Office 365

     

   • Step 3: Select mailboxes and set up connection with Office 365 server
     • Select the mailboxes and folders from the Exchange that you want to migrate to Office 365.

        Tip: If you’re migrating with EdbMails for the first time, the migration is a full migration. On subsequent migrations from the same source to the target, the migration is incremental, which migrates only the new and updated items. If you already have duplicate items in your source mailboxes, you can remove them with the duplicate remover tool. See how to delete duplicate emails in Exchange.

     • Click 'Migrate to Office 365' to set up the connection with the target server

       

        Tip: EdbMails provides the following additional options to help you customize the migration task.

       • Additional Include and Exclude Filter Options
       • Filter emails by Date: Migrate to Office 365 by applying the Date filter
       • Filter emails by Size: Exclude emails from migration larger than a specified size.
       • Filter emails by domain: You can also filter emails by the sender address or the email domain.
       • Remove deleted source items from the target folder: Selecting this option syncs and removes the deleted items at the source from the target folders.
       • Forcefully update items: You can choose to manually update and sync the source mailboxes with the target mailbox.
   • Step 4: Sign in to Office 365 tenant as a Global Admin

     EdbMails supports both modern and classic authentication. Connect to the target server by selecting Auto or Manual registration for modern authentication and the connection method as Mailboxes, Public folder or Archive Mailbox.

     EdbMails is a highly secure application and uses TLS encryption along with OAuth 2.0 authentication for login. It does not store your user credentials.

      Connect to Office 365 server with secure modern authentication

     

      Tip: When you use EdbMails for your mailbox migration, the mapping feature can save you time and effort by automatically matching and mapping the mailboxes and folders between your Exchange server and Office 365. This feature is particularly useful when migrating a large number of mailboxes.

   • Step 5: Start the migration to Office 365 from Exchange 2019

     Start and monitor the migration operation after you complete the mailbox mapping. Finally, verify the count of migrated emails, folders and mailbox items with EdbMails text-based log report.

     

   Method 2: Hybrid Exchange 2019 to Office 365 migration

   In a Hybrid scenario, the Exchange and Office 365 mailboxes coexist in the same Active Directory (AD) environment. This migration method can be a good option if you want to gradually move to Office 365 from Exchange or if you have specific on-premises applications that you need to keep running.

   EdbMails simplifies Hybrid migrations and enables you to directly migrate mailboxes from on-premises Exchange 2019 to Office 365 within or to the Hybrid environment.

   Hybrid migration prerequisites

    Make yourself familiar with the Exchange server Hybrid deployment and learn about the Hybrid deployment components. Consider the following points and ensure that you have the required bandwidth for the migration.

   • Ensure that you meet the Hybrid migration prerequisites
   • Install the latest version of the Exchange Server 2019 cumulative update on your on-premises servers.
   • In order to synchronize your on-premises Active Directory with Azure Active Directory in a hybrid deployment, you have to configure directory synchronization with the Azure AD Connect tool.
   • Update any Edge Transport servers to the latest CU.
   • Register any custom domains you want to use in the Hybrid with Office 365.

   Steps for Exchange 2019 to O365 Hybrid migration

   • Step 1: Prepare for the Hybrid migration
     • Confirm that your environment meets the necessary requirements for a hybrid migration.
     • Ensure stable network connection between on-premises Exchange server and Office 365
     • Set up necessary permissions and accounts in both environments
   • Step 2: Set up the Exchange hybrid configuration
     • Install Hybrid Configuration Wizard (HCW)
     • Run the wizard and configure the necessary settings
   • Step 3: Configure directory synchronization
     • Install Azure AD Connect tool
     • Run the tool and configure the necessary settings
   • Step 4: Perform Hybrid mailbox migration with EdbMails
     • Use EdbMails to migrate Hybrid Exchange to Office 365.
     • Your Public folders cannot exist on Office 365 and on-premises Exchange at the same time. See a workaround solution to migrate Public folders in an Exchange hybrid.
   • Step 5: Monitor and finalize the migration to Office 365
     • Verify the migration with EdbMails log report
     • Configure appropriate routing by adding MX records
     • Decommission on-premises Exchange server if you no longer require it.

   Method 3: Migrate Exchange 2019 to Microsoft 365 with an EDB file

   If you have an EDB file from Exchange Server 2019, you can use EdbMails for EDB to Office 365 migration. This method is beneficial in situations where your Exchange server is temporarily unavailable, or if you have a corrupted EDB file that needs to be repaired and migrated.

   In contrast to other methods that rely on PowerShell cmdlets, EdbMails offers a more user-friendly and efficient solution for migrating mailboxes from an EDB file. It can transfer all the mailbox data including emails, contacts, calendars, and tasks, with minimal effort. Additionally, the software is equipped with a simple and intuitive user interface. The following steps describe the migration operation with EDB.

   • Step 1: Install EdbMails software for EDB to Office 365 migration

     After installing the application, select the migration technique as 'EDB to Office 365, EDB to Exchange, EDB Public folder'.

     

   • Step 2: Select the Exchange 2019 EDB file from your computer

     Take a copy of your EDB file. Click 'Browse for EDB' and add the required file that contains the Exchange mailboxes and folders.

      Tip: If your EDB file is corrupted, damaged or inaccessible, EdbMails can fully repair and restore the contents. Learn how to repair a corrupted EDB file with the tool.

     

   • Step 3: Preview and select the mailboxes for Office 365 migration

     After the repair operation, you can preview emails, contacts, folders, calendars, tasks. Select the required mail items, folders, mailboxes and select 'Migrate to Office 365'.

     

     To connect to your Office 365 server, select the 'Auto Registration' method and sign in with your admin credentials. Then, choose the preferred method for migrating mailboxes and map the folders and mailboxes from the source to the target location.

     

   • Step 4: Start migrating Exchange 2019 mailboxes to Office 365

     Start importing your mailboxes from EDB to Office 365 and use the text-based log report to verify the number of items, folders and emails that have been migrated. The application enables you to pause and resume the migration without causing data loss.

   Method 4: Exchange 2019 to Office 365 migration with PST files

   If you have mailboxes saved or exported as PST files from Exchange server 2019, EdbMails can also assist you in importing the PST to Office 365. Download and run EdbMails if it hasn't already been installed on your system. The following steps outline the PST import operation.

   • Step 1: Install EdbMails for PST to Office 365 migration

     Before you start the migration, ensure you have a backup copy of the PST. On the EdbMails migration selection popup, select the migration method as Office 365 migration.

     

   • Step 2: Click Migrate PST to Office 365 and add the PST files

     To add multiple PST files, close the Connect to Office 365 (Source) connection window and follow the steps from 1 to 3 as shown.

     

   • Step 3: Log in to your Office 365 tenant as a Global Admin

     EdbMails supports both modern and classic authentication. Connect to the target server by selecting Auto or Manual registration for modern authentication and the connection method as Mailboxes, Public folder or Archive Mailbox.

      Connect to Office 365 server using secure modern authentication

   • Step 4: Start mailbox migration from Exchange 2019 to Office 365

     The mapping activity in EdbMails can automatically match and map the mailboxes and folders from the PST file to Office 365. This activity saves time when you’re migrating a large number of mailboxes. After you complete the migration, verify the count of the migrated items, folders and mailboxes.

      Tip: Manual mapping is time-consuming and may result in incorrect mapping when migrating a large number of mailboxes and folders to the target Office 365 server. EdbMails can easily auto-map folders and mailboxes, saving the user from having to map them manually during migration.

     After you complete the migration, verify the count of the migrated items, folders and mailboxes with the help of EdbMails log report.

4. Post Migration Tasks

   • Step 1: Verify that all mailboxes have been successfully migrated

     One of the most important steps after migrating is to ensure that all the Exchange mailboxes have been moved to Office 365. You can use the log report from EdbMails or log in to your account and verify the mailbox items.

   • Step 2: Test the functionality of email, calendar, and other features

     After the migration is complete, test all the features of the email, calendar and other features. For example, send and receive emails, create and manage calendar appointments and check if all the entries are successfully migrated.

   • Step 3: Update the MX records to point to Office 365

     To receive messages on Office 365, change the DNS records known as MX records to enable email to work with the new server you have migrated to. In addition, configure the Autodiscover record to allow Outlook to connect to the migrated mailboxes.

   • Step 4: Test email connectivity and perform a backup

     It is important to test the email connectivity after the migration to ensure that you are able to send and receive emails correctly. Take a complete Office 365 mailbox backup to ensure that you have a copy in case of any unexpected issues.

   • Step 5: Create a new Outlook profile for users in the new domain

     Ensure you have the latest version of Outlook installed to avoid compatibility issues. Configure the Outlook profile for each user in your domain if Outlook has problems connecting to Office 365 mailboxes.

   • Step 6: Decommission and uninstall Exchange server 2019

     If you are not using a Hybrid Exchange deployment, you can uninstall and decommission the Exchange 2019 server after you finish the migration. The following steps provide an overview on how you can decommission the Exchange server.

     1. Update all DNS records to point to Office 365 and remove any MX records for the on-premises Exchange server.
     2. Verify that no mailboxes are hosted on the on-premises Exchange server by running the Get-Mailbox command in the Exchange Management Shell.
     3. Remove all connectors from the on-premises Exchange server to Office 365. This can be done by running the Remove-OutlookAnywhere, Remove-WebServicesVirtualDirectory, and Remove-EcpVirtualDirectory commands in the Exchange Management Shell.
     4. Disable all email addresses and email domains from the on-premises Exchange server by running the Set-AcceptedDomain and Set-EmailAddressPolicy commands in the Exchange Management Shell.
     5. Remove any remaining public folders that are hosted on the on-premises Exchange server. Run the cmdlets Remove-PublicFolder and Remove-PublicFolderDatabase in the Exchange Management Shell.
     6. Backup all the necessary configuration data, such as Outlook and ActiveSync device partnership, from the on-premises Exchange Server by running the Export-AutoDiscoverConfig and Export-ActiveSync commands in the Exchange Management Shell.
     7. Uninstall the Exchange server components from the Add/Remove programs in the Control Panel.

        Here are the steps to uninstall Exchange server from your computer.

        • Click Start > search for Exchange Management Shell
        • Run the following command to stop all Exchange services:
          Command: Copy & Paste

          Stop-Service MSExchange*

        • Run the following command to prepare your organization for Exchange removal:
          Command: Copy & Paste

          setup.exe /mode:uninstall /role:all

        • Wait for the command to finish running and then follow the prompts in the Exchange Setup wizard to remove the Exchange server from your computer.
        • After the uninstall process is completed, restart the computer and verify that the Exchange server and all related services have been removed from your computer by opening services.msc and checking the services list.
        • Finally, remove any other Exchange related products from the Control Panel.

      See the list of post migration tasks to complete after you finish the Office 365 migration.

Exchange migration troubleshooting

 See Exchange migration troubleshooting guide for possible solutions related to common migration errors. For more information on EdbMails Exchange migration refer to the frequently asked questions (FAQ)