Skip Navigation LinksCutover-migration-from-Exchange-Server-2007-to-Exchange-Online


Cutover Migration from Exchange Server 2007

 ​EX07A.png

Verify the customer's environment using Remote Connectivity Analyzer with "Outlook Anywhere (RPC over HTTP) https://testconnectivity.microsoft.com

 

 

    • This type of migration is called a cutover Exchange migration because all on-premises mailboxes are migrated in preparation for moving your entire organization to Microsoft Office 365 and Exchange Online. After mailboxes are migrated to Exchange Online, the corresponding user accounts are managed in Office 365.

       
    • Estimated time to complete this task: 2-5 minutes to create a migration batch. After the migration batch is started, the duration of the migration will vary based on the number of mailboxes in the batch, the size of each mailbox, and your available network capacity. For information about other factors that affect how long it takes to migrate mailboxes to Exchange Online, see Migration Performance.
    • You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Migration" entry in the Recipients Permissions topic.
    • If you've activated and installed the Windows Azure Active Directory Sync tool, you can't run a cutover migration. If you've already installed the directory synchronization tool, but haven't run the tool yet, you can deactivate directory synchronization in your Office 365 tenant and then run a cutover migration. For more information, see Manage directory synchronization.
    • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.

       

       

       

      Add your on-premises Exchange organization as an accepted domain of your Office 365 organization. 

       

      The migration service uses the SMTP address of your on-premises mailboxes to create the Microsoft Online Services user ID and email address for the new Exchange Online mailboxes. Migration will fail if your Exchange domain isn't an accepted domain or the primary domain of your Office 365 organization. For more information, see Add your domain to Office 365.

       

      Example 1:

       

      Status: Failed

      administrador@amdocorp.com Skipped item details

      Data migrated: 

      Migration rate: 

      Error: ProvisioningFailedException: You can‎'t use the domain because it‎'s not an accepted domain for your organization. 

      Report: administrador@amdocorp.com Download the report for this user

       

       

       

       
Important:
Your Outlook Anywhere configuration must be configured with a certificate issued by a trusted certification authority (CA). It can't be configured with a self-signed certificate. For more information, see How to Configure SSL for Outlook Anywhere.

 

 

Verify that you can connect to your Exchange organization using Outlook Anywhere.   Try one of these methods to test your connection settings:

Use Microsoft Outlook from outside your corporate network to connect to your on-premises Exchange mailbox.

Use the Microsoft Exchange Remote Connectivity Analyzer to test your connection settings. Use the Outlook Anywhere (RPC over HTTP) or Outlook Autodiscover tests.

image001.png

Assign an on-premises user account the necessary permissions to access mailboxes in your Exchange organization

 

The following list shows the administrative privileges required to migrate mailboxes using a cutover migration. There are three possible options.

    • The migration administrator must be a member of the Domain Admins group in Active Directory in the on-premises organization.
      Or
    • The migration administrator must be assigned the FullAccess permission for each on-premises mailbox.
      Or
    • The migration administrator must be assigned the Receive As permission on the on-premises mailbox database that stores the user mailboxes.

      For more information about assigning Exchange permissions, see Assign permissions to migrate mailboxes to Exchange Online.
       

        
    • Disable Unified Messaging.   If the on-premises mailboxes you're migrating are enabled for Unified Messaging (UM), you have to disable UM on the mailboxes before you migrate them. You can then enable UM on the mailboxes after the migration is complete.
    • Security Groups and Delegates   The email migration service cannot detect whether on-premises Active Directory groups are security groups or not, so it cannot provision any migrated groups as security groups in Office 365. If you want to have security groups in your Office 365 tenant, you must first provision an empty mail-enabled security group in your Office 365 tenant before starting the cutover migration. Additionally, this migration method only moves mailboxes, mail users, mail contacts, and mail-enabled groups. If any other Active Directory object, such as user that is not migrated to Office 365, is assigned as a manager or delegate to an object being migrated, they must be removed from the object prior to migration.

       
      As previously stated, in a cutover migration, on-premises mailboxes are migrated to Exchange Online in a single migration batch. Therefore, you can create only a single migration batch for a cutover migration.

      Use the EAC to create the migration batch

      The following procedure will vary based on whether you or another administrator in your Exchange Online organization have created any migration endpoints. We recommend that you create a migration endpoint before you create a migration batch for a cutover Exchange migration.
    • In the EAC, navigate to Recipients > Migration.
    • Click New 

      then click Migrate to Exchange Online.
    • On the Select a migration type page, click Cutover migration, and then click Next.​


