Export (0) Print
Expand All
9 out of 18 rated this helpful - Rate this topic

Create Migration Endpoints

Exchange Online
 

Applies to: Exchange Online

Topic Last Modified: 2013-05-01

A migration endpoint is a management object in Exchange Online that contains the connection settings and administrator credentials for the source server that hosts the mailboxes that you want to migrate to Exchange Online. The migration endpoint also defines the number of mailboxes to migrate simultaneously during initial synchronization and the number of mailboxes to synchronize simultaneously during incremental synchronization, which occurs once every 24 hours for selected migration types. During incremental synchronization, on-premises and Exchange Online mailboxes are synchronized so that new email sent to mailboxes on the source server is copied to the corresponding Exchange Online mailbox.

  • Estimated time to complete each procedure: 3 minutes.
  • You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the"Mailbox Move and Migration Permissions" section in the Recipients Permissions topic.
  • When you create a migration endpoint, by default, it will support 20 maximum concurrent migrations during initial synchronization and a maximum of 10 concurrent incremental synchronizations. You can specify a different number of concurrent migrations when you create a migration endpoint. To change these settings, you can edit an existing migration endpoint using the EAC or the Set-MigrationEndpoint cmdlet.
  • There is a limit of 100 concurrent migrations for each type of migration endpoint. For example, your organization could have five Outlook Anywhere migration endpoints and each endpoint could be configured for 20 maximum concurrent migrations. Or you could have two IMAP migration endpoints, with each endpoint configured to support 50 maximum concurrent migrations.
  • We recommend that you test the connection settings to the server that hosts the mailboxes that you want to migrate. The connection settings will be tested when you create a migration endpoint, but verifying the settings before you create an endpoint will give you an opportunity to troubleshoot any issues.
    Run one of the following Shell commands to test the connection settings to the source server.
    • IMAP migrations
      Test-MigrationServerAvailability -IMAP -RemoteServer <FQDN of IMAP server> -Port <143 or 993> -Security <None, Ssl, or Tls>
      
      For the value of the Port parameter, it’s typical to use 143 for unencrypted or Transport Layer Security (TLS) connections and to use 993 for SSL connections.
    • Cutover and staged Exchange migrations
      $Credentials = Get-Credential
      
      Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress <email address for on-premises administrator account> -Credentials $Credentials
      
      To successfully test the connection settings for cutover and staged Exchange migrations, Outlook Anywhere must be enabled on the source server. For more information, see Create a migration endpoint for cutover and staged Exchange migrations later in this topic.
      tipTip:
      If you have problems connecting to your on-premises Exchange server, use the Outlook Anywhere or Outlook Autodiscover connectivity tests in the Microsoft Remote Connectivity Analyzer to troubleshoot connectivity errors. If a connectivity test fails, use the test details to troubleshoot the cause of the failure.
    • Migrations in an Exchange hybrid deployment
      $Credentials = Get-Credential
      
      Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress <email address for on-premises administrator account> -Credentials $Credentials
      
  • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard Shortcuts in the Exchange Admin Center.
tipTip:
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.

