Internal Portal

Search

Preparing For A Website Migration

Table of Contents

In some cases, we may need to rush through a website migration as part of a way to earn a client’s business. In these scenarios, it’s very important for the salesperson to leverage their relationship with the client to obtain this information in advance for the team so they can focus on completing the work needed to facilitate this process. In instances where the migration does not need to be expedited, this information may be referenced by the account strategist to help see the process through.

Details:

We need all of the following before we can begin working on the website migration.

  • Login info for domain registrar (i.e. GoDaddy, Network Solutions, etc).
    • Please be sure to test the login to ensure it works and there is no 2FA activated on the account. If there is, please coordinate with the client to get logged in and then disable this extra verification step in the account settings (be sure to let the client know you are doing this).
    • If the client’s existing agency is the one managing the domain (i.e. the client does not have access), we will need to do a domain transfer. Include the contact info for the agency in this task so that we can reach out to them. Please note that a domain transfer may extend the timeline for the migration.
  • Website Files:
    • If the client has a FindLaw website, we need the EUI file (they provide the website content, plugin settings and design files).
    • If the client has a Scorpion website, we need them to send us the website files (all they provide is the html files)
    • If the client has a Martindale website, we need their account manager to send us the xml files for the website (all they provide is website content)
    • If the client has a non-FindLaw, WordPress website, obtain their admin website credentials or have them create a login for us using the email [email protected]
    • For all other self-managed websites (such as Wix, Squarespace, Google, etc), please work obtain the website credentials so we can see what options exist to export the content.
  • Email Information:
    • Is the client using a branded email address? If so, confirm with the client that their existing website vendor is not providing their email services. If they are, then you will need to contact Josh or CJ for guidance on that process.
  • Access to accounts for integrations (if applicable)
    • If the client’s existing site has special functionality on their website that needs to be retained during the migration, we may also need access to those accounts. Examples of this would be:
      • Newsletter opt-ins (ex: MailChimp, Constant Contact, Klaviyo, etc)
      • Embedded / integrated scheduling or calendar features (ex: Calendly)
      • CRM / Intake functionality (ex: Clio Grow)
      • Shipping/Payment/Fulfillment integrations for eCommerce sites (i.e. Stripe, Paypal, Afterpay)
      • Webchat functionality (ex: Chat scripts for ApexChat, Tawk.io, Intaker).
      • Client portals, File Upload features

Migrations are only easy when we have all of the info that we need to complete them. It is the task owner’s responsibility to make the effort to equip the team with this information to help ensure the work can be completed on time and according to the client’s expectations.