How to Move a Wix Site to WordPress
Wix makes it easy to start a site and hard to take it with you: there is no button that exports the design. This guide shows how to transfer a Wix site to WordPress: your AI agent, connected to WordPress through Fabrement, rebuilds it as native Gutenberg blocks from the live pages, moves the content, and keeps the addresses and SEO, so the site keeps its search history after the switch.
Key takeaways
- There is no Wix to WordPress converter that keeps the design, because Wix does not export its pages as code. Your AI agent rebuilds the design from the live site as native Gutenberg blocks with editable fields, on one design system.
- The content comes over in parts: pages from the live site, blog posts, CMS collections and products through Wix’s own exports or the pages themselves, and images into your media library.
- Keep every address. Wix puts blog posts under /post/. WordPress can keep that path, and any address that has to change gets a redirect.
- The domain is the last step. Point it at the new host, or transfer it away from Wix once it is more than 60 days old.
- After the move, you run the site by asking your AI agent over the same MCP connection: content, pages, SEO and new sections.
Hand this to your AI first: fabrement.com/AGENTS.md. One link, and your agent knows what Fabrement can do on your site and how to connect to it.
Requirements
| What | Needed |
|---|---|
| Hosting | Wix includes hosting, WordPress does not. Choose a host first and install WordPress there. |
| WordPress | WordPress 6.9 or newer with HTTPS, and Fabrement installed and signed in. |
| PHP | PHP 8.0 or newer for the plugin. Use 8.2 or newer: older branches no longer get security fixes. |
| AI agent | Claude, ChatGPT, Codex or Cursor, connected to the site over MCP. Step by step: Claude, ChatGPT, Codex, Cursor. |
| The Wix site | Still live, and your Wix login. The agent rebuilds from the published pages, so keep the Wix plan active until the switch. |
| AI plan | Enough usage for a long session. A whole site is several hours of agent work. |
The steps
1. Map the Wix site
Before anything is built, ask the agent to list every page, blog post and collection item with its address, SEO title and description. Wix publishes a sitemap at your-site.com/sitemap.xml, so the agent can start there. Repeating content, such as services, team members or projects, should become its own post type in WordPress, not a pile of separate pages.
2. Get the content out of Wix
Wix exports no design, but most of the content can come out:
- Blog posts. The usual tip is the Wix RSS feed at your-site.com/blog-feed.xml, but it holds only the latest 20 posts. For a bigger blog, the agent reads each post from its live page instead.
- CMS collections. Export each collection as a CSV from the Wix CMS, and the agent fills the matching post type.
- Products. Wix Stores exports products as a CSV, which WooCommerce can import. The store design is a separate job.
- Images. The agent uploads them into your WordPress media library, so nothing loads from Wix after the switch.
If you also connect the official Wix MCP to the same agent, it can read posts, collections and products through Wix’s own APIs instead of from the pages.
3. Give the agent the address and the request
Start a new session with your connected agent. An example request:
I have a Wix website at https://your-site.com. Rebuild it on this WordPress site.
The design stays the same: build a design system from the site's colours, fonts and buttons, one header and footer, and a native block for each section with fields the team can edit. Move all pages and blog posts with their text and images, and upload the images to the media library.
Keep every address. Blog posts on Wix live under /post/: keep that path, and add a redirect for any address that has to change. Copy every SEO title and description word for word.
Before you start, check the website and tell me what you understood. Keep new pages as drafts. Check every page on desktop and mobile against the live Wix site, and finish with a report: what you built, your decisions, and what could not be carried over and why.
To keep the blog addresses, set Settings → Permalinks in WordPress to the custom structure /post/%postname%/ before the posts are created.
4. Replace what Wix ran for you
Wix runs some things behind the scenes that a WordPress site has to set up. Forms are rebuilt with Contact Form 7 or WPForms, in the site’s design. Analytics, tracking and chat codes move across as scripts. The cookie banner, the 404 page and the social sharing images need a check. Wix apps such as Bookings, Events or Members have no automatic equivalent: each needs a WordPress plugin or a separate service, so ask the agent for a list of every Wix app the site uses before you plan the switch.
5. Review, then switch the domain
Read the agent’s report first: it lists every decision it made and every gap. Check the drafts on desktop and mobile, compare them with the live Wix pages, then publish. Now point the domain at your new host. If Wix registered it, you can keep it at Wix and point it to the new host, or transfer it away: Wix sends a transfer code to the domain owner’s email, and under an ICANN rule a domain can’t be transferred within 60 days of registration or of a change to its owner details. After the switch, submit the new sitemap in Google Search Console and watch for addresses that return 404.
After the move: run the site with your AI agent
Once the move is done, the same MCP connection keeps working. You manage the site by asking your AI agent in plain language: pages built from the blocks you already have, posts, texts and images, menus, SEO titles and descriptions, redirects, and new sections from a screenshot. New pages wait as drafts, and every block change can be rolled back. That is the part of Wix most owners miss least after the switch: changing the site is still a request, not a session in an editor, and the team can edit the same blocks in the WordPress admin whenever they prefer.
Fabrement: the workplace for your AI agent
A free plugin for WordPress 6.9 or newer. Once your AI is connected, your agent can do all of this on your site.
What comes over, and what stays in Wix
The design comes over as a custom WordPress theme: a header, a footer and a native Gutenberg block for every section, with real fields, on one design system. Pages, blog posts and collections become WordPress pages, posts and post types the team edits in the block editor, with their addresses and SEO titles kept. What stays behind are the Wix apps and any Velo code: bookings, events, members and the store checkout need WordPress plugins or a separate service. How the two platforms compare in general is on Wix vs WordPress.
Other sources work the same way: Lovable to WordPress for a Lovable project, HTML to WordPress for static sites and AI builder exports, and Elementor to Gutenberg for a WordPress site built with Elementor.
Frequently asked questions
Is there a Wix to WordPress converter?
Can I export my Wix site?
Will I lose my Google rankings?
Can I transfer my Wix domain to WordPress?
How long does it take?
What does it cost?
Sources
Wix facts were checked on 23 October 2026: the 20-post limit of the blog RSS feed and the 60-day domain transfer rule from Wix’s help center, and the Wix MCP from Wix’s developer documentation. Fabrement steps come from our own AGENTS.md (plugin version 1.6.0), and follow the same workflow as our HTML and Elementor rebuilds. If a step has changed, tell us and we will correct it.