Most guides to switching from WordPress to Wix spend most of their length on moving posts and pages, then rush through everything else in a paragraph. That’s backwards. Wix has a genuinely working native importer for WordPress content — point it at your site’s URL and it pulls in posts, pages, images and categories without a paid tool or a workaround. The part that actually eats your time isn’t the content. It’s the plugins.
A WordPress site without its plugins is just a CMS with some posts and pages, and that part moves easily. The same site with a booking plugin, a membership system, a custom child theme and a page builder underneath it is a completely different migration — because none of that has a one-to-one equivalent in Wix, and no generic guide can predict what your specific plugin stack looks like. This guide splits the two apart, and instead of a separate checklist, timeline and hire-or-DIY section bolted on at the end, each of those questions gets answered right where the relevant plugin category comes up.
When WordPress Stops Being Worth the Maintenance
The reasons rarely come down to WordPress being bad software — it powers a large share of the web precisely because it’s flexible. The move usually comes from the maintenance side: plugin updates that break each other, security patching, hosting management, and the ongoing need for at least some coding comfort to keep things running smoothly.
Wix trades that flexibility for an all-in-one platform where hosting, security and updates are handled for you. Our full WordPress vs Wix comparison covers the trade-offs in more depth, and if you’re not certain Wix is the right destination for what you’re trying to simplify, it’s worth a look at WordPress alternatives more broadly before committing to this specific move.
What Actually Transfers Cleanly
Wix’s blog importer works directly against your WordPress site’s URL: go to Blog in your Wix dashboard, choose Import Posts, select WordPress, and enter your site’s address. It pulls posts, categories and images without you needing to manually export an XML file first, though a manual XML export and upload is also available if the URL-based import doesn’t work for your setup.
A few conditions have to be true for it to work at all:
- Your WordPress REST API needs to be reachable — some security or firewall plugins disable it, which breaks the importer before it starts.
- Your blog needs to be public, with no geographic access restrictions in place.
- Your blog URLs shouldn’t be mid-redirect to somewhere else when you run the import.
On volume: Wix’s own documentation isn’t fully consistent with itself here. One official support page states a limit of roughly 4,000 posts imported from WordPress in one go; another describes up to 5,000 posts per turn, with additional batches handled via XML for anything larger. Rather than treating either number as gospel, plan for an import in the low thousands per batch, and if your blog is larger than that, expect to run it more than once. This part of the migration is genuinely quick — a few hours of setup and waiting, not days.
Images embedded in imported blog posts generally come across along with the post content, since the importer pulls them as part of the post body. Images used elsewhere — in page templates, widgets, or theme-level design elements — don’t travel with the blog import at all and need to be downloaded from your WordPress media library and re-uploaded into Wix’s Media Manager as you rebuild each page. It’s worth doing this before you cancel your WordPress hosting, since media URLs stop resolving once the server is gone.
The Real Complication Isn’t Content, It’s Plugins
This is where the actual migration effort lives, and it’s not one task — it’s a different decision for every plugin your site runs. Go through your active plugin list and sort each one into whichever of these four categories it belongs to; the category tells you the time cost and whether this is something to handle yourself.
Contact forms, live chat, analytics. Wix Forms and the Wix App Market cover this ground directly with a close equivalent for almost everything in this category. Budget an afternoon per tool: find the Wix equivalent, reconfigure it, test it. This bucket is DIY-friendly regardless of how much content your site has.
SEO plugins. You don’t need a Wix equivalent at all, and there’s nothing to migrate here beyond copying settings. Wix has SEO controls — titles, meta descriptions, schema markup, sitemap generation — built into the platform itself, so a Yoast or Rank Math setup gets its values copied by hand into Wix’s native SEO panel rather than replaced with another plugin. Plan on an hour or two per important page, not a separate migration project.
Booking systems and membership/LMS plugins. A Wix equivalent generally exists (Wix Bookings, Wix’s membership tools), but setting it up is a from-scratch configuration, not a data migration. Member lists, course progress, and booking history don’t come across — you’re rebuilding the structure and asking users to re-register or re-enroll. Budget several days for this category alone if it’s central to your site, and plan the “please re-register” communication to your members as part of the timeline, not an afterthought.
Custom code, child themes, bespoke PHP functionality. This is the category with no Wix equivalent, full stop, and it’s the one place in this whole guide where the honest answer is often “don’t do this part yourself.” If your site relies on custom functions, a hand-built child theme, or a developer-written integration, there’s nothing to import — it’s a rebuild from a blank page. If that functionality is central to how the site works or makes money, this is where hiring a Wix expert or a developer for the rebuild specifically tends to cost less, in time and risk, than a week of finding out what breaks. If you’re weighing that against a full DIY attempt, what a website migration typically costs gives useful context for making that call.
Plugin audit worksheet. Before you touch the Wix editor, make a simple spreadsheet with one row per active plugin and these columns: plugin name, which of the four buckets above it falls into, the Wix App Market equivalent (if you’ve found one), and an estimated hour count. A site with fifteen plugins that are all contact forms and SEO tools is a weekend project. The same fifteen plugins with two custom-built ones mixed in is a different project entirely — and the worksheet is what tells you that before you’ve sunk a week into finding out the hard way.
If You’re Running WooCommerce
WooCommerce migration deserves its own walk-through, separate from the general plugin categories above, because it’s common enough on its own and the numbers involved are worth getting right — the current live version of this guide states a limit that no longer matches Wix’s own documentation.
From the WooCommerce side: export your products as a CSV through the CSV Import Suite, choosing which products, variants and columns to include.
From the Wix side: go to Store Products, click Import, download Wix’s template file, and map your WooCommerce export into that format rather than uploading the WooCommerce file directly — the two platforms don’t share a CSV structure. The real current limit is 15MB or 10,000 rows per file (not the flat “5,000 items” figure sometimes quoted), and digital products aren’t supported through this import path at all — those need to be rebuilt manually as separate listings.
Customer accounts and order history sit outside the free CSV path entirely, and customer passwords never transfer regardless of method — budget for a “reset your password” email to returning customers after launch. For catalogs too large for a clean manual CSV cleanup, or where order history needs to survive the move, Cart2Cart (available through the Wix App Market) handles products, orders and coupons for a fee, with a free preview before you commit to paying. Either way, you’ll need at least a Wix Core plan to accept payments — the free and Light plans don’t support selling at all.
On timing: a clean catalog under a couple hundred products with simple variants is realistically a few days of CSV work. A catalog past a thousand SKUs, or one with digital products or order history you need preserved, is where Cart2Cart or a specialist earns its cost rather than where DIY saves you money. For a broader sense of how Wix and WooCommerce compare as ongoing platforms rather than just as a migration pair, our WooCommerce vs Wix comparison is worth a look before you commit.
Setting Up and Rebuilding in Wix
Wix currently runs four paid tiers: Light (around $17/month), Core (around $29/month, the minimum needed to accept payments), Business (around $39/month), and Business Elite (around $159/month), all on annual billing — monthly billing runs higher across the board. Test the free 14-day trial against your actual WordPress feature list before committing, rather than guessing which tier you need based on your current WordPress hosting cost.
On the editor itself: the standard Wix Editor and Wix Studio are the two current options. If you’ve seen “Editor X” mentioned elsewhere as a separate product, that’s outdated — Editor X was fully merged into Wix Studio in early 2025 and no longer exists as its own platform. Wix Studio is aimed at more advanced, multi-page or agency-style builds; the standard Editor covers most single-site migrations without the extra complexity.
You can’t transfer your WordPress theme directly, so pick a Wix template that’s structurally close to what you have now — similar navigation depth, similar use of a blog or store section — and treat it as a starting point rather than an exact match. Rebuilding each page means copying your text and images across and reconstructing the layout with Wix’s blocks and widgets, which work on a different underlying logic than WordPress’s block editor even though both are visual, drag-oriented systems. Keep your heading structure intentional as you go — one clear H1 per page, logical H2s beneath it — since this doesn’t carry over automatically from your old theme’s template files.
Domain, Redirects, SEO and the Switch-Over
Connecting or transferring your domain works the same way for WordPress as it does for most platforms moving to Wix, and since we’ve already covered the mechanics in detail — unlocking the domain, getting the EPP code, DNS propagation timing — in our dedicated guide on transferring a domain from WordPress to Wix, we won’t repeat the full walkthrough here. The short version: decide between connecting (keep the domain registered elsewhere, just point DNS at Wix) or a full registrar transfer, and preserve your email DNS records either way.
Redirects matter just as much here as in any other migration. Map your highest-traffic WordPress URLs to their new Wix equivalents and set up 301s through Wix’s Redirect Manager before you publish — don’t let a changed URL structure turn indexed pages into 404s. Pair that with the SEO side: titles, meta descriptions and schema markup need to be manually re-entered in Wix’s own SEO panel, since none of it carries over from your old SEO plugin’s settings.
Once the site is live, our guide on getting a Wix site found and ranked on Google covers the ongoing work beyond this initial setup.
Before you actually flip the domain over, run through this in order:
- Every rebuilt page matches on desktop and mobile
- Imported blog posts display correctly — formatting, images, categories
- Every reconfigured plugin equivalent from your audit worksheet works end to end, not just visually
- Redirects resolve correctly with no 404s on your highest-traffic URLs
- SEO titles, meta descriptions and schema are entered, not just copied as plain text
- Page speed checked with a tool like Google PageSpeed Insights
- A test order completes successfully, if you migrated a WooCommerce store
Only connect the domain once this list is clean. A site Google indexes mid-rebuild is harder to recover from than the extra day this checklist costs you.
What Trips People Up
- Treating plugin functionality as content. A plugin doesn’t “migrate” the way a blog post does — the worksheet exists precisely so this stops being a surprise partway through.
- Skipping the REST API and geo-restriction checks before running the blog importer. This is the single most common reason the native importer fails outright, and it’s checked in minutes if you look before you start.
- Underestimating a WooCommerce catalog by comparing it to the blog import. A store with digital products or a five-figure order history isn’t a bigger version of the free CSV path — it’s a different tool entirely.
- Connecting the domain before the pre-launch checklist is clean. The redirect and SEO work has to happen first, not in parallel with going live.
FAQ
Conclusion
The content side of a WordPress-to-Wix move is easier than its reputation — the native blog importer genuinely works, conditions permitting. What decides how long this actually takes is the plugin audit: sorting what has a direct Wix equivalent from what needs a full rebuild, and being honest early about anything running on custom code rather than discovering it mid-migration. Do that sorting first, and the rest of this guide is mostly execution.
