Product Variants, Options & SKUs

Why Product Variants, Options & SKUs needs Custom Migration

Product variants, configurable options, and SKU rules rarely map one-to-one between ecommerce platforms. Magento configurable products, Shopify variant options, WooCommerce attribute combinations, and PrestaShop combinations each store relationships differently. When the default wizard cannot preserve option values, variant pricing, or SKU uniqueness, Cart2Cart Custom Migration adapts export and import logic so your catalog remains sellable and sync-ready.

Who this customization is for

• Merchants moving complex catalogs between Magento, Shopify, WooCommerce, PrestaShop, OpenCart, and similar carts
• Brands whose ERP, 3PL, or marketplace feeds depend on stable SKUs and option codes
• Stores using multi-attribute variants, custom options, or non-standard option types
• Teams that already saw incomplete variant trees or broken swatches in a Demo Migration

Common use cases

• Multi-attribute variants (size + color + material) with different option types on source and target
• SKU schemes that must stay unique across simple, variant, and parent products
• Variant-level pricing, compare-at price, weight, barcode, or image fields the standard mapping skips
• Option sets used by themes, apps, or ERP feeds that depend on exact attribute codes
• Rebuilding Magento custom options or bundle-related choices into Shopify/WooCommerce-compatible structures

What Cart2Cart customizes

Migration Experts remap option types, preserve or transform SKUs, align variant inventory with the destination model, and validate sample products before Full Migration. We document edge cases (shared SKUs, orphan options, required attributes) and tune the pipeline so storefront filters and swatches resolve correctly—not just so products “import.”

Platform considerations

Magento often uses configurable + simple children; Shopify uses options/variants with limits on option count; WooCommerce relies on attribute taxonomies and variations; PrestaShop uses combinations. Custom Migration bridges those models, including cases where the target cannot support the same option depth and a controlled rebuild is required.

Note: The Target platform may require installing additional apps, plugins, or add-ons when a capability is not available by default. Custom Migration can map and import the data, but those Target-side apps/plugins often need to be installed and configured so the feature works in admin and on the storefront.

The best way to make sure everything is mapped correctly is to run a Demo Migration with your real Source platform data, then carefully check how entities look on the Target store before Full Migration.

Checklist for evaluating this customized migration

• List option attributes on source vs target (types, required flags, sort order).
• Confirm SKU uniqueness rules for parents, variants, and simple products.
• Identify variant-level fields to keep (price, stock, barcode, weight, image).
• Spot-check 3–5 complex products in Demo Migration before Full Migration.
• Verify storefront filters/swatches still resolve after import.

How to apply for this customization

1. Open the Custom Migration directory or Schedule a Call.
2. Share source and target carts, catalog size, and 2–3 example products with complex options.
3. Note any SKU or barcode rules required by ERP, 3PL, or marketplace channels.
4. Run a Demo Migration where possible, then we scope custom variant/SKU rules and timeline.

Self-service Additional Options vs Custom Migration

Several self-service Additional Options in the Cart2Cart Migration Wizard cover common variant and SKU needs. Use Custom Migration when option models, SKU rules, or attribute combinations go beyond those checkboxes.

• Create product variants from option/attribute combinations — Self-service: Turn supported attribute combinations into target variants during a Wizard migration. Choose Custom Migration when: Custom Migration when option types, multi-attribute depth, or platform limits need remapping or a rebuild.
• Migrate product SKUs — Self-service: Carry SKUs (and related price fields where supported) in the Wizard for eligible pairs. Choose Custom Migration when: Custom Migration for uniqueness rules, parent/child SKU schemes, or ERP-critical identifier transforms.

Availability depends on your Source → Target pair—confirm checkboxes in the Migration Wizard Entities / Additional Options step. See the Additional Options guide and Additional Options FAQ for pair-specific details. If Wizard options are not enough, schedule a Custom Migration call.

Already ran a self-service migration?

Yes—you can still apply this Custom Migration after a Wizard (self-service) run. Cart2Cart can restart migration with the customized rules; the Target store typically needs Clear current data on Target Store before Migration (or an equivalent cleanup of the entities from the previous self-service migration) so customized results are not mixed with the old import. Share your Source/Target carts and what already moved—Migration Experts will confirm the safest clear-and-rerun plan before Full Migration. Schedule a call if you already completed a Demo or Full Wizard migration and need customization next.

Case studies from real Custom Migrations

Cart2Cart Migration Experts have delivered custom work related to Product Variants, Options & SKUs across 204 recorded customization projects spanning 55 Source→Target platform pairs. Below are pairs we see most often, the entities typically involved, and sample data volumes when available.

Platform pairs already in focus

• WooCommerce → Shopify — 35 customization projects
• Magento → Shopify — 34 customization projects
• Magento → WooCommerce — 21 customization projects
• PrestaShop → Shopify — 13 customization projects
• BigCommerce → Shopify — 11 customization projects
• Magento → Magento — 7 customization projects

Entities commonly customized

• Products — seen in 135 related projects
• Customers — seen in 78 related projects
• Orders — seen in 78 related projects
• Categories — seen in 57 related projects
• Coupons — seen in 15 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 12.6K records, with larger builds reaching roughly 171.9K at the 90th percentile and peaks near 2.6M. Exact counts depend on products, customers, orders, and related entities in scope.

Sample projects

• BigCommerce → Shopify — entities: Coupons 2.2M, Orders 302.3K, Customers 141.3K, Products 8.5K — total volume ~2.6M
• Shopify → BigCommerce — entities: Blogs, CMS pages, Products — total volume ~719.1K
• Magento → Shopify — ~371.3K records migrated
• Magento → WooCommerce — entities: Orders 175.5K, Customers 62.1K, Products 1.4K, Reviews 336 — total volume ~239.4K

Every store is different—share your Source/Target carts and entity scope on a Migration Expert call and we will estimate a similar Custom Migration path.

What we need to scope variant & SKU customization

Variant trees, option types, and SKU rules are rarely identical from store to store—even on the same platform pair. Magento configurables, Shopify option limits, and WooCommerce attributes each encode relationships differently, so we must inspect your catalog structure before quoting effort.

The most reliable path is temporary access to a staging (preferred) or production admin/API so Migration Experts can sample complex products, option sets, and SKU collisions. If live access is not possible, you can provide a database backup dump for offline analysis; dump review often requires a refundable deposit because of the engineering time to restore and inspect the schema. Share 2–3 worst-case SKUs up front to accelerate scoping.

FAQs

Will every Magento configurable become a Shopify product with variants?

In most cases yes, but option limits and attribute types may require remapping or splitting. We confirm feasibility on your sample set first.

Can you keep our existing SKUs?

Often yes, when the target allows unique SKUs at the required level. If not, we define a controlled transform and document it for your integrations.

Do we need Custom Migration if Demo variants look fine?

If Demo already preserves options, pricing, and SKUs you care about, standard migration may be enough. Custom work is for gaps Demo exposes or known platform mismatches.

Ready to protect your product structure during platform migration? Book a call with a Migration Expert.