image004.png

Depending on whether any Outlook Anywhere migration endpoints have been created for your Exchange Online organization, do one of the following:

No migration endpoints have been created: On the Enter on-premises account credentials page, type the following information, and then click Next.

o Email address   Type the email address of any user in the on-premises Exchange organization that will be migrated using this endpoint. Exchange Online will test the connectivity to this user's mailbox.

o Account with privileges   Type the user name (using the domain\user name format) for an account that has the necessary administrative privileges in the on-premises organization that hosts the mailboxes that you're migrating. Exchange Online will use the Autodiscover service and this account to detect the migration endpoint and to test the permissions assigned to this account by accessing the mailbox specified in the previous box.

o Password of account with privileges   Type the password for the administrator account that you specified in the previous box.


image006.png

If the connection settings are successfully discovered, the fully qualified domain name (FQDN) of your on-premises Exchange server and RPC proxy server are displayed on the Confirm the migration endpoint page. Verify the settings and then click Next. If the test connection to the source server isn't successful, you're prompted to manually specify the FQDN of your on-premises Exchange server and RPC proxy server. You have to successfully connect to the source server to continue.

Exchange Online creates a new migration endpoint using the connection settings that were successfully discovered or that you provided manually. By default, this migration endpoint is configured to support 20 maximum concurrent migrations and 10 maximum incremental synchronizations.

 

    • One migration endpoint has been created: Exchange Online displays the connection settings from the selected migration endpoint on a read-only page. Verify the connection settings, and then click Next.


image008.png

    • On the Move configuration page, type the name of the migration batch, and then click Next. This name will be displayed in the list of migration batches on the Migration page after you create the migration batch. Batch names can't contain spaces or special characters.

image010.png


    • On the Start the batch page, do the following:
      • Click Browse to send a copy of the migration reports to other users. By default, migration reports are sent to the administrator who creates the migration batch. You can also access the migration reports from the properties page of the migration batch.
      • Specify one of the following options to start the migration batch after it's created:
        • Automatically start the batch   The migration batch is started as soon as you save the new migration batch. The batch is first marked with a status of Created. It's changed to a status of Syncing after it's been started.
        • Manually start the batch later   The migration batch is created but it's not started. The status of the batch is set to Created. To start a migration batch, select it on the migration dashboard and then clickStart 

          Start Icon

          .
    1. Click New to create the migration batch.

image013.png

The new migration batch is displayed on the migration dashboard.image017.png

image019.png


migration endpoints are connection settings for the server that you want to migrate users to or from. They can be associated with any migration batch. Learn moreMigration endpoints are connection settings for the server that you want to migrate users to or from. They can be associated with any migration batch. Learn more

Associated endpoint:

Associated endpoint: legacy07.amdocorp.com

Associated administrator:

RPC proxy server:

Exchange server:

Maximum concurrent migrations:

 

https://outlook.office365.com/ecp/Migration/EditMigrationBatch.aspx?reqId=1403572713224&pwmcid=5&ReturnObjectType=1&id=6afa7767-00a8-464a-ba48-f23cb6d51bc5


image023.png

image025.png

    • Exchange Online provisions new mailboxes in your Office 365 email organization. It creates an Exchange Online mailbox for each user account in your on-premises Exchange organization. On-premises distribution groups and contacts are also migrated to Exchange Online during a cutover migration.


image027.png


The Cutover migration tool creates the users automatically when the migration start "Provisioning Status"


image029.png


It shows the Mailboxes in EAC

