How do I export my Wix website?

You can't, fully. Wix provides a blog RSS export that captures post titles, content, and publish dates (but not featured images or categories cleanly), and you can move your domain away. There is no HTML/CSS export, no structured content export for static pages, no product data export in a standard format, and no design export. Migrating from Wix is largely a manual rebuild, the 'export' is closer to 'gather references before you cancel.'

How long does a Wix to coded site migration take?

DIY, expect 30–80 hours for a small business site spread over 3–6 weeks. Wix migrations take longer than Squarespace or Webflow migrations because there's no clean content export, most content has to be manually transcribed or rebuilt. With a specialist, elapsed time is typically 3–5 weeks, with your hands-on time focused on content review and approvals. SiteShiftCo includes Wix migrations in the Core plan, priced to account for the higher manual rebuild overhead compared to other platforms.

Will I lose SEO if I migrate away from Wix?

Only if the migration is done badly. Wix URLs can be preserved exactly on the new site, and 301 redirects should map any URL that changes. Wix sites often have better SEO performance after migration because the replacement site typically has better Core Web Vitals (Wix sites consistently rank among the slower-loading CMS platforms). The risk is in the execution, missing redirects, lost metadata, changed URL structures without mapping.

What happens to my Wix blog posts when I migrate?

You can export the blog via Wix's RSS feed, which gives you post titles, content, publish dates, and basic HTML. What's NOT in the RSS export: featured images (need manual download), categories and tags (partially), custom metadata, embedded Wix widgets, and internal links that reference Wix-specific URL structures. Expect 30–60 minutes per post for cleanup and conversion to Markdown, unless you automate with scripts.

What about Wix Stores if I'm running an online store?

Wix Stores migrations are significantly more involved than content site migrations. Product data can be exported via CSV but customer accounts, order history, payment methods, and shipping configurations don't migrate. Most Wix Stores migrations end up on Shopify (which is built for ecommerce) rather than coded sites. If your site is primarily ecommerce, a coded site isn't usually the right destination, Shopify is.

What happens to my Wix bookings or restaurant reservations?

These don't migrate automatically, they're Wix-specific apps with their own data. For bookings, common replacements are Calendly, SavvyCal, or Cal.com; for restaurants, OpenTable or Resy. Existing customer bookings usually don't transfer and customers need to re-book on the new system. Plan for 5–10 hours of reconfiguration work per Wix app you're replacing.

What's the easiest path off Wix?

If you want to stay in the hosted CMS world: Squarespace is the closest upgrade path, similar all-in-one model, often better design, similar or slightly higher price. If you want to leave hosted CMS entirely: a coded static site (Astro on Cloudflare Pages) is cheaper long-term and faster, but requires either DIY technical work or a specialist to build. The choice depends on why you're leaving Wix, quality, cost, lock-in, or performance.

Will my Wix custom code (Velo) work on a different platform?

No. Wix Velo is JavaScript that runs specifically inside Wix's environment, using Wix-specific APIs (wix-data, wix-fetch, Wix CMS collections). That code will not run on a coded site, WordPress, Webflow, or anywhere else. Velo functionality needs to be rebuilt using platform-appropriate tools, serverless functions, a different backend, or third-party services. If your Wix site relies heavily on Velo, factor significant rebuild time into migration planning.

Can I keep my domain when moving off Wix?

Yes. Domains registered through Wix can be transferred to another registrar (Namecheap, Cloudflare Registrar, Porkbun) while keeping the same domain name. The transfer takes 5–7 days and requires an authorization code. You can also change nameservers without transferring the domain, pointing DNS at a new host while keeping the domain registered at Wix. Both approaches work; transferring away from Wix is cleaner long-term.

Is it worth hiring someone to migrate my Wix site?

For most small businesses, yes, Wix migrations have more manual rebuild work than other platforms, and the learning curve for DIY is steeper because you can't rely on automated content migration. Specialist services that handle Wix charge $2,000–$5,000 for typical small business migrations. SiteShiftCo treats Wix migrations as Custom projects (not the standard Starter/Core packages), specific pricing depends on page count, blog volume, and which Wix apps need replacing.

How to migrate from Wix to a coded site

Migrating from Wix is harder than migrating from Squarespace, Webflow, or WordPress. Not because the technical work is different, the destination stack (coded site on a CDN) is the same, but because Wix gives you less to work with on the way out. There’s no full HTML/CSS export, no clean content export for static pages, no standard format for products, and Wix-specific features (Bookings, Velo, Stores) don’t translate at all.

This guide covers what you actually need to do to move off Wix, realistic time estimates, and the specific gotchas Wix migrations hit that migrations from other platforms don’t.

Who this is for

Good fit:

Small business sites on Wix considering a move to a coded static site
Sites that are primarily content (pages, blog, contact form) without heavy commerce
Owners either willing to do significant manual content work, or willing to hire a specialist
People leaving Wix for cost, performance, design quality, or lock-in reasons

Not a good fit:

Heavy Wix Stores users (migrate to Shopify instead)
Sites built around Wix Bookings, Restaurants, or Hotels apps (these require specific app replacements on whatever stack)
Sites with significant Velo custom code you don’t want to rebuild
Teams with no technical comfort and no budget for specialist help

For sites that don’t fit, consider Squarespace as a Wix alternative (similar all-in-one model, generally better quality) or Shopify (if ecommerce is primary).

The Wix export reality

Before doing anything else, understand what you’re actually working with.

What Wix lets you export

Blog posts via RSS feed. Go to yoursite.com/blog-feed.xml. Captures titles, content, publish dates. Basic HTML formatting preserved. Categories and tags are inconsistent.
Domain transfer. You can move your domain to another registrar through standard domain transfer process.
Product data (Wix Stores only). CSV export of product titles, prices, SKUs, descriptions, and basic inventory data. Does not include customer accounts, orders, or settings.
Contact list. Via Wix’s dashboard, you can export contact submissions.

What Wix does not let you export

Full HTML/CSS of your site
Structured data for non-blog pages (About, Services, etc.)
Design files or theme information
Customer accounts and order history for Stores
Velo custom code in a portable form
Wix Bookings appointments or customer history
Form submission history beyond basic contact forms
Member areas and member data
Any Wix App data (Forum, Restaurants, Hotels, Events)

The practical implication: migrating from Wix is mostly a manual rebuild, not a content transfer.

Realistic time estimates

For a typical small business site (15–30 pages, blog with under 50 posts, contact form, maybe a booking integration):

Task	DIY time
Learning the new stack (if first time)	10–20 hours
Content audit and page-by-page inventory	3–6 hours
Downloading images (manual, no bulk tool)	3–8 hours
Rebuilding static pages in Markdown	10–20 hours
Converting blog posts from RSS to Markdown	4–12 hours
Rebuilding forms on the new stack	2–4 hours
Replacing Wix apps (Bookings → Calendly, etc.)	5–15 hours
Setting up SEO (redirects, metadata, schema)	3–6 hours
Testing on staging	2–4 hours
DNS cutover and verification	1–3 hours
Total	43–98 hours

Spread over 3–6 weeks of focused work. Longer if squeezed between other priorities.

A specialist service typically delivers in 3–5 weeks elapsed with 10–15 hours of your involvement.

Before you start: audit everything

Because so little of the site transfers automatically, your audit is the foundation of the migration. Spend 3–6 hours producing:

Full page inventory

Every URL on your Wix site. Page type, content source, status on the new site (migrating, consolidating, removing).

Every image asset

Wix has no bulk image export. Options:

Manual download, right-click each image, save. Tedious but reliable.
Site crawler, tools like SiteSucker, HTTrack, or wget --mirror can pull every image the site serves.
Scripted approach, crawl your sitemap URLs, extract image sources, download each.