An IMAP migration endpoint is used to migrate email items from mailboxes on an IMAP server to mailboxes in Exchange Online. Before you can run an IMAP migration, the Exchange Online mailboxes must be provisioned. For information about IMAP migrations, see Migrate Email from an IMAP Server to Exchange Online Mailboxes.

  1. In the EAC, navigate to Recipients > Migration.
  2. Click More More Options Icon, and then click Migration endpoints.
  3. On the Migration endpoints page, click New Add Icon.
  4. On the Select the migration endpoint type page, click IMAP, and then click Next.
  5. On the IMAP migration configuration page, complete the following boxes:
    • * IMAP server   Type the FQDN (also called the full computer name) of the IMAP server for the IMAP messaging system. This is required.
    • Authentication   Select the authentication method used by the IMAP server. Options are Basic (the default), or NTLM. Use NTLM if it's required by your IMAP server.
    • Encryption   Select the encryption method used by the IMAP server. Options are None, SSL (the default), or TLS.
    • * Port   Type the TCP port number used to connect to the IMAP server. Use port 143 for unencrypted connections, port 143 for TLS connections, or port 993 (the default), for SSL connections. This is required.
    • Click Next. The migration service will use the settings to test the connection to the IMAP server. You have to successfully connect to the source IMAP server to continue. If the test connection to the IMAP server is successful, the Enter general information page is displayed.
  6. Enter information in the following boxes:
    • Migration endpoint name   This name is displayed in the list of migration endpoints. It's also used in the drop-down list of migration endpoints when you select a migration endpoint when creating an IMAP migration batch. This is required.
    • Maximum concurrent migrations   This is total number of connections to the source server that are available to migrate items in mailboxes on the IMAP server to Exchange Online mailboxes during initial and incremental synchronization. If the value is set to 20, which is the default value, you can migrate up to 20 mailboxes at the same time.
      If multiple IMAP migration batches use the same IMAP migration endpoint, the maximum number of concurrent migrations allowed by the migration endpoint is shared across all the migration batches.
      noteNote:
      As previously stated, there is a limit of 100 concurrent migrations for all IMAP migration endpoints in your organization.
    • Maximum concurrent incremental syncs   This is the number of connections to the IMAP server available to perform incremental synchronizations. If the value is set to 10, the default value, then incremental synchronization can be performed for up to 10 mailboxes at the same time. For example, if the endpoint is configured with 50 maximum concurrent migrations and 20 maximum concurrent incremental syncs, 20 connections can be used for incremental synchronization, if necessary. The other 30 connections are reserved for initial synchronizations.
      During incremental synchronization, the mailboxes in the IMAP messaging system and the corresponding Exchange Online mailboxes are synchronized every 24 hours. This means that any new messages sent to the mailboxes on the IMAP server are copied to the corresponding Exchange Online mailbox.
  7. Click New to create the migration endpoint.

This example uses the New-MigrationEndpoint cmdlet to create an IMAP migration endpoint.

New-MigrationEndpoint -IMAP -Name IMAPEndpoint -RemoteServer imap.contoso.com -Port 993 -Security Ssl

This example creates an IMAP migration endpoint that supports 50 concurrent migrations and up to 25 concurrent incremental synchronizations. It also configures the endpoint to use port 143 for TLS encryption.

New-MigrationEndpoint -IMAP -Name IMAP_TLS_Endpoint -RemoteServer imap.contoso.com -Port 143 -Security Tls -MaxConcurrentMigrations
50 -MaxConcurrentIncrementalSyncs 25

To verify that you've successfully created an IMAP migration endpoint, do one of the following:

  1. In the EAC, navigate to Recipients > Migration.
  2. Click More More Options Icon, and then click Migration endpoints. The new migration endpoint is displayed in the list, and the endpoint type is IMAP.

Or

Run the following command to display information about the migration endpoint.

Get-MigrationEndpoint <identity> | FL EndpointType,RemoteServer,Port,Security,Max*

You can use a cutover Exchange migration or a staged Exchange migration to migrate on-premises Exchange mailboxes to Exchange Online. The primary difference between these migration types is that all mailboxes are migrated in a single batch during a cutover migration, and you can migrate a maximum of 1,000 mailboxes. For a staged migration, you can migrate mailboxes in batches and migrate more than 1,000 mailboxes. However, you can't migrate Exchange 2010 or Exchange 2013 mailboxes using a staged migration. In both cases, the Exchange Online mailboxes are provisioned during the migration process.

For more information about cutover and staged Exchange migrations, see:

