A Complete Guide to Perform Hybrid Migration in Office 365

Hybrid deployment permits migration of on-premises mailboxes to the Microsoft Cloud or cloud mailboxes to on-site. In other word, hybrid deployment helps in Exchange to Office 365 migration or vice versa. This approach permits users to move the already existing mailboxes between Exchange Online and Exchange Server, instead of making a new mailbox for users and importing the information of users. In the following section, we will discuss the prerequisites and ways to perform hybrid migration in Office 365.

User Queries Regarding Hybrid Migration in Office 365

Various users raise concerns regarding this deployment between O365 and on-premise server. After surfing on various forums, we have collected few queries which are stated below:

“I am an IT admin for my organization, we are planning to move our on premise Exchange  mailboxes to cloud. Can anyone suggest how we can proceed with this migration?”

“We have transferred our mailboxes from Exchange to Microsoft cloud. Please suggest what should be done after the migration is complete? Thanks in advance.”

“Our organization is currently using Office 365 collaboration suite. We are looking for an automated solution to move all the mailboxes to On-site Exchange.”

“Our company wants to migrate from Exchange Online to On-site. What are the prerequisites that needs to be performed before this migration.”

Migration in Office 365

Requirements for Hybrid Deployment in Exchange Online

  • Need of proper permissions before performing the migration.
  • Hybrid deployment is arranged between on-premises and Exchange online organization.
  • Make sure that Mailbox Replication Proxy Service is enabled if the user is using Exchange 2013.

How to Perform Hybrid Migration in Office 365

To successfully move mailbox from on premise to Office 365 or vice versa, the users must follow the steps given below:

Step 1: Create Endpoint of Migration

Prior for performing on and off boarding remote migration in Exchange hybrid deployment therefore, it is recommended to make Exchange remote migration endpoints. It contains the settings of connections for on-premises Exchange server, which is using MRS Proxy service that is needed for performing migration of Exchange Online.

Step 2:  Enable Proxy Service

If the proxy service is not enabled on, the on-premises Exchange 2013 servers then follow the mentioned steps:

  • Open EAC and click on servers then, virtual directories.
  • Choose CAS >> EWS virtual directory >> edit.
  • Click on the check box of MPS Proxy enabled >> click save.

Step 3: Use EAC for Moving Mailbox

  • There is a remote migration wizard on the tab of Office 365 or Exchange Server for performing hybrid migration in Office 365:
  • Move On-Premises Mailboxes to Cloud (O365)
  1. Open EAC, navigate to Office 365, click on recipients, and choose migration option.
  2. Choose Add option >> migrate to exchange online option.
  3. Type page on select migration >> remote move migration option >> next.
  4. Click on Add option and choose on-premises users to move the data to Office 365 >> choose add option >> OK.
  5. Now, enter the credentials on the Windows page and enter on-premises administrator account name in the on-premises administrator account name.
  6. On the migration endpoint confirmation page, verify FDQN of on-premises Exchange server list when the wizard confirms endpoint migration.
  7. On the move configuration page, enter a name of batch migration in the new migration batch name field.
  8. Choose at least one recipient for receiving for receiving batch complete report. Select automatically complete migration batch after verification >> new.
  • Move O365 Mailboxes to On-Premises
  1. Open EAC >> click on Office 365 then click on recipients >> migration.
  2. Choose Add option and choose migrate from Exchange online option.
  3. Choose the users that are required to be moved >> Next.
  4. Click on add option to choose Exchange online users to be moved from on-premises >> choose add >> ok.
  5. On the confirmation migration endpoint page, verify the FDQN of on-premises Exchange server list.
  6. Enter the new migration batch name on move configuration page and click down arrow to select the target delivery domain for mailboxes.
  7. Choose one recipient on the start batch page and verify the automatically batch starting >> new.

Step 4: Remove Batches of Complete Migration

Once the hybrid migration in Office 365 then, it is recommended to remove completed migration batches for minimizing the errors by following the steps given below:

  • Open EAC and navigate to Office 365 then select recipients >> migrations.
  • Click on delete option after the completion of migration in batch.
  • Click on yes for the confirmation.

Step 5: Re-enable OWA for Offline Access

Offline access of OWA allows the users to utilize their mailbox when users are not connected via network. However, if the user moves from Exchange mailboxes to Exchange Online then, they need to reset offline access in their browser for Outlook utilization.

Conclusion

As already discussed that hybrid deployment is done by organizations who want to switch/ move between on-site server and cloud server. After understanding this, we have discussed the same hybrid Migration in Office 365 that makes easy for users to transfer mailboxes in proper way by following the steps sequentially.

Add a Comment

Your email address will not be published. Required fields are marked *