Preserve original filenames where possible, they may be referenced in blog post content.

Every form

Contact forms, lead capture, quote requests, each needs to be rebuilt on the new stack. Document what fields each has, where submissions currently go (email address, CRM, Zapier trigger), and any conditional logic.

Every Wix app you use

List them all. For each, decide: replace with an alternative, consolidate, or drop. Common replacements:

Wix app	Typical replacement
Wix Bookings	Calendly, SavvyCal, Cal.com
Wix Stores (light use)	Stripe Payment Links, Gumroad, Snipcart
Wix Stores (serious ecommerce)	Shopify (separate decision, coded site may not be right)
Wix Restaurants	OpenTable, Resy, a booking service
Wix Hotel	Commercial hotel booking platform (Cloudbeds, Little Hotelier)
Wix Events	Eventbrite, Luma
Wix Forum	Circle, Discourse, Disqus
Wix Members Area	Memberstack, Outseta, Ghost
Wix Blog	Blog section on the new stack

Every tracking script and integration

Google Analytics, Facebook Pixel, LinkedIn Insight, Hotjar, chat widgets, email capture tools. Each has to be reinstalled on the new site.

Every Velo custom script

Inventory every Velo script in your Wix codebase. Document what each does in plain English. Plan the replacement approach on the new stack, serverless function, third-party API call, or “drop this feature.”

Every DNS record

A, AAAA, CNAME, MX, TXT, SRV. Export the full zone before making any changes. Especially critical: MX records for email (do not break these during DNS cutover).

Step-by-step migration

Step 1: Choose your stack

For small business Wix migrations in 2026, the most common destination:

Static site generator: Astro (recommended), Hugo, or Eleventy
Hosting: Cloudflare Pages (free tier covers most small business traffic)
Content: Markdown files in a Git repository
Forms: Cloudflare Pages Functions, Formspree, or similar
Bookings (if applicable): Calendly or Cal.com embedded
Ecommerce (if light): Stripe Payment Links or Snipcart
Analytics: Google Analytics 4, Plausible, or Cloudflare Web Analytics

See Static site generator (SSG) and the Squarespace migration guide for more background on the stack choice, it’s the same target regardless of source platform.

Step 2: Set up hosting and repository

Create a Git repository. Set up a Cloudflare Pages project pointing at the repo. Configure a build command (typically npm run build) and output directory (typically dist/).

Your first deploy goes live on a *.pages.dev subdomain. Keep the site here during development; you’ll point your custom domain at it at cutover.

Step 3: Export what you can from Wix

Grab the blog RSS feed (yoursite.com/blog-feed.xml)
Export products from Wix Stores if applicable (CSV)
Export contact submissions from Wix Contacts
Screenshot the site, every page, every state. You’ll need these as visual references during the rebuild.

Step 4: Download all images

Pick a method (manual, crawler, scripted) and capture every image. Organize them by page so you know where each belongs during the rebuild.

Step 5: Rebuild static pages in Markdown

For each page (About, Services, Contact, etc.), create a corresponding Markdown file. Copy text content. Reference the screenshots for layout. Build the layout in components (Astro components, HTML templates, whatever your stack supports), not a visual editor.

This is the most time-intensive step. No automation helps much because Wix’s export doesn’t include structured page content.

Step 6: Convert blog posts from RSS

RSS → Markdown conversion options:

Automated scripts, search GitHub for “wordpress-rss-to-markdown” or “rss-to-markdown”; many existing tools handle the conversion
AI-assisted, paste RSS XML into Claude or ChatGPT, ask for Markdown files with frontmatter
Manual, for small numbers of posts (under 20), manual conversion is tractable

Verify each converted post. Embedded Wix widgets, inline images, and platform-specific formatting rarely convert cleanly.

Step 7: Replace forms

Wix forms don’t transfer. Pick a replacement:

Simplest: Formspree, Web3Forms (paste an endpoint into the form’s action attribute)
No vendor dependency: Cloudflare Pages Function with an email service
CRM-connected: Direct integration to your CRM (HubSpot, Pipedrive, etc.) via their API

