A Wix site can look like a collection of pages while behaving like a bundle of separate Wix products. The Blog, Forms, Contacts, Stores, Bookings, Members, Automations, CMS, Inbox, Analytics, multilingual tools, and installed apps may each hold data or rules. A visual review will not reveal which contact fields are populated by a form, which automation sends a confirmation, or whether a members-only page depends on an account role. The first migration task is to uncover that operating system.

Accept that the site design will be rebuilt

Webflow's official Wix migration guidance is explicit: there is no automated conversion for Wix designs, layouts, and interactions. The destination is a fresh Webflow implementation using the current site as one reference, not a code or theme import. That is also an opportunity to avoid carrying forward duplicated sections, desktop-only fixes, obsolete pages, and unclear navigation. It is not a reason to discard useful URLs, copy, evidence, or customer journeys without review.

Preserve deliberatelyReconsider during the rebuild
PagesUseful page purposes, proven copy, authoritative resources, legal information, and valuable URLsDuplicate landing pages, empty service pages, confusing navigation, and sections built only to work around the old editor
BrandApproved logo files, colors, type licenses, photography rights, and recognizable visual assetsInconsistent spacing, text baked into images, inaccessible contrast, and one-off styles
FunctionsCustomer outcome, field requirements, routing, confirmations, schedules, transactions, and recordsAn exact copy of a Wix app when a simpler supported workflow serves the business
Content modelReal entities such as services, people, locations, projects, and resourcesWix collection names or fields that exist only because of an old implementation

Inventory Wix products and export routes

Exports are feature-specific; verify the current Wix documentation and your account.

Wix areaAvailable evidence or exportImportant limitation or next decision
Static pages and designManual page inventory, screenshots, copy and media captureThe Wix layout and design do not import into Webflow
Wix CMSWix documents CSV export for individual CMS CollectionsRelationships, permissions, dynamic-page rules, field behavior, and UTC time values need mapping and testing
Wix BlogPublic pages, feeds or approved capture methods may help inventoryWix states that exporting Wix Blog posts to other platforms is not currently supported; plan careful manual or authorized extraction
Wix FormsSubmission tables can export selected dataRebuild fields, validation, files, contacts, automations, notifications, consent, and destination systems separately
ContactsWix provides contact CSV exportsA contact is not automatically a consenting subscriber or transferable member account; retain consent and source context
Wix StoresProduct list export is available for eligible productsOrders, customers, discounts, tax, shipping, subscriptions, gift cards, and app data need separate plans
Redirect ManagerWix supports redirect CSV exportReconcile those rules with the full old-to-new URL map; remove obsolete chains or conflicts
Third-party or Wix appsApp-specific export, API, vendor report, or screenshotAvailability varies. Replace the business workflow, not the app tile

Keep raw exports unchanged and create working copies for cleanup. Add export date, account, feature, record count, filters, owner, and any known exclusions to a migration register. A successful CSV download does not prove that files, references, consent, payment information, or related records are included. Inspect columns, sample records, and official product notes before choosing the new system. The website redesign and migration library organizes the supporting audits and launch guides, and its complete website migration plan shows how to connect these exports to requirements, acceptance tests, launch, and rollback.

Recover Wix Blog content without pretending there is a clean export

Treat the blog as an editorial recovery project

01

Build the post ledger

List every live post URL, title, publication and update dates, author, categories, tags, featured image, canonical, index setting, internal links, and known performance or lead role. Include drafts or scheduled posts through dashboard review.

02

Choose approved capture methods

Wix currently says Blog posts cannot be exported to other platforms. Use authorized access and methods that preserve content accurately without violating account, privacy, or third-party rights. Manual transfer may be the safest choice for a small library.

03

Clean the content

Remove editor-specific markup, repair headings, replace unsupported embeds, download authorized media, preserve captions and alt text, and update internal URLs. Do not copy comments or personal data without a defined reason and lawful process.

04

Create the Webflow model

Define posts, authors, categories, SEO fields, social image, dates, related content, and any references before import or entry. Decide what happens to tags and archives instead of reproducing them automatically.

05

Verify one post at a time

Compare source and destination content, formatting, images, links, dates, metadata, structured data, canonical, and final URL. Reconcile the ledger before launch.

Do not let the Blog limitation force a rushed decision. A large, active publishing program may make staying on Wix, choosing another CMS, or running a staged content migration more responsible than an immediate move. Ask for a tested extraction plan and error budget before approving production. A Webflow-versus-Wix comparison should weigh this ongoing editorial reality, not only design freedom.

VISUAL CHECKPOINT · RedesignAn app card is not a migration requirement

Trace the human and data flow before selecting a replacement.

Replace Wix apps with named workflows

