Why Product Data Becomes the Migration Bottleneck
Most migration delays trace back to product data problems. Teams underestimate how messy their catalog has become over years of ad hoc updates, inconsistent processes, and platform-specific workarounds. When that data hits Shopify's structure, mismatches surface.
Cleaning data before migration is faster, cheaper, and less risky than fixing it after. This article covers the common pitfalls and how to avoid them.
Variant and Option Limits
Shopify has firm limits on product structure:
- Maximum 3 options per product (e.g., Size, Color, Material)
- Maximum 100 variants per product
- Option values must be text strings, not complex data
When you exceed limits
If your current platform allows 5 options or 500 variants, those products cannot migrate as-is. Options include:
- Splitting one product into multiple products
- Using apps that extend variant functionality
- Restructuring the product catalog to reduce variant counts
Identify limit violations early. Discovering them during import testing creates delays.
Option value inconsistency
Shopify expects consistent option names across related products. If some products use "Size" and others use "SIZE" or "Sz", filtering and navigation break.
Normalize option names before migration:
- Standardize capitalization
- Use consistent terminology (Small vs S vs SM)
- Remove leading/trailing spaces that look identical but are not
Image and Media Issues
Product images often cause unexpected problems during migration.
Broken image URLs
If your export references images by URL, those URLs must be accessible during import. Images hosted on your old platform may become unavailable after migration. Download and re-host images as part of the migration process.
Image quality and format
Shopify processes and optimizes images on upload. If your source images are low resolution, they stay low resolution. Migration is an opportunity to upgrade image quality if needed, but requires coordination with your content team.
Alt text and SEO
Image alt text affects accessibility and image search. Export alt text from your current platform and include it in the migration. Rebuilding alt text for thousands of images post-migration is tedious.
Pricing and Inventory Complexity
Simple pricing migrates cleanly. Complex pricing creates work.
Multi-currency pricing
If you maintain different prices per currency rather than using automatic conversion, plan how to represent this in Shopify. Shopify Markets handles multi-currency, but the configuration differs from legacy approaches.
Customer-specific pricing
B2B pricing tiers, customer group discounts, and negotiated pricing need translation into Shopify's model. Shopify Plus offers B2B features including price lists. Standard Shopify requires apps or workarounds.
For B2B pricing requirements, see B2B and wholesale on Shopify.
Inventory locations
Shopify supports multiple inventory locations natively. If your current system tracks inventory by warehouse, map locations before migration. Misaligned inventory data causes overselling and fulfillment confusion.
Custom Fields and Metafields
Most platforms store product data beyond the standard fields: specifications, warranty information, supplier codes, internal notes. Shopify uses metafields for this data.
Mapping custom fields to metafields
Metafields require definition before use. Plan your metafield namespace and key structure based on what custom data you need to preserve. Consider:
- Which custom fields are customer-facing vs internal
- Which fields need to appear in the storefront vs just the admin
- Data types: text, number, date, reference to other objects
Theme support for metafields
Migrating metafield data is only useful if your theme displays it. Standard themes have limited metafield support. Custom themes can display any metafield, but this requires development work scoped into the migration project.
Product Relationships
Bundles, kits, related products, and cross-sells often exist as custom relationships in legacy platforms.
Bundles and kits
Shopify does not have native bundle products that adjust inventory of component products. Apps exist to add this functionality, but the data model differs from what you might have in Magento or a custom system.
Decide whether to migrate bundle logic or rebuild it in Shopify. Migrating may not be worth the effort if the app handles bundles differently.
Related and cross-sell products
If your current platform maintains explicit related product relationships, export this data. Shopify themes can display related products, but the data source varies: some use collections, some use metafields, some use apps.
Category to Collection Mapping
Shopify uses collections rather than categories. The concepts are similar but not identical.
Flat vs hierarchical structure
Shopify collections are flat. There is no native parent-child relationship between collections. If your current category structure is deeply nested, you need to either flatten it or use navigation menus to simulate hierarchy.
Smart collections vs manual collections
Smart collections populate automatically based on product tags, types, or other attributes. Manual collections require explicit product assignment. Decide which approach fits each category during planning.
Tags often become the backbone of smart collections. Plan your tagging strategy before migration to avoid cleanup later.
Data Cleaning Checklist
Before exporting data for migration, work through this checklist:
- Remove discontinued products or flag them clearly
- Standardize option names and values
- Fix or remove products with broken images
- Normalize SKU formats
- Remove duplicate products
- Validate inventory counts against physical stock
- Update product descriptions that reference old platform features
- Check for special characters that may not encode correctly
This work is tedious but essential. Every hour spent cleaning data before migration saves multiple hours fixing problems after.
Testing Before Full Migration
Never migrate your full catalog without testing on a subset first.
Sample migration
Select 50 to 100 products that represent your catalog's variety: simple products, products with many variants, products with custom fields, products with complex pricing. Migrate this sample and verify everything imported correctly.
What to verify
- Variant structure matches expectations
- Images display correctly
- Prices are accurate including sale prices
- Inventory counts are correct
- Metafields populated and accessible
- SEO metadata imported (titles, descriptions)
Fix issues found in sample migration before running the full import.
Working with LiftKit Digital
Product data work is unglamorous but critical. LiftKit Digital includes data auditing and cleanup in our Shopify migration projects because skipping it creates problems that surface after launch.
If you are concerned about catalog complexity affecting your migration timeline, start a conversation early. We can assess the scope before you commit to a timeline.