How to Consolidate Shopify Expansion Stores into One Store

Before you move any data, stop engaging customers.

Disable order confirmations, shipping emails, gift card emails, and any automated flows tied to orders or customer actions. This prevents customers from receiving accidental emails while the consolidation store is still being built and tested.

If you are building a new store specifically for consolidation, disabling notifications is straightforward and should be done immediately.

If you are consolidating into an existing live store, you can’t simply turn notifications off without disrupting active sales. In this case, migrate data exclusively via the Shopify API and structure imports so they do not trigger customer-facing events. This is the only safe way to avoid accidental emails when notifications must remain enabled.

The rule is simple: no customer should hear from the consolidation store until you explicitly want them to.

Once notifications are under control, define your metafields and metaobjects.

At this stage, create definitions only. Do not import any values or entries yet.

This step ensures that when you later import products, customers, pages, and orders, every piece of data attaches to a predefined structure. If you skip this and import data first, Shopify will either drop unsupported fields or create inconsistent schemas that are extremely difficult to fix retroactively.

Think of this as laying the foundation. Once the schema exists, you can safely import data knowing it will attach correctly. Without it, every subsequent import introduces technical debt.

Now prepare the consolidation store so it’s capable of receiving data, but keep everything inactive until launch.

First, configure the structural elements:

• Create Markets that mirror your existing regional setup
• Enable only the languages required per market
• Connect domains according to your migration strategy
• Set the base currency

Next, configure the operational layer:

• Taxes
• Shipping zones and rates
• Payment methods
• Legal pages and policies
• Email templates

Nothing here should be live yet. The purpose of this step is to ensure that every object you migrate has a valid destination the moment it enters the store. Products need locations, prices need currencies, orders need tax rules, and customers need account logic already in place.

Before you migrate a single product, you must recreate your warehouse and fulfillment structure inside the consolidation store.

Create one location for each source store or fulfillment center you’re migrating from. These locations should mirror your existing setup as closely as possible, because inventory, orders, and fulfillment logic will rely on them later.

You can create locations manually (recommended for accuracy) or via Matrixify if your setup is large. What matters is that all locations exist before product import begins. If they don’t, Shopify will either misassign inventory or default it to the wrong location.

This is the most critical phase of the entire migration. Everything that follows—orders, inventory accuracy, reporting—depends on this step being done correctly.

Migrate products and variants first, including:

• Product data
• Variants and options
• Media (images, videos, files)
• Inventory levels per location

How to migrate products safely

Use a bulk migration tool such as Matrixify so you can control imports and re-run them if needed. After the initial product import, tools like Matrixify generate follow-up files that preserve relationships between products, media, and future order imports. This allows you to fix issues without rebuilding the entire catalog.

Product and variant IDs will change

There is one hard constraint you must plan around. Shopify never preserves product or variant IDs across stores. Every imported product and variant receives a new ID in the consolidation store. This is why:

• Migrate products before migrating orders.
• All future order imports must reference the new product and variant IDs.
• You must maintain an old-to-new ID mapping for later steps.

If you lose this mapping, historical orders will not attach correctly.

Language rules you must follow

Shopify enforces a strict order for multilingual catalogs:

• Import products in one primary language only.
• Enable Markets languages after product import.
• Add translations using language-specific CSVs once Markets is live.

If you import translations too early, Shopify will discard them.

Treat ID mapping as a first-class task

If products or variants are incomplete, mis-mapped, or re-imported incorrectly, every downstream step breaks. Document the old-to-new mapping carefully, because you will need it for:

• Order imports
• Refund reconstruction
• Analytics reconciliation

Once products have been moved in the consolidation store, migrate all non-product assets they depend on.

If assets are missing, pages may render incorrectly or contain broken links, even if the product data itself is intact. Migrating assets early prevents downstream cleanup and avoids having to re-edit content later just to fix file references.

Move all shared files, including:

• PDFs (manuals, size guides, warranties)
• Images and icons
• Videos
• Any downloadable assets referenced by products or pages

These assets exist outside the product catalog but are often embedded across PDPs, content pages, and email templates.

With products and assets in place, you can now migrate collections safely. Collections depend entirely on product handles, tags, and rules. Importing them before migrating products or recreating them incorrectly can cause empty or broken collections that must be rebuilt manually.

Here are two ways to handle different collection types:

• Manual collections: Import directly once products exist
• Automated collections: Import with their rules intact so Shopify can rebuild them dynamically

If you’re using Matrixify, always use “Merge” for collection imports. This ensures that existing collection IDs remain stable instead of being recreated.

Content migration comes after products and collections, not before. Pages and blogs often reference products, collections, and assets. Migrating them earlier risks broken links and missing references. By migrating content last, you ensure every dependency already exists.

