Last Updated on March 30, 2026
In Exchange Server, a move request refers to migrating a mailbox from one database to another. A local move request moves the mailbox within a single Active Directory forest. Remote requests happen across completely different Active Directory forests.
You can use the local request to move the primary mailbox and the linked archive to the same or another database. This is easily done through the Exchange Admin Center (EAC) or Exchange Management Shell. Using an EDB to PST converter tool like Stellar Converter for EDB averts the hassles involved in manual methods.
Move Exchange Mailbox by Using EAC
You can use the Exchange Admin Center (EAC) to move mailboxes in your on-premises organization. This specific method applies only to Exchange servers 2019, 2016, and 2013. Follow these exact steps to configure your migration batch.
1. Log Into the EAC
You must log into the Exchange Admin Center using your administrator account credentials. This portal gives you full graphical control over your server environment. Enter your domain username and password to proceed.
2. Navigate to Migration Settings
Click on the Recipients tab on the left navigation menu. Select the Migration option from the top menu bar. Click the Add+ icon and then choose the Move to a different database option from the dropdown list.
3. Start the Local Move Wizard
The New local mailbox move wizard will immediately appear on your screen. Follow the on-screen instructions to select the specific users you want to move. Click the Next button once you have your target mailboxes highlighted.
4. Configure the Move Settings
You will see the Move configuration page load in the subsequent window. You need to configure the new migration batch name and adjust the archive settings. Specify the target database for both the primary mailbox and the archive mailbox. Set the bad item limit to determine the maximum number of corrupted items allowed before the request fails. The default value in the EAC is exactly 10.
5. Finalize the Batch Process
Next you must configure the final settings on the Start the batch page. Click the New button when you are done adjusting the parameters. The server will begin processing the mailbox migration based on your criteria.
6. Understand EAC Limitations
This method appears convenient but does have certain demerits. You need to have the requisite permissions to perform the task. There are potential restrictions on the physical size of the mailbox you want to move. Large mailboxes take significantly longer to move and can cause severe network throttling. Advanced migration options are completely missing from the EAC interface.
Move Exchange Mailboxes Using EMS
Here are the steps to perform a mailbox migration to another database with the help of the Exchange Management Shell. This command-line approach offers much more granular control over the process.
1. Launch the Management Shell
Open the Exchange Management Shell as an administrator. You must have elevated privileges to execute migration commands. This ensures you have the proper rights to modify database records.
2. Locate the Current Database
You must get the exact database name that currently includes the mailbox you want to move. Run the EMS cmdlet Get-Mailbox to find the precise location of the mailbox. Type Get-Mailbox MBuser | Format-List Database and press enter.
3. Create a Local Move Request
Create a local move request by running the specific migration cmdlet. Type New-MoveRequest -Identity MBuser -TargetDatabase “DBUser01” -BadItemLimit 10 into the shell. DBUser01 is the name of the destination database where you want to move the mailbox. The BadItemLimit dictates the maximum number of damaged items you can safely skip.
4. Move Multiple Mailboxes at Once
You can easily move all mailboxes from one database to another using a bulk command. Run the Get-Mailbox -Database “DBUser02” | New-MoveRequest -BatchName “DBUser02 to DBUser01” -TargetDatabase “DBUser01” -Priority High -BadItemLimit 51 -AcceptLargeDataLoss command. This forces the server to migrate the entire database contents simultaneously.
5. Check the Migration Status
You need to verify that the migration completed successfully. Check the mailbox move status request by running the Get-MoveRequestStatistics -Identity MBuser command. This outputs the exact percentage and status of the current transfer.
6. Acknowledge EMS Drawbacks
This manual method helps you move your mailboxes to another database efficiently. It still accompanies several major drawbacks like considerable downtime during the transfer. It requires high-end technical acumen to run the EMS commands safely. An inexperienced person will likely end up losing data while executing these intricate shell commands. Read this Microsoft link for more detailed insights.
Migrate Mailboxes Using Stellar Converter for EDB
You may encounter several frustrating issues while running manual processes through PowerShell cmdlets or the EAC. You might also face major hassles when exporting public folders or mailboxes to PST to move them. Stellar Converter for EDB oversees all these shortcomings and helps migrate your data flawlessly.
1. Review Crucial Software Features
This software migrates mailbox components from online or offline EDB files directly to Outlook PST files. It easily moves multiple mailboxes from an offline EDB file to a live Exchange server. It saves up to four mailboxes simultaneously to speed up the process. You can even change the export priority order when migrating data to Office 365. It converts data from archive mailboxes and public folders to PST, Office 365, or Live Exchange.
2. Install the Converter Application
These simple steps help you convert EDB to PST files in a completely different database. Install and run the EDB to PST converter directly on your system. The interface is highly intuitive and easy to navigate.
3. Select Your Source File
Use the Browse option to select the exact EDB file you want to convert. The software scans your local drives to locate the database files. Click the Next button to start the conversion process.
4. Save the Converted Data
The software processes the database and prepares the output. Save the converted file into your preferred file format. You can now import this clean file directly into your new Exchange database.
