How to Consolidate Shopify Expansion Stores into One Store
Learn how to migrate multiple Shopify expansion stores into one Shopify Markets store without breaking SEO, data, or customer experience.
As brands scale across multiple countries, the challenge often shifts from expansion to efficiency. Running several Shopify Expansion Stores may have worked early on, but over time, it creates duplicated work, fragmented SEO, inconsistent customer experiences, and rising operational costs.
That’s why more Shopify Plus brands are consolidating their expansion stores into one store using Shopify Market.
This guide is for Shopify Plus brands managing 2–20 expansion stores who are actively considering that shift. We’ll walk through how consolidation actually works:
- What changes when you move to Shopify Markets
- What can and cannot be migrated
- Where Shopify’s limitations are non-negotiable
- How to preserve continuity across SEO, customers, and localized experiences during the transition.
It’s important to note that this is a complex migration. But with the right preparation, order of operations, and safeguards in place, you can successfully move to a single-store architecture that’s easier to scale, easier to manage, and better aligned with Shopify’s international roadmap.
Why you might want to migrate
As brands scale across regions with multiple Shopify Expansion Stores, operational complexity increases. For many teams, migrating to a single store powered by Shopify Markets is the next logical step, driven by a need for simplicity, consistency, and scale.
|
Key benefits |
|
|
Operational streamlining and lower overhead |
Work stops being duplicated across stores. Apps, themes, workflows, campaigns, and fixes are managed in one place instead of being repeated market by market. |
|
Centralized catalog, pricing, and content governance |
Products, collections, pricing rules, and content are managed once, with regional overrides applied only where needed, instead of being recreated and constantly kept in sync across stores. |
|
Stronger international SEO |
Consolidation allows you to bring traffic under a single domain structure, use subfolders, and rely on Shopify’s native hreflang handling instead of managing SEO signals manually across multiple domains. |
|
Unified analytics and reporting |
Sales, conversion rates, and customer behavior are visible in one analytics environment, removing the need to reconcile fragmented data across multiple stores and currencies. |
|
Lower total cost of ownership |
Apps, integrations, and maintenance are paid for once rather than per store, delivering meaningful cost savings as the number of markets grows. |
|
Consistent customer experience |
Customers interact with one brand experience instead of being split across different stores, domains, and uneven localization setups. |
|
Faster market expansion |
Adding a new country becomes a configuration step inside Shopify Markets, not a full store launch with new infrastructure, domains, and integrations. |
|
Simplified compliance and governance |
While multi-entity setups still require care, centralization reduces duplicated compliance logic and makes it easier to audit and manage global operations. |
|
A more scalable future architecture |
A single Markets-powered store provides a cleaner foundation that scales more predictably as Shopify continues to invest in its international commerce stack. |
What changes when you consolidate from multiple stores to one
When you move from multiple Shopify Expansion Stores to a single store using Shopify Markets, you’re not just reducing the number of storefronts you manage. You’re changing how Shopify models your business internally, from isolated, self-contained environments to one shared system with regional rules layered on top.
This shift brings meaningful long-term benefits, but it also introduces constraints you need to account for during migration.
How Shopify Markets replaces Expansion Stores
With Shopify Markets, you stop duplicating infrastructure country by country. Instead, you run a single store that offers many localized experiences.
Here’s what that means in practice:
- You manage one catalog and one theme, rather than maintaining separate versions per store.
- Analytics, reporting, and integrations live in a single, unified environment rather than being fragmented across multiple stores.
- You apply regional overrides (for pricing, availability, currencies, languages, and content) at the market level, rather than recreating products or pages.
- SEO is managed centrally. You can use subfolders, subdomains, or ccTLDs, with Shopify Markets automatically managing hreflang signals when the structure allows it.
Operationally, this replaces the “many stores, many systems” model with one system that adapts by region.
⚠️ Limitations to be aware of
While consolidation simplifies future operations, Shopify enforces strict boundaries on what can and cannot move cleanly into a single store. Key limitations include:
- Customer accounts don’t migrate: Shopify only allows you to migrate customer records, not account credentials. Passwords are never transferred. If you use legacy customer accounts, customers must reset their passwords after migration. If you’re already using Shopify’s new customer accounts (email-based login), password resets aren’t required, since customers authenticate using a one-time code instead of a stored password.
- Gift card codes can’t be preserved: Existing gift card balances must be reissued as new cards. Original codes cannot be reused across stores.
- Orders can only be imported via API: Shopify does not support CSV-based order imports. Historical orders require API-based migration, and even then, some transaction details are limited.
- Not all channels and apps support Shopify Markets: Only the Online Store channel fully supports Markets. Many third-party apps assume a single-currency or single-market setup and may break, require workarounds, or need to be replaced.
- Redirects depend on domain consistency: Shopify cannot redirect from subdomains or TLDs to subfolders. If you change your domain architecture during consolidation, URLs will break, even if redirect rules exist. Orbe helps bridge this gap by routing visitors to the correct market and store version at entry, reducing reliance on fragile cross-domain redirects during consolidation.
- Analytics inconsistencies are unavoidable: In real multi-store migrations, especially when stores sell in different currencies (using Shopify Payments), historical analytics will never reconcile perfectly. Exchange rates, refunds, and transaction timing can’t be reconstructed exactly once data is consolidated into one store.
Pre-migration planning
Before you make any changes, you need to lock the foundation. Most consolidation issues don’t stem from migration steps. They come from poor planning.
This phase determines whether the rest of the process is controlled or chaotic.
Inventory your current architecture
Start by documenting exactly what you’re running today. Create a complete inventory of:
- Number of Shopify stores and their domains
- Installed apps and custom workflows
- Product catalogs, variants, and collections
- Active languages and localized content
- Automations, scripts, and checkout logic
Then map dependencies along with stack:
- Payment providers and payout flows
- ERP and OMS connections
- Loyalty, subscriptions, and CRM systems
- Analytics, attribution, and reporting pipelines
This gives you visibility into what you must migrate, what can be retired, and what will break if handled out of order.
Decide where to consolidate
You shouldn’t merge multiple stores into a blank slate unless there’s a strong reason to do so. In most cases, it’s best to consolidate into the store with the highest historical order volume, since Shopify preserves more usable customer and order data from that store.
For example:
- Store 1 (GB): 1M orders
- Store 2 (EU): 4M orders
- Store 3 (US): 6M orders → consolidation target
- Store 4 (Asia): 1M orders
In this scenario, Store 3 becomes your main store. You migrate the other regions into it using Shopify Markets. This approach minimizes data loss and reduces friction when linking historical customers, orders, and reporting.
Define your target Shopify Markets setup
Before migrating anything, define how the consolidated store should operate. Shopify Markets is flexible but only if you design it intentionally.
Decide upfront:
- Market groups (e.g., EU, UK, US, GCC, ROW)
- Domain strategy (subfolders, subdomains, or ccTLDs—aligned with your existing setup)
- Language strategy (only enable languages that are actually required per market)
- Price and catalog overrides (regional pricing, availability, or exclusions)
This ensures every piece of migrated data has a clear destination once it lands in the consolidated store.
Freeze window & cutover date
Finally, define when migration work happens and when it stops.
- Choose a low-volume sales period to reduce customer impact.
- Set a clear freeze window for catalog changes, promotions, and app updates.
- Align teams across engineering, logistics, marketing, CRM, and customer support ahead of time so no one is surprised during cutover.
A clearly defined freeze window prevents last-minute changes from invalidating your migration work.
How to migrate multiple stores to one under Shopify Markets (step-by-step instructions)
Want the full migration checklist?
We broke down the entire consolidation process into a 19-step sequence, the exact order of operations to migrate your Expansion Stores into Shopify Markets without losing data, SEO, or customer history.
Maintaining SEO continuity during migration
When consolidating multiple Expansion Stores into a single Shopify Markets store, SEO continuity depends less on “best practices” and more on respecting your existing architecture. Most migration issues occur when the new setup doesn’t match the structure of the old stores.
Some tips to maintain SEO continuity during migration are:
- Match your domain strategy to the old setup: If your Expansion Stores used subdomains or separate top-level domains, your Markets setup must use the same structure. Shopify does not support redirects from subdomains or TLDs to subfolders, so changing the architecture mid-migration will break URLs.
- Create and validate redirect mappings before going live: Every URL that existed on your Expansion Stores must resolve to a valid path on the consolidated store. Redirects to another store only work when both the source and destination paths exist, so missing pages will result in 404s after the domain cutover.
- Check and preserve high-value backlinks: Identify pages with strong inbound links and confirm their redirect targets are correct. These URLs are often responsible for a large share of organic traffic and should be treated as non-negotiable during migration.
- Submit updated sitemaps immediately after launch: Once domains are pointed to the new store, submit fresh sitemaps in Search Console, so search engines crawl the new structure quickly and consistently.
- Validate hreflang implementation: Shopify Markets generates hreflang tags automatically, but you still need to verify that each market and language is scoped correctly and mapped to the right domain or subfolder.
Monitor Search Console closely after cutover: Watch for crawl errors, indexing issues, and unexpected drops in impressions. The first few weeks post-migration are when problems surface, and when they’re easiest to fix.
Post-migration QA checklist
Before declaring the migration complete, use this checklist to validate that the consolidated store works as expected across all markets:
Recommended tools for a smooth migration
Migrating from multiple Shopify Expansion Stores to a single Shopify Markets store isn’t about choosing one tool and hoping for the best. Each phase of the migration introduces different risks, and the tools address specific failure points you will encounter during consolidation:
Matrixify
Matrixify allows you to bulk export and import Shopify data using structured spreadsheets. This includes products, variants, inventory, media, collections, customers, orders, metafields, metaobjects, and redirects.
Why it matters during this migration
When you consolidate multiple stores, Shopify regenerates product and variant IDs. Matrixify gives you the visibility and control you need to remap those IDs correctly, especially when importing historical orders. It also allows you to re-run imports safely, which is critical when migrations happen in phases rather than all at once.
Rely on Matrixify when you want control without custom development and when data accuracy matters more than speed.
Shopify API
The Shopify API allows you to migrate and transform data programmatically, with full control over sequencing, relationships, and error handling.
Why it matters during this migration
Some consolidation scenarios simply exceed what import tools can handle cleanly, especially when you have complex order histories, refunds across currencies, custom objects, or dependencies tied to external systems like ERP or OMS.
Use the API when:
- You need to migrate orders with precision.
- You must control how legacy data attaches to new product IDs.
- You want to minimize data loss in edge cases.
This is the highest-fidelity option but it requires engineering resources and careful testing.
Excel Export Import app
Using Shopify’s native CSV import and export features, you can move certain data types, such as products, customers, and basic records.
Export the data to Excel or CSV files, edit them manually, and import them back into the destination store.
Why it matters during this migration
This method works best for small, well-scoped tasks during consolidation. You might use it to clean customer records, adjust product attributes, or import limited datasets where relationships are simple and volume is low.
It is not suitable for complex migrations involving orders, refunds, or deeply linked data. But it can be useful as a lightweight alternative when you need manual control over specific fields.
Orbe
Orbe Geolocation is a geolocation and redirection layer that detects a visitor’s location and language and routes them to the correct localized experience. It operates independently of Shopify’s domain and redirect system, working at the entry point of the user session.
The platform supports both multi-store and single-store (Markets) setups and updates routing logic dynamically as store configurations change.
Why it matters during this migration
During consolidation, redirects alone are not enough. Shopify cannot redirect users from subdomains or TLDs to subfolders, which means international users often land on the wrong market after domains are pointed to the new store.
Orbe fills this gap by routing users the moment they arrive on the site, before Shopify Markets logic or redirects can fail them. This is especially important:
- During domain cutover
- While SEO redirects settle
- After consolidation, when all traffic hits one main domain
Orbe doesn’t migrate data, but it protects customer experience while everything else changes.
Translate & Adapt
Translate & Adapt is Shopify’s native localization tool for managing translated content within a single store. It allows you to create, edit, and manage translations for products, collections, pages, policies, and other content types.
Why it matters during this migration
Shopify requires you to import products in a single primary language. Once your Markets setup is live, Translate & Adapt allows you to layer translations back in without breaking content structure or market scoping.
Use this tool after core data migration to rebuild multilingual content cleanly inside one store.
Shopify SimGym
Shopify SimGym is a simulation tool that generates synthetic traffic and test orders within a Shopify store. It mimics real customer behavior across browsing, cart, checkout, and order placement, without involving real users or payment methods.
Why it matters during this migration
Many issues only surface under real conditions, like currency switching, tax calculation, checkout behavior, and routing logic. SimGym lets you stress-test these scenarios before customers ever see them.
Use SimGym right before launch to:
- Validate pricing and checkout per market
- Test routing logic across regions
- Catch performance or UX issues early
This reduces risk during final cutover, when mistakes are most expensive.
Challenges to expect after migration
Migrating from multiple Shopify Expansion Stores to a single Shopify Markets store simplifies future operations, but it also resets certain systems permanently.
Understanding these constraints upfront prevents false expectations and helps you plan around Shopify’s hard limits.
Analytics inaccuracies
After consolidation, your historical analytics will never reconcile perfectly. Orders created across different stores and currencies were calculated using exchange rates at the time of purchase, and those rates cannot be reconstructed accurately during import.
You’ll see this most clearly in:
- Revenue totals that don’t equal the sum of your old stores
- Refunds and exchanges that distort historical reporting
- Multi-currency orders that no longer normalize cleanly
Treat analytics after migration as a new baseline. You’ll preserve operational history, but forcing perfect historical continuity isn’t possible within Shopify’s data model.
Lost legacy data
Some historical data won’t survive consolidation cleanly.
- Archived or deleted products often fail to map correctly when orders are imported.
- Orders referencing products that no longer exist may appear partially incomplete in reports or order views.
This does not affect live selling, fulfillment, or customers, but it does limit how reliably you can analyze deep historical performance inside the new store.
App incompatibility
Not all Shopify apps support Markets, and this is one of the most underestimated risks. Many apps assume a single currency, single market, or simplified checkout logic.
After consolidation, you may need to:
- Replace apps that don’t support Markets.
- Reconfigure others with market-specific logic.
- Rebuild custom workflows using the Shopify API.
If app compatibility isn’t audited early, migration delays are almost guaranteed.
Customer reactivation friction
How customers experience the migration depends entirely on your account system:
- Legacy customer accounts: Customers must reset their passwords after migration, which often leads to friction, support tickets, and confusion (especially for repeat buyers).
- New Shopify customer accounts (email-based login): The experience is largely seamless. Customers log in using a one-time email code. If profiles and orders are migrated correctly, they can access their order history without a disruptive reset flow.
SEO risks
SEO loss is almost always caused by redirect mistakes. Shopify only supports redirects when the target URL path exists. If a path disappears during consolidation, traffic drops immediately.
Common failure points include:
- Redirects created before target pages exist
- Domain structures changing mid-migration
- Old URLs that never get mapped
While redirect planning should happen late in the process, it should be designed early to avoid irreversible SEO damage.
Ready to make the most of Shopify Markets?
Consolidating multiple Shopify Expansion Stores into a single Markets-powered store isn’t a simple switch. It’s a structural migration that affects your data, SEO, operations, and customer experience.
When it’s planned correctly, it delivers clear long-term advantages: fewer duplicated workflows, stronger international SEO, cleaner reporting, and an architecture that’s easier to scale.
The difference between a smooth consolidation and a painful one comes down to process. Teams that follow a clear migration order, plan redirects before touching domains, and work within Shopify’s constraints avoid most of the issues that make these projects risky.
Once consolidated, Shopify Markets gives you a solid foundation to run multilingual, multi-currency commerce from a single store. You manage one catalog and one analytics environment, while still tailoring the experience for each region where it matters.
For customers, the migration should be invisible. They don’t need to know that stores were merged or that the architecture has changed. They should simply arrive on the correct version of the site, in the right language, automatically.
That’s where Orbe fits in. After consolidation, Orbe ensures that all site visitors are automatically routed to the right localized experience from their first visit, so the transition feels seamless to customers even as your backend changes.
