When performing mailbox migrations, it is utmost important that you stay on top of the progress. However, given the current user interface (UI), it is next to impossible to identify the most current status of mailbox migration. As a result, you find it difficult to report exact status to the concerned teams.

Using this PowerShell script, we can export migration status summary of not only the mailbox for which the migration is complete but also for the mailbox that is still being migrated. Best part of this is that the script runs in the background and saves a separate migration report for each mailbox. This can also be used for auditing purpose post migration, if needed.

Note: Below listed process will only work if the migration batches (containing the email IDs of the users that have been added to the CSV File) exist in the Exchange Admin Center (EAC). It will not work if you have deleted the batches.

• You will have to reach out to your Tenant’s Global Admin and request him to grant you access
• Login to Microsoft 365 Admin Portal
• Expand the Users section and click on Active Users
• Search for the user who needs to be granted EXO Service Admin role and click on the user’s Display name
• You will be presented with the user details panel
• On the Accounts tab, you will see a section called Roles
• Clicking on Manage Roles option will present the Manage admin roles panel
• Click the Admin center access radio button and then select Exchange Administrator option
• Click Save changes button

The user will have to log out and log back in again so that the role change becomes effective.

Exchange Online PowerShell Module v1 (EXO V1) does not support Multi-Factor Authentication (MFA). So, if the account that you are using for performing the action has MFA enabled, consider using Exchange Online PowerShell Module v2 (EXO V2).

• EXO V1 does not require any installation. All you need to do is connect and import the module using PowerShell commands (commands discussed later).
• Since EXO V2 requires an installation, it is always a good practice to check if the required module is installed or not using the below command:
  • Get-Module -ListAvailable -Name *Exch*
• If EXO V2 module is installed, check what version is currently installed, you can run the below command:
  • Import-Module ExchangeOnlineManagement; Get-Module ExchangeOnlineManagement

At the time of writing this content, latest version of EXO V2 module was 2.0.4. You can refer to the Release Notes section of this article to get the version of Current Release:

About the Exchange Online PowerShell V2 module | Microsoft Docs

As stated above, only Exchange Online PowerShell version v.2 (EXO V2) requires installation, to install the EXO V2 module for the first time, complete the following steps

• Install or update the PowerShellGet module as described in Installing PowerShellGet.
• Close and re-open the Windows PowerShell window
• Now you can use the Install-Module cmdlet to install the EXO V2 module from the PowerShell Gallery:
• In an elevated PowerShell window (all users):
  • Install-Module -Name ExchangeOnlineManagement
• When you are finished, enter Y to accept the license agreement.

If the module is already installed on your computer, you can run the command we shared above to see the version that is currently installed and update it to the latest version using the below command:

• Update-Module -Name ExchangeOnlineManagement

To uninstall the module, run one of the below command (in an elevated PowerShell window)

• Uninstall-Module -Name ExchangeOnlineManagement

• Ensure the CSV file is in the same folder where you run this PowerShell script from
• Below is the sample for CSV file:

Now that you have clarity on whether you are using EXOV1 or EXO V2 PowerShell Module, it should be easy for you to decide which path to follow.

Before you run the script, please ensure you have met all the pre-requisites so that you get the desired outcome. After you confirm having met all the pre-requisites, copy and save the below script in your favourite script editor and save it as a GetMigrationReport.ps1 file ensuring that the script and the CSV File are saved in the same location.

Don’t forget to create a blank folder named Reports at the same location. This is where all the reports will be saved.

#Make sure the csv file is in the same folder where you run this PowerShell from

#Connect to Exchange Online PowerShell

#Change this to path of the csv file that contains EmailAddress of all User Mailboxes you want to get a report for

#Loop through each row in csv

• Launch Windows PowerShell (in elevated mode)
• Change the path to the location where you saved the .ps1 file
• Run the below command:
  • .GetMigrationReport.ps1
• Navigate to the reports folder and you will notice that text files start appearing in this folder.
• The report for each mailbox will be saved as the user’s UPN and in .txt format

Before you run the script, please ensure you have met all the pre-requisites so that you get the desired outcome. After you confirm having met all the pre-requisites, copy and save the below script in your favourite script editor and save it as a GetMigrationReport.ps1 file ensuring that the script and the CSV File are saved in the same location.

Don’t forget to create a blank folder named Reports at the same location. This is where all the reports will be saved.

#Import Exchange Online PowerShell Module

#Connect to Exchange Online PowerShell

#<UPN> is your account in user principal name format

#Change this to path of the csv file that contains EmailAddress of all User Mailboxes you want to get a report for

#Loop through each row in csv

• Launch Windows PowerShell (in elevated mode)
• Change the path to the location where you saved the .ps1 file
• Run the below command:
  • .GetMigrationReport.ps1
• Navigate to the reports folder and you will notice that text files start appearing in this folder.
• The report for each mailbox will be saved as the user’s UPN and in .txt format

You can check migration status for a single mailbox using this command:

You can check migration status for a single batch using this command:

• We can customize this report as per our requirements. In this example, we are extracting the Creation Time, Server Name, Type, TypeInt, Flags, FlagsInt, Message columns and also using the AutoSize switch to make the report look neat and tidy.
• The report begins the details of the user who created the migration batch.

• It then establishes connection to the target mailbox (Office 365). Connection is made to both the primary mailbox and Archive mailbox (if it exists)

• It then establishes connection to the source mailbox (Exchange On-Premises). Connection is made to both the primary mailbox and Archive mailbox (if it exists)

• Once the connection has been established, it starts the item discovery process and gathers the item count and size of the mailbox for both Primary mailbox & Archive mailbox

• Folder hierarchy is created at the destination so that the data can be copied to respective folders from the source

• Last step before the copy process begins is creating of an Initial Sync Check point

• Then the copy process begins

• As the copy process progresses, it continues to log updates and the same are available in the file that is generated by running the script
• Once the copy process is complete, you will see it writes the finalization to the logs

• The copied content is then verified for both primary mailbox and the archive mailbox

• Target mailbox information is logged

• he mail user is converted to a mailbox at the destination

• Final incremental Sync runs followed by the final clean-up process

• The mailbox is converted to a mail user at the source

• Reset & Clean-up tasks for the mailboxes are logged

• Changes are replicated and Migration completion is logged

We just saw how we can generate migration report for each mailbox via PowerShell.

In this demo we first populate the CSV File with the list of users and then install Exchange Online PowerShell Module. After that we connect to our Microsoft 365 environment and extract the migration reports. This saves lot of time when comparted to manually going to each migration batch and viewing details of each mailbox being migrated.

Connect to Exchange Online PowerShell | Microsoft Docs

Basic auth - Connect to Exchange Online PowerShell | Microsoft Docs

About the Exchange Online PowerShell V2 module | Microsoft Docs