image031.png


 

 

 

6/24/2014 1:26:09 AM [CO1PR07MB299] Copying messages is complete. Copying rules and security descriptors.

6/24/2014 1:26:09 AM [CO1PR07MB299] Verifying mailbox contents...

6/24/2014 1:26:14 AM [CO1PR07MB299] Mailbox contents verification complete: 20 folders, 8 items, 7.625 KB (7,808 bytes).

6/24/2014 1:26:14 AM [CO1PR07MB299] Automatically suspending job.

6/24/2014 1:26:14 AM [CO1PR07MB299] Stage: IncrementalSync. Percent complete: 95.


image036.jpg 

    • After the new Exchange Online mailboxes are created, email messages, contacts, and calendar items from each on-premises Exchange mailbox are copied to the corresponding mailbox in Exchange Online. This process is called initial synchronization.


image037.png


 
After the initial synchronization, the on-premises and Exchange Online Exchange mailboxes are synchronized every 24 hours, so that new email sent to on-premises mailboxes is copied to the corresponding Exchange Online mailboxes. This process is called incremental synchronization.
 
 
Exchange Online sends an email message to the administrator when the migration batch has completed initial synchronization. This message lists the number of mailboxes that were successfully migrated and how many couldn’t be migrated. The message also includes links to migration statistics and error reports that contain more detailed information.
 
During the Migration the mailboxes can be accessed from Onpremise

image038.png



image040.png


See the original Migration email message that confirm the migrations status:

 

 

The report with the migration status and details

 

 

How do you know this step worked?

If a migration batch is successfully started, its status on the migration dashboard is specified as Syncing. To verify that you've successfully started a migration batch, do one of the following:

    • In the EAC, navigate to Recipients > Migration. Verify that the migration batch was started.
    • In the Shell, run the following command to verify that the migration batch was started.
      Get-MigrationBatch -Identity <identity> | fl Status

      Return to top

      Step 5: Configure your MX record to point to Office 365

      Until you change your MX record, email sent to users is still routed to their on-premises Exchange mailboxes. After a mailbox is successfully migrated, the incremental synchronization process synchronizes the on-premises Exchange mailbox and Exchange Online mailbox once every 24 hours until you stop or delete the migration batch. This ensures that messages sent to on-premises mailboxes are copied to Exchange Online mailboxes until you configure your organization's MX record to point to your Office 365 email organization. After you configure your organization's MX record, all email is sent directly to the Exchange Online mailboxes. For information about configuring MX records, see Create DNS records for Office 365.

      How do you know this step worked?

      It can take from 24 to 72 hours for the updated MX record to be propagated. Wait at least 24 hours after you change the MX record and then verify that mail is being routed directly to Exchange Online mailboxes.

      Return to top

      Step 6: Delete the cutover migration batch

      After you change the MX record and verify that all email is being routed to Exchange Online mailboxes, you're ready to delete the cutover migration batch. Verify the following before you delete the migration batch:
    • That mail is being sent directly to the Exchange Online mailboxes after you change your MX record to point to your Office 365 email organization.
    • That all users are using their Exchange Online mailboxes. After the batch is deleted, mail sent to mailboxes on the on-premises Exchange server will not be copied to the corresponding Exchange Online mailboxes.
    • That Exchange Online mailboxes have been synchronized at least once after mail began being sent directly to them. To do this, make sure that the value in the Last Synced Time box for the migration batch is more recent than the date and time when mail started being routed directly to Exchange Online mailboxes. This will help ensure that the most recent mail was migrated to Exchange Online mailboxes before mail was sent directly. After you delete the migration batch, on-premises and Exchange Online mailboxes will no longer be synchronized.

      When you delete a cutover migration batch, the migration service cleans up any records related to the migration batch and deletes the migration batch. The batch is removed from the list of migration batches on the migration dashboard.
Important

Important:

Migration batches with a status of Synced that have no administrator-initiated activity (for example, no administrator has stopped and restarted a migration batch or edited a migration batch) for the last 90 days will be stopped, and then deleted 30 days later if no further action is taken by the administrator.