Here’s a migration approach that Shopify recommends:

• Manual copy for small or highly curated content sets
• API-based migration for larger sites with many pages or blogs (or a third-party app like Matrixify)

Once pages and articles exist, migrate translations using the translations CSV export/import workflow.

Metaobjects often power:

• Product specifications
• Size guides and comparison tables
• Structured content blocks reused across pages

These entries frequently reference products, variants, or pages by ID or handle.

But, only import metaobject entries after products and pages exist in the consolidation store. If you import metaobject entries before their referenced objects exist, Shopify cannot resolve those links.

The result is broken references that don’t automatically fix themselves later. By waiting until products and pages are already in place, you ensure every metaobject entry attaches cleanly and behaves as expected across the storefront.

Navigation should be one of the last things you migrate.

You have two safe options her. Choose based on how customized your menus are:

• Rebuild manually (recommended): This gives you the best control over UX consistency. It also lets you clean up legacy menu items, remove dead links, and align navigation with the consolidated store’s structure.
• Import menus: If you import menus, do it only after all objects exist and all handles match exactly. Any mismatch will result in broken or missing menu links.

This step comes in late because menus depend on products, collections, pages, and URLs. Migrating them earlier almost guarantees broken links and rework. Handling navigation at this stage ensures that everything it points to already exists.

SEO continuity during a Shopify Markets consolidation depends on whether your existing URLs resolve cleanly after migration. Redirects preserve those URLs but only if you work within Shopify’s constraints.

How Shopify redirects actually work

Shopify only supports redirects where both the source and destination are URL paths on the same domain. Redirects run after the domain level, not across domains or subdomains.

As a result:

• Redirects can move traffic from one path to another on the same domain.
• Redirects cannot move traffic from a subdomain or top-level domain into a subfolder.

This rule defines what is technically possible during consolidation.

What happens when you connect Expansion Store domains

When you connect a domain like “eu.store.com” to the consolidated store at “store.com”, Shopify automatically routes traffic to the main domain.

Shopify can resolve:

• eu.store.com/products/product-1 → store.com/products/product-1

Shopify cannot resolve:

• eu.store.com/products/product-1 → store.com/en-eu/products/product-1

This limitation exists regardless of redirect rules.

Why old URL paths must still exist

Because redirects only work path-to-path, every URL path that existed on your Expansion Stores must also exist on the consolidated store. If an old store served “/products/product-1”, that same path must resolve after migration. If it doesn’t:

• Redirects fail
• Users land on 404 pages
• Search engines drop indexed URLs

This is why redirect mappings must be finalized and validated before go-live.

Where geolocation fits into the flow

After redirects resolve, all shoppers initially land on the same domain without market context. Redirects preserve URLs, but they do not determine localization.

At this stage, geolocation becomes important. Tools like Orbe route shoppers to the correct market and language experience once they arrive on the consolidated domain. This ensures international shoppers land in the right Shopify Markets experience, even when redirects can’t express market intent.

What to validate before launch

Before cutover, confirm that:

• Every legacy URL path resolves on the new store
• Redirect targets exist and return a 200 status
• No redirect relies on subdomain to subfolder logic
• Geolocation routing directs shoppers to the correct market

Customer migration determines whether buyers recognize themselves in the new store. The goal here is continuity without forcing unnecessary friction.

Deduplicate customers by email

Start by deduplicating customers across all source stores using email address as the unique identifier. Shopify associates historical orders to customers by email, not by account ID.

This means:

• You can recreate customer profiles in the consolidated store.
• Historical orders will correctly attach as long as the email matches.
• Duplicate records create confusion in reporting and support.

How customer accounts behave after migration

Customer accounts do not migrate. Only customer records do. What your customers experience next depends entirely on the account system you choose for the consolidated store.

• Legacy Customer Accounts: Customers must reactivate their accounts and set a new password via email. This introduces friction, increases support tickets, and often confuses repeat buyers.
• New Shopify Customer Accounts: Customers log in using a one-time email code. They don’t reset passwords and typically don’t notice the migration. Their order history appears automatically once they log in.

If minimizing disruption matters, use New Shopify Customer Accounts before you migrate customers.

Migrate all customer addresses

Import all customer addresses along with customer records. Addresses affect:

• Checkout defaults
• Shipping calculations
• Tax logic
• Post-purchase flows

Missing or partial address data creates downstream issues that surface only after launch.

Order migration preserves reporting continuity and customer history, but it requires precision. This is one of the most sensitive steps in a Shopify Markets consolidation.

