Migrate Exchange Mailboxes to another Using New Move Request Cmdlet

Updated On - February 17, 2024 by Nasir Khan | Reading Time: 5 minutes

It is very common for users to migrate Exchange mailboxes to another database. For this purpose, most users are now using the PowerShell Command-Line (New-MoveRequest command line). An Exchange Administrator can easily transfer mailbox databases in the Live Directory forest from one database to another via the New-MoveRequest command.

Users may move mailboxes in almost all Exchange versions (like 2010/2013/2016/2019) using “Exchange Management PowerShell.” Migration between the same Active Directory forests is referred to as a “local move request,” whereas migration between other forests is considered a “remote move request.”

Related Post: Your Mailbox has been Temporarily Moved on Exchange Server

Exchange Management Shell (PowerShell): In a Nutshell

The Exchange Management Shell is based on Windows PowerShell technology and offers robust command-line functionality for automating Exchange administration operations. It may be used to handle all aspects of the exchange. You may, for instance, establish email accounts, send and receive connections, set mailbox database characteristics, and configure distribution teams.

You may use the Exchange Management Shell to conduct any job that is accessible in the Exchange graphical management tools, as well as those that are not available in those tools (for example, bulk operations).

In reality, whenever you perform an action in the Exchange admin center (EAC), the Exchange Control Panel (ECP), or the Exchange Management Console (EMC), the Exchange Management Shell is responsible for the work behind the action sequences.

The Exchange Management Shell also includes a powerful and adaptable coding environment. Visual Basic scripts with numerous lines of code can be supplanted by Exchange Management Shell commands with as few as one line of code.

Because it employs an asset model based on the Microsoft.NET Framework, the Exchange Management Shell gives this adaptability. Exchange cmdlets can use this object type to apply the outcome of one command to future actions.

How to migrate Exchange mailboxes to another database using the New-MoveRequest cmdlet.

Migrating Exchange mailbox data to another database is a common affair for users, and there are various methods available for this purpose. Within them, the usage of New-MoveRequest is well known. But the process has some usage of critical codes or command lines. Read the process as follows:

1. First and foremost, you must obtain the mailbox database that contains the user’s mailbox. Execute the following command in the Exchange Management Shell (known as EMS):

“Get-Mailbox jkurtin| Format-List Database”

(In the above instance that you can see in the image, a user’s mailbox is stored in the “DB01” database.)

2. The New-MoveRequest cmdlet is generally used to generate a local or basic request to relocate or move a mailbox. As an example code line:

“New-MoveRequest -Identity jkurtin -TargetDatabase “DB02″ –BadItemLimit 10”

Here in this code, “jkurtin” is a username. It differs from user to user, as everybody needs to use a unique username.

In this command, “TargetDatabase” is the name of the mailbox database to which you wish to relocate or move a mailbox.

Are you aware of what the “BadItemLimit 10” is in this code? Actually, it is the number of damaged objects in the mailbox that may be bypassed or ignored when the mailbox is being moved. In this command line, we have set the limit for bad items to 10.

[ Note: If “BadItemLimit” is set to 0, the mailbox will not be copied to the destination database if any corrupted items are discovered. If you set “BadItemLimit” to more than 50, you must also include the AcceptLargeDataLoss option.]

3. Then in the cmdlet you can see the mailbox and archive sizes (see in the picture “TotalMailboxSize” and “TotalArchiveSize”), as well as a message indicating that the transfer request has been line.

4. Use the command line as follows to transfer all mail from one Exchange database to another:

“Get-Mailbox -Database DB01 -ResultSize Unlimited | New-MoveRequest -TargetDatabase DB02″

[Note: To perform the migration, you must use the Arbitration option.]

5. Moving a mailbox might take a long time based on the volume of the mailbox and the location of the target server. You can use the following command line to track the mailbox migration status in percent.

“Get-MoveRequestStatistics -Identity jkurtin”

