How to Solve Exchange Migration Error: MigrationTransientException MapiExceptionMdbOffline? Get Solution

Summary: When users try to move/migrate their mailboxes from one Exchange Server to another either one by one or in bulk and they end up receiving this error Exchange migration error: migrationtransientexception mapiexceptionmdboffline unable to get mailbox information. In this write-up, we will guide users to solve or fix the error smoothly.

Users use the New-MailboxMoveRequest cmdlet to move the Exchange database to another or to a mailbox database to different server.

New-MoveRequest -Identity test1 -TargetDatabase "testing"

This command move the Exchange database mailboxes one by one. If you want to move the complete mailbox database in a single shot, then use the cmdlet given below:

Get-Mailbox -Database "testing" | New-MoveRequest -BatchName "testing to test2" -TargetDatabase "test2"

You cannot move the mailbox selectively because this command move the entire mailbox database and users will also notice the degradation of performance in the server. If you want to perform selective migration, in that case users can use different parameters to migrate mailboxes selectively specified in CSV file.

While during migration in bulk or one by one, users may encounter with the error message given below in the Microsoft Exchange Server.

The given error occurred when users perform single or bulk mailbox migration. It is easy for users to find the cause of this issue when they migrate single mailboxes but in batch migration it is hard to know the reason behind the error because they have to dig deeper in the log file to find the cause.

Solution to Fix the Exchange Migration Error: MigrationTransientException MapiExceptionMdbOffline

Let’s consider the migration of Exchange Server 2010 to Exchange 2016.

One simple way to solve the issue or error is to restart the Exchange 2010 services.

Firstly, users need to use the PowerShell Get-ServerHeath command to run the health test on both Exchange Server to view the running state of both servers. Corruption in mailboxes or folders is one of the causes of the export failure.

Another option is to use the machine where MS Outlook is installed & the account is setup. Users can run Outlook by using the cmdlet given below:

Outlook.exe /cleanfinders

After completion of this users can again try to move the mailboxes but if this option fails, you can use the application called MCFMAPI to identify the folder which causes the error or issue.

After opening the tool, follow the steps that is given below:

Step 1: Click Tools >> Then, options

Step 2: Enable this option “Use the MDB_ONLINE flag when calling OpenMsgStore” by clicking on it

Step 3: On session menu, click logon >> Select profile name & Click OK

Step 4: Now this will connect to the mailboxes on Exchange Server >> Right-click on the Exchange database loaded mailboxes >> Click OK

Step 5: Now users will see all the structures & mailbox folder. You can use the PowerShell Get-MoveRequestStatistics cmdlet to view the detailed report and export it into the XML file. When users search for any failure in this file, they will find the folder under DataContext. Here, you will find the folder which are causing issue.

Step 6: Then, on the MFCMAPI application >> Go to the particular folder that is causing the problem >> Right-click on it & click on the Delete Folder option

Step 7: When a window will pop up, select the Hard Deletion >> Click OK

After that, users can perform the migration. If the solution is successful, users will face data loss. By using this method, the only way is left is to delete the content that are causing problem.

But this would consume so much time and effort to complete the task. To avoid all this complexity and trouble, users can also use the advanced solution provided by SysTools i.e. Exchange Server Recovery Software that easily perform migration of Exchange mailboxes to the Exchange Server in a simplified manner without using any command.

Use Best Automated Wizard

Exchange Server Recovery Tool is the advanced software that is designed and developed with advanced algorithm that easily export EDB mailboxes to Live Exchange Server in a hassle-freeway. This utility is used by various IT professionals, Exchange & novice users. It provides graphical interface which reduces the time and effort of users to perform the migration.

The software provides scan mode option which resolves database corruption Exchange 2010 / 2013 / 2016 and recovers as well as repair Exchange mailbox & EDB file with no data loss. Quick scan is used to remove minimal corruption and if the Exchange database file is highly corrupted then select the advance scan. This option also recover permanently deleted mailboxes & data items from offline/dismounted EDB file.

It supports both private and public offline/dismounted Exchange database file & STM file. Users can extract mailbox from EDB file Exchange 2016/2013 and migrate to the Office 365, Exchange Server and various file formats (HTML, EML, MBOX, MSG, PDF, PST). This utility automatically creates the export report which contains the success and fail count of export Exchange mailbox data.

Key Features Of Automated Software

1. Extract mailbox from public and private EDB file
2. Preview Exchange database mailbox items before conversion
3. Keep metadata intact and preserve folder hierarchy
4. Date filter option migrate data items in a specified period of time
5. Option to decrypt emails from Exchange mailboxes in bulk
6. Migrate offline EDB to Office 365, Exchange Server, & multiple file formats
7. Categories filter option migrate selective mailbox items
8. Support all Exchange Server, Windows OS, and Microsoft Outlook version

Bringing It All Together

Now users have detailed information on how to fix or solve the Exchange migration error: MigrationTransientException MapiExceptionMdbOffline with the help of solution provided here. If users want the simplest and quickest way to migrate offline / dismounted mailboxes from one Exchange Server to another, then they can go for the advanced solution described in the above solution which easily recovers and repair EDB file from corruption and export the healthy as well as recover mailboxes directly to the Live Exchange Server mailboxes, O365, and different file formats in a simple way.