Browse Definitions :
Definition

cutover migration

Cutover migration moves all mailboxes and data from an older Exchange server to either a newer on-premise Exchange server or to a cloud-based service.

The cutover migration process starts with the destination Exchange server -- on-premise or online -- which receives information about the mailboxes, groups, calendars and contacts. The system then provisions the new mailboxes and copies content, duplicating as much of the original system as possible.

Administrators receive reports of the cutover -- including details of failed mailbox migrations. Old mail is deleted and the Exchange administrator can send mail directly to the new server and delete the cutover migration batch. At this point, the old Exchange server can be decommissioned.

IT administrators typically perform cutover migrations through the migration dashboard in the Exchange Administration Center or the Exchange Management Shell.

The migration process is limited to Exchange deployments of 1,000 mailboxes and can take numerous hours to days depending on the number of mailboxes and the volume of migrated content.

When migration involves a larger number of mailboxes, or the process must be performed incrementally using smaller mailbox groups, administrators can opt for staged (partial) migration. Non-Exchange mailboxes can be migrated into a new Exchange server environment using Internet Message Access Protocol migration.

This was last updated in October 2015

Continue Reading About cutover migration

Join the conversation

4 comments

Send me notifications when other members comment.

Please create a username to comment.

In your cutover migration, are you moving your mailboxes to an on-premise Exchange server, or a cloud based service?
Cancel
Is cutover migration limited to Exchange servers? I thought it was a much more general term.
Cancel
Wow, this is the most technical and time consuming explanation with lots of "gotchas" glossed over. Using SkyKick automates the end-to-end migration (cutover or stages) with much less effort and no need for PowerShell scripting.

From the article: "The cutover migration process starts with the destination Exchange server -- on-premise or online -- which receives information about the mailboxes, groups, calendars and contacts." -- Where does this information magically come from? This is actually a lot of work without an automated solution like SkyKick.

From the article: "The system then provisions the new mailboxes and copies content, duplicating as much of the original system as possible." Exchange Online does not "auto-magically" provision new mailboxes, initiate to receive data or de-dupe. This is all done manually via PowerShell scripting without an automated solution like SkyKick.
Cancel
What is Skykick? I'm not seeing it mentioned here.
Cancel

SearchCompliance

  • risk assessment

    Risk assessment is the identification of hazards that could negatively impact an organization's ability to conduct business.

  • PCI DSS (Payment Card Industry Data Security Standard)

    The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of policies and procedures intended to ...

  • risk management

    Risk management is the process of identifying, assessing and controlling threats to an organization's capital and earnings.

SearchSecurity

SearchHealthIT

SearchDisasterRecovery

  • call tree

    A call tree is a layered hierarchical communication model that is used to notify specific individuals of an event and coordinate ...

  • Disaster Recovery as a Service (DRaaS)

    Disaster recovery as a service (DRaaS) is the replication and hosting of physical or virtual servers by a third party to provide ...

  • cloud disaster recovery (cloud DR)

    Cloud disaster recovery (cloud DR) is a combination of strategies and services intended to back up data, applications and other ...

SearchStorage

Close