Migrating from Microsoft Exchange 2007 and BPOS

This quick start guide provides you with the basic information to configure CloudM Migrate for a migration from Exchange 2007 and Microsoft Business Productivity Online Services. It is highly recommended that you read the application documentation in full for your platforms in order to understand all of the options available to you during a migration.


Software Requirements

The following software should be installed on the migration workstation:

  • CloudM Migrate
  • Microsoft Powershell


What else do I need?


Configuring Exchange 2007

  • Open The Exchange management shell found on your Exchange 2007 server.
  • Follow the steps below

To perform migrations with Exchange 2007 it is recommended a new user is setup to perform the migrations. Create a new user in the Exchange 2007 Management Console, or from the Exchange Management Shell. An example cmdlet to use from the console could be (replacing 'migrator@domain', 'migrator' and 'SERVER\First Storage Group\Mailbox Database' text with entries appropriate for your environment):

PS> New-Mailbox -Name 'Migrator User' -Alias 'migrator' -OrganizationalUnit 'domain/Users' -UserPrincipalName 'migrator@domain' -SamAccountName 'migrator' -Password (ConvertTo-SecureString 'password' -AsPlainText -Force) -ResetPasswordOnNextLogon $false -Database 'SERVER\First Storage Group\Mailbox Database'

This user should not be a member of the Administrator group. When the new user has been setup it should be given impersonation rights to impersonate all users on the server. To perform this issue the following command from the Exchange Management Console.


PS> Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity migrator | select-object).identity -extendedRights ms-Exch-EPI-Impersonation,ms-Exch-EPI-May-Impersonate}

When this command has been run the specified user can impersonate users on the server. If a user has been setup in this way then ‘Impersonation’ should be used in the configuration options.

It often useful to enable Basic authentication for the Exchange Web Services endpoint, as to use Ntlm you must be logged into the workstation running the migration tool as the migration admin user. Run the following to enable Basic authentication, replacing the name of the site if required.

PS> Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -BasicAuthentication $true


Generating the user list

When migrating from Exchange 2007 special consideration needs to be given to generating the user list. The user list should be generated by running the following PowerShell command in the Exchange Management Shell on the Exchange Server, changing the name of the CSV file if appropriate.

Get-Mailbox | select @{Name="Migrate";Expression="$true"},@{Name="ExportName";Expression={(Get-Mailbox $_).PrimarySmtpAddress.ToString().Split("@")[0]}},@{Name="ImportName";Expression={(Get-Mailbox $_).PrimarySmtpAddress.ToString().Split("@")[0]}},@{Name="GivenName";Expression={(Get-User $_).FirstName}},@{Name="FamilyName";Expression={(Get-User $_).LastName}} | Export-CSV c:\import.csv -notype


You should then import the generated CSV file using ‘File->Import User List’.


Configuring CloudM Migrate

  1. Select Microsoft Exchange 2007 SP1 / BPOS in the platform selector
  2. Enter the server settings into CloudM Migrate, making sure to follow the instructions for each setting as documented here for source and destination. Choose the Credential Method, depending on what you have setup.
  3. Make sure that the ‘Import Name’ for all of your users is correct. The combination of ‘Import Name’@’Domain Name’ should match the primary SMTP address of the users in your destination system. If you are using the built-in PowerShell scripts to create users then they will be created, or verified before a migration for each user begins.
  4. You may also need to run the following command in PowerShell before running any other commands: Set-ExecutionPolicy RemoteSigned as Administrator, or Set-ExecutionPolicy Unrestricted CurrentUser as the user you will be logged in as when running the CloudM Migrate.
  5. Check the PowerShell scripts for your migration are setup correctly. You may or may not need to run PowerShell scripts depending on your migration.
  6. Enter your license key.  Please click Help > Licence Key to apply the licence.  Paste in licence key and click Apply.
  7. Setup your destination platform.  Instructions are available for G Suite, Google Vault, Microsoft Exchange or Office 365 and Exchange Online Archives.
  8. Test the configuration using the configuration test tool, available at ‘Tools->Check Connections’. See this article for more information about the connection test tool. You will also need to complete the settings for the destination platform before running this test. If any problems are encountered with the connection test, please examine the error and make the adjustments to your configuration settings.
  9. Generate your user list and select the users and items you would like to migrate in the ‘Users/Resources’ tab.
  10. Start your migration

If you have any specialized needs, or would like to learn more about the migration options and how they can be used to make sure your migration is performed in an appropriate way for your organisation, please refer to the advanced settings.

Was this article helpful?
0 out of 0 found this helpful