Migrate your site from Wix to Webflow

Learn how to rebuild your existing Wix site in Webflow.

This article walks you through migrating an existing Wix site to Webflow. While Wix makes it fast to launch a site, its drag-and-drop editor can limit how much control you have over layout, code, and performance. Webflow gives designers, marketers, and developers a single platform to build production-quality sites without those constraints.

High-level instructions:

1. Complete the pre-migration audit checklist

2. Re-build your site and re-configure all site settings in Webflow

3. Lastly, set up your domains, redirects and DNS settings to minimize downtime

Pre-migration audit checklist

Before you begin rebuilding in Webflow, perform a thorough audit of your current Wix setup. Check out Wix's help pages for detailed steps.

Pages

• Inventory all static, dynamic, and custom member pages (including main pages, CMS pages, signup and login pages, and error pages)

• Note current URL paths, page hierarchy, and any subdomain or language-based paths (e.g., /es/, /fr-CA/)

• Note all page transitions or animations

CMS, data, and assets

• List all content types (e.g., blog posts, portfolio items, products)

• Export your CMS collections from Wix. You can use these exports to help populate your Webflow CMS.

• Export your store products if applicable. Note that exporting digital products isn't currently supported.

• Blog posts can't be exported to other platforms from Wix. You'll need to manually copy blog content or reference your live site during the rebuild.

• Wix doesn't currently allow exporting all media files at once. You can download images individually from the Media Manager.

• Note current asset libraries (i.e., images, videos, downloads) including file names, asset locations, alt text, and any versioning or large asset usage

Fonts and typography

• Audit all fonts used in your Wix site, including any custom fonts you've uploaded

• Confirm that you have the appropriate licenses to use each font in Webflow. Fonts available through Wix are licensed for digital use only within your Wix site, so you'll need to source those fonts separately for use in Webflow.

• Document font sizes, line heights, letter spacing, and responsive typography rules so you can accurately rebuild your type system in Webflow

Domains

• Identify your primary domain and any additional domains or subdomains in use

• Document domain-level routing needs for locales (e.g., es.domain.com)

• Note whether your domain is registered through Wix or a third-party registrar. Webflow isn't a domain registrar, so you can't transfer a domain to Webflow — you'll connect it by updating DNS records with your current registrar. If your domain is registered through Wix, you have two options: keep it at Wix and update the DNS records there to point to Webflow, or transfer it away from Wix to a third-party registrar first. Either way, before connecting to Webflow you'll need to reset your DNS settings, like removing existing A records on the root domain and CNAME records on the www subdomain, to avoid conflicts. Prepare connect your domain to Webflow.

• To minimize downtime during cutover, lower your TTL to the lowest available value (typically 30 seconds) at least one full TTL period before making DNS changes. For example, if your current TTL is 24 hours, reduce it 24 hours in advance.

SEO and redirects

• Create a list of all current URLs with their meta titles, meta descriptions, Open Graph tags, and canonical tags

• Note any existing redirects, SEO settings for different locales, and schema data

• Document your robots.txt rules and any pages excluded from your sitemap

• Document your analytics and tracking setup (Google Analytics, Google Search Console, tag manager, etc.)

• For multilingual pages, document your current hreflang implementation

Forms, integrations, and custom code

• List all forms

• Note any Wix apps installed on your site, embedded tools, analytics, scripts, and third-party widgets

• List all custom code snippets embedded in your site (in the head, body, or footer)

• Note any dynamic behavior built with Velo by Wix or external APIs

Global sections, layouts, and interactions

• Identify global sections (e.g., headers, footers, cards, announcement bars, promotional pop-ups)

• Record reusable layout patterns

• Note interactive elements: hover states, animations, and any custom code embeds

Process and performance

• Plan your DNS cutover (i.e., changing your DNS settings from Wix to Webflow), staging workflows, and publishing window. You’ll want to migrate DNS only after you've completed all other migration steps and you're ready to publish, to minimize site downtime.

• Document existing performance or SEO issues you want to address during migration (e.g., large image files, slow scripts)

Set up your Webflow site

Once you’ve completed your audit and planning, you can start building the foundation in Webflow.

1. Create a new site in your Webflow Workspace

2. Choose the right Site plan based on traffic, CMS scale, and localization needs

3. In Site settings > Localization, set your primary locale and additional locales (if needed). Decide on your URL strategy (subdirectory vs subdomain vs separate domain).

4. Create a CMS architecture that maps to your Framer content structure

5. Build your global style guide: define color palette, typography, spacing, utility classes, and reusable components

6. Set up integrations, forms and custom code embeds

Migrate content and structure

Now you’re ready to move content and build the new site in Webflow.

1. Rebuild each static page in Webflow, matching layouts and responsive behavior

2. Create CMS Collections and import content via CSV or manually

3. Upload and organize assets in the Webflow Asset panel: images, videos, downloads, icons. Ensure every image has alt‑text and is optimized (compressed, correct format)

4. For each locale:

   • Duplicate or set up localized variants of pages and CMS items. Use Webflow’s built-in machine translation to accelerate localization, then review and refine translations manually to ensure accuracy and brand consistency.

   • Ensure slugs, meta tags (title/description), and asset alt‑text are localized

   • Configure localized SEO settings including titles, descriptions, Open Graph data

5. Rebuild or adapt interactions using Webflow’s native animation tools. Some Framer animations may not translate directly to Webflow and may require redesigning interactions using Webflow Interactions with GSAP or custom code.

6. Re‑implement global components (navigation, footer, banners, callouts)

7. Re-build forms and integrate with tools (e.g., Zapier, HubSpot) as needed

8. Configure analytics: Ensure tracking scripts and tag managers are placed in Site settings → Custom code or page settings as needed.

9. Use the Audit panel to optimize SEO and accessibility

10. Publish your staging version and run a full QA across breakpoints and locales

11. In Site settings > Publishing, add your custom domain, subdomain(s), and configure DNS

Redirects, SEO, and publishing

To preserve rankings and prevent 404s:

• Set up 301 redirects under Site settings > Publishing > 301 redirects

  • For bulk changes, import redirects via CSV

• Enable sitemap and robots.txt configuration

• Check localized SEO and routing behavior

• Set canonical tags for all duplicate pages

• Configure your custom domain(s) via your DNS provider and Webflow’s hosting settings and verify SSL and default domain to avoid duplicate content issues

Once ready:

• Push your site live and monitor in Google Search Console

• Verify that your localized versions are indexed properly

• Test locale switching, redirects, and canonical structure

• Submit your new sitemap (if changed) to Google Search Console and other search engines, then monitor for indexing errors or 404 spikes

After launch: what to monitor

Post-launch, monitor the following:

• Traffic and search engine indexing

• Redirects and crawl errors

• Form submissions and conversion metrics

• SEO metrics by locale and landing page

• Load times and core web vitals

• Locale switching functionality