Which migration strategies are supported for this scenario?

HOTSPOT

A company has an on-premises deployment of Microsoft Exchange Server 2016. The company is migrating to Office 365.

During the migration, users must be able to see availability information between the on-premises deployment and Office 365.

You need to identify the appropriate mailbox migration strategy to use.

Which migration strategies are supported for this scenario? To answer, use the drop-down menus to select the correct answers.

View Answer

Answer:

Explanation:

Box 1: Cutover migration: No

You can migrate the contents of user mailboxes from a source email system to Office 365 all at once by using a cutover migration.

Box 2: Staged Migration: No

You can’t use a staged migration to migrate Exchange 2016, Exchange 2013 or Exchange 2010 mailboxes to Office 365.

Box 3: Remote Move migration: Yes

The only migration method that enables users to see availability information between the on-premises deployment and Office 365 is a remote move migration.

A remote move migration is used to migrate on-premises Exchange mailboxes to Exchange Online in an Exchange hybrid deployment. You must have an Exchange hybrid deployment to use a remote move migration. With a hybrid deployment, you get the following capabilities:

Even if you plan to permanently move your on-premises email organization to Exchange Online and Office 365 over a longer period of time, you can take advantage of these hybrid deployment features during the transition.

Box 4: IMAP Migration: No

You can use the Internet MessageAccess Protocol (IMAP) to migrate user email from Gmail, Exchange, and other email systems that support IMAP migration.

References:

https://technet.microsoft.com/en-us/library/jj863291(v=exchg.150).aspx

https://support.office.com/en-us/article/What-you-need-to-know-about-a-staged-email-migration-to-Office-365-7e2c82be-5f3d-4e36-bc6b-e5b4d411e207