For cutover and staged Exchange migrations, Exchange Online uses RPC over HTTP, or Outlook Anywhere, to connect to your on-premises Exchange server. Therefore, Outlook Anywhere must be enabled in your on-premises Exchange organization. For information about how to set up Outlook Anywhere for Exchange 2010, Exchange 2007, and Exchange 2003, see the following topics:

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

  1. In the EAC, navigate to Recipients > Migration.
  2. Click More More Options Icon, and then click Migration endpoints.
  3. On the Migration endpoints page, click New Add Icon.
  4. On the Select the migration endpoint type page, click Outlook Anywhere, and then click Next.
  5. On the Enter on-premises account credentials page, complete the following boxes:
    • 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.
    • Account with privileges   Type the user name (using the domain\user name format or an email address) 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.
    • Password of account with privileges   Type the password for the administrator account that you specified in the previous box.
  6. Click Next. Exchange Online uses the information on the Enter on-premises account credentials page to test connectivity to the source server, and then displays the Confirm the migration endpoint page. Do one of the following based on whether the connection settings were successfully detected:
    • If Exchange Online successfully connects to the source server, the connection settings are displayed. Click Next.
    • If the test connection to the source server isn't successful, you have to provide values for the following boxes:
      • Exchange server   Type the fully qualified domain name (FQDN) for the on-premises Exchange server. This would be the host name for your Mailbox server; for example, EXCH-SRV-01.corp.contoso.com.
      • RPC proxy server   Type the FQDN for the RPC proxy server for Outlook Anywhere. Typically, this will be the same as your Outlook Web App URL; for example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server.
      You have to successfully connect to the source server to continue.
      importantImportant:
      Exchange Online creates a new migration endpoint using the connection settings that were successfully discovered or that you provided manually. We recommend that you create migration endpoints whose connection settings were automatically discovered rather than creating endpoints whose settings you entered manually. This is because the Autodiscover service will be used to connect to each user mailbox during the migration. If manual settings are used, Exchange Online won't use the Autodiscover service, but will connect to a specific source server using the connection settings you manually entered. If you use manual settings and have multiple on-premises Exchange servers, you may need to create different migration endpoints that correspond to each server.
  7. Click Next. Enter information in the following boxes:
    • Migration endpoint name   This name is displayed in the list of migration endpoints. It's also used in the drop-down list of migration endpoints when you select a migration endpoint while you’re creating a migration batch. This is required.
    • Maximum concurrent migrations   This is the number of connections to the source server that are available to migrate on-premises mailboxes and mailbox items to Exchange Online during initial and incremental synchronization. If the value is set to 20, which is the default value, you can migrate up to 20 mailboxes at the same time.
      If multiple migration batches use the same Outlook Anywhere migration endpoint, the maximum number of concurrent migrations allowed by the migration endpoint is shared across all the migration batches.
      noteNote:
      As previously stated, there is a limit of100 concurrent migrations for all Outlook Anywhere migration endpoints in your organization.
    • Maximum concurrent incremental syncs   This is the number of connections to the source server that are available to perform incremental synchronizations. If the value is set to 10, the default value, then incremental synchronization can be performed on up to 10 mailboxes at the same time. For example, if the endpoint is configured with 50 maximum concurrent migrations and 20 maximum concurrent incremental syncs, 20 connections can be used for incremental synchronization, if necessary. The other 30 connections are reserved for initial synchronizations.
      During incremental synchronization for cutover Exchange migrations, the mailboxes in the on-premises Exchange organization and the corresponding Exchange Online mailboxes are synchronized every 24 hours. This means that any new messages sent to the on-premises mailboxes are copied to the corresponding Exchange Online mailbox.
  8. Click New to create the migration endpoint.

This example creates a migration endpoint for a staged Exchange migration.

$Credentials = Get-Credential
New-MigrationEndpoint -ExchangeOutlookAnywhere -Name StagedEndpoint -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials

This example creates a migration endpoint for a cutover Exchange migration. The example uses the Test-MigrationServerAvailability cmdlet to obtain and test the connection settings to the on-premises Exchange server, and then uses those connection settings to create the migration endpoint.

$credentials = Get-Credential
$TSMA = Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress administrator@contoso.com -Credentials $credentials
New-MigrationEndpoint -ExchangeOutlookAnywhere -Name CutoverEndpoint -ConnectionSettings $TSMA.ConnectionSettings

To verify that you've successfully created an Outlook Anywhere migration endpoint, do one of the following:

  1. In the EAC, navigate to Recipients > Migration.
  2. Click More More Options Icon, and then click Migration endpoints. The new migration endpoint is displayed in the list, and the endpoint type is Exchange Outlook Anywhere.

Or

In the Shell, run the following command to display information about the migration endpoint.

Get-MigrationEndpoint <identity> | FL EndpointType,ExchangeServer,UseAutoDiscover,Max*

For onboarding and offboarding remote move migrations in an Exchange hybrid deployment, you have to create Exchange Remote migration endpoints. The migration endpoint contains the connection settings for a Client Access server in your on-premises Exchange organization. To allow this Client Access server to accept incoming remote move requests, you have to enable the MRS Proxy endpoint. For more information, see Enable the MRS Proxy Endpoint for Remote Moves.

