Skip to content
Browse documentation

Migrating from WooCommerce

Bring a WooCommerce (WordPress) store into NanoSite with one of three sources. All three share the same ids — the product and variation ids WordPress assigns — so you can mix them without duplicates. See Migrating your store for how imports work in general.

Store URL (no login)

Enter your store address (your-store.com). NanoSite reads the public WooCommerce Store API (/wp-json/wc/store/v1) that WooCommerce stores expose publicly.

Brings: published simple and variable products with their variations, regular and sale prices, images, and categories with their products.

Doesn't bring: stock quantities (in-stock variants import as untracked; out-of-stock products import tracked at 0), draft and private products, and customers. Use REST API keys for those.

Try it without signing in on the WooCommerce migration page.

REST API keys (most complete)

A read-only key pair from WooCommerce:

  1. In WordPress admin, open WooCommerce → Settings → Advanced → REST API.
  2. Click Add key, give it a description (e.g. "NanoSite import"), pick your user, and set Permissions to Read.
  3. Click Generate API key and copy the Consumer key (ck_…) and Consumer secret (cs_…).
  4. In NanoSite, choose WooCommerce → REST API keys, enter your store address (it must be https://) and paste both values.

Brings: everything the store URL brings, plus stock quantities and backorder settings, draft, pending and private products, every variation, customers with their shipping (or billing) address, and the store currency.

The keys are sent only over https, as an HTTP Basic auth header, never in the URL. They're stored encrypted for the duration of the import and deleted when it finishes. Revoke them in WooCommerce afterwards if you like.

Product CSV export

Use WooCommerce's built-in exporter: Products → Export, leave "Export all columns" selected, and click Generate CSV. WooCommerce has no built-in customer export, so customers come over only with REST API keys. See Importing CSV files for details.

How WooCommerce data maps

WooCommerce NanoSite
Simple product Product with a single variant
Variable product + variations Product with options (from the variation attributes) and one variant per variation
Sale price Price, with the regular price as compare-at
Manage stock + stock quantity Tracked inventory; "use parent's stock" variations take the product's quantity
Backorders: "Allow" or "Allow, but notify" Allow backorder
Categories (nested) Flat collections; the parent path (e.g. Clothing > Tops) is kept in the collection's metadata
"Uncategorized" Skipped (it's WooCommerce's placeholder)
Published / draft / private Published / draft / draft

Not imported: grouped and external/affiliate products (the preview tells you how many were skipped), a variation attribute set to "Any …", product reviews, and WooCommerce Subscriptions data.

Troubleshooting

  • "Doesn't look like a WooCommerce store" — the address didn't answer /wp-json/ with the WooCommerce namespaces. Check the domain (use the one your shop is on, not a separate blog), and that the WordPress REST API isn't disabled.
  • "Refused the request" / blocked — a firewall, security plugin (e.g. Wordfence) or bot protection blocked NanoSite. Allow the request, use REST API keys, or upload a product CSV instead.
  • "Rejected the API keys" — the key or secret is wrong, revoked, or doesn't have Read permission.
  • Images skipped — only https:// images are downloaded. The preview warns about any http:// image URLs; switch your site to https or re-upload those images in NanoSite.
  • Slow or throttled hosts — NanoSite backs off and retries when your host answers "too many requests", so large catalogs on small hosting plans just take longer.