Chat now with support
Chat with Support

Reference Materials for Migration 8.15 - Migrating to Microsoft Office 365

Introduction BeforeYou Begin Migration to Microsoft Office 365 Post-Migration Activities Tracking the Migration Progress Hybrid Migration Scenarios Advanced Migration Topics Troubleshooting Migration to Microsoft Office 365

Redirecting Email to Microsoft Exchange Online

After you finished migrating mailboxes to Microsoft Exchange Online, you may need to update the Mail Exchange (MX) records in your DNS so that all mail is redirected to the cloud. This step can only be performed after all on-premises mailboxes are migrated to Microsoft Exchange Online. Note that this step is mandatory only if you plan to completely decommission your on-premises Exchange infrastructure.

For information on how to do that, go to

Updating Outlook Profiles

During migration, Migration Manager for Exchange switches mailboxes from the source Exchange server to Microsoft Office 365. Before users can start working with their new cloud mailboxes, their Microsoft Outlook profiles must also be updated. To update Outlook profiles you may use Client Profile Updating Utility (abbreviated to CPUU) shipped with Migration Manager. The utility allows you to update Outlook profiles automatically and transparently.

Caution: You have to provide all users with their Microsoft Office 365 passwords before CPUU switches Outlook profiles. Otherwise, the user cannot log on to his or her mailbox and get an access to his/her emails after the switch.

For information on how to update Outlook profiles using CPUU, see the Client Profile Updating Utility Administrator Guide included in the Migration Manager documentation set.

Decommissioning Exchange Servers (Optional)

After you successfully migrated all mailboxes from on-premises Exchange organization to Microsoft Office 365, ensured that all users can connect to their cloud mailboxes, and mail flow is established properly, you may start decommissioning your on-premises Exchange servers. Refer to Microsoft documentation for information on how to do that.

For information on how to decommission existing Exchange servers, go to

Switching to Other Directory Synchronization Tools (Optional)

Establishing co-existence of objects between Active Directory domain and Microsoft Office 365 using Migration Manager for Active Directory is supported only during calendar synchronization and mailbox migration. To continue synchronizing objects after you finished migrating mailboxes, consider to use the Microsoft Azure AD Connect (link) or Quest One Quick Connect solution (link).

Note: Windows Azure Active Directory Sync (DirSync) and Azure AD Sync Azure AD Connect can be also used. However, these tools are now deprecated by Microsoft and will reach end of support on April 13, 2017. So if still you use one of them, it is recommended to upgrade to Azure AD Connect.

You may also need Quest One Quick Connect for the following procedures described below:

  • Synchronizing password changes for users
  • Synchronizing users membership in distribution lists

Synchronizing Password Changes

You may synchronize password changes from Active Directory to Microsoft Office 365 using Quest One Quick Connect. For that, you will need to set up the same matching in One Quick Connect as you configured in Migration Manager for Active Directory (Microsoft Office 365) console and then set up password changes synchronization.

TIP: The most reliable way to achieve the same matching is to use users' UPN prefixes as matching criteria.

For information how to use Quest One Quick Connect, refer to its documentation.

Synchronizing Distribution List Membership

You may use One Quick Connect to synchronize users' membership in distribution lists (DLs) from Microsoft Office 365 to Active Directory. For information on how to do that, refer to Quest One Quick Connect documentation.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating