WordPress Multisite running WooCommerce is a specific architectural pattern where multiple storefronts share a single WordPress installation — but each site has its own products, orders, and customers. Migrating this to Shopify requires understanding both what Multisite does and what Shopify's multi-store architecture looks like.

What is WordPress Multisite with WooCommerce?

WordPress Multisite creates a network of sites under one WordPress installation. Each site in the network can run WooCommerce independently, sharing the same server and WordPress codebase but operating as separate stores with their own:

Product catalogs (each site has its own WooCommerce instance)
Orders and customers
Settings, payment gateways, and shipping rules
Themes and plugins (some shared, some per-site)
Domains or subdomains (e.g., en.store.com, fr.store.com)

Common WooCommerce Multisite use cases

Geographic stores: Separate stores per country (different currencies, tax rules, language)
Brand stores: Multiple brands under one parent company, each with its own store
Wholesale + retail: Public store and private B2B store on separate sites
Franchise stores: Each franchisee has their own store with a shared product catalog
White-label stores: Agency running multiple client stores on one install

Shopify's multi-store architecture

Shopify does not have a native Multisite equivalent. Instead, Shopify's model for multiple stores is:

Option 1: Multiple separate Shopify stores

Each site becomes its own Shopify store with its own subscription, admin, domain, and product catalog. This is the most straightforward approach:

Each site migrates independently
Completely separate admin UIs, billing, and analytics
No shared products natively (apps or manual sync required)
Cost: separate Shopify subscription per store

Option 2: Single Shopify store with Shopify Markets

If your Multisite was primarily used for geographic localization (different languages/currencies per country), Shopify Markets consolidates this into one store:

One product catalog, multiple market configurations
Per-market: currency, language (Translate & Adapt or Weglot), domain, pricing
Simpler to manage, lower cost than multiple stores
Limitation: all markets share the same product catalog and checkout flow

Option 3: Shopify Plus multi-store

Shopify Plus ($2,300+/month) includes up to 9 expansion stores (additional stores at $250/month each):

Multiple stores under one Plus account, centralized admin
Shared product catalog via Shopify Markets or Shopify's multi-store sync
Each store can have different branding, currencies, and shipping
Better for enterprise Multisite setups with complex per-brand requirements

Assessing your Multisite structure

Before choosing a migration approach, answer these questions:

Question	→ Shopify approach
Each site sells the same products in different languages/currencies?	Single Shopify store + Shopify Markets
Each site is a completely different brand with different products?	Separate Shopify stores
Sites share some products but have unique collections?	Separate Shopify stores + manual product sync or app (Syncio, Stock Sync)
More than 3 stores + enterprise budget?	Shopify Plus multi-store
Wholesale + retail separation?	Shopify Plus B2B (one store with B2B company accounts)

Migrating each site independently

Regardless of the Shopify architecture you choose, each WooCommerce site migrates as an independent migration:

Per-site migration steps

Connect to the site's WooCommerce API: In WordPress Multisite, each site has its own WooCommerce API endpoint. The URL for sub-sites is typically: https://example.com/site-name/wp-json/wc/v3/ for subdirectory networks, or https://subsite.example.com/wp-json/wc/v3/ for subdomain networks. Create API keys in each site's WooCommerce → Settings → Advanced → REST API panel.
Import products: Use k-sync to import from each site's WooCommerce API into separate k-sync projects (one project per store)
Validate and push: Each project gets pushed to its target Shopify store

WooCommerce REST API URLs in Multisite

The WooCommerce REST API URL structure in Multisite:

Main site: https://example.com/wp-json/wc/v3/
Subdirectory sub-site: https://example.com/shop2/wp-json/wc/v3/
Subdomain sub-site: https://shop2.example.com/wp-json/wc/v3/
Mapped domain sub-site: https://shop2.com/wp-json/wc/v3/

Shared product catalogs: syncing across Shopify stores

If your Multisite sites share products (e.g., a parent company with multiple brand stores selling some of the same products), Shopify doesn't have native cross-store product sync. Options:

Syncio: Syncs products and inventory between multiple Shopify stores in real time. Best for franchise-style setups where stores share a product catalog but manage orders separately.
Stock Sync: Sync inventory levels across stores via Google Sheets or CSV. Less real-time than Syncio but cheaper.
Shopify Plus + Markets: If you move to a single-store architecture, Markets handles product availability per region natively

Domain migration for Multisite stores

Multisite DNS configurations vary. Common patterns and their Shopify equivalents:

Multisite URL structure	Shopify equivalent
example.com/en/ (main site)	Shopify store at example.com with /en/ locale via Shopify Markets
fr.example.com (subdomain per country)	Separate Shopify store at fr.example.com, or Shopify Markets domain per market
example.fr (separate domain per country)	Separate Shopify store per domain, or Shopify Markets with domain per market
brand1.com + brand2.com (separate brands)	Separate Shopify stores, each with its own domain

SEO considerations for Multisite migration

Each sub-site has its own URL structure, indexed separately by Google. When migrating:

Set up 301 redirects per site: old sub-site URLs → new Shopify URLs
Update hreflang tags: if sites are language variants of each other, hreflang needs to reflect the new URL structure on Shopify
Submit each domain separately in Google Search Console
If consolidating multiple sites into one Shopify store + Markets, Google will see this as a domain merge — expect 4–8 weeks of ranking flux per domain

Timeline for Multisite migration

Multisite migrations take proportionally longer than single-store migrations:

Each store follows the same migration process independently
Allow time for coordinating DNS changes (ideally do all stores in the same maintenance window to avoid split inventory)
Shopify account setup: if creating multiple stores, set them all up before migration day
Testing: each store needs its own full test pass before DNS cutover

Multisite migration checklist

Map your Multisite network: list each sub-site, its domain, product count, and unique characteristics
Decide Shopify architecture: separate stores, one store + Shopify Markets, or Shopify Plus
Create API keys for each WooCommerce sub-site
Create a separate k-sync project for each sub-site
Import products from each sub-site independently
Validate and configure each project's mappings
Create Shopify stores (one per sub-site, or one centralized store)
Push each project to its target Shopify store
Set up 301 redirects per store (old sub-site URLs → new Shopify URLs)
Configure Shopify Markets if consolidating language/currency variants
Update hreflang tags if applicable
Coordinate DNS changes for all stores in a single maintenance window
Verify each store independently after DNS propagation
Submit all domains to Google Search Console

The main difference between Multisite and single-store migrations is multiplying the work: each store needs its own connection, mapping configuration, validation, and DNS change. The per-store process is identical — it's the coordination that adds complexity.

Migrating a WooCommerce multisite to Shopify (2026)