Moving a website feels like moving house with the furniture on fire. One wrong step — a missed redirect, a DNS change at the wrong hour, a staging site left indexable — and months of SEO work evaporates overnight. A proper website migration is not complicated, but it is unforgiving. Every step has to happen in the right order.
This guide covers all three kinds of migration — new host, new domain, and new CMS — with a complete pre-launch checklist, the redirect strategy that preserves your rankings, a move-day process, and a 30-day monitoring plan. Follow it in order and your traffic won’t even notice you moved.
The three kinds of website migration
Not all moves are equal. A hosting migration — same domain, same site, new server — is the safest kind. Done right, visitors and Google see zero change. A domain migration — moving from oldsite.com to newsite.com — is riskier because every URL changes and Google has to relearn your entire site. A CMS or platform migration — WordPress to Shopify, for example — is the riskiest of all, because URLs, page structure, and content can all change at once.
Many projects combine two or three of these. A rebrand that changes the domain, the platform, and the design simultaneously is three migrations stacked on top of each other. If you can, split them: move the host first, wait a month, then change the CMS, then the domain. Each isolated move is easy to diagnose. Combined moves make it impossible to know what broke. If your move is driven by performance problems, check our why your website is slow guide first — sometimes the fix is cheaper than the move.
Before you move: the pre-migration checklist
Preparation is 80 percent of a successful migration. Start with a full backup of files and database, stored somewhere you control — not just on the host you’re leaving. Then crawl your current site with a tool like Screaming Frog and export every URL, its status code, its title, and its traffic. This URL inventory becomes your redirect map and your post-launch comparison baseline.
Record your benchmarks too: rankings for your top 20 keywords, organic traffic for the last 90 days, page speed scores, and indexed page counts from Search Console. Without “before” numbers you can’t prove the migration worked — or diagnose what didn’t. Set up the new environment and test everything on a staging URL blocked from search engines (password-protect it; a noindex tag alone is not enough). Lower your DNS TTL to 300 seconds at least 24 hours before the move so the switch propagates fast. Finally, schedule the move for your lowest-traffic window — usually a weekend night — and have a rollback plan: know exactly how you’d revert if something breaks.

Redirects: the part that saves your rankings
Redirects are the single most important technical piece of any migration. Every old URL that earned traffic, links, or rankings must 301-redirect to its closest equivalent on the new site — not to the homepage. Redirecting everything to the homepage is a soft 404 in Google’s eyes, and it bleeds ranking power.
Build your redirect map from the URL inventory: old URL in the left column, new URL in the right. One-to-one where pages still exist, closest-match where they’ve merged, and a proper 404 page for genuinely dead content. Implement with server-level 301 redirects (in .htaccess, nginx config, or your CDN) — never JavaScript redirects, which Google may not follow. Avoid redirect chains (A to B to C); every hop loses a little authority. Test every redirect before launch with a crawler, and keep the old domain’s redirects live for at least 12 months — a year is the safe minimum for link equity to fully transfer.

