Email Migration

  1. Create a hosted zone on Route53 for the customers domain if it doesn’t already exist
  2. Copy and create all known records for the domain into Route53

Set the TTL records for TXT and MX records to very low (60 seconds). Make note of what they use to be. We do this since we will be changing them soon. For now, the values need to stay as what they currently are set to.

Chris Elkins
  1. Get control of the customers DNS by changing their nameservers over to the new Route53 nameservers
  2. After nameservers are pointed to us, we can then initiate a domain transfer (if desired by the customer; in most cases we will do this)
  3. Create the new email inboxes and domain on the new mail platform, such as Zoho, Google, or Office 365. Setting up verification DNS records is OK but don’t change MX record yet.
  4. Setup all inboxes, aliases, and groups. Don’t change the MX record yet. However, the TXT record for SPF can be updated now to support the new mail provider.
  5. Test inboxes with a mail client. Document the new usernames/passwords for the customer.
  6. Finally, coordinate with customer to choose time to make the email switch. This will be when we change MX record to now point to the new email service platform and customer’s employees will start using the new inboxes. They will need assistance getting each computer and phone connected to the new platform.