Switching From FindLaw: A Step-by-Step Migration Plan

Short answer

Switching from FindLaw is easiest when you separate the work into four parts: account access, content and data, website launch, and follow-up. First, confirm what your current agreement includes and which assets you can take with you. Then prepare the replacement site, map important URLs, test contact forms, and coordinate the domain change. Keep the old service active until the new site is working and you have checked the launch.

1. Inventory your current website and account

Before cancelling or changing a service, make a record of what your firm uses. FindLaw offerings and contract terms can differ, so confirm your own plan and documents rather than assuming every account includes the same items.

Create a simple inventory that covers:

• Website pages: List every page, including practice-area pages, attorney biographies, office locations, FAQs, and contact pages.
• Domain and DNS: Identify the domain registrar, the account holder, and who can change DNS settings. Do not assume the website provider and registrar are the same.
• Email: Note whether your firm email uses the domain and who manages its records. Website changes should not interrupt email delivery.
• Leads and forms: Record where inquiries go, who receives notifications, and how the firm tracks follow-up.
• Analytics and listings: Locate access to Google Analytics, Google Search Console, Google Business Profile, and any call-tracking tools you use.
• Agreement and billing: Check renewal dates, notice requirements, cancellation terms, and what happens to the website and content when service ends.

Ask the provider for the files or exports you are entitled to receive, such as page text, images, blog posts, and lead records. Save copies in a firm-controlled location. For client information, use your existing security and retention procedures when deciding what to export or delete.

2. Decide what to keep, revise, or leave behind

Do not automatically copy every page. Some content may be outdated, duplicated, or tied to a service you will no longer use. Review each page and choose one of three actions: keep it, revise it, or retire it.

Preserve accurate attorney biographies, useful practice-area explanations, office details, and pages that already attract relevant visitors. Update old phone numbers, staff listings, service descriptions, and calls to action. If you remove a page, identify its closest useful replacement rather than sending visitors to an unrelated page.

Keep a spreadsheet with these columns:

The exact URL examples above are placeholders. Use the real addresses from your website. Record URLs with and without trailing slashes if your site treats them differently, and include important blog posts and campaign landing pages.

3. Build the replacement before changing the domain

Choose the new structure, design, and features while the existing website remains available. Confirm that the replacement includes the pages your firm needs and that you can edit them after launch.

Review mobile layouts, page titles, contact details, and calls to action. Test the site on a phone and desktop. Make sure each practice-area page has a clear next step, such as calling the office or submitting an inquiry.

If you are comparing providers, check what the monthly price includes, who owns the site and data, whether a contract applies, and how support works. LegalWebDesigns offers $0 setup and a $49 monthly option, with domain, hosting, and SSL included; it also offers a $490 annual option. Its practice management software includes matters, calendar, documents, billing, and a client portal. The firm owns its site and data, and there are no contracts. Review current details on the pricing page and available website examples.

4. Map URLs and plan the launch

A new design does not require every page address to change. Keeping useful existing URLs can reduce the number of redirects and make the transition simpler. When an address must change, create a direct redirect from the old URL to the closest relevant new page.

Before launch, confirm who will make the DNS change and when. Save the current DNS records, especially records used for email. Coordinate the change with whoever manages your domain and email. Avoid making several unrelated changes at once; if email or the website stops working, a clear change record helps identify the cause.

Use this launch checklist:

1. Confirm the new site is complete and accessible for review.
2. Test every form, phone link, email link, and booking path.
3. Check redirects for important old URLs.
4. Confirm analytics and Search Console access on the replacement site.
5. Save existing DNS settings and arrange the domain change.
6. Keep the old account available until the new site and lead delivery are confirmed.

5. Test after launch and monitor the transition

After the domain points to the new site, visit the homepage and key pages from a phone and computer. Submit a test inquiry and confirm it reaches the right person. Check that phone numbers, office hours, maps, and email links work.

Review Search Console for crawl or indexing issues and check analytics for an unexpected change in visits. Test a sample of old URLs from your inventory, including high-value pages and any links used in advertising. Correct redirect errors and broken links promptly. A redirect should lead to a useful, closely related page—not just the homepage by default.

Keep a record of the launch date, DNS changes, redirects, and any issues resolved. Continue checking forms and call routing during the first few weeks. Once you have verified the new site, lead delivery, and access to your assets, follow the cancellation steps in your existing agreement.

What to do next

1. Find your current service agreement, renewal date, and cancellation instructions.
2. Confirm domain, DNS, email, analytics, and website account access.
3. Export content and make a page-by-page keep, revise, or retire list.
4. Prepare URL redirects and test the replacement site before changing DNS.
5. Compare providers, inclusions, ownership terms, and support on the comparison pages before choosing a migration date.