​Introduction

This video provides information on the key differences to be aware of when performing a tenant to tenant migration, while keeping the same domain name. It also provides step-by-step instructions on how to perform your migration, and includes instructions on how to set up PowerShell (the scripts to use to change user email addresses to their .onmicrosoft.com addresses), and more.

 

 

Note: There may be differences between the user interface shown in this video and the user interface in MSPComplete. We are continually improving the user experience to make our platform more intuitive and easier to use.

Related Articles

Migration Checklist

  • Export user list to CSV file (from Source Office 365 admin portal)
    • Change both Source and Destination domain names to their corresponding ".onmicrosoft.com" addresses
  • Create users on Destination tenant, and assign SKUs.
    • Choices include:
      • Manually, one at a time
      • Bulk import via CSV file
      • By PowerShell scripts
      • MS DirSync - Note: read KB004336 before choosing this method! Do not run if you have extended local AD schema to support Exchange. Instead, use an alternative method, listed above, to create accounts. After accounts have been fully set up, then you can run DirSync or AADSync, in order to synchronize your local AD and Office 365.
  • Set up the MigrationWiz project
    • Add users with onmicrosoft.com addresses at Source and Destination
    • Set Advanced Options:
      • Use impersonation to authenticate at both Source and Destination
      • Add recipient mapping, e.g., RecipientMapping="TIMHUFF.onmicrosoft.com->@bpostech.us"
  • Run Migration:
    • Perform verification check
    • First pass: Pre-Stage pass. Mail items > 90 days (this is performed 1-3 weeks prior to domain switchover to new tenant)
    • Launch DeploymentPro. After users are imported into the dashboard, before proceeding you should change the Destination domain name in DeploymentPro to be the vanity domain name rather than the onmicrosoft.com domain name. This way, when the profiles are created, they will reflect the vanity domain name, and thus will avoid any user confusion when they see their email address within Outlook. KB005160 provides the exact steps to do this.
    • Install the DeploymentPro agent on users' machines (watch video on DeploymentPro, in supporting videos section above, to find out more information on this and the other DeploymentPro steps)
    • Note: These steps are only required if you are using DeploymentPro for the automation of Outlook profile re-configuration, rather than having users create new profiles (and re-attach PST files, and re-create new signatures)
    • Remove domain from Source:
      • Enable remote PowerShell access for Office 365. KB005174 provides more information on the steps to follow.
        • Example PowerShell script to change the domain name to the onmicrosoft.com addresses:
          • $testpath = test-path c:\temp; If ($testpath -eq $false) {new-item -type directory c:\temp}; $dataout = @();
            Get-MsolUser | ? {$_.UserPrincipalName -match "bpostech.us" -and $_.UserPrincipalName -notmatch "admin"} | % {Set-MsolUserPrincipalName -ObjectId $_.objectId -NewUserPrincipalName ($_.UserPrincipalName.Split("@")[0] + "@TIMHUFF.onmicrosoft.com"); $dataout += "$($_.UserPrincipalName)" ; $_.UserPrincipalName };$dataout | out-file c:\temp\UPNchangeOutput.txt
      • Change admin account domain name (from admin portal, or via PowerShell)
      • Remove domain (from admin portal, or via PowerShell). KB005173 provides more information on the steps to follow.
    • Wait 30 minutes for Microsoft domain replication services to complete.
    • Add domain to Destination tenant.
    • Within your DeploymentPro portal, click on "Configure Outlook" button (this step is only required if using DeploymentPro).
    • Second pass: Full Migration pass. No date filter. Leave all items selected (this is performed ASAP after domain switchover).
    • Get project migration statistics by clicking on pie chart icon at top level of the MigrationWiz dashboard.​