Magento → Shopify · product modelling
Magento configurable products to Shopify variants.
This is where a lot of Magento migrations quietly go wrong. Magento’s configurable and bundle products don’t map one-to-one to Shopify variants, and big catalogues can blow past Shopify’s limits if you don’t plan the model first. Here’s how the mapping works and how to split products before they break your build.
Quick answer
A Magento configurable product maps to a Shopify product, and each child simple product becomes a variant, with attributes like size and colour as options. Shopify allows up to 2,048 variants per product, so high-cardinality catalogues can exceed the limit — the fix is to split the product, move non-purchasable attributes to metafields, or model kits with a bundle app. Decide the model before you import, not after.
How each Magento product type maps
| Magento | Shopify target | How to handle it |
|---|---|---|
| Simple product | Product with one variant | One sellable SKU becomes one variant. The cleanest, most direct map. |
| Configurable product | Product + variants + options | The parent becomes the Shopify product; each child simple becomes a variant. Attributes like size and colour become options. |
| Bundle / grouped product | Bundle app or merchandising | No 1:1 equivalent. Re-model as a kit (bundle app), a set of linked products, or a curated collection — a design decision, not a copy. |
| Non-purchasable attribute | Metafield | Material, care instructions, specs and filters that don’t create a buyable combination belong in metafields, not options — this is how you avoid variant explosion. |
When products “explode” — and how to split them
Variants multiply. A shirt with 8 colours × 6 sizes is 48 variants — fine. Add 4 fits and 3 sleeve lengths and you’re at 576; a few more attributes and you’re over Shopify’s 2,048-variant ceiling. Magento happily stores this; Shopify won’t import it. Three ways to fix it:
- Split into multiple products. One product per colour (or per collection line), with size as the variant. Cleaner product pages, better for SEO, and it sidesteps the limit.
- Move non-purchasable attributes to metafields. If “material” or “care” doesn’t create a separately-buyable SKU, it shouldn’t be an option — put it in a metafield and surface it on the page.
- Model kits with a bundle app. Magento bundle and grouped products become curated kits or linked products, not thousands of native variants.
Not sure how many of your products are at risk? Our migration calculator flags variant-limit risk from your largest product.
Frequently asked questions
How do Magento configurable products map to Shopify?
A Magento configurable product is a parent with child “simple” products for each option combination. On Shopify, the parent becomes the product and each child becomes a variant, with attributes like size and colour becoming options. Attributes that don’t create a buyable combination (material, care, specs) should become metafields instead of options — that keeps your variant count under control.
What is Shopify’s variant limit?
Shopify allows up to 2,048 variants per product. Magento configurable products with several high-cardinality options — for example colour × size × length × fit — can multiply past that limit once mapped to Shopify variants. Any product that would exceed the limit must be split or re-modelled before import.
How do I fix a product that exceeds the variant limit?
You have three main options: split the product into several products (for example one product per colour, with size as the variant); move non-purchasable attributes to metafields so they stop multiplying combinations; or model complex kits with a bundle app instead of native variants. The right choice depends on how customers shop and how you merchandise.
Will splitting products hurt my SEO?
Not if it’s planned. When you split a configurable product into several Shopify products, set up 301 redirects from the old Magento URL to the most relevant new product, use canonical tags sensibly, and keep the core keyword in each product’s title. Done properly, you keep your rankings and often improve them with cleaner, more specific product pages.
Should I decide this before or after importing?
Before — always. Your product-page UX, filtering and even theme layout depend on how products are modelled. Deciding variant structure after the catalogue is already live means a painful rebuild. Model first, validate in a dev store, then import.
An official Shopify Select Partner
Vetted by Shopify and trusted by brands across the US, UK, Canada, Singapore, UAE, Australia and India — with a money-back guarantee and on-time delivery on every build.
Migrating a big Magento catalogue?
We model your products before we import — so nothing explodes past Shopify's limits mid-build. Get a fixed quote.