Migrating from Wix to Swell - A Complete Guide

Wix sells time-to-launch, and it delivers. A merchant can design a storefront, load a catalog, and take payments in an afternoon without writing code. The trade is architectural: every Wix site runs on Wix's servers, the checkout cannot be restyled from the editor, catalog structure stops at 6 options and 1,000 variants per product, and premium plans cover a single site. Those ceilings are documented and mostly not removable at any price. The full list of Wix ecommerce limitations is worth reading either way; merchants who hit several at once tend to evaluate headless commerce platforms like Swell, where the backend stays managed but the storefront, checkout, and data model open up to code.

Leaving Wix differs from leaving WooCommerce or Shopify in one decisive way: there is no site export. Wix states plainly that because it is a SaaS solution, a site must run on Wix's servers. The storefront gets rebuilt rather than moved, and the data that does travel comes out through a narrow pipe. This guide covers what exports and what does not, why subscribers are the hardest part of the cutover, how to protect rankings, the migration paths on the Swell side, and what Swell costs.

Key Takeaways

• Wix publishes no site export. Product, contact, and order CSVs travel, along with whatever the Wix Stores and CMS APIs expose, but the storefront is rebuilt.
• Product exports cap at 5,000 rows per CSV file, that file carries no SEO or URL slug columns, and digital products cannot be exported at all.
• Active subscribers have to repurchase. Wix requires cancelling every active subscription before switching payment providers, making this a re-consent campaign, not a data transfer.
• SEO metadata has no export path: Wix confirms title tags and meta descriptions cannot be exported to CSV or any other format.
• Product images are referenced by URL and served from Wix's CDN, so every image needs rehosting before the Wix plan is cancelled.
• Swell publishes no Wix-specific migration guide as of publication. Its WooCommerce and BigCommerce guides document the pattern to adapt.

Understanding Swell: What Makes It a Wix Alternative?

Swell is an API-first commerce platform: a managed backend exposing every data model through a unified Backend API, the same API powering Swell's own dashboard and hosted checkout. Where Wix assembles a store inside a site builder, Swell ships commerce primitives as one system.

Swell's Core Platform: Commerce Primitives, Not a Site Builder

Swell's feature set covers ground Wix either caps or routes through its App Market: unlimited variants and options, native multi-store architecture, marketplace models with split payments, and B2B tooling including customer group pricing, payment terms, and quotes. A model editor adds custom fields to any data model, which matters here because Wix product modifiers and CMS collection fields need somewhere structured to land.

The Headless, API-First Advantage

Headless architecture separates storefront from backend, so a Swell store can run hosted or on a custom frontend in any framework, all consuming the same APIs in REST or GraphQL. The contrast with Wix Headless is instructive: Wix exposes commerce APIs but still redirects shoppers to a Wix-hosted checkout page, so the transactional core never leaves Wix.

Why Consider Swell: Key Differentiators from Wix

Checkout: A Sealed Component Versus an API

Wix's documentation is direct: the checkout page cannot be customized from the editor. Merchants adjust dashboard settings such as form fields and policy checkboxes; design and layout stay fixed, and Velo code does not unlock them. That forecloses conversion optimization where it pays best. Swell inverts the arrangement: a hosted checkout works immediately, and a Checkout API lets developers build fully custom checkout and payment flows on the same APIs behind it.

Catalog Ceilings Versus Unlimited Modeling

A Wix Stores product supports at most 6 options, 100 choices per option, and 1,000 variants, with a store-wide cap of 50,000 products. The variant ceiling is an open feature request Wix is still collecting votes on as of publication. Swell supports unlimited variants and options, so a catalog simplified for Wix's matrix can be modeled properly on arrival.

Per-Site Licensing and Gateway Choice

Wix premium plans are valid for a single site, so regional storefronts or multiple brands multiply cost and administration. Swell's multi-store architecture runs several storefronts and brands from one account.

Payment flexibility follows the same pattern. Wix Payments publishes a prohibited list barring products containing CBD or THC, tobacco, weapons, and adult content, and US merchants selling hemp-derived CBD must submit a declaration that permanently closes their Wix Payments account. Swell imposes no platform-level restrictions on lawful high-risk categories; its payment abstraction layer integrates Stripe, PayPal, Braintree, Authorize.Net, and Amazon Pay, and custom gateways can be built as extension apps. Platform policy and gateway policy stay separate questions.

Navigating the Migration: From Wix to Swell

Planning Your Data Transfer

Wix product data exports as CSV, capped at 5,000 rows per file, across columns spanning catalog, pricing, inventory, shipping, and options. Contacts export up to 50,000 at a time, site owner only; pick Regular CSV over the Google format, which drops subscription status, language, and created date. Order exports allow column selection and record purchase time in UTC, so timestamps need correcting before load. Variant-heavy catalogs are better served by the Stores Products V3 API. V3 and V1 coexist and are not backwards compatible, so a script should call the Catalog Versioning API to detect which version a store runs.

