Exchange Migration 2016 & O365 RRS feed

  • Question

  • We are planning to install Exchange server 2016 co-existence with Exchange 2010 and want to migrate mailboxes to Office 365 while migrating our on-premises Exchange 2010 servers to Exchange 2016 due to short time for the end of support. Please give your thought

    Already 2010 Hybrid in place and moved a couple of mailbox to 365
    Friday, July 26, 2019 6:03 AM

All replies

  • You can get the help of an Exchange migration software to migrate Exchange to office 365 mailboxes. To know more about the migration tool, visit:
    Friday, July 26, 2019 6:15 AM
  • Although time is short, maybe you could consider doing the full migration to Exchange 2016 if you use use a third party tool like CB Exchange Server Sync
    Friday, July 26, 2019 8:13 AM
  • First, we’ll ensure that we’ve added all of our custom domains to our Office 365 tenant. These will need to match the email domains we use on-premises:

    <Portal Domain

    To add a new domain, choose <Path> and Add Domain. You’ll need to follow the steps, and verify each domain using a TXT record, similar to the one shown below:

    The first step in migrating Exchange to Office 365

    Use your DNS provider’s control panel to add the corresponding TXT record to each domain, then continue the verification process. 

    Exchange to Office 365 migration- Step 2

    Once you reach the point to add additional DNS records, it’s important you choose to Skip adding records such as Autodiscover or MX record changes.

    This is crucial because at this point in the process your email is still looked after by on-premises systems, and you do not want to redirect clients to Office 365. The Hybrid relationship we create will manage this for us, later on.

    We’ll sign-in to Office 365 using a login ID in the same format as an email address. In an Exchange Hybrid relationship, we expect this to match the Active Directory UserPrincipalName for each user.

    Friday, April 17, 2020 10:20 AM
  • Hello,

    damned, you do not have any good anwser for this.

    Only robot tried to sell some licence

    i hope all is fine for your migration.

    and , yes, use 2016 as hybrid server work well (and free) and/or keep 2010 as hybrid too.

    all you need is external acces to your EWS URL that provide move application.


    Friday, April 17, 2020 12:08 PM