Jump to
Oct 08, 2025
The complete website migration checklist: a step-by-step guide
Moving a website is like moving house. You think it is boxes and tape until you notice the Wi-Fi password is gone, the fridge will not fit through the door, and the cat is somewhere under the sofa refusing to negotiate. A sloppy move costs you rankings, broken links, and a queue of irritated customers. A proper checklist is the difference, one that covers every step rather than the popular method of crossing your fingers and pressing go.
This walks through the steps in order, so a migration does not wreck your traffic, flatten your SEO, or turn launch day into something you tell people about years later in a bad way.
Plan before you touch anything
Planning is not the exciting part, and skipping it is how a project quietly goes wrong. Before a single file moves, settle five things.
Define the scope. Be specific about what is actually changing, the domain, the hosting, the CMS, the URL structure, or all of it at once. A domain change and a CMS change are different projects with different risks, and pretending they are one is how things slip.
Set the goal. Faster load times, a better design, a platform that holds up under traffic, name it, because the goal decides what you test later.
Assign the roles. One person owns the redirects, one owns the content, one watches the SEO. Vague ownership is how the redirect map ends up being nobody’s job until launch morning.
Benchmark the numbers. Write down current traffic, conversions, and rankings now. After launch, those numbers are the only way to tell a normal dip from a real problem.
Audit the site. Crawl every page, image, and link, so you know exactly what you are moving and what can quietly be left behind.
Prepare the new environment
You would not move furniture into a half-built house, so prepare the new home before the switch.
Get the hosting and server ready to actually serve pages, under real load, not just in theory. Build a staging site, a private copy of the new build, and block search engines from it with a noindex so Google never indexes your test kitchen. Take a full backup, database and files, before anything happens. Build the redirect map, every old URL pointed at its new home, because a migration without redirects is a house move with no forwarding address. And check the SSL certificate is valid, the canonical tags are tidy, and robots.txt is not quietly blocking something it should not.
The prep is dull. It is also what stands between you and a launch-day scramble.
Test before launch
This is the rehearsal. You do not invite guests until you know the oven works.
Test every function a user can touch, forms, logins, checkout, popups. Compare the layouts side by side on mobile and desktop, not just on the screen you happen to design on. Measure performance, Core Web Vitals in particular, since that is roughly how Google judges whether a site feels fast or sluggish. And confirm the SEO essentials survived the move, meta titles, descriptions, schema, hreflang, canonical tags. Test it the way your most pedantic QA person would, because your visitors will be far less forgiving and far less patient.
Launch day
Launch day is less champagne and confetti, more caffeine and a spreadsheet. The list is short and every line matters.
Switch the DNS to point the domain at the new server. Activate the redirects, then test the top fifty pages by hand rather than trusting that the map is fine. Remove the staging noindex so search engines can finally crawl the real site, the single most common way a migration silently disappears from Google. Submit fresh sitemaps in Google Search Console. And watch the server logs for 404s, server errors, and crawl problems as they happen, not a week later.
Monitor after the move
The site is live, which feels like the finish line and is not. Migration hangovers are real, and they show up in the weeks after, not on launch day.
Compare traffic, rankings, and conversions against the benchmarks you wrote down. Crawl the site again for missing pages, broken links, and duplicate content. Clean up redirect chains and loops before they tangle into something slow and hard to read. Clear out legacy files, since old assets eat server space and confuse crawlers. And keep the backups within reach, so a rollback is an option and not a panic.
The pitfalls that catch people
Most migration disasters are predictable, which is the good news. Forgetting redirects sends traffic off a cliff. Leaving the staging noindex live means search engines cannot find the new site at all. Missing assets break images and layouts. Unplanned downtime makes customers think you have closed. Ignoring performance gives you a beautiful new site that loads like it is 2009. Every one of these is on the checklist above, which is rather the point of having one.
How Studio Ubique handles it
Studio Ubique has migrated sites ranging from small local businesses to multilingual platforms with thousands of pages. There is no secret to it, only process: plan, stage, test, and monitor, with clear ownership at every step. We hold to a performance budget so the new site does not arrive bloated, and we keep UX and SEO in view throughout so the traffic you worked for does not leak away in the move.
If a move is on your mind, our website migration support is the place to start.
A solid checklist is the whole job
A good migration checklist is the moving truck, the packing list, and the GPS in one. Without it, you lose visitors, rankings, and sleep. With it, the move is calm, and you might even enjoy parts of it.
FAQs
Q. What is website migration
Moving a site to a new domain, host, CMS, or structure while keeping the design, content, and SEO intact. The word covers anything from a hosting change to a full rebuild.
Q. How long does a migration take
A few days for a small site, several weeks for a large or complex one. The variables are page count, how many systems change at once, and how clean the existing site is.
Q. Will I lose SEO when migrating
A short dip is common in the first weeks. Careful redirects and thorough checks are what protect the long-term rankings, and a planned migration usually recovers quickly.
Q. Do I need a staging environment
Yes. Staging is the test kitchen, the place to find the broken things before real visitors do. Skipping it means launching straight to your audience and hoping.
Q. What kind of downtime should I expect
Done properly, downtime is minutes, and often invisible to most visitors. A DNS switch handled well is not something your customers should ever notice.
Takeaway: preparation, testing, and redirects keep your SEO and users safe.
