Read time 7 min
Many times, Exchange administrators have to move mailboxes in bulk to a different database. Manually moving them would be a difficult task. So, you need a different approach to migrate multiple mailboxes. That is why you need to perform a batch migration. Batch migration involves the use of a CSV file containing both the source and target details, like username, address, password, etc.
Here, we are providing the procedure of batch migration in Exchange Server 2013.
This manual way to migrate data from one database to another database is feasible but takes too much time; also, it and does not use any filters for selective migration. Risk of data loss is always there during the migration. Also, you cannot perform migration to other destinations like Office 365. That is why professional Exchange migration tools like Kernel Migrator for Exchange are preferred for bulk mailbox migration to Office 365.
With Kernel Migrator for Exchange (KME), batch migration is easier. In KME, you need to create a migration project and then a migration job, which involves the addition of a source and subsequent selection of mailboxes as shown below.
Instead of proceeding with the manual selection of mailboxes, you can use the Import from CSV option of the tool to add mailboxes. This is the sample CSV file which you have to create. With such a CSV file, the addition of mailboxes is easier.
Once you add the destination for migration, you can map the source mailboxes with the destination mailboxes as shown below:
The Map button of the dialogue box provides multiple options to map the mailboxes.
When you click the Map using CSV option in the software, the Select CSV to Map wizard gets opened. Browse and select the mapping CSV file. Finally, click OK.
Note: This is the sample of the CSV file that you can use for mapping.
After the mapping, you can proceed with the migration as usual.
Here, we have discussed the native and professional ways to migrate a batch of mailboxes to the target. Limitations of the manual way are also mentioned. You can easily understand how an advanced tool is more beneficial for Exchange administrators.