Read time 7 minutes
Due to the advent of efficient cloud platforms and their efficient services, many business owners try migration from On-premises Exchange to Office 365. The size of exchange mailbox is generally quite heavy, and it can be a time consuming and error-prone task to perform a complete migration. There are some methods which can help you in completing the desired tasks-
A CSV file is completely suitable for bulk migration of large mailboxes to Office 365. You can use a CSV file while using the Exchange admin center (EAC) or the New-MigraitonBatch cmdlet in Exchange Management Shell to create a migration batch. There are following migration scenario where a CSV file is useful –
Onboarding remote move migration
Onboarding remote move migration helps you to migrate mailboxes from on-premises Exchange online to Office 365. It works in the Exchange hybrid deployment scenario.
Offboarding remote move migration
Offboarding remote move migration is opposite to onboarding remote move migration; here you can migrate Office 365 mailboxes to your on-premises Exchange environment.
Staged Exchange migration
In Staged Exchange migration, you can migrate a subset of mailboxes from an on-premise Exchange organization to Office 365.
In this type of migration, you can migrate mailbox data from an IMAP server (including Exchange server) to Office 365.
The CSV file has a defined format under you can insert the required mailbox information. The first row (header row) lists the names of attributes, or fields, specified on the rows downwards. Each attribute is separated by a comma. Each row under the header row represents a user and provides complete information required for migration. The attributes in the row must follow the same order as the attributes names in the header row. Finally, you can create a CSV file in any text editor, but it is better to create in Microsoft Excel Spreadsheet page as it can make easier to insert attribute in the dedicated cells. Always save the file in .csv or .txt format.
Note: If the attribute value for a record is null, then don’t type anything for that attribute. But, you should enter the comma to separate the null value from the next attribute.
The following section will describe you what attributes you should enter for different methods of migration –
Staged Exchange Migration
Attribute – EmailAddress, Password, ForceChangePassword.
Attribute – EmailAddress, UserName, Password.
Cutover migration is suitable in such situations when the number of mailboxes in Exchange Account is lesser than 2000. Here is a brief procedure of cutover migration conducted by Exchange Administrator –
The Hybrid Migration is done when you have to maintain both on-premises exchange and online Exchange. This can be done when:
Kernel Office 365 Migration is a tool that can migrate an unlimited number of mailboxes from on-premise and hosted exchange to Office 365. It does not require any prior preparation and fully migrates mailboxes and provides a full report after successful migration. Let’s see how this migration tool works:
Note: You can save the CSV report of the process by clicking on the Save report to CSV option.
Though there are different native methods to migrate mailboxes to Office 365, most of these methods are technically complex. But with Kernel Office 365 Migration tool, you do not need to face any such complexities; just start with the migration as soon as you map mailboxes and filter their content.