WordPress or Wix to Webflow: What a Migration Really Involves
Moving a website is a lot like moving apartments. The furniture is the easy part. It's the forwarding address everybody forgets.
If you're still deciding whether to switch, we covered the why in Should I Migrate My WordPress Website to Webflow? This post is about the how: what really happens between "let's do it" and launch day, and the parts most people don't see coming.
Step 1: Take inventory of everything
Before we touch a pixel, we list every page, post, image, form and file on your current site, plus every URL that still gets traffic. Sites collect stuff over the years. That landing page from an old promotion might still be pulling visitors from an email nobody remembers sending, and you only find out when it breaks.
Step 2: Decide what moves, what changes and what retires
A migration is the perfect excuse to clean house. Some pages move as they are, some get merged, and some get a respectful farewell. Your team decides with us, because it's your content.
Step 3: Get the content out
This is where WordPress and Wix part ways.
WordPress is fairly generous. Posts, pages and media can be exported, so blog content usually comes across in bulk, gets cleaned up, and lands in Webflow's CMS.
Wix is less of a sharer. It doesn't offer a simple way to export your whole site to another platform, so content often has to be collected page by page. Not hard, just slower, and worth knowing up front.
Under the hood WordPress can export its content as an XML file and also exposes it through its REST API, which makes scripted imports possible. On the Webflow side, content goes into CMS collections through Webflow's Data API, so a blog with hundreds of posts can be mapped field by field (title, date, author, category, body, featured image) instead of copied by hand. We check the result against the original, because rich text and images are where imports like to get creative.
Step 4: Rebuild the design, properly
We don't copy your old theme. We design the site in Webflow from scratch, with a content system your team can run and with SEO and AEO structure built in from the first page: one clear main heading per page, descriptive titles, image descriptions and structured data.
Step 5: The forwarding addresses
This is the step that protects your search traffic. Every old URL that matters gets pointed at its new home, so Google, your old emails and everyone's bookmarks still land somewhere real instead of a "page not found."
Under the hood These are 301 redirects, the permanent kind, which tell search engines a page has moved for good so its search history follows it. Webflow manages them in site settings, including pattern rules that can move a whole old folder like /blog/ in one line. After launch we test every rule by actually following it, not by trusting the list.
Step 6: Forms, integrations and the little things
Contact forms, newsletter signups, booking widgets, analytics, the tracking pixel someone installed years ago. All of it gets reconnected, tested and pointed at the right inbox.
Step 7: Launch day
We build and test on a staging copy first, so your current site keeps running the whole time. On launch day, your domain gets pointed at Webflow, we run our full set of checks on the live site, and we submit the new sitemap to Google Search Console. Here's how we check a website before it ships.
What it costs, and what comes after
Every migration is scoped to the site, and a custom Webflow build starts at $5,000. Afterward, hosting and care start at $300 a month. If you'd rather hand us the whole technical layer, the full partnership covers the site, SEO and AEO, analytics and more.
One more thing: make sure the new site lives in accounts you own. A migration is the perfect moment to fix that, and we explain why in who actually owns your website.
Thinking about moving? See how our migrations work, or book a free consult and we'll look at your current site together.