“From GoDaddy Manged Exchange Online”

Recently I had a customer with Exchange online that was purchased through GoDaddy “I never recommend this”. GoDaddy offers a very limited set of licensing and features and the customer now wanted to deploy Teams as well as some of the other services not available through GoDaddy such as Azure AD Connect. I managed to do this migration with only about 20 minutes of email service downtime “I thought this was pretty good considering the situation”

Preliminary Setup

  1. Create a new Office 365 Tenant.
  2. Export users from old tenant, modify the UPN to match the new tenants “CompanyName.onMicrosoft.com” domain and import the users into the new Tenant.
  3. Start adding the organization’s domain name to the new tenant, and add the TXT DNS record awhile. “Note: it will not actually verify in Office 365 until the domain is removed from the old tenant” but at least it will be propagated ahead of time.
  4. Set TTL “Time to Live” as short as possible on all DNS records relating to Exchange Online “MX, autodiscover, SPF”.

Performing the Migration

  1. I Then started the migration using BitTitan to do a “Pre-Stage” migration to copy all mail older than 60 Days to the new tenant “You may want to do 30 days if you have a lot of mail so the full Migration later goes faster”.
    NOTE: The next series of step should be done in rapid succession.
  2. Change your primary MX record from the old tenant to a domain that is not reachable, i.e. “unreachable.example.com”. Most mail servers attempting to deliver new mail will queue the mail and attempt redelivery for 24 hours.
  3. As soon as the MX record changes propagate across the internet start the Full Migration using BitTitan.
  4. Once the BitTitan Mail sync is completed call GoDaddy and have them delete the old tenant. “Recommend having them on the phone ahead of time”
  5. Soon after the old tenant is deleted by GoDaddy you can verify the domain in the new tenant.
  6. Change all the users UPN’s from the .onmicrosoft.com domain to the organization’s domain name you just added to the tenant.
  7. Configure the DNS / MX records to point to the new tenant.
  8. Now that mail is flowing again “whew” sit back, relax, and reconnect all the users mail clients while they pace anxiously around the office wondering what they are missing out on. Note: This can be done using multiple different types of tools, I would recommend checking out BitTitan’s option for Outlook.