Test submission end-to-end before launching.

Step 8: Replace Wix apps

For each app on your audit list, set up the replacement. Migrate any existing data if possible (Calendly can import bookings from some sources; most replacements require starting fresh).

Step 9: Set up SEO preservation

Preserve meta titles and descriptions from each Wix page
Re-implement schema markup as JSON-LD (Organization, LocalBusiness, Article, FAQPage, whatever was in use)
Generate a sitemap (Astro has @astrojs/sitemap)
Configure robots.txt

See Sitemap, Schema markup, Meta description.

Step 10: Build the redirect map

Every old URL → its new URL. For most Wix migrations, the URL structure can be preserved exactly (same page paths, same blog post slugs). Still implement 301 redirects as a safety layer.

Common Wix URL patterns to consider:

/blog/yyyy/mm/slug or /post/slug, preserve exactly or map as needed
/store/product/..., product URLs if applicable
/about-us vs /about, trailing slashes and capitalization consistency

Implement redirects in your hosting platform, for Cloudflare Pages, a _redirects file.

Step 11: Test on staging

Before DNS changes, verify on the *.pages.dev URL:

Every page renders correctly
Forms submit and emails arrive
Analytics events fire
Structured data validates (Rich Results Test)
Core Web Vitals scores are acceptable
Images load correctly with alt text
Redirects work when tested manually
Mobile experience is solid

Step 12: DNS cutover

Lower TTL on existing DNS records to 300 seconds, 48 hours before cutover
Document existing DNS records (especially MX for email)
Change A or CNAME records to point at Cloudflare Pages
Keep MX records unchanged (unless you’re also migrating email)
Verify SSL provisions (usually within minutes on Cloudflare)
Test the site at your custom domain in incognito
Keep Wix site active for 48 hours as a rollback option

Step 13: Post-launch verification

Submit new sitemap to Google Search Console
Check every redirect URL with httpstatus.io
Verify all tracking scripts are firing (GA4 Real-time, Facebook Pixel Helper)
Monitor Search Console coverage report for 1–4 weeks for any errors
Cancel Wix Premium plan only after 30 days of clean analytics on the new site

Cost of DIY vs hiring

DIY:

Learning curve (first-time): 10–20 hours
Migration work: 35–80 hours
Out-of-pocket: $10–$20 (domain renewal only; hosting is free)
Risk: higher, Wix migrations have more manual work, more places to make mistakes

Hiring a specialist:

SiteShiftCo handles Wix as Custom projects, pricing depends on page count, blog volume, and Wix apps to replace. Typical range: $2,000–$5,000.
Specialist Wix-focused services: $3,000–$6,000
Full-service agency: $8,000–$20,000

For most small businesses with revenue-generating sites, hiring a specialist is the right call because the manual rebuild work is so concentrated, a specialist moves faster per hour than a first-time DIYer learning along the way.

After migration: how you’ll edit the site

A common concern leaving Wix: “will I still be able to update my site easily?” For a Markdown-based coded site, options are:

Edit Markdown files directly, in any text editor, including AI assistants like Claude or ChatGPT
Use a Git-based CMS layer, TinaCMS, Decap, or Keystatic give you a visual editor that commits to your repository
Use AI for content updates, describe changes in natural language, AI produces Markdown, you review and commit

Counterintuitively, editing speed often improves after leaving Wix, the multi-step Wix editor workflow is replaced by direct file editing or AI-assisted updates. See Can I update my website using AI? for the details.

Wix alternatives, if you haven’t decided where to go yet
Will I lose SEO if I rebuild my site?, SEO preservation details
What breaks when you move a website?, the full audit checklist
How to choose a website migration service, buyer guide if hiring
Should you migrate yourself or hire someone?, DIY vs hire decision
Glossary: Site migration, Site export, 301 redirect, Static site, DNS