Import Limitations Every Migration Faces
Shopify's import tools handle products, customers, and basic data well. But every migration encounters data that Shopify cannot import directly. Knowing these limitations upfront lets you plan workarounds or set appropriate expectations.
Customer Passwords
This is the limitation that affects customers most directly.
Why passwords cannot migrate
Password hashing algorithms differ between platforms. Shopify uses a specific hashing method that is incompatible with passwords hashed by Magento, WooCommerce, or other systems. There is no way to convert between formats without knowing the original password, which you do not have.
What happens to customers
Migrated customers exist in Shopify with their email and order history (if imported), but no password. When they try to log in, they must use password reset.
Managing the transition
- Send advance notice about the new site
- Proactively send password reset emails post-migration
- Make password reset prominent on the login page
- Train support for increased password-related tickets
Some friction is unavoidable. Minimize it with clear communication.
Order History
Shopify does not have a native order import.
Why order import is limited
Orders in Shopify are complex objects tied to products, customers, inventory, and financial records. Importing historical orders that reference products with different IDs, payment methods that no longer exist, and fulfillments that happened externally creates data integrity challenges.
Options for order history
API-based import: Custom scripts can create order records via the Admin API. These orders appear in customer accounts and admin, but may have limitations around refunds, fulfillment, and financial reporting.
Third-party apps: Apps like Matrixify or EZ Importer can import orders with varying degrees of completeness.
Reference only: Keep order history in your old system for reference. Customers see orders in Shopify only from migration forward.
Deciding what to import
Consider:
- How important is it for customers to see old orders?
- Do you need historical data for reporting?
- What is the effort versus value trade-off?
Many brands import recent orders (6-12 months) and archive older history elsewhere.
Product Reviews
Native Shopify does not have a review system. Reviews live in apps.
Migration path
Most review apps (Judge.me, Yotpo, Stamped, Loox) offer migration from other platforms or from exported review data. The process typically involves:
- Exporting reviews from your current platform
- Formatting to the new app's import requirements
- Mapping products between old and new systems
- Importing via the app's migration tool
Reviews without a source app
If your current platform has native reviews not in a third-party app, export them manually and import to your chosen Shopify review app. This requires more effort but preserves social proof.
Custom Fields and Structured Data
Platforms store custom product and customer data differently.
Product custom fields
Shopify uses metafields for custom data. Your current platform may use custom attributes, product specifications, or proprietary data structures. These require:
- Defining metafield schema in Shopify
- Mapping old fields to new metafields
- Importing via API (CSV import has limited metafield support)
Customer custom fields
Customer tags and metafields can store custom data, but the structure differs from what you may have. Plan how to represent customer segments, preferences, or custom attributes.
Subscriptions
Subscription data is particularly complex.
What needs migration
- Active subscription records
- Billing schedules and next charge dates
- Payment method tokens
- Subscription-specific discounts
- Pause and skip status
App-dependent migration
Subscription migration depends on your target Shopify app. Recharge, Bold, and others have varying migration capabilities. Some can import from specific source platforms, others require manual setup.
See migrating subscriptions to Shopify for details.
Loyalty and Rewards
Loyalty program data requires special handling.
Point balances
Customer point balances need migration to your new loyalty app. Most apps can import balances from CSV. Verify point values and tiers transfer correctly.
Reward history
Historical redemption data may not migrate fully. Decide if this matters for your program.
Gift Cards
Gift card balances have financial implications.
Outstanding balances
Shopify can import gift cards with balances via the API. Each gift card needs:
- Code or new generated code
- Current balance
- Expiry date if applicable
Already redeemed partial balances
Cards with partial remaining balances need accurate balance import. Incorrect balances create customer service issues or financial discrepancies.
Theme and Design
Your current theme does not migrate.
Starting fresh
Choose a Shopify theme and customize it for your brand. You can recreate the look of your old site, but you are building on a new foundation.
Content migration
Text content, images, and some layout concepts can move over. Custom functionality requires reimplementation in Shopify's theme architecture.
Integrations
All integrations need rebuilding.
No automatic transfer
Integrations built for your old platform's APIs do not work on Shopify. Every ERP connection, marketing integration, and custom tool needs reconfiguration or rebuilding.
See Shopify integrations for approaches.
Working with LiftKit Digital
LiftKit Digital understands these limitations and plans for them. We identify what cannot import directly and implement appropriate workarounds.
For migration planning, see Shopify migration. To discuss your migration, get in touch.