Most WooCommerce variable products fit without changes. Shopify allows three options per product and up to 2,048 variants1, and in our experience simple products, most variable products, categories (as collections), customers with addresses, and order history move cleanly2. The products that need restructuring are the ones with more than three attributes, more than 2,048 combinations, or add-ons that change the price.
Which products will need restructuring
There are two kinds of product to look for. The first is variable products with more than three attributes or more than 2,048 combinations2. The variant ceiling is rarely the problem now; since October 2025, Shopify has allowed up to 2,048 variants, so most groups fit3. The three-option limit is more often what forces a change.
The second is product add-ons that change the price. Shopify has no native price modifier on a non-variant option, so those add-ons become variants, add-on products or an options app2. If your store uses an add-ons plugin alongside variations, look at those products first, because the plugin’s price rules sit outside WooCommerce’s own variation data.
Pricing logic is a quieter risk. WooCommerce variable products (with multiple attributes like size, color and material) are structured differently from Shopify variants, and complex SKU logic and pricing often break during migration4.
What happens to attributes that don’t fit
We sort each attribute by what it does, not by where it sits in WooCommerce, and we use the same approach on every platform we migrate:
- Attributes that identify a stocked item, such as size, color or finish, become options, and each combination becomes a variant with its own SKU, price, stock and image1.
- Free-text attributes such as engraving or a customer reference become line item properties in the theme, so the text still arrives on the order1.
- Checkbox add-ons with a price (gift wrap, installation kits) become add-on products or bundles, so the price is charged correctly and reported on its own1.
- Specifications that describe the product become metafields with definitions, which the theme displays and Search and Discovery can use as filters1.
A product with more than three real options is split, or one option moves to a metafield5. We show you the proposed structure for each affected product family before anything is imported1.
Traps we see on real projects
A product options app is not always the right fix. When most products share the same set of sizes, an options app is usually the wrong tool: it adds line-item notes rather than real variants, charges for priced add-ons and loses per-size SKUs6. In that case, a draft template product with the standard sizes and prices, duplicated for each new item, keeps everything native6.
Turning add-ons into products creates two smaller issues. Add-ons sold across many products, such as samples or gift bags, are often a single tracked SKU, and if it sells out on a busy sale day it can affect every page that offers it7. We either keep that SKU stocked or let it keep selling when out of stock. Also, one-click add-to-cart on collection or search cards can bypass required choices from a product-options app, such as a size8, so on those products we send the quick-add button to the product page instead.
On every WooCommerce migration, we audit all variable product configurations, recreate them as Shopify variants with proper pricing and inventory, and test 100% of attribute combinations before launch4.
What decides it for your store
For your catalog, the answer depends on three things: how many attributes your most complex products use to create variations, whether any single product goes past 2,048 combinations, and whether a plugin adds paid extras outside the variations. If all your variable products use three attributes or fewer and their prices are set on each variation, they will most likely move one to one. If you sell configurable products with four or more attributes or priced add-ons, plan for a restructure, and agree on that structure before launch rather than discovering the need after import.
Sources
- Miva to Shopify Migration Guide (2026): Cost & Process Migration guide
- WooCommerce vs Shopify (2026): Costs, Fees and Verdict Comparison
- CS-Cart to Shopify Migration Guide (2026): Cost & Steps Migration guide
- WooCommerce to Shopify Migration Guide (2026): Cost & Timeline Migration guide
- osCommerce to Shopify Migration Guide (2026): Cost & Steps Migration guide
- Apps From our project notes
- Inventory From our project notes
- B2B and wholesale From our project notes
“From our project notes” are short, anonymised lessons from migrations we have run. They describe what we typically see, not a guarantee for every store.