Several categories never leave. Reviews cannot be exported from Wix Reviews. Blog posts cannot be exported, and digital products support neither import nor export. Customer passwords have no export path, so a reset flow belongs in launch communications. Velo code is the item most often reported wrong: Wix Studio's Git Integration and Wix CLI for Sites stores site code in a clonable GitHub repository, so the files do come out. They bind to Wix-only modules such as wix-data, wix-stores, and $w, and to collections on Wix servers. The code is retrievable; it is not portable. Images ruin more migrations than anything else: Wix media is served from Wix's CDN and dies with the plan. Rehost every image before cancelling anything.

SEO carries the largest hidden cost. Wix confirms it is not possible to export SEO tags to a CSV file or any other document type, and the product CSV has no title tag, meta description, or slug column. There is partial relief: Wix generates product SEO from product data by default, using product name plus site name as the title tag and the description as the meta description, so anything still on defaults is reconstructible. Hand-tuned overrides are the genuine loss. Products default to /product-page/{slug} and posts to /post/{slug}, but the prefix is removable in SEO Settings, so audit live URLs. Direction of travel matters more than most guides admit: Wix's URL Redirect Manager governs only traffic to a site Wix serves, and works only with custom domains. Because the domain moves with the merchant, the redirect map belongs on the new host, at the storefront or hosting layer; Swell's storefront settings documentation lists no redirect manager as of publication.

Google's site-move guidance sets the rest: permanent redirects do not cause a loss in PageRank, they should stay live at least a year, and only one thing should change at a time, so migrate first and redesign later. The Change of Address tool applies to domain and subdomain moves, so a migration keeping the same domain is a path-only change that does not need it. Wix notes that transferring a domain away disconnects the Wix site, takes up to 7 days, and is blocked by a 60-day ICANN lock after registration or a registrant contact change.

Subscriptions are the hardest category, and the constraint comes from Wix. Product subscriptions require one of the 16 providers Wix lists as supporting recurring payments, and most of those restrict recurring charges to credit and debit cards. Wix's instruction for fulfilling subscriptions is unambiguous: switching payment providers means cancelling all active subscriptions, switching, then asking clients to repurchase. The identical rule applies to Pricing Plans. Records can move; the billing relationship cannot without customer re-authorization.

Migration Tools: The Paths That Exist

Swell does not publish a Wix migration guide as of publication. Its Developer Center covers Shopify, WooCommerce, and BigCommerce, and the pattern those three share is what a Wix migration adapts: a Node.js script running two API clients, one reading the source REST API and one writing to Swell, paginating 100 records at a time. Three details carry over. The hub prescribes a fixed order set by data dependencies: products, customers, orders, shipments, then subscriptions. Source identifiers are retained as custom fields, woocommerce_id in one guide and bigcommerce_id in another, which becomes wix_id here and reattaches orders to the right products and customers. And the $migrate flag skips validation, events, and webhooks, which is what lets orders retain original creation dates.

That flag carries one exception: Swell's guidance states it should not be used for subscriptions, which rely on subsequent events to be created properly. Two companion steps matter: adjusting date_trial_end so nothing bills on import and disabling subscription notifications during the load. Swell's subscription model supports daily, weekly, monthly, and yearly intervals with an interval_count multiplier, plus statuses covering pending, active, trial, pastdue, unpaid, canceled, and paid.

Two lower-effort paths round out the options. Swell's dashboard imports and exports products as CSV or JSON with a downloadable sample file, and customers import the same way, covering a few hundred SKUs without scripting. For larger transfers, FlexiPort is a partner migration service accepting CSV, JSON, or XML exports, the formats Wix produces, mapping products, customers, orders, and categories into Swell in one business day at $50 for a test migration and $240 for production. Wix supplies categorySlugs and primaryCategorySlug in the CSV, so the category mapping data travels with the export.

Swell Pricing: Finding the Right Plan

Breaking Down Each Swell Tier

Swell's pricing spans four self-serve plans, billed yearly: Starter at $29/month, Basic at $79/month, Standard at $299/month, and Unlimited at $2,250/month, plus a Custom tier above $10 million in annual sales. Each carries a revenue ceiling measured on trailing 12-month sales in USD, at $50K, $250K, $1M, and $5M respectively, with revenue-based fees applying only above that ceiling, at 2%, 1.5%, 1%, and 0.4%. Usage scales alongside: API requests from 100K per month to unlimited, storage from 1GB to unlimited, seats from 2 to unlimited, with overages at $5 per additional 100K API requests, 100K function calls, or gigabyte of storage. Monthly billing costs more, since those figures reflect the yearly option.

