Magento configurable products become one Shopify product with variants. Each child simple product turns into a variant with its own SKU, stock and price, within Shopify’s limit of three options and 2,048 variants per product. Custom options go one of two ways: options that change the price become variants or run through an options app, and the rest become line item properties.

How configurable products and their children map

A Magento configurable product is a parent with a child simple product for each combination, and the children usually have their own SKUs, stock, prices and sometimes their own URLs. On Shopify they become one product with variants.1 The attributes that create the combinations in Magento (size, color, finish) become the option names on Shopify, and the child records supply the variant data.

The mistake to avoid is in how the children are treated. One trap is importing children marked “not visible individually” as separate products, which fills the store with orphans and duplicates. The opposite trap is merging children that were sold individually and do need their own product pages.1 That’s why we read the visibility flag and the URL rewrites for every child before deciding.1 Children that had their own URLs also need a 301 redirect to the parent product, or to their own page if they get one.

The variant ceiling used to be a reason to stay on Magento. In October 2025 Shopify raised the limit from 100 to 2,048 variants per product,1 so most large configurable products now fit without being split.

What happens to custom options

Magento custom options (dropdowns, checkboxes and text fields added to a single product) have no direct equivalent on Shopify. They become variants, or line item properties through the theme or an app, and as a rule of thumb, options that change the price need variants or an options app.1 Which route is right depends on what the option does:

  • An option that changes the price, has its own SKU or needs its own stock becomes a variant.
  • Free text such as engraving or a gift message becomes a line item property, so it shows on the order line, carries through to fulfillment, and can be validated before the item reaches the cart.2
  • A priced add-on that doesn’t need its own stock can run through an options app.

Options apps aren’t always the easy answer. On projects like this, we have found that when most products share the same set of sizes, options apps add line-item notes rather than real variants, charge for priced add-ons and lose per-size SKUs.3 Real variants keep everything native.

When a product has more than three options

Magento puts no practical limit on how many options a product can have, but Shopify allows three. Options also multiply quickly: three independent choices of a dozen values each already approaches the variant cap. For pick-several or made-to-measure products, dropdowns saved as order notes (line item properties) usually scale better than variants.4 We handle products that break Shopify’s limits the same way on every platform: we restructure them during the audit, and the common fix is to move the least-used option to a line item property or split the product into two.5

What decides the answer for your store

Three things decide how your catalog maps. The first is how your configurable children are set up: whether they’re visible individually, whether they have their own URLs, and whether they’re priced differently from the parent. The second is which of your custom options change the price or need their own stock. The third is whether any product needs more than three options. Your attribute sets matter too. If you want your layered navigation to work as filters on Shopify, filterable attributes must become metafields first. We list every custom attribute before we migrate, ask what each one does on the storefront, and decide whether it becomes a metafield, a tag, a product type or nothing.1 A product-by-product review of these points is what turns your Magento catalog into a clean Shopify one.

Sources

  1. Magento to Shopify Migration Guide (2026): Cost & Timeline Migration guide
  2. Checkout From our project notes
  3. Apps From our project notes
  4. Theme and storefront From our project notes
  5. Webflow to Shopify Migration Guide (2026): Full Move or Split Migration guide

“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.

Want it answered for your store?

Tell us about your store in ten minutes. We come back within one business day with an honest assessment, a recommended track and a fixed price.