Use the EAC to delete the migration batch

    • In the EAC, navigate to Recipients > Migration.
    • On the migration dashboard, select the batch, and then click Delete 

      Delete icon

      .

      Use the Shell to delete the migration batch

      Run the following Shell command to delete a migration batch.

      Remove-MigrationBatch -Identity <identity>

      How do you know this step worked?
    • In the EAC, navigate to Recipients > Migration. Verify that the migration batch is no longer listed on the migration dashboard.
      Or
    • Run the following command to verify that the migration batch has been deleted.
      Get-MigrationBatch <identity>

      The command will either return the migration batch with a status of Removing or it will return an error stating that the migration batch couldn't be found, verifying that the batch was deleted.

      Return to top

      Step 7: Complete post-migration tasks
    • Assign licenses to Office 365 users.   When you migrate a user's mailbox to Exchange Online using a cutover migration, an Office 365 user account is created for the user. You have to activate this user account by assigning a license. If you don't assign a license, the mailbox will be disabled when the grace period ends. To assign a license in the Office 365 admin center, see Assign or remove a license.
    • Create an Autodiscover DNS record.   After all on-premises mailboxes are migrated to Exchange Online, you can configure an Autodiscover DNS record for your Office 365 organization to enable users to easily connect to their new Exchange Online mailboxes with Microsoft Outlook and mobile clients. This new Autodiscover DNS record has to use the same namespace that you're using for your Office 365 organization. For example, if your cloud-based namespace is cloud.contoso.com, the Autodiscover DNS record you need to create is autodiscover.cloud.contoso.com.
      Exchange Online uses a CNAME record to implement the Autodiscover service for Outlook and mobile clients. The Autodiscover CNAME record must contain the following information:
    • Implement a single sign-on solution.   After all mailboxes are migrated to the cloud, you can implement a single sign-on solution to enable users to use their on-premises Active Directory credentials (user name and password) to access their Office 365 mailboxes and existing on-premises resources. You implement a single sign-on solution by deploying Active Directory Federation Services 2.0 (AD FS 2.0). For more information, see Cutover Exchange Migration and Single Sign-on.
    • Decommission on-premises Exchange servers.   After you've verified that all email is being routed directly to the Exchange Online mailboxes, have completed the migration, and no longer need to maintain your on-premises email organization or don't plan on implementing a single sign-on solution, you can uninstall Exchange from your servers and remove your on-premises Exchange organization.
Important

Important:

If you implement a single sign-on solution, we strongly recommend that you maintain at least one Exchange server so that you can access Exchange System Manager (Exchange 2003) or the Exchange Management Console/Exchange Management Shell (Exchange 2007, Exchange 2010, and Exchange 2013) to manage mail-related attributes on the on-premises mail-enabled users. For Exchange 2007 and Exchange 2010, the Exchange server that you maintain should have the Hub Transport, Client Access, and Mailbox server roles installed.

For more information, see the following:

Caution

Caution:

