Start running cutover migration to Office 365
Step 1 – In the migration, the SMTP address for every single mailbox of an on-premises server is utilised to make the email address for the new mailbox on Office 365. For running the cutover migration, the domain of on-premises server has to be an authenticate domain for Office 365 Organisation.
Login to MS Office 365 using your school or work account.
Select SETUP > Domains.
Go to Domains – then new page will appear where click on Add Domain for starting domain wizard.
A page named ADD A Domain will appear in which type domain name that you want to use for the on-premises Exchange Organization. Then click on Next.
Go on the page – Verify Domain where choose Add a TXT record or Login to GoDaddy for another registrars. After that, click on the Next button.
There are DNS hosting instructions that should be followed and to authenticate ownership, TXT record is followed.
There instructions can also be found within Create DNS records while managing DNS records in Office 365. Once you include MX or TXT record, you should wait for 15 minutes prior to proceed for next level.
In domain wizard of Office 365, select Done and Verify Now. Then a verification page will appear before you where you should select FINISH.
In case, the verification goes wrong or you get a fail message, you should wait for some time and retry.
Don’t go for the next level in domain wizard immediately. Make sure to check that you have the ownership of Exchange organization of your on-premises domain and prepare with the mail migration.
Step II – Link Email System With Office 365
The endpoints of migration comprises of credentials and settings required to link on your on-premises Exchange server which hosts your mailboxes which are required to be migration on Office 365. The endpoint of the migration also narrates the mailboxes number for migrating simultaneously. In cutover migration process, one should make migration endpoint for Outlook Anywhere.
Open Exchange admin center
Go to Recipients > Migration
Select More > Migration Endpoints
On endpoints page, select New +
Select migration endpoint type page, select Outlook Anywhere > Next.
1. Migrating Email Address – Write email address of a user in on-premises Exchange that needs to be migrated. Then, Office 365 verifies connectivity of mailbox of the user.
2. Migrating Privileged Account – Write the name of the user for the account which has required admin permissions in on-premises Exchange. Office 365 uses this certain account for discovering endpoint of migration and verify permissions associated with the account by accessing mailbox having the certain email address.
3. Password of privileged account – enter the password of the privileged account that will be an admin account.
Select Next and then follow this step
When Office 365 links to the key server successfully, the settings of connection will start displaying. Then, select next.
- Go on to the page and Enter general detail where type the name of migration endpoint. Leave rest two boxes empty to utilize default values.
- Select New option for make migration endpoint
- For verifying connected Exchange Online to On-premises Exchange server, run this command Test – MigrationServerAvailability.
Step 3 – Creating batch for cutover migration
As said earlier, cutover migration is done in batches. So, in this step, you should create a batch for the migration to Office 365. Here are simple steps to make batches in this step.
Open Exchange Admin center and then go to Recipients > Migration
Select New+ and then Migrate to Exchange Online
Go on a new page of Select a Migration Type where choose cutover migration and then click on Next.
Go on to a new page to Conform the migration endpoint where you will see all detail related to an endpoint. Authenticate details and select Next.
Manual start of batch later
Automatic start of the batch
Select New option to make the batch for migration
Step 4 – Start the batch of Cutover Migration
In case you choose manual start of batch, it can be started from Exchange admin center.
Follow these instructions to start the batch
Open Exchange Admin Center, then go on Recipients > Migration
The dashboard of migration will appear where choose batch and click on start.
In case batch starts on its own, the migration dashboard status will change to sync.
Step 5 – Email Routing To MS Office 365
Email systems utilise MX record as DNS record to discover the location of email delivery. In the migration process, the MX record points to the main email system. Now, email migration is done, now point MX record to Office 365. It will contribute to ensure that email delivery to Office 365 mailboxes is done. Migration MX record also enables you to switch off previous email system once you are prepared. For recognising MX record by your partners or customers, 72 hours are required. So, wait for this much long and then proceed for next step.
Step 6 – Delete batch for cutover migration
Once the MX record is changed, verify each and every email routing for Office 365 and let users know that emails are routed to Office 365. Once you are done with this step, delete the batch in cutover migration. Before you delete the batch, verify these things:
Each user has started using mailboxes in Office 365. Once deleting the batch, no mail which you sent to on-premises Exchange server’s mailboxes will be copied to the mailboxes of Office 365.
The mailboxes of Office 365 had synchronised once email start to be sent straight to the mailbox.
Once deleting the batch in cutover migration, the service of migration wash out all records of migration batch as well as the batch too.
Go to admin center of Exchange where choose Recipients > Migration
In the dashboard, choose batch and then delete
In the admin center, go to Recipients > Migration
Recheck for the unavailability of the batch.
Step 7 – License Assigning To Users
This is the last step of Office 365 cutover migration process in which you should assign licenses to Office 365 users. All the users whose accounts are being migrated to Office 365 are required license to use the services.