Changing your website shouldn't feel like defusing a bomb. But a lot of businesses treat website migrations as if one wrong move will bring everything crashing down.
Migrations go wrong for predictable, avoidable reasons. Here's what they are.
What a Website Migration Really Is
A website migration is any significant change to your site's URL structure, hosting platform, CMS, domain, or site architecture. Redesigns that change URLs. Platform moves from Webflow to WordPress or from one hosting provider to another. Domain changes. HTTPS upgrades. Structural reorganisations of your content.
What makes migrations risky isn't the technical complexity. Most modern CMS platforms handle the mechanics well. What makes them risky is when the preparation is rushed or skipped entirely.
The Real Issues That Cause Migration Problems
1. SEO not considered until after launch
The most common cause of post-migration traffic drops: URL changes without redirects. If your page for "commercial plumbing Melbourne" was at /services/commercial-plumbing and after the migration it's at /commercial, every link pointing to the old URL now returns a 404. Every bit of ranking authority that page had earned is severed.
The fix is straightforward: before the new site launches, map every URL on the old site to its equivalent on the new site. Set up 301 redirects for every change. Test them all before going live. This is not optional if you care about organic traffic.
2. No full backup exists
Migrations require a safety net. Before you touch anything on the live site, you need a full backup (database, files, all of it) that you can restore from if something goes wrong. Not a partial backup. Not a backup you haven't tested restoring from. A complete, verified backup sitting somewhere separate from the live environment.
3. Performance is assumed, not tested
A new platform doesn't automatically mean a faster site. New design, new plugins, new hosting. Each can add or subtract from load speed. Run a PageSpeed Insights check on the new site before it goes live. If it's meaningfully slower than the old site, find out why. Page speed affects rankings and conversion rates; a beautiful new site that's three seconds slower than the old one is a net negative.
4. The site isn't properly tested end-to-end
Before launch: test every form, every checkout path, every interactive element. Test on mobile, not just desktop. Test in Safari and Chrome, not just whichever browser you use. Check that tracking is firing correctly: GA4 events, Google Ads conversion tags, any other measurement setup. A migration that breaks your conversion tracking is a migration where you'll have no idea whether the new site is working.
5. Launch is rushed or poorly timed
Migrations should not launch on a Friday. They should not launch the day before a major campaign goes live. They should not launch during peak season if your business is seasonal. You need time to monitor, time to identify issues, and time to fix them without the pressure of a major promotion running simultaneously.
If a deadline is forcing a rushed migration, push back. The cost of a bad migration is almost always higher than the cost of a delay.
6. Nobody is told what's changing
Internal teams, agencies managing your paid ads, SEO partners. Anyone who has links to your site or campaigns pointing to specific URLs needs to know what's changing and when. Ad campaigns sending traffic to old URLs that now 404 waste budget immediately. Email campaigns with old links lose conversion value. Tell the people who need to know, before you launch.
Frequently Asked Questions
How long does a proper migration take to prepare?
For a small business site (under 50 pages), a couple of weeks of preparation is usually sufficient if done properly. For a large site with thousands of pages, complex URL structures, or significant organic traffic at risk, you're looking at a month or more of preparation. The live work can be fast. The preparation cannot be.
Will our Google rankings drop after a migration?
There's often a short-term fluctuation while Google recrawls and re-evaluates the new site. A well-executed migration with proper redirects and consistent content usually recovers within 4–8 weeks. A migration with missing redirects, slow speed, or broken content can produce longer-lasting drops that take months to recover from.
Do we need an SEO specialist for a migration?
If you have meaningful organic traffic, yes. Someone who understands technical SEO should be involved in planning the URL mapping and redirect strategy. If your site is new and you have minimal organic traffic to protect, the stakes are lower and a careful developer can handle it.
What should we monitor in the weeks after launch?
GA4 traffic (especially organic), Google Search Console crawl errors and indexing status, Core Web Vitals, and conversion rates for your key conversion paths. Set up alerts if you can. The issues that need fixing usually surface in the first two weeks.
If you're planning a migration and want a second pair of eyes on your checklist, we're here.