An app card is not a migration requirementTrace the human and data flow before selecting a replacement.
01Visitor actionSubmit, book, buy, join, chat, search, or download
02RulesValidation, availability, consent, payment, eligibility, routing
03Records and messagesContacts, CRM, orders, notifications, reminders, analytics
04New solutionWebflow feature, integration, specialist service, or retained system
  • For every form, record fields, conditional rules, validation, file handling, spam controls, contact mapping, automations, notifications, thank-you behavior, consent, storage, and retention.
  • For bookings, record services, staff, locations, availability, buffers, capacity, pricing, payments, cancellation, reminders, calendars, time zones, and customer records.
  • For members, record registration, verification, roles, protected resources, profile data, passwords, subscriptions, deletion, and support. Wix notes that site members are not simply moved by exporting contacts.
  • For stores, trace product and variant data, inventory, orders, customers, checkout, payments, tax, shipping, discounts, subscriptions, gift cards, feeds, returns, and accounting.
  • For multilingual sites, inventory locale-specific pages, slugs, metadata, collections, language routing, forms, and third-party widgets. A translation CSV is not a full cross-platform site export.
  • For custom Velo code, identify data collections, permissions, secrets, APIs, scheduled jobs, events, and failure behavior. Webflow custom code is not a drop-in server replacement.

Prototype the hardest workflow before rebuilding every page. If the business depends on recurring bookings, gated programs, complex store behavior, or member roles, a basic mockup cannot prove Webflow fit. A website design partner should document what remains native, what connects to another service, who owns that service, and how staff recover when the connection fails.

Review Wix URL families, not only menu pages.

URL familyQuestions before launchDestination action
Static and dynamic pagesCan Webflow reproduce the path and purpose? Are parameters or dynamic routes in use?Keep the URL or map it to the closest replacement
Blog posts and archivesWhich posts remain, and do category, tag, author, pagination, or feed URLs receive links or traffic?Preserve post slugs where feasible; make explicit archive decisions
Store, booking, event, or member pagesAre these public URLs, app routes, account screens, or transactional states?Recreate only verified flows; redirect public equivalents and do not expose private data
Files and imagesAre assets served from Wix URLs that will disappear? Are rights and source files known?Download authorized originals, upload to the destination, and update links
Existing redirectsDoes Wix Redirect Manager contain active rules, chains, or old campaigns?Export, reconcile, simplify, and implement final one-hop rules in Webflow

Google recommends permanent server-side redirects for permanently moved URLs. Avoid sending every removed page to the home page; use a relevant destination or an honest 404/410 when nothing replaces it. Update internal links, canonicals, structured data, social metadata, and the XML sitemap to final URLs. Do not promise fixed rankings: Google notes that URL-changing moves can create temporary fluctuations while new locations are crawled and indexed.

Keep the domain decision separate from the website account

A Wix site, Wix account, premium plan, domain registration, DNS hosting, and business email are related but not identical. The domain does not have to be transferred to a new registrar simply because the website moves; it can often remain with its current registrar while DNS points to Webflow. If the business chooses to transfer a Wix-registered domain away, follow Wix's current transfer instructions and timing rules. Inventory the entire DNS zone before any change so MX, TXT, SPF, DKIM, DMARC, verification, and other service records are preserved.

Run the cutover without losing the Wix record

01

Freeze and export by product

Set separate cutoffs for pages, blog posts, CMS, forms, contacts, store, bookings, members, and app data. Produce final deltas after the main migration.

02

Back up the evidence

Keep Wix ownership under the business, duplicate the site when appropriate, retain exports, screenshots, configuration records, invoices, and an access plan. Do not cancel the source to force a deadline.

03

Test Webflow on its staging domain

Verify responsive pages, CMS edge cases, forms, integrations, accessibility, analytics, metadata, robots behavior, and redirects without exposing the unfinished site to indexing.

04

Connect production carefully

Publish the approved build, add final redirects, change only required DNS records, verify the certificate and primary domain behavior, then run external smoke tests.

05

Retire after acceptance

Confirm lead or transaction destinations, search configuration, content reconciliation, staff access, exports, billing, and support. Preserve required business records before downgrading or canceling Wix services.

Can I export my Wix website and import it into Webflow?

Not as a working site. Webflow states that Wix layouts, styles, and interactions must be rebuilt manually. Some Wix products provide their own data exports, such as CMS Collection CSV files, contacts, form submissions, products, and redirects, subject to current feature rules.

Can Wix Blog posts be exported to Webflow?

Wix currently states that Wix Blog posts cannot be exported to other platforms. Build a post ledger and plan an authorized manual or carefully engineered recovery process, then verify each destination post. Do not assume that a general site export contains the blog.

Do I need to transfer my domain away from Wix?

Not necessarily. Domain registration and website hosting are separate. You may keep the domain with its current registrar and update DNS to Webflow, or transfer it for an operational reason. Preserve email and verification records either way.

Will Wix Forms and Automations continue after the move?

Not on the new Webflow pages by default. Rebuild each form and its complete workflow, including contact mapping, notifications, automations, files, consent, storage, and integrations. Export required historical submissions before retiring Wix.