Move mailbox to Exchange Online with PowerShell

After installing the Hybrid Configuration Wizard (HCW), you like to move a mailbox to Exchange Online with PowerShell. The term is also known as onboarding a mailbox to the cloud. So what do we need to fill in PowerShell to start the mailbox migration? In this article, you will learn how to migrate a mailbox to Exchange Online with PowerShell.

Before you start to move a mailbox to Exchange Online with PowerShell

The first step is to make sure to install and connect with Exchange Online PowerShell. When you are connected, go to the next part to find the remote server URL.

Good to know is that you are not pushing the mailbox from on-premises to Exchange Online. In fact, you are pulling the mailbox from on-premises to Exchange Online. That’s why you need to run the commands from Exchange Online PowerShell.

Find migration endpoint remote server URL

Get the remote server URL by using the Get-MigrationEndpoint cmdlet. Read more about how to find RemoteHostName URL for mailbox migration. The Hybrid Configuration Wizard created this migration endpoint. Copy the RemoteServer URL as you will need it in the next part.

PS C:\> Get-MigrationEndpoint | Format-List Identity, RemoteServer


Identity     : Hybrid Migration Endpoint - EWS (Default Web Site)
RemoteServer : d07c851a-d141-2c91-f2b3-4bb87r5e51gg.resource.mailboxmigration.his.msappproxy.net

Move mailbox to Exchange Online with PowerShell

Create a new move request to Exchange Online. Fill in the following details

• -Identity: Mailbox name or email address
• -RemoteHostName: The remote server that you copied in the previous step
• -TargetDeliveryDomain: Primary SMTP domain used for the Exchange Online organization mailboxes
• -RemoteCredential: On-premises administrator account with privileges

After running the cmdlet, a credential sign-in request will show up. Fill in the password of the on-premises credentials (RemoteCredential).

PS C:\> New-MoveRequest -Identity "Maisha.Lee@exoip.com" -Remote -RemoteHostName "d07c851a-d141-2c91-f2b3-4bb87r5e51gg.resource.mailboxmigration.his.msappproxy.net" -TargetDeliveryDomain "exoip.mail.onmicrosoft.com" -RemoteCredential (Get-Credential exoip\administrator)

DisplayName StatusDetail        TotalMailboxSize            TotalArchiveSize PercentComplete
----------- ------------        ----------------            ---------------- ---------------
Maisha Lee  WaitingForJobPickup 32.11 MB (33,670,771 bytes)                  0

Get the status of the mailbox move request by using the Get-MoveRequest cmdlet.

PS C:\> Get-MoveRequest -Identity "Maisha.Lee@exoip.com" | Get-MoveRequestStatistics

DisplayName StatusDetail TotalMailboxSize            TotalArchiveSize PercentComplete
----------- ------------ ----------------            ---------------- ---------------
Maisha Lee  Completed    32.11 MB (33,670,771 bytes) 0 B (0 bytes)    100

The mailbox will complete.

If that is not the case and you can’t complete the mailbox move request, you can suspend and resume the move request. It helps in most situations when you get a failed status. For example, the status detail TransientFailure.

Did this article help you to migrate the mailbox to Exchange Online with PowerShell? I hope it did.

Read more: Complete migration batch with PowerShell »

Conclusion

In this article, you learned how to move a mailbox to Exchange Online with PowerShell. Connect to Exchange Online PowerShell and run the cmdlet as shown in the article. Keep an eye if the mailbox move to Exchange Online successfully completed.

Did you enjoy this article? You may also like Target mailbox doesn’t have an SMTP proxy matching. Don’t forget to follow us and share this article.