WordPress to Wix Studio: the complete migration guide

Only the blog. Wix states that importing a site created outside of Wix isn't supported, and names WordPress blog posts as the single exception. The importer brings post text, images, video, original dates and categories across. Your pages, theme, plugins and everything they powered are rebuilt in Studio. So the honest answer is that WordPress is the one platform Wix will meet you halfway on, and halfway is the blog.

Wix lists the exclusions explicitly: contact forms, author names, tags, custom plugins, manually inserted HTML and CSS, PDFs and other attached documents, and comments. It also imports published posts only, so drafts and scheduled posts are copied manually, and password-protected posts need unlocking first. Wix also warns that some but possibly not all of your formatting survives, which is why posts get checked individually rather than sampled.

Not if the URLs are handled deliberately, and on this move most of them don't have to change at all. Static pages keep their paths. Blog posts depend on one build decision: Wix's Blog app puts every post under a /post/ prefix that can't be removed, while a blog built on the CMS lets you set the prefix yourself, so a WordPress site already publishing at /blog/post-name can keep exactly that. The quieter risk is metadata: Yoast and Rank Math settings live in the plugin, not the post, so titles and descriptions get re-entered and diffed against the crawl before the domain moves.

Mostly not, and where they do it's a choice rather than a constraint. Wix Studio imposes no path structure on standard pages, so /about stays /about. Your blog comes down to how it gets built: Wix's Blog app forces every post under a /post/ prefix, so a site with three hundred posts needs three hundred mapped redirects, while a CMS-driven blog lets you set the prefix and the slug, which is how an existing /blog/post-name structure survives the move untouched. Where redirects are needed they get mapped post by post, never a blanket rule pointing the old blog at the new index, which technically avoids 404s and quietly converts every ranking post into a bounce.

From €1,750, quoted as a fixed price before any work starts. The number moves on your post count first, since every post gets a formatting pass after import, then on how many plugins were doing real work that has to be rebuilt rather than replaced, and whether custom post types need modelling as CMS collections. A five-page brochure site with a dormant blog sits at the bottom of that range.

Two to five weeks from kickoff to launch for most sites, then a 30-day monitoring window that runs while you're already live. The blog archive drives the number: the import itself is a day, but checking formatting across four hundred posts, one by one, is not. Your WordPress site keeps serving traffic throughout.

For a small site, yes, and the blog importer genuinely helps. The trap is that it succeeds loudly while the rest of the site quietly doesn't come. A five-page site with a short blog is a reasonable weekend project. It turns when you have a few hundred posts carrying organic traffic, custom post types holding real content, WooCommerce, or plugins doing work you'd have to replace rather than drop. The reliable signal is your organic traffic: if the blog earns enquiries, the risk isn't the rebuild, it's the redirect map you can't check afterwards.

Most of what plugins were doing is native in Wix, so the work is matching behaviour rather than porting code. Forms, SEO controls, bookings, memberships, galleries and analytics all exist without an add-on. What needs a decision is anything truly custom: a plugin doing something Wix has no equivalent for is the one thing that can make this move the wrong call, and you hear that during the audit rather than after the invoice.

Wix Stores covers the same ground, but Wix documents no product import path from WordPress, so this is the row to check against your own catalogue before planning around it. Send us a product export before we quote. For a small catalogue this is straightforward. For a large store with variants, subscriptions or complex fulfilment, WooCommerce may be the reason to stay, and we'll say so.

Yes, and it should. The Studio build lives on its own staging URL while WordPress keeps serving your domain, so there's no maintenance page and no gap in enquiries. You sign off on a working site you can open on your own phone. The domain moves in a single afternoon at the end, once the redirect map has been uploaded and tested.