Guide to Move Office 365 Mailbox to Another Account


Do you want to move Office 365 mailbox to another account but aren’t sure how to go about it? If you answered yes, you’ve come to the right place. We’ll go over every aspect of Office 365 migration here. Migrate Office 365 to Office 365 appear to be distinct from other migration tasks. Many users are even unsure where to start with their Office 365 migration. Fortunately, it is not as difficult as it appears.

You might wonder why someone would want to switch from Office 365 to something else. So, here it is: Office 365 tenant to tenant migration is initiated for a variety of reasons, including company mergers, tenant migration, data storage location shifts, domain changes, and so on.

Methods for Migrating from Office 365 to Office 365

Users of Office 365 occasionally want to move Office 365 mailbox to another account. They fail, however, due to a lack of knowledge and tools. Users can migrate their mailboxes between Office 365 using both manual methods and professional software.

Migration from Office 365 to Office 365 using the Manual Method

The PowerShell commands can be used to migrate Office 365 to Office 365. However, before using the PowerShell Scripts, the user must complete the following Pre and Post-migration steps:

Warning: the manual method should be avoided if you are a non-technical user. Also, look into the recommended and painless Office 365 tenant-to-tenant migration method.

Single-user migration

Preparing the Domain:

  • To begin, double-check that you have enough Office 365 licenses.
  • Second, in both the source and target Office 365 environments, create admin accounts.
  • In the target tenant, create a user mailbox, a resource mailbox, and distribution groups.
  • Consolidate ADDS (Active Directory Domain Service) with the ADDS tool.
  • Now, both the source and target domains must be synchronized.

Validate the Domain:

  • Begin the verification process in Office 365 for the target domain.
  • To create the TXT record in DNS, add the source domain to the target domain.

(Note: Ensure that the domain only has one tenant.) And it will take 72 hours for the changes to appear).

Schedule a Migration from Office 365 to Office 365:

  • To begin, make a list of the user mailboxes you want to migrate.
  • Second, make a CSV file for mapping.
  • On the MX (Mail Exchange) record, write down the lowest TTL value (Time to Live).
  • Finally, turn off the source domain’s synchronization. (From the Admin Center, disable.)

Office 365 to Office: Migrate

  • Change the MX value to an unreachable value to stop the source tenant’s mail flow. (Enter the MX record’s lowest TTL value) (Noted in the previous step).

Prepare Office 365 as a source:

  • Delete all objects from the primary domain on the source Office 365 before transferring the mailbox to another Office 365.
  • Run the following command in PowerShell to remove all objects from the primary email address.

Prepare for Office 365 with the following steps:

The final step is to move Office 365 mailbox to another account. Start this step one hour after you finished the previous one.

  • Set up CNAME auto-discovery.
  • Configure a new domain in the target Office 365 for Active Directory Federation Services (ADFS) if you’re using it.
  • Now, in the target Office 365, activate the new users and assign new licenses.
  • Then, using the PowerShell Scripts listed below, set the new primary email address.
  • Decide on the end user’s communication password now.
  • Change the mail routing and point the MX record to the new primary email address once the user mailboxes have been activated.
  • Finally, examine the target Office 365’s mail flow.
  • The pre-migration task has come to an end. To migrate Office 365 to Office 365, run the PowerShell command.

If you have corrupted items in your mailbox, you can move them with PowerShell, but you must specify how many things must fail before the move is canceled.

Right-click PowerShell and select Run as administrator.

First and foremost, double-check that you’re using PowerShell rather than the Exchange Management Shell.

  • For Office 365, use the Global Admin account.
  • Make use of an on-premises account.

Users in Large groups should be Moved.

Moving mailboxes in bulk (in a hybrid deployment) is easiest to do with Exchange Admin Center 2013 or Exchange Management Console 2010, in my opinion. We can, however, use a list of commands for the same task with some additional preparation.

Install Microsoft Online Services and Sign-In Assistant for IT Professionals RTW first on a hybrid server. Then, to finish the installation, install Azure Active Directory Module for Windows PowerShell (64-bit version) and reboot the hybrid server.

Create a list of mailbox aliases for the users you want to bulk-move. The file must be a CSV file (userlist.csv) with an ‘Alias’ header.

Connect to Microsoft Office 365

  1. To connect to Office 365 from the hybrid server, use the ‘Windows Azure Active Directory Module for Windows PowerShell console and the commands below.
  2. Use your on-premise credentials for the variable ($ONPREMCREDS) (i.e., DOMAINNAME\Administrator).

Execute the Office 365 Migration in Bulk

To perform the bulk migration, we’ll now use the CSV file we created earlier. Make sure the CSV’s path is local. Set the variable with this command.

This command is used to start and run the bulk moves.

Keep an eye on the requests for relocation.

  • Use the following command to keep track of mailbox movements.
  • Use the following command to cancel mailbox move requests.

For free Office 365 migration, use the manual method (PowerShell). Let me point out some of the disadvantages of the manual method before you use it.

PowerShell’s Disadvantages

• For starters, it is complicated and difficult to use for non-technocrats.
• Second, it is time-consuming and lengthy. And users must go through the same procedure over and over.
• There is a risk of data loss, as well as the possibility of human error. If you make a mistake manually, your Office 365 data may become inaccessible or lost.
• There is no guarantee of a successful migration when done manually.
• Folder hierarchy and data integrity are not guaranteed.

Users prefer professional Office 365 migration tools to avoid data loss and the drawbacks of the manual method.

Try it for Free.

Nowadays, everyone wants to be certain about the software before purchasing it. For this reason, the software provides a free demo version that can be used to test the software’s capabilities before purchasing it. Only the first 2 users can be migrated to the free version.

Finally, you will learn about Office 365 to Office 365 migration. For this task, there are also some manual methods available. However, the manual method is not recommended or efficient. It’s like walking on eggshells when you use a manual approach. As a result, one misstep will result in the loss of your Office 365 data. PCVITA Office 365 to Office 365 migration is recommended for those who want a secure and painless migration. It is the simplest method for transferring Office 365 mailboxes to Office 365.


Please enter your comment!
Please enter your name here