Short answer
Switching from a freelancer’s WordPress site to a managed platform can reduce the work your firm handles for hosting, updates, and support. Before you move, confirm who controls the domain, obtain a complete backup, save your content and analytics, and plan redirects for changed URLs. Decide how email and any connected forms or software will keep working. Compare the new platform’s features, fees, data access, and exit process before making the change.
Check what your freelancer controls
Start by listing the accounts and services connected to your current site. A freelancer may have set up WordPress, hosting, domain registration, email, analytics, or form tools under separate accounts. The firm should know who controls each one and how to access it.
Ask for administrative access or a handover plan before ending the working relationship. Make sure you can log in to the domain registrar and hosting account, not just the WordPress dashboard. Confirm that the domain is registered to the firm or to an account the firm can control.
Also ask where the site’s files and database are stored. You may not need to move every plugin or theme to the new platform, but you should know what the existing site contains before it is taken offline.
Make a migration inventory
Record the important parts of the site and what each one needs to do after the move. This helps you spot missing pages, broken forms, and services that depend on the old host.
| Item | What to record before switching |
|---|---|
| Domain | Registrar, account owner, renewal date, and DNS settings |
| Pages | Page titles, current URLs, key text, images, and downloads |
| Contact tools | Form fields, notification recipients, and where submissions go |
| Email provider, addresses, and any DNS records used for delivery | |
| Search and analytics | Analytics account, search tools, and current tracking setup |
| Integrations | Calendars, payment tools, chat, maps, and other connected services |
| Backups | A recent copy of the WordPress files and database, plus who holds it |
Keep a copy of the inventory and backup somewhere the firm controls. If the site receives inquiries, test where those inquiries go before and after launch. Do not assume a form works just because it appears on the page.
Protect URLs and search visibility
A new platform may use different page addresses. For example, a page that used to end in /practice-area/ might have a different URL after the move. List the old URLs that matter, then map each one to the closest relevant page on the new site.
Set up redirects where URLs change, and test them after launch. Update internal links so pages on the new site point directly to their new addresses. Check page titles, descriptions, images, and contact details while reviewing each page.
Avoid taking down the old site before the replacement is ready. Coordinate the launch so the domain points to the new platform at the right time. After the change, test the site on a phone and desktop, submit test inquiries, and check the important links.
Compare the platform and the exit terms
A managed platform can bundle website hosting and maintenance, but the details vary. Ask what the monthly price includes, which features cost extra, and what happens if you leave. A lower workload is useful only if the firm can still access its site information and keep control of its domain.
Compare these points before choosing:
- Ownership and access: Who owns the domain, site content, and submitted data? Can the firm export or retrieve them?
- Included services: Are hosting, SSL, maintenance, support, and software included, or billed separately?
- Website changes: Can staff update common content themselves? Who handles design or technical changes?
- Forms and integrations: Do inquiries reach the right people? Can the platform connect to the tools the firm already uses?
- Contract and cancellation terms: Is there a fixed commitment, cancellation fee, or required notice period?
- Migration support: Who handles redirects, domain settings, testing, and the launch?
Get answers in writing, especially about ownership, data access, cancellation, and what happens to the site if the firm switches again. A demo can clarify the workflow, but it should not replace a review of the terms.
What to do next
- Ask the freelancer for account access, a current backup, and a list of connected services.
- Build the migration inventory and identify pages, forms, and URLs the firm cannot afford to lose.
- Compare platform features, total costs, data access, and cancellation terms. LegalWebDesigns offers a $0 setup and a $49 monthly plan, with domain, hosting, and SSL included; the firm owns its site and data. Review the pricing and website examples before deciding.
- Choose a launch date, test forms and email, and confirm redirects before pointing the domain to the new site.
- Use the comparison pages to weigh platform options against the firm’s current setup.
A careful handover matters more than moving quickly. Keep the domain and account access under firm control, verify that inquiries reach the right place, and check key pages after launch.
law firm websitesmanaged platformswebsite migrationWordPress