Migrate Exchange to Office 365

Best Method to Migrate Exchange to Office 365

There are inbuilt features such as staged and cutover migrations within Microsoft for migrating your Exchange Server mailboxes to the Microsoft 365 portal, however, in reality these processes end up being quite complicated due to their lengthy prerequisites, complicated configurations, unexpected downtime and a real chance of data inconsistencies during the migration process. EdbMails Exchange to Office 365 migration tool goes at the source of migration complexities, as opposed to working around the limitations and it has been developed solely to eliminate migration problems. The tool manages the entire migration of mailbox data, from emails, contacts, calendars, tasks, journals, appointments, to the entire notes section, keeping everything intact and consistent throughout the migration.

EdbMails lets the user migrate mailboxes, public folders, shared mailboxes, archives etc. This can be beneficial for different organizations that require various kinds of migration. Native methods usually rely on various complicated PowerShell scripts and extensive knowledge of these technologies. However, EdbMails interface provides a simplified solution that is easy to navigate and operate. It would enable the companies and individuals to perform migrations with confidence, minimize all potential risks and ensure seamless migration into Office 365 and utilize its 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 Office 365 licenses for all users that will be migrated.
      • 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: Select appropriate Exchange to Microsoft 365 migration type

     The first step that needs to be done is planning the migration of Exchange to Microsoft 365 mailbox. Available migration options depend on your target and source environments.

     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 network and bandwidth requirements
     1. Network requirements
        1. Network Configuration: Make yourself aware of the networking road map for Microsoft 365. You should be capable of planning, deploying and administering your network.
        2. Internet Connectivity: It is important to have a robust and reliable internet connection before migrating the exchange environment to office 365. The internet should also be able to maintain high bandwidth to transfer data and should not face any kind of network congestion.
        3. Firewall and Port Configuration: Review the firewall and port configurations to allow required data transfer to Office 365 tenants.
        4. DNS Configuration: Review the DNS record and configure them to point to Office 365 tenants. These must be set up with MX records and Autodiscover to ensure mails are routed to Office 365 tenant after migration.
        5. Network Latency: Check and configure Network Latency for the smooth data transfer as High Network Latency will result in low migration speeds. (refer how Microsoft 365 networking differs)
        6. Office 365 Throttling: Microsoft will limit the number of concurrently moved mailboxes in order to provide a stable service. Consider the Office 365 throttling policies while migrating large mailboxes.
        7. Network Security: Ensure that the transfer of the data over the network is secure. This includes configuring any encryption, authentication and access controls.
        8. Network Load Balancing: Take into consideration the Network load balancing to have balanced data transfer over the various networks and avoid any bottlenecks.
     2. Bandwidth requirement

        The bandwidth requirements for migrating Exchange to Office 365 can change, depending on the number of mailboxes, size of mailbox and type of migration method used. Use Microsoft Remote Connectivity Analyzer or connectivity test tool to test your network connectivity.

        1. Number of mailboxes: It impacts the bandwidth requirement based on the number of mailboxes you plan to migrate. As the number of mailboxes to be migrated grows, your bandwidth requirement is increased. Check the bandwidth requirement of office 365 migration.
        2. Size of mailbox: It also impacts on the bandwidth requirement of Office 365 migration based on size of mailbox. As the mailbox size increases, bandwidth requirement is increased.
        3. Migration Type: The type of migration you are undertaking will influence the network bandwidth requirements. For instance, a cutover migration in which all mailboxes are migrated to the destination at one time will require a large amount of bandwidth compared to a staged migration in which mailboxes are migrated in smaller groups.
        4. Migration schedule: The schedule of migration is a further influential factor for network bandwidth. For instance migrating off peak hours or at the weekend when network traffic is typically lower will reduce the overall bandwidth requirements.
        5. Network infrastructure: The network infrastructure which the migration will be utilizing is also a significant factor. If the infrastructure in place supports high bandwidth it will be capable of handling the migration effectively.
        6. Network Latency: Network Latency between source and destination servers also impacts the migration. High Network Latency necessitates greater bandwidth.

       See best practices for network planning and improving migration performance.

   • Step 4: Choose appropriate Microsoft 365 licensing plan

     The Microsoft 365 is a cloud-based service which is available as a subscription and comes with a list of licensing plans, one of which caters to certain user requirements. It is advised to analyze the office 365 business plans and office 365 enterprise plans in detail in order to choose the most appropriate one for your organization. You can also sign up for a 30-day free trial of Office 365 to test out the various plans before making a final decision.

   • Step 5: Set up your target Office 365 Tenant for Migration
     1. Create the Office 365 Tenant: Develop a plan for the implementation of the tenant and deploy the tenant. See the tenant roadmap to Office 365.
     2. Sign in the Microsoft 365 admin center: Microsoft 365 admin center (https://admin.microsoft.com/) and log in with global admin credentials.
     3. Configure the Tenant setting: Once the tenant is created, you would like to configure and customize the settings for your needs, such as email domains, language and time zone etc.
     4. Configure Azure AD Connect: Azure AD Connect is the tool used to synchronize your on-premises AD to Azure AD. This step is necessary if you want to keep on-premises in a Hybrid environment and to enable single sign-on (SSO) for your users.
     5. Set up email clients/applications: If you plan to install Office 365 apps and Outlook, review System requirements for Microsoft 365 and Office configuration support matrix. Since Office 365 is a cloud based solution, it will be valuable to know where your Microsoft 365 customer data resides.
     6. Office 365 services setup: Beside the mail setup you will like to setup other services, such as share point, OneDrive, Teams.
     7. Setup data retention policies: Data retention is configurable in office 365 to ensure that your data retention is legally compliant and can be set according to business requirements. Setup data retention policies in order to meet your organization's compliance requirements, optionally set mailbox specific data retention policies.
   • 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 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 youremail addresses and other Office 365 services.

      To set up your custom domain, follow these steps:

     1. Confirm ownership of your domain by adding a TXT record to your DNS settings.
     2. Add new domain to your Office 365 tenant. You can add either your own domain 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. Your DNS records must be updated before you can send and receive e-mail from your new Office 365 e-mail address. You can add or update your MX records after your migration is complete.
   • 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 an Office 365 Public folder and assign permissions to admin users.

        If you are migrating to Office 365 archive mailboxes, ensure to enable In-Place Archives on the Office 365 server.

     2. Steps to enable In-Place Archive mailboxes in the Office 365 server
   • Step 8: Set admin user impersonation rights in the source server

     In case you connect to the source Exchange server using the global admin account, do not forget to set 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 admin account mailbox

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

   • Step 10: Set up Office 365 for sending and receiving large messages

     The message size limit can be set to 150 MB on Office 365 Migration. This option will allow us to bypass message size restrictions during the migration process.

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 and make new mail routing to Office 365

     The MX record must be updated to make the email routed to the new server. Also Autodiscover records must be configured to make the new mailboxes connected with the client, such as outlook.

   • Step 2: Create Outlook profiles in the new domain

     If users are having trouble connecting outlook to Office 365 mailboxes, then manually configure Outlook profiles in the new domain.

   • Step 3: Uninstall and decommission the source Exchange server

     The following points provide a view of the actions taken to decommission on-premise exchange server.

     • Confirm all mailboxes have been migrated to Office 365.
     • The status can be checked either in the Exchange admin center or with running the PowerShell Get-MailboxStatistics cmdlet.
     • Make sure that every Outlook client is connected to Office 365. You may verify it using the Test-OutlookWebServices cmdlet on each Outlook client.
     • You must disable all the mail flow on the Exchange server (delete Receive Connector or disabled the SMTP services).
     • All public folders must be migrated to Office 365. You may verify it using the Get-PublicFolder cmdlet.
     • Uninstall the exchange software from the control panel.
     • Remove the remaining exchange-related hardware or machines from the existing servers.
     • Make sure that no mailbox or public folder remains on the exchange server.
     • And then delete the server from the Active Directory and the records from the DNS servers.
     • Once you are confident that everything has been migrated, then you will be able to decommission the 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.