Skip to content

Webflow

The 28-Point Webflow Site Migration Checklist (WordPress, Divi, Elementor & Wix)

Siddik

This is the checklist I work through when a site moves to Webflow, whether it's coming from WordPress with Elementor or Divi on top, or from Wix. It's the short version of my full WordPress migration guide: no explanations, just the 28 checks that decide whether you keep your rankings on cutover day.

Tick items as you go. Progress is saved in your browser, so you can close the tab and pick up where you left off. If you're hiring someone for the migration, it doubles as a list of what to ask them.

Want the reasoning behind each step? Read the full WordPress to Webflow guide

Interactive checklist

The 28-point Webflow migration checklist

Tick items as you go. Your progress stays in this browser, so you can come back to it.

0 / 28 completed · Not ready for DNS cutover yet

  1. Phase 1: Pre-migration crawl & benchmark0 / 7

    Record everything that exists and everything that currently earns traffic, before anything changes.

  2. Phase 2: CMS cleanup & Divi / Elementor / Wix trap removal0 / 7

    Get the content clean before it goes into the Webflow CMS, not after.

  3. Phase 3: 301 wildcard redirects & staging QA0 / 7

    Every old URL gets a home, and the staging site is checked like it's already live.

  4. Phase 4: DNS cutover & post-launch monitoring0 / 7

    Switch with a rollback plan, then watch Search Console closely for the first weeks.

Checked fewer than 20 boxes? Don’t risk your rankings on cutover day. Have me run your migration in 5–10 business days, or book a $250 48-hour redirect & staging audit.

Book the $250 48-hr auditHave me run the migration

Elementor and Divi to Webflow: the traps

A page builder on WordPress hides most of the mess until you export. The content looks fine on the live site because the builder renders it; the export gives you the raw material underneath.

  • Divi and WPBakery content comes out wrapped in shortcodes like [et_pb_section] and [vc_row]. Imported as-is, they show up as literal text in Webflow.
  • Elementor stores layout in its own data, so exported post bodies come with elementor- wrapper divs, inline styles and hard-coded font sizes that fight your Webflow typography.
  • Theme Builder headers, footers and archive templates don't export at all. They get rebuilt in Webflow, not migrated.
  • Images live under /wp-content/uploads/ and keep pointing there after import. They break the day the old hosting is cancelled.
  • WordPress URLs end in a trailing slash and often sit at the root (/post-name/). Webflow CMS items live under their collection (/blog/post-name), so posts need 301s.
  • Plain permalinks (?p=123, ?page_id=45) and /amp/ versions sometimes still have backlinks. Check the backlink export before deciding they can go.

Wix to Webflow: the traps

Wix is simpler to export from in one way (there are fewer layers) and harder in another: there is no full content export, so blog posts usually come out through the RSS feed or a scraper and get cleaned into a CSV.

  • Wix blog posts live under /post/post-name. One wildcard rule, /post/(.*) to /blog/%1, covers them, as long as the slugs stay the same.
  • Blog category and tag pages (/blog/categories/…, /blog/tags/…) and paginated lists need either their own Webflow pages or redirects to the blog.
  • Duplicated Wix pages often carry slugs like /copy-of-services. Find them in the crawl and redirect them to the real page.
  • Images are served from static.wixstatic.com with long generated file names. Re-host them in Webflow and write proper alt text while you're there; Wix exports rarely include it.
  • Store pages (/product-page/…) and member areas don't have a direct Webflow equivalent. Decide early whether they move to Webflow Ecommerce, a third-party tool, or stay where they are.
Where URLs and content break when moving to Webflow, by source platform
What breaksWordPress (Elementor / Divi)WixFix in Webflow
Blog post URLs/post-name/ at the root, or /2023/05/post-name//post/post-namePosts collection at /blog/[slug], plus a wildcard 301
Post body markupShortcodes, elementor- wrappers, inline stylesMostly clean, but from RSS or a scraperClean HTML into the Rich Text field before import
Images/wp-content/uploads/…static.wixstatic.com/…Re-hosted in Webflow, with alt text
Archive pages/category/, /tag/, /author/, /page/2//blog/categories/, /blog/tags/Category collection pages, or 301s to the blog
SEO fieldsYoast / Rank Math title and descriptionWix SEO settings per pageCMS fields mapped to the page SEO settings

Common questions about Webflow site migration

What should a Webflow migration checklist include?

Four stages: a full crawl and benchmark of the old site, a content cleanup before import, a complete 301 redirect map tested on staging, and a monitored DNS cutover. Most ranking losses come from skipping the first and third stages, not from the design.

Can I move from Wix to Webflow without losing SEO?

Yes, if every old URL gets a home. Wix blog posts sit under /post/, so a single wildcard rule (/post/(.*) to /blog/%1) handles them; pages, category lists and any duplicated /copy-of- pages need their own redirects.

Is it hard to move from Elementor or Divi to Webflow?

The design is rebuilt rather than moved, which is usually the point of the switch. The work is in the content: stripping builder shortcodes and inline styles from every post so it imports as clean HTML.

How long does a Webflow site migration take?

For most marketing sites, 5–10 business days. Sites with hundreds of CMS items, custom post types or a store take 2–3 weeks, mostly because of content cleanup and redirect testing.

Rather hand it off? See how I run Webflow migrations

Still deciding whether to move? Webflow vs WordPress, compared

All articles