Read time 4 minutes
While migrating Exchange mailbox from one database to another, the Exchange Administrator does not need to sync the data to each folder, but Exchange Server does it automatically. But occasionally you may have to face some error related to the syncing of a mailbox. One such error is following –
Couldn't switch the mailbox into Sync Source mode. This could be because another administrator is currently moving the mailbox into the destination database,
the mailbox is locked, or the Microsoft Exchange Mailbox Replication service doesn't have the correct permissions.
The error mentions that it cannot sync the source mailbox with the destination. It also shows some possible causes like the mailbox is locked, Microsoft Exchange Mailbox Replication service lacks necessary permission for syncing the mailbox.
First of all, you can try to run the repair request and fix the mailbox in such state that you can complete the migration.
Run the command:
The command checks and repairs all types of corruption from the mailbox named Tony.
Run the soft recovery.
Run the hard recovery:
After recovering the database file, you can rerun the migration for the mailbox in the database file.
When you do not get satisfactory results even after applying any of these methods for fixing the error, then you need to use a professional tool which can recover the EDB file in full health. Later, you can migrate the EDB file content to Office 365. Kernel for Exchange Server is one such efficient Exchange Recovery tool which can recover Exchange Server data including all its messages, contacts, notes, appointments, journals, deleted items, etc.
It not only recovers the EDB file but also allows you to migrate them directly to Office 365. It accesses the EDB file from its location, scans it deeply, and retrieves whole mailboxes along with their folders. After retrieving the EDB file, you can add Office 365 as the destination and perform the migration. The migration is done by a simple copy-paste, drag-&-drop, or copy all mailboxes operation. After each migration, the tool provides a migration report which denotes the status of migration.