Decommissioning Exchange can have unintended consequences. Before decommissioning your on-premises Exchange organization, we recommend that you contact Microsoft Support.
    • Re-enable offline access for Outlook Web App.   Offline access in Outlook Web App lets users access their mailbox when they're not connected to a network. If you migrate Exchange 2013 mailboxes to Exchange Online, users have to reset the offline access setting in their browser to use Outlook Web App offline. For more information about offline access in Outlook Web App, the browsers that support it, and how to turn it on, see Using Outlook Web App Offline.

      Return to top

      Best practices

      Here are some tips to optimize your cutover Exchange migration:
    • Change the DNS Time-to-Live (TTL) setting on your MX record.   Before you start to migrate mailboxes, change the DNS TTL setting on your current MX record to a shorter interval, such as 3600 seconds (one hour). Then, when you change your MX record to point to your Office 365 organization after all mailboxes are migrated, the updated MX record should propagate more quickly because of the shortened TTL interval.
    • Updating the WindowsEmailAddress attribute   The WindowsEmailAddress attribute is used as the primary key for the cutover migration and changing theWindowsEmailAddress attribute on the on-premises side during a cutover migration isn't recommended. If the WindowsEmailAddress attribute needs to be changed, we recommend that you remove the target MigrationUser attribute, remove the target mailbox, group and contact, and then restart the migration batch.
    • Communicate with your users.   Let users know ahead of time that you're migrating the content of their on-premises mailboxes to Exchange Online. Consider doing the following:
      • Asking users to delete old or unnecessary email messages from their Exchange mailboxes before migration. This helps reduce the amount of data that has to be migrated and can help reduce the overall migration time. Or, you can clean up their mailboxes yourself.
      • Suggesting that users back up their Inboxes.
      • Telling users when they can use their Office 365 user account to access the email that was migrated from their on-premises accounts. Don't give users access to their Exchange Online mailboxes until you're ready to switch your MX record to point to Office 365.

         

         

        Migrate All Mailboxes to Exchange Online with a Cutover Migration

        http://technet.microsoft.com/en-US/library/jj874016(v=exchg.150).aspx

         

         

         

        Troubleshooting IMAP Migration Batch:

         

         

         

        Get-MigrationBatch -Diagnostic |FL >MigrationBatchDiagnostic.txt

         

         

        Test-MigrationServerAvailability -IMAP -RemoteServer  imap.n.mail.yahoo.com -Port 993 -Security None

        Test-MigrationServerAvailability -IMAP -RemoteServer  mail.msftsupport.com -Port 993 -Security None

         

         Get-MigrationStatistics |FL >Get-MigrationStatistics.txt

Step 6: Delete the cutover migration batch

 

After you change the MX record and verify that all email is being routed to Exchange Online mailboxes, you're ready to delete the cutover migration batch. Verify the following before you delete the migration batch:

  • That mail is being sent directly to the Exchange Online mailboxes after you change your MX record to point to your Office 365 email organization.

  • That all users are using their Exchange Online mailboxes. After the batch is deleted, mail sent to mailboxes on the on-premises Exchange server will not be copied to the corresponding Exchange Online mailboxes.

  • That Exchange Online mailboxes have been synchronized at least once after mail began being sent directly to them. To do this, make sure that the value in the Last Synced Time box for the migration batch is more recent than the date and time when mail started being routed directly to Exchange Online mailboxes. This will help ensure that the most recent mail was migrated to Exchange Online mailboxes before mail was sent directly. After you delete the migration batch, on-premises and Exchange Online mailboxes will no longer be synchronized.

When you delete a cutover migration batch, the migration service cleans up any records related to the migration batch and deletes the migration batch. The batch is removed from the list of migration batches on the migration dashboard.

ImportantImportant:
Migration batches with a status of Synced that have no administrator-initiated activity (for example, no administrator has stopped and restarted a migration batch or edited a migration batch) for the last 90 days will be stopped, and then deleted 30 days later if no further action is taken by the administrator.

Use the EAC to delete the migration batch

 

  1. In the EAC, navigate to Recipients > Migration.

  2. On the migration dashboard, select the batch, and then click Delete Delete icon.

Use the Shell to delete the migration batch

 

Run the following Shell command to delete a migration batch.

Remove-MigrationBatch -Identity <identity>

How do you know this step worked?

 

  • In the EAC, navigate to Recipients > Migration. Verify that the migration batch is no longer listed on the migration dashboard.

    Or

  • Run the following command to verify that the migration batch has been deleted.

    Get-MigrationBatch <identity>
    

    The command will either return the migration batch with a status of Removing or it will return an error stating that the migration batch couldn’t be found, verifying that the batch was deleted.​



