Home » Blog » Exchange Server » How to Move Corrupted Mailbox from One Exchange Server to Another?
Exchange Server

How to Move Corrupted Mailbox from One Exchange Server to Another?

Ugra Narayan Pandey | Modified: 2022-04-15T15:48:29+05:30 | 5 Minutes Reading
Exchange Server

“The Exchange Server 2013 is used in a particular organization. Now, this organization wants to upgrade the Exchange Server from version 2013 to 2016. For doing this, the admin builds a new Exchange Server and deploys the role of Exchange 2016. Now, there are two different servers. First is the Exchange Server Version 2013 and the second is the Exchange Server with 2016 configuration. The second step is that the admin wants to move corrupted mailbox from one Exchange Server to another.”

The problem arises when the user encounter corrupted mailboxes while transferring the mailboxes from one Exchange to the another. In this scenario ‘move corrupted mailbox from one Exchange Server to Another’, a user is unable to export the mailboxes.

Reasons to Export Exiting Database into New Exchange Database

Some of the reasons due to an Admin required to move old Exchange database into new one:

  • File System is Corrupted
  • Outlook Add-ins are Faulty
  • Failure of Exchange Hardware or Data storage
  • Sudden Power Failure at the Exchange Site
  • Broken ActiveSync Clients
  • Outdated Antivirus Software

Move Corrupted Mailbox From One Exchange Server to Another

Approach 1: Enable and Disable the Mailbox Quarantine Commands

Damaged mailboxes are quarantined by the Exchange Server. Due to this, a user is unable to access mailbox making the use of Outlook Client. The Exchange 2013 and later version provides the feature to enable cmdlets to manage mailbox quarantine. The commands used are described below:

  • Enable-Mailbox Quarantine
  • Disable-Mailbox Quarantine

Manual deletion of the registry key can be replaced with the help of these commands. Moreover, users can use this command to identify the currently quarantined mailbox:


In case, this method cannot resolve the problem, users can go with second method

Approach 2: Use 4 Steps Repair & Migration Process

This is the manual method to move corrupted items from the Exchange Server. Follow these steps to move corrupted mailbox from one Exchange Server to another:

Step 1: Repair the Mailboxes at Page Level

If there is corruption in the database at the page level, users can repair the page using ESEUTIL/p. If the log files are unavailable, that also results in clean shutdown of the database. In this case, the database needs to be repaired using Eseutil/p utility.


A message will appear on the screen warning you about the data loss. Click on OK and continue the process.


Eseutil/p utility may also result in the clean shutdown state. You can verify the state with Eseutil/mh utility


A message of operation completed successfully along with the time taken will be displayed on screen.

Step 2: Break the Database to Restructure and Recreate It

In this step, you have to defragment the data using Eseutil/d. Before you begin the process, make sure that there is sufficient disk space. This is to host the temporary database, same as it was made during the process.


A message of operation completed successfully along with the time taken will be displayed on screen.

Step 3: Repair the Logical Corruption

In this step, users have to repair the objects logically within the Exchange Server. The logical repair is different for different versions.

For Exchange 2007: The ISINTEG that is used to do logical repair is:


The databases which are marked Offline are tested.

New-MailboxRepairRequest can be executed for the entire database or for a single database, as required. If it is working for a single mailbox, then service for only that mailbox will be suspended.

New-MailboxRepairRequest checks for the following:

  • Search for Folder Corruption: Confirms the existence of the folder names in ptagSearchBacklinks, ptagSearchFIDs, and ptagRecursiveSearchFIDs. If any of the folders do not exist, it is removed.
  • Counts the messages in Folder: It counts the total number of message present in a folder. This computed count is then matched with persisted count on the Table record for that folder. If both of the counts do not match, in that case, persisted count is replaced with calculated count.
  • Provisioned Folders: Examines the provisioned folder with the non-provisioned parent folder.
  • Folder View: The command is capable to generate a complete itinerary of “Views” of any particular folder. Also, it reconstructs a replica of that folder. If there is any discrepancy between original and replicated copy, the view gets deleted to regenerate it from the scratch whenever it is requested.

For Exchange 2010:


For Exchange 2013:


Generally, the Exchange database can be repaired.

Step 4: Export Mailbox Content

Once the Exchange Server database is repaired, it can be exported with the help of EMS cmdlets. Once all the data is exported, disable the Exchange Server mailbox. At last, complete the process by importing the data with the help of Exchange Management Shell.


When users want to transfer the data from one Exchange Server to another, they face an issue when the mailbox they are trying to export is corrupted. To do this, users can go with a manual method. But, the manual method may result in data loss. And the process can be very time-consuming. In that case, users can go for third-party tool like Exchange Mailbox Recovery. It is the professional solution to move corrupted mailbox from one Exchange Server to another.

Exchange Mailbox Recovery tool helps to repair any version Exchange Server database and transfer into new Exchange Server database easily. Also, recover the corrupted Exchange Server mailbox and move into Live Exchange Server, Office 365. For the older version, it helps to repair Exchange Server Priv.edb, Pub.edb & Stm files. Restore data from Dismounted & Offline Exchange Server EDB files

Download Now    Purchase Now