Reading the Numbers Against a Wix Stack

A Wix stack is a plan price plus App Market subscriptions for capabilities native elsewhere, plus a separate plan per additional storefront. Swell's subscription bundles the platform, hosting, and native features, with fees tied to revenue thresholds. Subscription merchants feel the difference first, since native subscriptions on every plan replace a recurring app bill, which Recharge's pricing illustrates on the comparable side of the market.

Technical Deep Dive: Swell's Developer-Friendly Ecosystem

Empowering Developers: APIs Built for Extension

Swell's developer surface centers on two APIs: the Backend API, with secret-key authentication and full CRUD access to every data model, and the Frontend API, offering partial CRUD scoped for browser contexts. Both REST and GraphQL are available. Because the Backend API is the same one powering Swell's dashboard and checkout, there is no gap between what the platform does and what a developer can script. For a team arriving from Velo, the mental model transfers while the boundaries change shape: no sealed checkout, and full CRUD on every data model rather than a fixed set of Velo modules. Swell's own ceilings are usage-based — API requests, function calls, storage and seats by plan — not capability-based.

Seamless Integrations: Building Your Tech Stack

Swell ships 40+ built-in integrations including Klaviyo, Omnisend, Mailchimp, ShipStation, Algolia, and Contentful, categories a Wix store covers through App Market installs. Two matter here: an email platform for the subscriber re-consent sequence and password-reset announcement, and a search provider to replace whatever the Wix site used. Because reviews and blog content cannot be exported, make those choices before launch so re-collection starts on day one.

Support, Reliability, and Global Reach

A Managed Platform With a Real SLA

The operational picture after migration stays closer to Wix than to a self-hosted stack. Hosting, scaling, and security patching stay the platform's responsibility, and at the top tier that commitment is contractual, with the Unlimited plan including a 100% uptime SLA.

Expanding Your Reach: International Commerce

Swell supports 230 currencies with explicit per-currency price rules and automatic conversion as the fallback, plus 170 languages. Wix, by contrast, converts prices automatically using market rates updated daily, and publishes no mechanism for setting a fixed price per currency. Tax automation is native through Avalara AvaTax and TaxJar, with custom tax rule groups by location and product.

Frequently Asked Questions

Can I keep my payment processor when leaving Wix?

Usually, for one-time payments. Swell supports Stripe, PayPal, Braintree, Authorize.Net, and Amazon Pay, so a Wix merchant already on Stripe or PayPal can connect that same account, since it belongs to the merchant rather than to Wix. Recurring billing is the exception: Wix requires cancelling all active subscriptions before a provider change, and Wix gives no path to port existing recurring authorizations to a new provider. Merchants staying on Stripe should ask Stripe about its account-to-account card migration process; everyone else should plan for customers to re-enter payment details.

Will migrating from Wix hurt my Google rankings?

Expect temporary fluctuation rather than permanent loss, provided redirects are handled properly. Google states that permanent redirects do not cause a loss in PageRank and recommends keeping them live for at least a year, with a few weeks of recrawling for a small to medium site. Two Wix-specific points matter: the redirect map goes on the new host, not in Wix's URL Redirect Manager, because the domain leaves with the merchant; and SEO metadata cannot be exported at all, so title tags and meta descriptions must be captured manually before the plan lapses.

Do my Wix subscribers transfer without re-entering their cards?

No, and this is the largest planning item in a Wix migration. Wix requires cancelling all active subscriptions before switching payment providers, then asking customers to repurchase. The records, meaning who subscribed to what, at what price, and since when, can be recreated in Swell using its billing intervals and status model, with date_trial_end adjusted so nothing bills on import. The relationship itself has to be re-earned, so budget for the email sequence and an incentive and run it as a launch milestone.

Can I move my Wix site design to Swell, or does it get rebuilt?

It gets rebuilt. Wix's SaaS architecture requires sites to run on Wix's servers, and the only alternative offered is embedding it elsewhere, which Wix does not support or control. Velo code files can be extracted through Wix Studio's Git Integration, but that code binds to Wix-only modules and to collections on Wix servers, so it does not run on another platform. On Swell, storefronts are fully customizable and can be hosted or built headless on any framework.

How long does a Wix-to-Swell migration take?

Swell publishes no duration benchmarks by catalog size. What it does publish is an operational limit: keep batch imports to no more than 1,000 records at a time, since larger batches can take hours and are more prone to interruption. Plan around that, plus two costs unique to Wix: manual SEO metadata capture, since no export exists, and the subscriber re-consent campaign, which runs on customer response time rather than engineering time. A 60-day ICANN domain lock can block the cutover outright, so check that first. For comparison, the WooCommerce and Shopify guides walk the same process on platforms with more export tooling.