Moving from Webflow, WordPress or Framer is mostly a planning job. Most of the risk sits in the week before launch, not on launch day. This is the checklist we run on every move.
Before you start
A migration has one job: the new site should be better than the old one without losing anything the old one earned. That means search rankings, links other sites point to, form submissions, and the small details your customers rely on, like a booking link in an old email.
Almost every problem we see after a migration comes from something nobody wrote down. So the first step is always an inventory of what exists today.
The do’s
1. Crawl the old site and list every URL
Pages, blog posts, CMS items, PDFs and images that rank in search. Export what Google Search Console says is getting traffic so you know which pages matter most.
2. Map a 301 redirect for each one
Every old URL points to its closest new match, one to one. Keep the URL the same where you can. The fewest redirects is the best outcome.
3. Carry the SEO details across
Page titles, meta descriptions, headings, image alt text and structured data. These are easy to lose when content is moved by copy and paste.
4. Record a baseline
Note your current speed scores, top search queries and monthly enquiries. Without a before, nobody can say whether the after is better.
5. Agree a content freeze
Pick a date after which nobody edits the old site. Changes made during the move are the ones that quietly go missing.
6. Test every form and integration on staging
Contact forms, CRM connections, booking tools, analytics and cookie settings. Submit each form and confirm the email or record actually arrives.
A good migration is one your customers never notice. A great one is where they notice it’s faster.
The don’ts
| Don’t | Do this instead |
|---|---|
| Redirect every old page to the homepage | Send each page to its closest match. Search engines treat mass homepage redirects much like missing pages. |
| Leave the staging site open to search engines | Block indexing on staging, then remove that block on launch. Forgetting the second half is common. |
| Launch on a Friday afternoon | Go live early in the week, when people are around to fix anything that comes up. |
| Change DNS without preparing it | Lower the DNS TTL a day or two ahead so the switch takes minutes, not hours. |
| Cancel the old hosting on launch day | Keep it for a few weeks. It is your backup and your reference if something was missed. |
| Rewrite every page at the same time | Change as little copy on top pages as you can at launch. Improve it once traffic has settled. |
Launch-day checklist
- Point DNS to the new site and confirm HTTPS works
- Remove the noindex setting from the live site
- Spot-check twenty old URLs, including your top pages
- Submit the new sitemap in Google Search Console
- Send a real enquiry through every form
- Check analytics is recording visits
The first four weeks
Rankings often move a little in the first weeks while search engines recrawl. That is normal. What you are watching for is anything that does not recover: pages reporting 404 errors in Search Console, a drop in enquiries, or a top page slipping and staying down.
We check Search Console weekly for the first month and fix any missed redirects as they appear. After that, the old hosting can go.
If you are planning a move and want a second opinion on the plan, we are happy to look at it.