Website migrations work by copying your site to a new host or platform, testing it in a staging area, updating DNS, then checking speed, forms, redirects, tracking, and search performance after launch.
A migration can be simple, like moving a WordPress site from one host to another. It can also be risky, like changing your domain, redesigning your site, changing URLs, or moving from a custom CMS into WordPress. The goal is not only to get the site live. The goal is to keep leads coming in, protect SEO value, and avoid broken pages that cost you calls, forms, bookings, and sales.
For a local business, the biggest migration mistakes usually happen around URLs, tracking, forms, DNS, and page speed. A dental office, law firm, pest control company, or lawn care business may not notice a broken blog post right away, but a broken service page or contact form can affect revenue the same day.
| Migration step | What it means | What to check |
|---|---|---|
| Backup | Create a full copy of files, database, media, plugins, and settings. | Confirm the backup can be restored, not just downloaded. |
| Staging setup | Build and test the site away from the public domain. | Check menus, forms, images, mobile layouts, and checkout or booking flows. |
| URL mapping | List old URLs and match them to new URLs. | Add 301 redirects for changed pages so users and Google land in the right place. |
| DNS change | Point the domain to the new server. | Lower DNS TTL before launch when possible and test SSL after the switch. |
| Post-launch QA | Review the live site after traffic starts hitting the new host. | Test speed, forms, analytics, Search Console, and high-value landing pages. |
Good example: A plumber moves hosting but keeps the same domain, same service page URLs, same phone tracking setup, and the same contact form fields. The team tests the new server first, launches during a low-traffic window, then checks Google Search Console and GA4 after launch.
Bad example: A business launches a redesigned site, changes every service page URL, forgets redirects, blocks search engines in WordPress, and only finds out weeks later when rankings and lead volume drop.
Before a migration, we like to capture a baseline. Pull top pages from Google Search Console, landing page traffic from GA4, current rankings from Ahrefs or Semrush, and crawl data from Screaming Frog. This gives you a clean before-and-after view, so you can tell whether the migration worked or caused damage.
Use this short checklist before launch:
- Back up the old site and database.
- Crawl the old site and export all indexable URLs.
- Map changed URLs to their new destination.
- Test forms, phone buttons, booking tools, payment tools, and email alerts.
- Check mobile layouts on the most valuable service pages.
- Test SSL, caching, redirects, robots.txt, sitemap, and analytics.
- Submit the new sitemap in Google Search Console after launch.
Hosting migrations also affect performance. A faster server can improve user experience, but weak setup can slow pages down even if the hosting plan looks better on paper. Watch Time to First Byte, Core Web Vitals, image loading, caching, plugin load, and database performance. PageSpeed Insights can flag issues, but the real question is whether people can quickly call, book, or submit a form.
If you are also changing design or site structure, treat the migration as an SEO project, not just a development task. Keep high-performing pages, protect internal links, and avoid removing proof such as reviews, case results, photos, service details, and local trust signals. Our web design and WordPress hosting work covers the technical move and the lead path, so the new site is faster, cleaner, and safer for search performance.
Recommended action: Before moving your site, list your top 10 traffic and lead pages. Test those pages first after launch. If calls, forms, tracking, redirects, and mobile speed work on those pages, you have reduced the largest migration risks.
