Office 365 being a renowned software and services subscription is deployed in a large number of organizations. It automatically detects the running server, i.e. Exchange 2013, 2010, 2007 on-premises. It uses a process known as cutover migration or cut over email migration, in which user can use the Office 365 setup wizard to copy the data if there are less than 151 mailboxes. After copying the data, they can add all the users at the same time. In the following session, we will discuss a way to use PowerShell to perform a cutover migration to Office 365.
Users need to log in and import cmdlets on local Windows PowerShell session to access cmdlets of Exchange Online PowerShell. Discover what you need to know about a cutover email migration to Office 365.
Before performing this process, users require various permission.
The following section in this article discusses complete step by step guide of cutover migration to Office 365. But when it comes to the proven solution to migrate On-Premise Exchange to Office 365, then many experts recommend the one-stop solution by SysTools. Its top-rated features and easy to use interface helps users to make the process efficient and effortless. It helped many organizations to carry out migration at rapid pace and cut migration costs to higher extent.
There are few steps involved, which helps users to perform a cutover migration of email to Office 365 by utilizing PowerShell as mentioned below:
Step 1: Prepare for Migration
Before Wizard can copy the email data and add users, complete few changes on-premises Exchange Server environment.
Note: Outlook Anywhere configuration should be configured with certificate that is issued via CA (certification authority).
1. In active directory in the on-premises organization, administrator should be a member of group of Domain Admins.
2. Full Access permission should be assigned to the administrators for every on-premises mailbox.
3. Receive As permission must be allotted to administrator for storage of user mailbox.
Step 2: Create Endpoint
For the successful migration, Office 365 should be connected with email system of source. To perform this, Office 365 utilizes endpoint of migration. Firstly, user needs to connect to Exchange Online for the creation of endpoint of Outlook Anywhere migration. Now run the following command on PowerShell in Exchange online:
User can utilize Test –MigrationServerAvailbility cmdlet to obtain and test the settings of connection to on-premises Exchange server, and then utilize those settings of connections for the creation of migration endpoints known as CutoverEndpoint.
Note: The cmdlet New-MigrationEndpoint can be utilized for specifying database service by using targetDatabase randomly allocated from services of Active Directory Federation, where mailbox is located.
For the Verification run the mentioned command on PowerShell to displayinformation about CutoverEndpoint migration.
Step 3: Create Cutover Batch Migration
User can create cmdlet New-Migration Batch in Exchange OnlinePowerShell for the creation of batch migration. They can create batch migration and begin it automatically by including AutoStart parameter. Even, the user can create it and then manually start it after utilizing cmdlet Start-MigrationBatch.
Step 4: Begin Batch Cutover
User can run the mentioned command to begin the batch migration in Exchange online. It creates migration batch known as “CutoverBatch.”
Step 5: Route All Emails
Mail systems utilize DNS record known as MX record that helps to figure out where the mail has to deliver. At the time of email migration procedure, MX record was pointing towards source mail system. Now, that mail migration is completed to Office 365, its time to point MX record at Office 365. It helps to make sure that the mails are delivered to mailboxes of Office 365. With MX record, user can also off the old mail system after completion of migration.
Step 6: Deletion of Cutover Migration
After changing the MX record, verify all the emails are routed to mailboxes of Office 365 properly or not. After this, user can delete the cutover migration batch. Before deletion, verify the following:
1. All users are utilizing Office 365 mailboxes. After the deletion of batch, mail is sent to mailboxes and on-premises server is not copied to resultant mailboxes of Office 365.
2. Mailboxes of office 365 were synchronized at least once after beginning the sending of mail directly. For this, make sure that value in last synced time box for batch migration is more recent than the started mail.
Step 7: Allot Licenses
Assign licenses to users to activate Office 365 user accounts for the migrated accounts. If the license is not assigned then, mailbox is disabled when the grace period ends.
Step 8: Complete Task of Post-Migration
In the above discussion, complete process is discussed to use PowerShell to perform a cutover migration to Office 365. If the steps are followed in a correct manner then user can perform a Cutover email Migration to Office 365. However, if any issue is faced while performing the process of migration, drop a comment below, and the problem will be seen by experts.