noteNote:
The same Exchange Remote migration endpoint can be used for moving on-premises mailboxes to Exchange Online or for moving Exchange Online mailboxes to your on-premises organization.
importantImportant:
You must have a hybrid deployment configured between your on-premises and Exchange Online organizations to create an Exchange Remote migration endpoint and use remote move migrations to move mailboxes between your on-premises and Exchange Online organizations. For more information, see:
  1. In the EAC, navigate to Recipients > Migration.
  2. Click More More Options Icon, and then click Migration endpoints.
  3. On the Migration endpoints page, click New Add Icon.
  4. On the Select the migration endpoint type page, click Exchange Remote, and then click Next.
  5. On the Enter on-premises account credentials page, complete the following boxes:
    • 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.
    • Account with privileges   Type the user name (using the domain\user name format or email address) for an account that has the necessary administrative privileges in the on-premises organization. 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.
    • Password of account with privileges   Type the password for the administrator account that you specified in the previous box.
  6. Click Next. Exchange Online uses this to test connectivity to an on-premises server, and then displays the Confirm the migration endpoint page. Do one of the following based on whether the connection settings were successfully detected:
    • If Exchange Online successfully connects to an on-premises server, the connection settings are displayed. Click Next.
    • If the test connection to an on-premises server isn't successful, you have to enter the fully qualified domain name (FQDN) of the on-premises server that the MRS Proxy service is running on in your hybrid deployment. For example, mail.contoso.com. The MRS Proxy service typically runs on the Exchange Client Access server in your on-premises organization.
      You have to successfully connect to an on-premises server to continue.
      importantImportant:
      Exchange Online creates a new migration endpoint using the connection settings that were successfully discovered or that you provided manually. We recommend that you create migration endpoints whose connection settings were automatically discovered rather than creating endpoints whose settings you entered manually. This is because the Autodiscover service will be used to connect to each user mailbox during the migration. If manual settings are used, Exchange Online won't use the Autodiscover service, but will connect to a specific source server using the connection settings you manually entered. If you use manual settings and have multiple on-premises Exchange servers, you may need to create different migration endpoints that correspond to each server.
  7. Click Next. Enter information in the following boxes:
    • Migration endpoint name   This name is displayed in the list of migration endpoints. It's also used in the drop-down list of migration endpoints when you select a migration endpoint while creating a migration batch. This is required.
    • Maximum concurrent migrations   This is the number of connections to the source server that are available to migrate on-premises mailboxes and mailbox items to Exchange Online during initial and incremental synchronization. If the value is set to 20, which is the default value, you can migrate up to 20 mailboxes at the same time.
      If multiple migration batches use the same Exchange Remote migration endpoint, the maximum number of concurrent migrations allowed by the migration endpoint is shared across all the migration batches.
      noteNote:
      As previously stated, there is a limit of 100 concurrent migrations for all Exchange Remote migration endpoints in your organization.
    • Maximum concurrent incremental syncs   This is the number of connections to the source server that are available to perform incremental synchronizations. If the value is set to 10, the default value, then incremental synchronization can be performed on up to 10 mailboxes at the same time.
      For example, if the endpoint is configured with 100 maximum concurrent migrations and 40 maximum concurrent incremental syncs, 40 connections can be used for incremental synchronization, if necessary. The other 60 connections are reserved for initial synchronizations.
  8. Click New to create the migration endpoint.

This example creates a migration endpoint that can be used for either onboarding or offboarding remote move migrations. In both cases, the migration endpoint is an Exchange server in your on-premises Exchange organization that’s running the MRS proxy service. This is typically the Client Access server.

$Credentials = Get-Credential
New-MigrationEndpoint -ExchangeRemoteMove -Name OnpremEndpoint -Autodiscover -EmailAddress administrator@onprem.contoso.com -Credentials $Credentials

To verify that you've successfully created an Exchange Remote migration endpoint, do one of the following:

  1. In the EAC, navigate to Recipients > Migration.
  2. Click More More Options Icon, and then click Migration endpoints. The new migration endpoint is displayed in the list, and the endpoint type is Exchange Remote.

Or

In the Shell, run the following command to display information about the migration endpoint.

Get-MigrationEndpoint <identity> | FL EndpointType,RemoteServer,UseAutoDiscover,Max*
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.