Read time 9 minutes
The emergence of cloud computing has allowed businesses to keep their data over a secure cloud platform like Office 365 and access it from anywhere. Although Exchange Server is a powerful email management server, it can be combined with the benefits of Office 365 in a hybrid deployment scenario to achieve more. In the present article, we will go through a method to migrate the archive mailboxes from on-premises Exchange to Office 365.
Here are some points which you need to understand before starting the migration –
After fulfilling the prerequisites, you can further start the migration for the Exchange archive mailbox. Here are various stages of the migration:
Before migrating the on-premises Exchange Server mailboxes to Office 365, you need to create a migration endpoint which contains the information of the on-premises Exchange Server which has active MRSProxy Service. The migration endpoint is useful in creating remote migration batches.
Why is Migration Endpoint important to Migrate Office 365?
Migration Endpoint is the component that saves the Administrator credentials and connection settings for source Exchange server containing the archive mailboxes. For the cutover and staged migration, the Migration endpoint also contains the information for the number of mailboxes selected for migration. The Exchange Administrator requires to create the migration endpoint for multiple types of migrations like cross-forest move, remote move, cutover migration, staged migration, IMAP migration.
There is the Get-MigrationEndpoint cmdlet available to run in Exchange Management Shell to bring the minute details of about the created migration endpoint.
The available parameters are ConnectionStrings, Diagnostic, DiagnosticArgument, DiagnosticInfo, DomainController, Partition, Type.
Follow the steps to create the migration endpoint –
Follow the upcoming steps to enable the MRSProxy service if it is not already enabled.
Follow these steps:
The migration will start, and the mailbox data along with the archive mailbox will instantly migrate to the Office 365 mailbox. The time of the migration will depend on the size and the total number of mailboxes.
Sometimes, during the manual process, the archive mailbox is not migrated to Office 365, but a new archive mailbox is created. It causes a failure of whole process and the user requires to restart the whole process.
If the user creates a migration batch from archive mailbox to Office 365 and enable the archive mailbox after the creation of batch, then it will not migrate it. Only the primary mailbox will be moved.
The method indicates that it migrates the archive mailbox along with the primary mailbox and there is no option to handle the archive mailbox separately. In such cases, you need to take the assistance of a professional migrator tool which can manage the environment of the Exchange Server and Office 365. Kernel Migrator for Exchange – Express Edition is a powerful yet user-friendly software which can access the mailboxes from the Exchange account and place them to the Office 365. It automatically synchronizes the mailboxes at Office 365, and you can access them instantly.
Assisting the users on various migration topics such as, migrate from Office 365 to Hosted Exchange, how to perform Hosted Exchange to Hosted Exchange migration, how to migrate Exchange archive folders, and more, it’s the one stop shop for all your migration requirements.
Follow the upcoming steps to use the functional procedure of Kernel Migrator for Exchange – Express Edition:
Kernel Migrator for Exchange – Express Edition is a complete migrator tool which removes all the complexities related to the migration and safely places the data at the destination Office 365 mailbox, and if you’re looking help on how to migrate Office 365 to Hosted Exchange, need not to download a new tool, as Exchange Migrator Express Edition is an all-in-one.