Leaving Wix: how to get your content out and own your site

You built a site on Wix. It got you online fast, the drag-and-drop was easy, and now you are stuck. There is something you want to change that Wix will not let you change, your content lives inside their platform, and you pay every month for a site you do not really own. So you go looking for the export button, and this is where the trouble starts.

Let us be straight about it. Leaving a closed builder is harder than leaving an open CMS, and not by accident. Lock-in is the business model of a hosted builder: the easier leaving is, the weaker the reason to keep paying. So a move off Wix is less a migration and more a rescue, followed by a rebuild. Here is what that involves.

Why this is different from other migrations

With WordPress you press Export and get a single file containing your posts, pages, categories and comments. Joomla and Drupal have similar routes. Even Squarespace hands you a partial WordPress-format export.

Wix does not. There is no button that gives you your whole site as portable data. What exists is a handful of narrow exports, and everything outside them has to be recovered from your own public website. That is the honest starting position, and knowing it up front saves you an afternoon of hunting through settings for a feature that is not there.

The reward is real, though. Once your site is rebuilt on infrastructure you control, with the content in an open format and the code in your own repository, you never have to do this again. The next move, if you ever want one, is straightforward.

What you genuinely can export from Wix

Worth doing first, because it is the cleanest material you will get:

• Blog posts, via the RSS feed. Wix blogs publish a feed, usually at /blog-feed.xml on your domain. Open that address in a browser and you should see your posts as raw data: titles, publication dates and the post body. This is a legitimate export route and the single most useful thing available to you. The catch is that feeds are usually capped, often at the most recent 20 or 25 posts, so an older archive will be partly missing.
• Wix Blog’s own export. On some plans the blog section offers an export that produces a WordPress-compatible file. If you see it, use it; it is far better than the feed. Availability varies by plan and by when your site was built, so check rather than assume.
• CMS collections, as CSV. If you used the Wix Content Manager (the database collections behind things like a team directory or a property list), each collection can usually be exported as a CSV spreadsheet. Do this per collection.
• Store products, as CSV. Wix Stores generally allows a product export in CSV form. Check whether it includes your product images or only their addresses.
• Contacts and orders. These live in your Wix dashboard and export as CSV. They are not website content, but you want them, and they are easy to forget until after you have cancelled the subscription.

What you cannot export, and how to rescue it

Everything else has to come off the live website. The practical routes:

Your pages. Your About page, services pages, landing pages and contact page have no export at all. Every Wix site does publish a sitemap at /sitemap.xml, which is a machine-readable list of every public address on the site. That list is your inventory: it tells you exactly how many pages you have, which is usually fewer than people expect. From there each page’s content is read off the live site.

For a small site, and most Wix sites are small, honest advice: copy the text by hand. Fifteen pages of copy and paste is an evening’s work and the result is cleaner than anything a script produces. Save your money for the rebuild.

Your images. There is no bulk media download. Wix serves images from static.wixstatic.com, and each one can be saved individually from the live page. The important detail is resolution: a Wix page often displays a resized version, so you want the original file rather than the thumbnail the page happens to show. Original photography you no longer have a copy of is the thing people most often lose in a builder migration, so start here, not last.

Your design. It does not transfer, at all, to anywhere. Take full-page screenshots of every page before you cancel anything. They become the reference for the rebuild.

Anything behind a login. Member areas, bookings, forum posts and course content are generally not recoverable through any of the routes above. If you run one of these, work out the answer before you commit to leaving.

A warning about the raw material you rescue from the live site: it is rendered Wix markup, which means heavy wrapper elements, Wix-specific class names and inline styling everywhere. It is the source of your words and pictures, not something to keep. All of it gets stripped back to plain content before it goes anywhere near the new site.

Where you are moving to

Once the content is out, the destination is an open decision. The common options for a Cloudflare-hosted site:

• A modern static site, usually built with Astro. Pages are prepared in advance and served from Cloudflare’s network, so they load faster than a Wix page that has to boot its own runtime in the visitor’s browser. Ideal for small business sites, portfolios and brochure sites.
• EmDash, Cloudflare’s own open-source CMS, MIT-licensed, which Cloudflare describes as a “spiritual successor to WordPress”. It is built on Astro 6 and runs on Workers, with content in D1 and files in R2. If you want an admin panel for writing, this is the closest match. It is also new: Cloudflare launched it in April 2026, v1.0 lands around late September, and the plugin ecosystem is still small.
• A static site with a hosted editor attached, if you mostly want to edit text and swap photos without touching code.

Whichever you pick, the properties that matter are the same: the content is in an open format, the code sits in a repository you own, and no single company can hold the site hostage.

What replaces Wix’s built-in features

Wix bundles a lot behind the scenes, and this is the step people underestimate. Write down every feature you actually use: the contact form, the newsletter signup, the booking calendar, the Google Analytics connection, the cookie banner, the live chat widget, the store.

On a modern site each of those becomes either a built-in feature, a few lines of code, or a third-party service you connect. Forms, analytics and newsletters are easy and often cheaper than the Wix equivalent. Bookings and ecommerce are the ones to check carefully before you commit, because that is where a migration can stall.

Do not skip: keep your URLs

Wix addresses are often unlovely (/copy-of-services-1 is a real pattern), but Google knows them and other sites link to them. Losing that is losing your search traffic.

The routine:

1. Save the full list from /sitemap.xml before you change or cancel anything.
2. Note which pages actually get traffic, using Google Search Console or your analytics. Usually a handful carry most of it.
3. Keep those addresses on the new site where you can, and set a 301 redirect from old to new for anything that has to change.
4. Resubmit your sitemap after launch and watch the coverage report for a few weeks.

Done properly, traffic dips briefly and recovers. Skipped, you start again from nothing.

The honest trade-offs

Leaving Wix gets you a faster site, lower running costs and genuine ownership. It costs you the thing Wix was actually good at: changing your own site by dragging boxes around, with no help from anyone. On a code-based site, structural changes go through either a developer or a service. If what you truly wanted was “no code, ever, by myself”, a builder is still a builder, and staying is a legitimate choice.

But if you are leaving because you outgrew the template, because the monthly bill buys you nothing you own, or because you were told no once too often, then this is worth the afternoon it takes. If you are weighing options broadly, the best WordPress alternatives for 2026 shows the wider field. The same escape from the other platforms is covered in leaving Squarespace, leaving Joomla and moving WordPress to Cloudflare.

At 2emdash we do this for people who would rather not do it themselves: we rebuild your existing site on Cloudflare and hand you a simple panel to run it from. We’re an independent service, not affiliated with Cloudflare or the EmDash project.