Steps for Exchange 2010 to Office 365 Migration Explained
The reason to look for a method to migrate Exchange 2010 to Office 365 is quite simple. It is no longer officially supported and is therefore filled with numerous security vulnerabilities. Moreover, problems that occur within this on-premise setup have to be fixed manually. This is quite time-consuming and complex, especially for those organizations that are shifting their data for the first time.
As we know, the Exchange server has been a core component of managing communication in various organizations. So whenever a situation arises where they have to move from the Exchange server, many long-term users are hesitant. However, they can keep all their concerns at bay. As we have just the right solution for this task, let’s get straight to it.
Table of Contents
Professional Means to Migrate Exchange 2010 to Office 365
Expert-endorsed Exchange to Office 365 migration tool, which outshines all the other tools of the same variety.
It comes with industrial-standard protocols coupled with an easy-to-understand interface. With which even technically naive users will have no difficulty moving their data.
Therefore, users no longer need to look elsewhere to solve their migration-related tasks, as this tool is more than enough for all their needs.
Some of the groundbreaking features that make the tool a favorite of experts and beginners alike are as follows:
- You can migrate Exchange mailbox items, such as email, contacts, and calendars.
- This tool supports multiple user mailbox migrations simultaneously, using admin credentials.
- The platform can be used to migrate Exchange 2016 to Office 365 as well.
- You have the provision to transfer newly arrived data using delta migration.
- There’s a date filter available to prioritize the transfer of important data first.
- You can map Exchange users to Office 365 users for authentic migration.
- The software maintains calendar recurrence for scheduled events.
- It provides the provision to retry failed migration for uninterrupted progress.
- You can prioritize the migration of important mailboxes to be done first.
- It allows you to migrate user mailboxes present in any subdomain or organizational unit.
- The tool comes with an in-built dashboard to track the ongoing migration process.
- It is compatible with various operating systems, including Windows Server 2012, 2016, Windows 10, and 11 (64-bit).
Simple Steps to Transfer Exchange Server Data Via the Tool
Step 1. Download and Install the tool on the Machine that houses the data. Then fire up the utility, select Exchange as your Source and Office 365 as Destination.
Step 2. Go to the Workload Section, make the task selection, and apply the required Date Filter as well. (If you want to migrate Groups toggle the button at the bottom of your screen).
Step 3. On the Source page, type in Exchange Server details like Version, admin ID and password, and the IP address of the Exchange Server and Active Directory. Click on Validate and move ahead by pressing Next.
Step 4. On the Target Page, type in the Admin Email and the Application ID, then, as in the last step, Validate before hitting Next. After which, you can continue to migrate Exchange 2010 to Office 365 environment
Step 5. Now you will find yourself in the Users section, where it is up to you to decide upon the method to map users from source to destination. Choose one of three ways out of (Fetch, Import, Download).
Step 6. Once the users load into the preview window, you can separate the ones that are to be migrated on a priority basis by clicking on the star icon beside them.
Step 7. Click on the validate button to confirm all selections. Once validated, hit the Start Migration button to begin the data transfer.
Also Read: Guide on How to Migrate Office 365 to Office 365 in an Easy Manner
Next up, we have a few other migration methods that require a more hands-on approach from the users.
Cutover Method to Migrate Exchange 2010 to Office 365 Manually
Step-1. Domain Verification
- Login to Microsoft 365
- Select Setup > Domains.
- On the Domains page, click “Add domain” to start.
- Choose “Add domain”, enter your on-premises Exchange domain, then click “Next.”
- On the Verify Domain page, select your DNS provider and follow their instructions.
- Wait 15 minutes, then click “done,” followed by “verify now,” and finally, “Finish.”
Step-2. Connect Office 365 to Email System
- Visit EAC, hop over to Migration Section in Recipients.
- Click “More”, then press “Migration endpoints.”
- On Migration Endpoints page, click “New”.
- Select “Outlook Anywhere”, and click “Next.”
- Provide the following information on the Enter on-premises account credentials page:
- Email address: Enter any user’s email address
- Account with privileges: Enter the administrative username
- Password of account with privileges: Enter the administrator account’s password.
- Click “Next” and proceed:
- On successful connection, settings are displayed. Click “Next.”
- If the connection test fails, enter:
- Exchange server (FQDN).
- RPC proxy server (FQDN).
- On “Enter General Information” page, type endpoint name and leave other at default value.
- Click “New” to create the migration endpoint.
Step-3. Create Migration Batch
- In EAC visit Recipients > Migration
- Click New > Migrate to Exchange Online.
- Select “Cutover migration” and click “Next.”
- Confirm migration endpoint info, then click “Next.”
- Create a new batch with the endpoint.
- Name the batch (no spaces) and click “Next.”
- Choose to start the batch now or later.
- Press “New” and build a batch.
Step-4. Start Cutover Migration
- Within EAC, visit Recipients > Migration.
- On the dashboard, choose batch and press Start.
- Migration status “Syncing” indicates a successful start.
Step-5. Reroute Emails to Microsoft 365
- Point your MX records towards Office 365.
- Use method prescribed by your Domain provider.
Step-6. Delete Batch
- Within EAC Visit Recipients > Migration.
- There, pick your batch and click Delete.
- Revisit the Migration section to check that the batch is no longer there.
Minimal Hybrid Data Transfer Technique
Step-1. Domain Verification
Repeat the same steps as mentioned in the Cutover Migration section
Step-2. Begin Hybrid Migration
- In the Microsoft 365 Admin center, go to Setup > Migrations.
- Within the Migrations page, pick Email.
- Then, visit the Migrate your email page, and click Get started.
- Download the Hybrid Configuration Wizard.
- Run the downloaded application.
- Accept default values for the On-premises Exchange Server Organization.
- Use current Windows credentials for both Exchange and Microsoft 365.
- Select Minimal Hybrid Configuration on the Hybrid Features page.
- Finally, choose Update to prepare on-premises mailboxes for migration.
Step-3. Create Users Via Directory Synchronization
- On “User Provisioning” page, choose “Synchronize my users and passwords one time”.
- Download Azure AD Connect wizard and run it on the default settings
- View the synchronized users on Data migration page after which it automatically closes.
Step-4. Provide Microsoft 365 License to Users So that they have a location to migrate Exchange 2010 to Office 365.
Step-5. Start Mailbox Migration
- Navigate to Setup > Data migration.
- Choose Exchange as your data service.
- Select the users to migrate and click Start migration.
Step-6. Make changes to DNS records
Update all the following parameters on your Domain registrar’s site.
- A Record: Points a domain or subdomain to an IPv4 address.
- CNAME Record: Creates an alias for a domain or subdomain.
- MX Record: Specifies the mail server for receiving email.
- TXT Record: Used for domain verification or SPF/DKIM for email authentication.
How to Migrate Exchange 2010 to Office 365 Which uses IMAP Protocol
Step-1. Find the Full name of the Current Server
- Open Outlook on the web.
- Click “Settings” on the toolbar.
- Within search box, type “pop”, pick “POP and IMAP”.
- Server name is in “IMAP setting”.
Step-2. Create a mailbox list in CSV
Step-3. Connect Office 365 to Email System
- Visit EAC, hop over to Migration Section in Recipients.
- Click “More”, then press “Migration endpoints.”
- On Migration Endpoints page, click “New”.
- Choose IMAP
- Provide the server name and leave other settings at default
- On “Enter General Information” page, type endpoint name and leave other at default value.
- Click “New” to create the migration endpoint.
Step-4. Create Migration Batch and Begin Migration
- Open the new EAC,
- Go to Migration.
- Click “Add migration batch.”
- Name the migration batch
- Choose “Migrate to Exchange Online” in the mailbox migration path dropdown and click “Next.”
- Select “IMAP migration” as the migration type and click “Next.”
- Confirm completion of prerequisites and click “Next.”
- Create a new migration endpoint and name it on the Migration endpoint name page. Use default settings for the other fields and click “Next.”
- Configure IMAP settings:
- Enter the source email server’s name (e.g., imap.contoso.com) as the IMAP server.
- Keep default settings for other fields (usually suitable).
- Click “Next.”
- Verify the creation of the new endpoint, click “Next.”
- Specify the migration file by clicking “Browse” in the Add user mailboxes page, then click “Next.”
- Proceed with configuration settings by clicking “Next.”
- Set up batch migration preferences, including reporting and start/end modes.
- Click “Save” and then “Done.”
Step-5. Reroute Emails to Office 365
- Make the changes in DNS records.
- Follow the instructions given by domain registrar.
Step-6. Stop Email Sync and Delete the Migration Batch
- Ensure enough time has passed before batch removal
- Follow the same steps outlined in the Cutover Migration.
Staged Migration Procedure for Moving Mailboxes
Step-1. Preparations
- Setup Outlook Anywhere
- Assign FullAccess or Receive As permission
- Stop Unified Messaging
Step-2. Perform Domain Verification as in Cutover Migration
Step-3. Use directory Sync to Create Users
- Within 30 days assign licenses and use Microsoft Azure Active Directory Synchronization Tool or AAD Sync to create users.
Step-4. Create a Mailbox list in CSV Format
- EmailAddress is mandatory whereas others are optional
Step-5. Connect Office 365 to Email System
- Follow the same steps as the Cutover Migration.
Step-6. Create Staged Batch to Migrate Exchange 2010 to Office 365
- Signin to EAC
- Click Migration > Batch.
- Press “New Migration Batch” and follow instructions.
- Migration Onboarding:
- Enter batch name.
- Choose migration path.
- Click “Next.”
- Select Migration Type:
- From dropdown list, select “Staged migration.”
- Click “Next.”
- Prerequisites:
- Read.
- Click “Next.”
- Set Migration Endpoint by Either:
- a. Choose “Create a new migration endpoint”.
- Or
- b. Select an existing migration endpoint.
- Click “Next.”
- Upload User CSV File, Click “Next”.
- Configure Move Settings:
- Type details.
- Click “Next.”
- Schedule Batch Migration:
- Review details.
- Click “Save,” then “Done.”
- Monitor Batch Status:
- The batch status changes to “Synced.”
- Complete the Batch:
- Choose migration group.
- In the details pane, choose your preferred option.
- Click “Save.”
- Batch Completion:
- The batch status is “Completed.”
Step-7. Start Staged Migration
- Within EAC, visit Recipients > Migration.
- On the dashboard, choose batch and press Start.
- Migration status “Syncing” indicates a successful start.
Step-8. Change On-premises Mailboxes to Mail-enabled Users
- Do this to have an uninterrupted mail flow and retain proxy addresses.
Step-9. Reroute Emails to Office 365
- Make the changes in DNS records.
- Follow the instructions given by domain registrar.
Step-10. Remove Staged Migration Batch
- Login to EAC visit Migration > Batch
- Within migration dashboard, choose batch, click Delete.
Step-11. Complete Post-migration Tasks
- Assign licenses and activate accounts
- Creation of Autodiscover DNS records
- Decommissioning of On-premise Servers
Conclusion
In this article, we covered the best method to migrate Exchange 2010 to Office 365 Moreover, users who choose the utility get an unparalleled advantage over those who don’t. These include faster and more accurate data transfers. Apart from this, we also mentioned the reasons why users should skip the various manual approaches entirely.