{"id":2091,"date":"2018-08-14T07:26:11","date_gmt":"2018-08-14T07:26:11","guid":{"rendered":"https:\/\/www.kerneldatarecovery.com\/blog\/?p=2091"},"modified":"2022-12-07T10:08:09","modified_gmt":"2022-12-07T10:08:09","slug":"exchange-to-office-365-migration-using-cutover-migration-part-3","status":"publish","type":"post","link":"https:\/\/www.kerneldatarecovery.com\/blog\/exchange-to-office-365-migration-using-cutover-migration-part-3\/","title":{"rendered":"Exchange to Office 365 Migration using Cutover Migration Part-3"},"content":{"rendered":"

Post-Migration Processes<\/h4>\n

A successful confirmation message after the cutover migration from Exchange on-premises to Office 365 does not mean that the task is over. Vital post-migration processes need to be executed after that.<\/p>\n

Exchange-to-Office-365-Migration-using-Cutover-Migration-Part-1<\/a>
\nExchange-to-Office-365-Migration-using-Cutover-Migration-Part-2<\/a>
\nExchange-to-Office-365-Migration-using-Cutover-Migration-Part-3
\nExchange-to-Office-365-Migration-using-Cutover-Migration-Part-4<\/a><\/p>\n

We will discuss these post-migration tasks now:<\/h4>\n
    \n
  1. Assigning licenses to new users in Office 365 \u2013<\/strong><\/li>\n

    It is required to assign licenses to the users in Office 365; otherwise, mailboxes get disabled after the grace period of 30 days. Licenses can be assigned to each user one by one (if using different license types) or in bulk (with the same type). Let us see how to assign the license to Office 365 users.<\/p>\n

      \n
    1. Open Office 365 Admin Center<\/strong>. Go to the Active Users<\/strong> page.<\/li>\n
    2. Select the user for assigning the license.<\/li>\n
    3. In the Product Licenses<\/strong> option, click Edit<\/strong> on the rightmost side.<\/li>\n

      \"\"<\/p>\n

    4. Select your Location<\/strong> and toggle the license to ON<\/strong> from OFF <\/strong>(against the user name). By default, all licenses are turned ON. Toggle OFF the licenses in the list that you don\u2019t want to assign.<\/li>\n

      \"\"<\/p>\n

    5. Finally, click Save <\/strong>to complete the process.<\/li>\n

      Similarly, you can assign licenses to other users as well.<\/ol>\n

    6. Creating Autodiscover DNS record (connecting new Office 365 mailboxes to Outlook and other clients)<\/strong><\/li>\n

      Configuring a new Autodiscover DNS record for the Office 365 organization helps users connect their Office 365 mailboxes with Outlook and mobile clients. The new Autodiscover DNS record should have the same namespace as the one using for Office 365 organization. You can create DNS records for Office 365 when you manage your DNS records<\/a>.<\/p>\n

      Note:<\/strong> In Exchange 2013, Exchange 2010, and Exchange 2007, the administrator should set<\/p>\n

      Set-ClientAccessServer AutodiscoverInternalConnectionURI to Null.<\/strong><\/p>\n

    7. Decommissioning On-premises Exchange Server \u2013 <\/strong><\/li>\n

      Once you are sure that all emails are routed to your Office 365 and don\u2019t want to keep Exchange on-premises any longer, you can decommission your on-premises Exchange Server. In simple words, uninstall or remove your on-premises Exchange Server from the organization.<\/p>\n

      Easier ways for mailbox migrations<\/strong><\/p>\n

      After going through the native method for Exchange to Office 365 migration, we can find that the method is quite lengthy and hence, time-consuming. Also, a simple manual error at any level could derail the migration process and hinder its success.<\/p>\n

      But, we have a solution for you, Exchange Migrator \u2013 a smartly designed professional Exchange Migration<\/a> tool that can migrate mailboxes from any Exchange Server version to Office 365 within the minimum possible time. It migrates mailboxes and public folders from any version of Exchange Server to another easily. For easy and safe migration, you can trust this software.<\/p>\n

      Read the 4th part of the series<\/a> to know in detail about this migration tool.<\/p>\n

      FAQs<\/h4>\n

      Q. Why should I create an Autodiscover DNS record after cutover migration?<\/b><\/p>\n

      A. It is needed to configure a new Autodiscover DNS record (with the same namespace as used in Office 365 account) after the migration from Exchange to Cloud to help in connecting Office 365 users with Outlook and mobile device clients.<\/p>\n

      Q. Do I need to decommission Exchange Serve after migration using the tool?<\/b><\/p>\n

      A. Decommissioning of Exchange Server is the post-migration task that is optional to its administrators. It refers to the uninstallation or removal of the Exchange Server from the organization.<\/p>\n

      Q. Can I migrate content from Exchange Server 2010 to Exchange Server 2019 with this tool?<\/b><\/p>\n

      A. Yes, definitely. The advanced migrator tool supports migrating any Exchange Server version to another, be it in the same or different domains. It supports both hosted and on-premises Exchange Server migrations.<\/p>\n

      Q. What if I do not assign licenses to Office 365 users post cutover migration?<\/b><\/p>\n

      A. If no licenses are assigned to Office 365 users after the cutover migration, the user mailboxes will get disabled after a short period of 30 days. To continue using and working with the mailboxes, it is required to purchase and assign licenses for the same.<\/p>\n