Migration sequence
Nothing leaves Wix automatically
Each stage recovers something Wix would otherwise lose on its own.- InventoryDocument every page and setting
Wix has no full HTML or CMS export to lean on.
- CMSMap repeaters to Collections
Blog posts, products, and listings become structured content.
- SEORebuild metadata by hand
Wix's automatic SEO Wiz settings don't transfer.
- RedirectsMap every live URL
Wix URLs rarely match a clean Webflow structure.
- CutoverTest, then move the domain
Forms, apps, and DNS verified before launch.
Export everything Wix will actually let you export
Wix does not offer a full HTML, CSS, or CMS export. Content, design, and code stay inside the Wix Editor, so the starting point is a manual, page-by-page inventory rather than a file download.
Document every page, its content blocks, and any custom code added through Velo or a third-party embed. Download media assets at their original resolution before the account access changes.
- Full page and content inventory, built by hand
- Per-page SEO titles, descriptions, and alt text recorded
- Velo and custom code embeds documented
- Media assets downloaded at original resolution
Decide what becomes Webflow CMS instead of static pages
Wix Blog posts, Wix Stores products, and Wix Bookings services are repeater-driven content, not one-off pages. Each of these maps to a Webflow Collection, and the field structure should be planned before any template is built.
Dynamic Wix pages built from repeaters are the clearest signal that a Collection is needed. Static, one-off pages can stay as regular Webflow pages.
- Blog posts, products, or listings mapped to CMS collections
- Custom fields and categories planned before templates are built
- Author, tag, and category structure decided
- Repeater-driven Wix pages identified for CMS conversion
Rebuild Wix's SEO settings deliberately, not automatically
Wix's SEO Wiz generates some metadata and sitemap entries automatically. None of that configuration transfers, so meta titles, descriptions, and structured data need to be recreated directly in Webflow.
Compare the old Wix sitemap against the new Webflow sitemap before launch. Pages that quietly existed only because Wix auto-generated them are easy to miss otherwise.
- Meta titles and descriptions recreated for every indexable page
- Structured data rebuilt where Wix applied it automatically
- Canonical URLs and XML sitemap configured in Webflow
- Old Wix sitemap compared against the new one before launch
Map every Wix URL and prepare redirects
Wix URL patterns, including auto-generated blog and member-page slugs, rarely match a clean Webflow structure. Once the domain leaves Wix hosting, Wix can no longer serve redirects for its old URLs, so the map has to be built and tested on the Webflow side first.
Treat every live URL as needing an explicit destination. A blanket redirect to the homepage loses the ranking and relevance signal a specific page carried.
- Every live Wix URL inventoried with its current status
- Each URL mapped to its closest Webflow destination
- 301 redirects configured and tested in Webflow before DNS changes
- Wix-generated URLs such as checkout, cart, and member pages accounted for
Test forms, integrations, and the domain cutover
Wix Forms, Wix Bookings, Wix Stores checkout, and connected apps such as email marketing tools all need to be rebuilt in Webflow-compatible form and tested with real submissions before launch.
Confirm the DNS and domain transfer plan ahead of time, including who holds registrar access, so the cutover happens in a single planned window rather than an extended partial outage.
- Forms rebuilt and tested with real submissions
- Connected apps and integrations reconnected in the new system
- DNS and domain transfer plan confirmed before cutover
- Post-launch crawl and indexing check scheduled