Whether you migrate Wix to WordPress, migrate Squarespace to WordPress, or run a Magento to WooCommerce migration or a BigCommerce to WooCommerce migration, the same three things decide whether it goes well: what the old platform will actually export, what it will not, and whether every old URL redirects to the right new one. Content and products move on every platform. Design never moves from Wix or Squarespace. Customer passwords never move from any hosted platform. Redirects are where search traffic is lost, and they are the part most migrations skip. This post takes each source platform in turn and names the trap specific to it.
Why redirects matter more than the export
Every page on your old site has a URL that Google has indexed and that other sites may link to. When the site moves, those URLs change. If the old URL returns a 404, the ranking it held is gone and the link pointing at it is wasted. A 301 redirect from each old URL to its new equivalent passes the ranking across. This is mechanical work: crawl the old site, list every URL, map each to its replacement, test the map before launch. It is tedious and it is the single biggest reason a migrated site loses traffic. A migration quote that does not mention a redirect map is a quote for half the job.
Migrate Wix to WordPress: what moves and what does not
Wix exports blog posts as an RSS feed, and that is the extent of the built-in export. Pages, images in galleries, forms, bookings and store products have to be extracted by other means, usually a crawler that pulls the rendered HTML and downloads the media. The design does not export at all. Wix sites are built in Wix's own editor and there is no path from that editor to a WordPress theme, so the design is rebuilt from scratch, using the old site as a visual reference.
The Wix trap is URL structure. Wix generates URLs like /post/my-article-title for blog posts and /product-page/product-name for products, and image URLs on Wix's own CDN that stop working when the subscription ends. Every one of these needs a redirect, and the media needs to be downloaded and rehosted before the old site is cancelled, not after. We have seen business owners cancel Wix on launch day and lose every image on their new site the same afternoon.
Migrate Squarespace to WordPress: cleaner export, same design problem
Squarespace is more cooperative. It exports pages, blog posts and gallery text as a WordPress-format XML file, which the WordPress importer reads directly. Media still references Squarespace's CDN and must be fetched and rehosted. Commerce products do export to CSV. Like Wix, the design does not export. Squarespace templates are Squarespace's property and there is no conversion to a WordPress theme, so the design is rebuilt.
The Squarespace trap is what the XML leaves out. Index pages, which are Squarespace's stacked landing page layout, export as a list of sub-page links rather than as a page. Product pages export as posts with no product data, so the store needs the CSV import into WooCommerce separately. Summary blocks, which pull content from other sections, come across as empty. If a site relies heavily on these, the imported content looks complete at a glance and is missing the parts that made the site work. A content audit before import, comparing the old site page by page to the export, catches this in an hour and saves a week.
Magento to WooCommerce migration: the data is yours, the model is different
Magento is self-hosted and open source, so unlike Wix and Squarespace, you own the database and can export everything: products, categories, customers, orders, reviews, configurable product relationships. Magento 1 reached end of life in June 2020, which means stores still on it are running software with no security patches, and that is usually the reason a business finally moves. The migration is a data transformation job rather than a scraping job.
The Magento trap is the product model. Magento's configurable products with attribute sets, tiered pricing, customer groups and multi-store setups do not map one to one onto WooCommerce's simple and variable products. A configurable product with three attributes and forty combinations becomes a WooCommerce variable product with forty variations, which works, but tier pricing per customer group has no native WooCommerce equivalent and needs either a plugin or custom code. Decide which pricing rules the business still uses before migrating them all. Most stores find they were carrying rules nobody had touched in years.
Customer passwords are the other question. Magento stores password hashes, and WooCommerce can be taught to verify those hashes on first login and rehash them, so customers keep their passwords. That takes custom code on the WooCommerce side but is well worth it for a store with thousands of accounts. This is a WooCommerce development task, not a plugin setting.
BigCommerce to WooCommerce migration: the Shopify pattern
BigCommerce is a hosted platform with an app marketplace and app fees, the same commercial model as Shopify, and a migration from it looks like a Shopify migration. Products, categories, customers and orders export to CSV or through the API. The theme does not transfer, though BigCommerce themes are closer to standard HTML and CSS than Wix or Squarespace, so the rebuild has a better reference. Customer passwords do not export, because no hosted platform exports them. Customers will reset their password on first login to the new store, and the migration plan should include the email that tells them to expect it.
The BigCommerce trap is the apps. Every function the store gets from a marketplace app, such as subscriptions, product options, bundles, wholesale pricing, reviews, needs a WooCommerce equivalent, and the data inside those apps often does not come out in the platform export. Subscription records in particular live with the app and the payment processor, and card tokens do not transfer between platforms, so active subscribers have to re-enter payment details. List the apps, find out where each one's data lives, and decide per app whether to migrate, replace or drop it. Our Shopify to WooCommerce migration service covers BigCommerce with the same process, from $2,500, and the price is driven by the number of apps far more than by the number of products.
Platform by platform at a glance
| Source | Exports | Does not export | The trap |
|---|---|---|---|
| Wix | Blog posts (RSS); everything else by crawling | Design, forms, bookings, media hosting | URL patterns and CDN images that die on cancellation |
| Squarespace | Pages and posts (XML), products (CSV) | Design, index pages, summary blocks | Export looks complete and is not |
| Magento | Everything, from the database | Nothing, but much of it maps badly | Product model and customer-group pricing |
| BigCommerce | Products, customers, orders (CSV or API) | Passwords, theme, app data, card tokens | Marketplace apps with no export |
What a migration costs
A content site from Wix or Squarespace is priced as a WordPress build plus the import and redirect work, and a custom WordPress website starts at $4,000 on our pricing page. A store migration from Magento or BigCommerce starts at $2,500 for the migration itself, with the theme build and any custom pricing logic quoted separately against a written scope. Most of our projects land between $1,500 and $6,000. The variables that move a quote are the number of apps or extensions to replace, the number of URLs to redirect, and how much of the old site's design needs to be rebuilt rather than redesigned.
Common questions
Will we lose search rankings when we migrate?
Not if every indexed URL redirects to its equivalent and the new pages carry the same titles, headings and content. Rankings drop when redirects are missing or point everything at the home page. Expect some movement in the first few weeks as Google recrawls, then a return to the previous position if the redirect map is complete.
Can customers keep their accounts and passwords?
From Magento, yes, with custom code that verifies the old password hash on first login. From Wix, Squarespace and BigCommerce, accounts move but passwords do not, and customers reset their password once. Order history moves on all four platforms if it is exported and imported against the same customer email.
How long does the old site need to stay up?
Until the new site is live, the redirects are tested and all media has been rehosted. Keep the old subscription for at least a month after launch so that anything missed can still be retrieved. Cancelling on launch day is the most common self-inflicted wound in migrations.
Do we need a developer, or can a migration plugin do it?
Migration plugins move the data they know about and skip everything else, which is the app data, the redirects and the design. For a small blog they are fine. For a store with customer accounts, pricing rules or marketplace apps, the plugin is the first ten percent of the work.
Next step
Tell us which platform you are leaving and roughly how many products, pages and apps you have, through start a project, and the developer who would run the migration will reply with what moves, what does not, and a price.
Want a senior developer to look at your site?
Tell us what you need. You get a written scope and a fixed price, usually within one business day.


