Switch From Wix to Webflow: Migration Steps and Gotchas

There is no one-click way to move a Wix site to Webflow. This guide covers the CSV export, rebuild, CMS import, redirects and gotchas to avoid.

By Galactic News Editorial · Published 2026-11-12T16:28:49+00:00 · Updated 2026-11-12T16:28:49+00:00

Switch from Wix to Webflow migration steps guide

To switch from Wix to Webflow is a rebuild, not a transfer. There is no one-click import that moves a whole site across. The old platform is closed, with no full-site export. The new one gives you a blank canvas and a powerful CMS. The move works well if you plan it in stages: audit, export, rebuild, import, redirect and launch. This guide walks through each step and flags the gotchas that catch most people.

Budget a few days for a small site and a few weeks for a large one. The design must be recreated by hand. Content can move by CSV. Your search rankings survive only if you set up redirects. Read the whole guide before you start.

How to switch from Wix to Webflow: the honest overview

Here is what moves and what does not. Your text, images and blog posts can move. Your design, animations and Wix apps cannot. The old platform does not let you export source code. The new one has no direct importer for it. Every page layout must be rebuilt in the Designer.

That sounds worse than it is. A rebuild is also a chance to fix a messy site. Most older sites carry years of unused pages and outdated content. The migration forces a cleanup. The result is usually a faster, cleaner site.

Site plans start free on a webflow.io subdomain. A custom domain needs a paid plan. Basic costs $15 a month billed yearly and suits simple sites without a CMS. Premium costs $25 a month billed yearly and adds the CMS. Pick the plan after you know how many CMS items you need.

Step 1: Audit your old site

List every page on your old site. Use your sitemap and your analytics. Note which pages get traffic and which get none. Delete pages nobody visits. Keep the pages that rank or convert.

Record the URL of every page you keep. You will need this list for redirects later. Also list every blog post, product and form. Note which Wix apps you use, such as bookings, stores or member areas. The new platform has no direct replacement for every one of them. Check each one before you commit.

Export your analytics data too. Download your top landing pages from Google Search Console. A sitemap can miss pages that still receive traffic or backlinks. Your analytics list is the safety net.

Step 2: Export your content

The old platform lets you export some structured content as CSV. CMS collections can usually be exported this way. Blog posts are the exception: Wix says it is not currently possible to export them to other platforms, so copy posts by hand or test an RSS feed. Export each collection separately. Check the file for data quality before you go further. Fix broken dates, missing images and empty fields in a spreadsheet first.

Images need public URLs. The new platform cannot import images from local file paths. During a CSV import, it downloads images from the URLs in the file and stores them on its own CDN. Make sure every image URL is public and reachable.

Static page content does not export cleanly. Plan to copy text and images for regular pages by hand. Download your media library too, so you have originals for the rebuild.

One warning: importing content into a collection can overwrite existing items. Back up any content already in the receiving collection. If you need to keep existing items there, merge the two sets in a spreadsheet before importing.

Step 3: Rebuild the site

Create a new project in your dashboard. Start blank or pick a template. Set up your main pages first: Home, About, Services, Contact and any others in your audit. Match the page structure of the old site where it makes sense.

Build your CMS collections before importing anything. A blog needs a collection with fields for name, body, image and date. You cannot create a collection during an import. The structure must exist first, so each CSV column has a field waiting for it.

Keep each item's slug the same as its old URL ending where possible. That keeps your URLs stable and makes redirects simpler. Put body content in as HTML so headings, links and lists survive the import.

The free Starter site plan gives you a webflow.io domain, 2 static pages and 1 GB of bandwidth. That is enough to start building. Upgrade to a paid plan when you are ready to connect a custom domain and publish.

Step 4: Import your content into the CMS

Open the collection, go to Settings, then Import. Upload your CSV file. Map each column onto a collection field. Map body text onto a rich text field. Map image URLs onto image fields. The importer shows errors if a row does not line up, so you can fix the file and re-import.

The importer handles up to 10,000 items per CSV. For larger imports, split the file or use the CMS API. The API suits recurring syncs and imports above 10,000 items. Third-party tools like Whalesync can sync content from Airtable, Notion or HubSpot.

Import reference fields first. Categories and authors should go in before the posts that link to them. That lets the platform connect the references automatically instead of forcing manual data entry.

Check every imported item after the import. Look at images, dates and formatting. Small errors are normal. Fix them now, while the old site is still live for comparison.

Step 5: Set up 301 redirects

Redirects protect your search rankings. Open Site settings, go to Publishing and find the 301 redirects section. Add a rule for every old URL that changed. You can import redirects in bulk with a CSV file.

One caution: importing a CSV of redirects replaces your existing redirect list. Export the current list first if you already have redirects in place. Then merge and re-import.

Test the redirects on the staging domain before launch. Click through your most important old URLs. Each one should land on the right new page. A missing redirect means a 404 and lost rankings.

Step 6: Rebuild forms, SEO settings and integrations

Forms do not migrate. Rebuild each form in the new builder. The Starter plan allows 50 form submissions. Paid plans allow unlimited submissions. Connect forms to your email tool or CRM before launch.

Copy your page titles and meta descriptions from the old site. Set them in the new platform's page settings. Add your analytics and tracking codes. Reconnect any tools you used, such as email marketing or booking software. It integrates with tools like HubSpot Forms and Marketo through embeds and third-party services.

Check your site on mobile. Designs here are responsive, but a rebuild can introduce layout problems on small screens. Test every page type on a phone before you publish.

Step 7: Launch and cancel the old plan

Point your domain at the new site when it is ready. The publishing settings guide you through the DNS change. Wait for the DNS to propagate, then test the live site on your real domain.

Keep your old site active for at least a month after launch. That gives you a fallback if something breaks. It also keeps your old redirects working while search engines update. Cancel the old plan only when the new site has run cleanly for several weeks.

Watch your analytics after launch. Check for 404 errors in Search Console. Fix any missed redirects in the first week. Most ranking dips after a migration trace back to a redirect that was never added.

Common gotchas in a Wix to Webflow move

Bottom line

Switch from Wix to Webflow and you face a rebuild with a content import, not a one-click move. Audit first, export your content as CSV, rebuild the design and collections in the new platform, import, redirect and then launch. The work pays off in a faster site with full design control and clean code export. Start on the free plan, build the new site alongside the old one, and cancel the old plan only after the new site has proven itself live.