Move day: the step-by-step process
On move day, work through this sequence and don’t skip steps. First, put up a brief maintenance notice if the site takes transactions — then take a final fresh backup. Deploy the site to the new host or publish the new domain, and immediately verify the redirects are live by testing a sample of old URLs. Update the DNS to point at the new server.
Once DNS propagates, walk the new site like a customer: homepage, key landing pages, checkout or contact forms, and the mobile view. Check that analytics, Search Console, and conversion tracking are firing on the new property. Don’t forget the SSL certificate — the new host must serve every page over HTTPS before you flip the switch, or browsers will flash security warnings that tank trust and rankings on day one. In Search Console, use the Change of Address tool for domain moves, and submit the new XML sitemap. Update your most valuable external links where you control them — social profiles, directory listings, partner pages. Then monitor Search Console’s crawl stats and coverage report daily for the first week; a spike in 404s or excluded pages tells you exactly where to look.
After launch: the 30-day monitoring window
A migration isn’t done at launch — it’s done when the numbers stabilize. For the first week, check daily: Search Console coverage errors, server response codes, and traffic in analytics. A 10 to 15 percent traffic dip in week one is normal while Google recrawls; a 40 percent cliff is not, and means something structural broke.
Weeks two through four: compare rankings for your tracked keywords against the pre-migration baseline, watch indexed page counts recover toward their old levels, and review server logs for URLs getting unexpected 404s — each one is a redirect you missed. If you changed domains, update your Google Business Profile, social bios, and key directory listings to the new URL so local and referral traffic follows you. Keep the old hosting active for at least a month as insurance. By day 30, traffic and rankings should be at or near pre-move levels. If they’re not, don’t wait and hope — diagnose with the crawl data and fix it. Hope is not a migration strategy.
The mistakes that cost people their traffic
The classics, in order of damage: launching the new site without any redirects; blocking the new site with robots.txt or noindex and forgetting to remove it; changing URL structure and content simultaneously so nothing matches; letting the staging site get indexed, creating duplicate content; and migrating during peak season. Each of these has destroyed real businesses’ traffic for months.
Subtler killers: losing meta titles and descriptions in a CMS move (new platforms often auto-generate worse ones), dropping structured data, breaking internal links so authority stops flowing, and forgetting hreflang on multilingual sites. The pattern behind every one of these is the same — no checklist, no crawl comparison, no baseline. Migrations don’t fail because they’re technically hard. They fail because someone skipped the boring verification steps.
When to hire help (and what it should cost)
A simple host-to-host move with identical URLs is genuinely DIY-able if you’re comfortable with DNS and backups. Hire help when the domain changes, the CMS changes, the site has hundreds of pages, or the business depends on organic traffic for revenue. That’s when a missed redirect costs real money.
A professional migration for a small business site typically runs $500 to $2,000 depending on size and complexity — a fraction of what lost rankings cost. Ask any provider for their process: they should mention a URL inventory, redirect mapping, staging tests, and post-launch monitoring. If their plan is “we’ll move the files over the weekend,” keep looking. At Vibstack we handle migrations with the full checklist above, and our SEO team monitors rankings through the 30-day window. Get a fixed quote before you move — it’s cheaper than fixing a broken one after.
Frequently asked questions
Will a website migration hurt my SEO rankings?
It doesn’t have to. With proper 301 redirects, preserved content and metadata, and post-launch monitoring, most sites recover fully within 30 days. Rankings drop when redirects are missed, URLs change without mapping, or the new site gets accidentally blocked from indexing.
How long should I keep 301 redirects after a website migration?
Keep them live for at least 12 months. Google needs time to transfer ranking signals and link equity to the new URLs, and old backlinks from other sites will keep sending visitors to the old addresses for years. A year is the safe minimum.
What is the biggest mistake in a website migration?
Launching without a redirect map. Every old URL with traffic or backlinks must 301-redirect to its closest new equivalent — never bulk-redirect everything to the homepage. The second biggest mistake is forgetting to remove a noindex tag or robots.txt block on the new site.
Should I change my domain and redesign at the same time?
Avoid it if you can. Each change — new host, new CMS, new domain, new design — is its own migration with its own risks. Stack them and you can’t tell what broke. Space them at least a month apart so each move can be verified independently.
How do I check if my website migration worked?
Compare against your pre-migration baseline: keyword rankings, organic traffic, indexed page counts, and page speed. Watch Search Console daily for crawl errors and 404 spikes in the first week. By day 30, traffic and rankings should be at or near their old levels.
Can I migrate my website myself?
A simple move to a new host with identical URLs is DIY-able if you’re comfortable with DNS and backups. Hire a professional when the domain or CMS changes, the site is large, or your revenue depends on organic traffic — that’s when mistakes get expensive.
Like what you just read?
Tell us about your project and get a clear, fixed quote within 24 hours — free, no obligation.
Get a free quote →