1. Choose an API-based migration method: Migrate orders using the Shopify API or a tool like Matrixify that relies on the API. Shopify does not support CSV-based order imports, so any approach that doesn’t use the API will fail.
   
   
2. Import orders as archived or closed: Import all historical orders in an archived or closed state. You are migrating order history for reporting and customer context, not reactivating fulfillment, notifications, or financial workflows.
   
   
3. Map old product and variant IDs to new ones: Before importing, map every legacy product and variant ID to the new IDs created during product migration. Shopify always generates new IDs when products are imported into another store, and orders will not attach correctly unless they reference those new IDs.
   
   
4. Import orders in controlled batches: Migrate orders in batches rather than all at once. This makes failures easier to identify and correct without re-running the entire import.
   
   
5. Handle refunds deliberately: Decide upfront how you will treat refunds. Refunds can be recreated, but multi-currency refunds often introduce inconsistencies due to exchange-rate differences and partial refund logic. This is the primary reason that historical analytics rarely match perfectly after consolidation.
   
   
6. Validate order integrity after import: Spot-check imported orders to confirm:

• Products and variants are attached correctly.
• Customer records link by email.
• Totals, currencies, and statuses make sense for reporting.

Gift cards cannot be transferred between Shopify stores. This means customers retain their balance, not their original code. If you handle this cleanly and communicate it clearly, friction stays minimal.

So, make sure to:

1. Reissue gift card balances as new gift cards in the consolidated store.
2. Disable original gift cards in all legacy stores.

Shopify does not allow gift card codes to be reused across stores, regardless of setup.

Before launch, ensure that all promotional logic still applies correctly in the consolidated Shopify Markets store, especially if discounts are tied to specific products, collections, or regions.

1. Export existing discounts: Export discount data from legacy stores using CSVs or API access so you have a complete reference.
   
   
2. Recreate or import discounts in the consolidated store: Import discounts via the API where possible, or recreate them manually when logic is simple. Verify eligibility rules, usage limits, and market scoping.
   
   
3. Update Shopify Scripts and custom logic: If you use Shopify Scripts or custom discount logic, update them to reference the new product and variant IDs created during product migration. Legacy IDs will no longer resolve.
   
   

Test discounts by market: Validate that discounts apply correctly across markets, currencies, and checkout flows before proceeding.

Draft orders don’t need to be migrated in most cases. Here’s when and how to migrate draft orders:

1. Decide if draft orders are required: Review existing draft orders and flag only those tied to live quotes, B2B negotiations, or carts that customers are actively waiting to complete. Ignore expired, abandoned, or internal-only drafts.
   
   
2. Recreate draft orders selectively: Recreate only active or high-priority draft orders. Migrating every draft order adds complexity without meaningful value.
   
   
3. Validate pricing and products: Confirm that recreated draft orders reference the correct products, prices, and currencies in the consolidated store.

Between your initial data imports and launch, new orders, inventory changes, and product edits will occur. This step closes that gap and ensures the consolidated store reflects the most up-to-date state before cutover.

1. Reimport new orders since the cutoff date: Import all orders created after your initial migration to close the gap between legacy stores and the consolidated store.
   
   
2. Sync last-minute inventory changes: Reconcile inventory levels across locations to ensure stock accuracy at launch.
   
   
3. Reimport updated product edits: Apply any product changes made during the freeze window, like pricing updates, descriptions, or availability changes.
   
   
4. Validate redirects and URL paths: Confirm that all legacy URLs resolve correctly and that no redirects point to missing paths.

This is the point where the migration becomes visible to the outside world. Once domains move, all traffic is redirected to the consolidated Shopify Markets store, so this step needs to be deliberate and controlled.

1. Point all domains to the consolidated Markets store: Update DNS settings so each legacy domain resolves to the new store. Do this only after all data, redirects, and routing logic are in place.
   
   
2. Validate redirects end-to-end: Confirm that every legacy URL resolves to a valid path and returns a 200 status. Test high-traffic pages, top backlinks, and category URLs manually before proceeding.
   
   
3. Ensure correct market routing after domain cutover: Once domains point to a single store, shoppers land without market context. Use geolocation routing with tools like Orbe to send visitors to the correct country and language experience immediately. This way, shoppers won’t land in the wrong market after consolidation.
   
   
4. Shut down legacy stores: After traffic and orders flow correctly through the consolidated store, close the legacy Expansion Stores to avoid duplicate operations, reporting noise, or accidental sales.

Only re-enable customer communications once the migration is fully complete and verified.

1. Restore email flows intentionally: Turn order confirmations, shipping emails, and automated flows back on only if you disabled them earlier. Re-enable them gradually to catch issues early.
   
   
2. Test live customer communication: Place test orders in different markets to confirm that emails, language, currency, and content render correctly before treating the migration as finished.

After this step, the consolidation is operationally complete. What remains is ongoing monitoring and optimization, but the structural migration is done.