6. When the migration is finished, the “PercentComplete” number will hit 100, and the migration status will be changed to “Completed.”

Related Post: How to Setup Outlook with Exchange Server? 

Drawbacks of the New Move Request Cmdlet

The New Move Request Cmdlet method of Exchange migration involves exporting mailbox data to PST files, transferring the files to the new server, and importing the data to the new mailboxes. While this method may work for small organizations, it has several drawbacks, including:

• Time-consuming and error-prone: The manual method involves a lot of manual work and is time-consuming. It is also prone to errors, such as data loss, data corruption, and duplicate items.
• Lack of automation: The manual method does not have any automation features, which can be a problem when dealing with large amounts of data.
• Limited scalability: The manual method is not scalable and may not work well for organizations with a large number of mailboxes.
• Complex migration scenarios: The manual method may not work well for complex migration scenarios, such as cross-forest migrations or migrations from non-Exchange platforms.

How to overcome these limitations

Using a third-party tool for Exchange migration can overcome many of the limitations of the manual method. Some benefits of using a third-party tool include:

• Automated migration process: Third-party tools automate the migration process, reducing the risk of errors and saving time.
• Scalability and flexibility: Third-party tools are scalable and can handle large amounts of data. They also provide flexibility in terms of migration scenarios.
• Support for complex migration scenarios: Third-party tools can handle complex migration scenarios, such as cross-forest migrations, mergers and acquisitions, and migrations from non-Exchange platforms.
• Advanced reporting and monitoring: Third-party tools provide advanced reporting and monitoring features, which can help administrators track the progress of the migration and troubleshoot any issues.

Perform the Exchange migration using professional software

If you are not experienced with any programming language or any technical expertise, then it might be critical for you. However, you can use the Regain EDB to PST Converter software.

Free Download100% Secure Buy NowPrice: $99

It is a powerful tool for converting both offline and online EDB files from Exchange Server databases into Outlook PST files. This expert program may extract single or numerous messages based on your requirements.

Exchange to Exchange Migration using Regain Exchange migration tool

Here are the general steps for Exchange migration using the Regain Exchange Migration Tool:

• Download and install the Regain Exchange Migration Tool on your system.
• Launch the tool and select the source Exchange Server from which you want to migrate data.
• Connect to the source Exchange Server using the administrator credentials and select the mailboxes that you want to migrate.
• Choose the target Exchange Server or Office 365 environment to which you want to migrate the data.
• Connect to the target environment using the administrator credentials and create the target mailboxes.
• Start the migration process and monitor the progress of the migration using the tool’s dashboard.
• Verify that the data has been migrated correctly and test the new environment to ensure that it is functioning as expected.

Generally, users who need to migrate their Exchange mailboxes to the Outlook database find that this software is so much more efficient for them. Besides, PST formatted files are more secure than others, so it can be a great option for backing up your important Exchange data.

Features of the Regain Exchange Migration Tool

Some of the key features of Regain Exchange migration tool for Exchange migration include:

• Pre-migration analysis: The software analyze the source environment to identify any issues or potential problems before the migration begins.
• User mapping and rehydration: Regain Exchange migration tool can map user accounts and rehydrate data during the migration process, reducing the risk of data loss or corruption.
• Incremental migration: Our tool can perform incremental migration, which means that only the changes made since the last migration are migrated, reducing the migration time.
• Support for multiple migration scenarios: We provide free support for various migration scenarios, such as cross-forest migrations, mergers and acquisitions, and migrations from non-Exchange platforms.

Conclusion

Exchange migration is an important process for organizations that need to move to a new email platform. While the manual method may work for small organizations, it has several drawbacks that can make it unsuitable for large organizations or complex migration scenarios. Using a third-party tool like Regain Exchange migration tool can overcome many of these limitations and provide advanced features such as automation, scalability, and support for complex migration scenarios. It is important to carefully evaluate different third-party tools before choosing the best one for your organization.