Step 7: Complete post-migration tasks

 

  • Assign licenses to Office 365 users.   When you migrate a user's mailbox to Exchange Online using a cutover migration, an Office 365 user account is created for the user. You have to activate this user account by assigning a license. If you don't assign a license, the mailbox will be disabled when the grace period ends. To assign a license in the Office 365 admin center, see Assign or remove a license.

  • Create an Autodiscover DNS record.   After all on-premises mailboxes are migrated to Exchange Online, you can configure an Autodiscover DNS record for your Office 365 organization to enable users to easily connect to their new Exchange Online mailboxes with Microsoft Outlook and mobile clients. This new Autodiscover DNS record has to use the same namespace that you’re using for your Office 365 organization. For example, if your cloud-based namespace is cloud.contoso.com, the Autodiscover DNS record you need to create is autodiscover.cloud.contoso.com.

    Exchange Online uses a CNAME record to implement the Autodiscover service for Outlook and mobile clients. The Autodiscover CNAME record must contain the following information:

    • Alias   autodiscover

    • Target   autodiscover.outlook.com

    For more information, see Create DNS records for Office 365.

  • Implement a single sign-on solution.   After all mailboxes are migrated to the cloud, you can implement a single sign-on solution to enable users to use their on-premises Active Directory credentials (user name and password) to access their Office 365 mailboxes and existing on-premises resources. You implement a single sign-on solution by deploying Active Directory Federation Services 2.0 (AD FS 2.0). For more information, see Cutover Exchange Migration and Single Sign-on.

  • Decommission on-premises Exchange servers.   After you’ve verified that all email is being routed directly to the Exchange Online mailboxes, have completed the migration, and no longer need to maintain your on-premises email organization or don’t plan on implementing a single sign-on solution, you can uninstall Exchange from your servers and remove your on-premises Exchange organization.

    ImportantImportant:
    If you implement a single sign-on solution, we strongly recommend that you maintain at least one Exchange server so that you can access Exchange System Manager (Exchange 2003) or the Exchange Management Console/Exchange Management Shell (Exchange 2007, Exchange 2010, and Exchange 2013) to manage mail-related attributes on the on-premises mail-enabled users. For Exchange 2007 and Exchange 2010, the Exchange server that you maintain should have the Hub Transport, Client Access, and Mailbox server roles installed.

    For more information, see the following:

    CautionCaution:
    Decommissioning Exchange can have unintended consequences. Before decommissioning your on-premises Exchange organization, we recommend that you contact Microsoft Support.
  • Re-enable offline access for Outlook Web App.   Offline access in Outlook Web App lets users access their mailbox when they're not connected to a network. If you migrate Exchange 2013 mailboxes to Exchange Online, users have to reset the offline access setting in their browser to use Outlook Web App offline. For more information about offline access in Outlook Web App, the browsers that support it, and how to turn it on, see Using Outlook Web App Offline.



Migrate all mailboxes to Exchange Online with a cutover migration​

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




Best practices

 

Here are some tips to optimize your cutover Exchange migration:

  • Change the DNS Time-to-Live (TTL) setting on your MX record.   Before you start to migrate mailboxes, change the DNS TTL setting on your current MX record to a shorter interval, such as 3600 seconds (one hour). Then, when you change your MX record to point to your Office 365 organization after all mailboxes are migrated, the updated MX record should propagate more quickly because of the shortened TTL interval.

  • Updating the WindowsEmailAddress attribute   The WindowsEmailAddress attribute is used as the primary key for the cutover migration and changing the WindowsEmailAddress attribute on the on-premises side during a cutover migration isn’t recommended. If the WindowsEmailAddress attribute needs to be changed, we recommend that you remove the target MigrationUser attribute, remove the target mailbox, group and contact, and then restart the migration batch.

  • Communicate with your users.   Let users know ahead of time that you’re migrating the content of their on-premises mailboxes to Exchange Online. Consider doing the following:

    • Asking users to delete old or unnecessary email messages from their Exchange mailboxes before migration. This helps reduce the amount of data that has to be migrated and can help reduce the overall migration time. Or, you can clean up their mailboxes yourself.

    • Suggesting that users back up their Inboxes.

    • Telling users when they can use their Office 365 user account to access the email that was migrated from their on-premises accounts. Don't give users access to their Exchange Online mailboxes until you're ready to switch your MX record to point to Office 365.