How to Migrate Products from One Shopify Store to Another (3 Methods That Work)

If you need to migrate products from one Shopify store to another, you are usually not replatforming. You are copying a catalog: a new regional store, a wholesale front, a redesign launch, or a staging clone that finally needs to go live. Shopify does not offer a one-click "duplicate this store" button for products alone, so merchants end up choosing between a free CSV, a URL importer, or a bulk spreadsheet app.

That choice matters more than most roundups admit. U.S. retail ecommerce hit $1,233.7 billion in 2025, and Shopify still describes its footprint as millions of merchants in more than 175 countries. Plenty of those merchants already run more than one Shopify store. This guide walks through three methods that actually move product titles, images, variants, and prices, plus the traps that quietly break imports (dead image URLs, draft vs live status, and expecting customers or orders to ride along).

If you are coming from Amazon, Etsy, or Daraz instead of another Shopify admin, use our Amazon product catalog migration guide, the Etsy to Shopify product move, or how to import products from Daraz to Shopify. Those are different translation jobs. This page stays on Shopify to Shopify.

What Product Data Actually Transfers Between Shopify Stores?

Product records transfer. Customer accounts, order history, reviews, gift cards, themes, and most SEO redirects do not. Plan the catalog copy as its own project, then handle the leftovers separately.

On a clean product row you should expect titles, descriptions (HTML), vendor, product type, tags, variants and option values, prices and compare-at prices, SKUs, barcodes, inventory quantities (with caveats by location), and image URLs that Shopify re-downloads into the destination store. Shopify raised the per-product variant ceiling to 2,048 variants for all merchants on October 15, 2025, so large variant matrices can move when the tool supports them. You still only get three option dimensions per product.

What usually does not survive a basic product copy:

• Customers, orders, and reviews. Those need Shopify's customer CSV, a dedicated migration app, or a review importer. Product tools are not full-store movers.
• Collections as objects. Products can land ungrouped. You rebuild manual or automated collections on the destination.
• Theme, navigation, and pages. Storefront design is never in a product export.
• Metafields and metaobjects unless you use a tool that explicitly exports them (native Shopify product CSV support for metafields is limited, and variant metafields are a known gap).
• Inventory split by location in many simple CSV flows. You may need a follow-up pass for multi-location stock.

Shopify's own Store Migration app skip list is a useful reminder even when both stores are already on Shopify: a product importer is not a replatform. Our 2026 migration apps comparison covers tools built for orders and broader data when that is the real job.

Most Shopify-to-Shopify "migrations" are catalog copies dressed up as full-store moves. Buy a suite that moves customers and orders only when you need those objects. For products alone, CSV or a URL paste is the honest tool, not the biggest invoice.

How Do You Migrate Products from One Shopify Store to Another with CSV?

Use Shopify's built-in Products export on the source store, then Products import on the destination. It is free, inspectable in a spreadsheet, and enough for many one-time catalog copies under a few hundred SKUs.

Export from the source store

1. In the source Shopify admin, open Products.
2. Select the products you need, or leave them unselected if you want the full catalog.
3. Click Export. Choose current page, selected products, or all products.
4. Pick the CSV format for Excel, Numbers, or other spreadsheet programs, then export. Small exports download in-browser; large ones arrive by email.

Import into the destination store

1. Open Products in the destination admin and click Import.
2. Upload the CSV. Preview the sample rows before you confirm.
3. Decide whether new products should publish to sales channels. For a first pass, leave them unpublished or treat them as drafts until you spot-check.
4. Only check overwrite-by-handle if you intentionally want matching handles to replace existing products.
5. Run the import, then wait for Shopify's confirmation email.

The image trap is the one Shopify documents clearly: the CSV stores image URLs, not binary files. Shopify downloads those URLs during import. Keep the source store and its product listings publicly reachable until the destination finishes pulling images. Delete the old products too early and you get blank galleries.

CSV quirks that still burn merchants in 2026:

• Handles must stay unique. Near-duplicate titles get numeric suffixes and permanent ugly URLs.
• Option names must match exactly across variant rows ("Color" vs "Colour" splits products).
• Changing option values on a re-import can recreate variant IDs and break apps that stored the old IDs.
• Metafield coverage is incomplete compared with dedicated bulk tools.

For column-by-column failure modes, use our walkthrough on importing products to Shopify from a CSV without errors. CSV is the right default when you want a free, auditable file and a one-time move.

How Do You Copy Products Between Shopify Stores with a URL Importer?

A URL importer skips the spreadsheet. You install the app on the destination store, paste a product URL, a collection URL, or the source storefront homepage, preview what was found, then start the import. This is the fastest path when the source catalog is already public on a Shopify storefront.

Migratify is one option built for this job. Its docs state you can import from any Shopify store using a product, collection, or whole-store URL, plus Amazon, Etsy, Lazada, Daraz, BigCommerce, and many other public sites. On the App Store it holds a 4.5-star rating across 53 reviews, with a Free plan (up to 5 products total), Standard at $14/month for unlimited imports, and Plus at $29/month for heavy Magic Edit use.

A typical Shopify-to-Shopify run looks like this:

1. Install Migratify on the destination store (the one receiving products). Migratify needs a paid Shopify plan; trial stores can install but cannot import until Shopify is upgraded.
2. Open the Import page and paste a product URL, a collection URL such as https://examplestore.com/collections/summer, or the store homepage for the whole catalog.
3. Wait for validation and the product preview. Spot-check titles, prices, images, and variants.
4. Set import options: add to a manual collection if you want, price multiplier (use 1 to keep prices), create as active or draft, shipping/tax flags, and inventory tracking.
5. Click Start migration. The job runs on Migratify's servers, so closing the browser does not cancel it. Only one import can run at a time.

Hard limits to know before you paste a homepage URL: a single Shopify-store import is capped at 10,000 products, Free is a lifetime 5-product ceiling (not monthly), and Migratify imports products only. It does not move customers, orders, reviews, gift cards, or store settings. Collections are not recreated as objects, though you can drop every imported product into one existing manual collection. Videos on the source page are not imported. Title, description, images, variants, prices, compare-at prices, SKU, barcode, tags (up to 30), vendor, and product type do come across.

Use drafts for large runs. Turning "Set product as active" off lets you review the catalog in admin before customers see duplicates or wrong prices. If you are also cleaning tags and variants afterward, pair this with our guide to cleaning up product data after a Shopify migration.

When Should You Use a Bulk Spreadsheet App Instead?

Use a Matrixify-style bulk tool when native CSV loses fidelity or when you need metafields, metaobjects, location inventory, or a repeatable export/import pipeline between stores. These apps speak a richer spreadsheet format than Shopify's native product CSV.

Matrixify is the common pick for this lane. On the App Store it sits at 4.9 stars from more than 1,600 reviews, with paid plans that scale by catalog size (list pricing commonly starts around $20/month on the listing). The workflow is export Products in Matrixify format from the source store, optionally edit the sheet, then import that file into Matrixify on the destination store.

Typical steps:

1. Install Matrixify on both stores (or use the linked additional-store setup Matrixify documents for multi-store merchants).
2. On the source, create a New Export, choose a Matrixify Excel or CSV format, select the Products sheet (and any related sheets you need), then download the file.
3. Open the sheet only if you need edits: clear Shopify IDs when creating new products, fix handles, or adjust metafield columns.
4. On the destination, upload the file, review Matrixify's analysis warnings, then run with MERGE (create missing, update matches) unless you have a deliberate UPDATE or REPLACE plan.
5. Test one variant-heavy product end to end before you push the full catalog.

Pick this method when any of these are true: you rely on metafields your theme reads, you manage inventory across many locations, you need collections and smarter relationships in the same job, or you will re-sync catalogs on a schedule. For a simple 80-SKU lifestyle brand with no custom fields, native CSV or a URL importer is usually enough and cheaper.

Which Method Should You Choose for Your Catalog Size?

Match the tool to catalog size, how often you copy, and whether metafields matter. Do not default to the most expensive option.

• Under ~200 products, one-time, no metafields: native CSV. Free, transparent, and fine if you keep the source store live for images.
• Public Shopify storefront, collection or whole-store paste, want preview before create: URL importer such as Migratify. Fastest path when you do not want to touch a spreadsheet.
• Metafields, metaobjects, multi-location inventory, or recurring sync: Matrixify-style bulk spreadsheet. Worth the subscription when fidelity matters.
• Need customers or orders too: stop treating this as a product-only job. Use a dedicated full migration path or Shopify's customer/order tools alongside the product method above.

A practical sequence for most consolidations: copy products as drafts, spot-check 20 SKUs across categories, fix handles and images, build collections, then publish. Inventory counts drift during any move, so reconcile quantities before you open ads on the new storefront.

What Should You Check After Products Land in the Destination Store?

Validate before you decorate. A green progress bar is not a clean catalog.

• Open 20 products spanning simple and variant-heavy items. Confirm titles, prices, compare-at prices, SKUs, barcodes, and images.
• Click every image on those samples. Blank galleries almost always mean the source URLs died mid-import.
• Search for duplicate handles and near-duplicate titles. Merge or delete before you build redirects or ads.
• Confirm publication status. Draft-first imports should stay draft until you intentionally publish.
• Rebuild collections and menus. Products arriving ungrouped is normal.
• If reviews matter on day one, import them with a review app after handles are stable, not before.

Only then point a custom domain, flip password protection off, and send traffic. Product copy is the mechanical slice. Theme, redirects, and apps are still a separate afternoon.

Do You Need 301 Redirects When Both Stores Are Already on Shopify?

Only if you are retiring the source storefront and moving its public URLs. Copying products into a second live brand usually does not require redirects, because the old store keeps its own domain and handles.

If the destination will replace the source on the same domain, export a URL map first. Shopify product URLs follow /products/{handle}. Matching handles across stores makes redirects simpler: old /products/blue-mug can 301 to the same path on the new store once DNS points there. Mismatched handles need a spreadsheet of old URL to new URL before you cut over.

Redirect work is separate from the product import itself. Finish the catalog copy, lock handles, then build the redirect map. Skipping that order is how you 404 rank pages you already earned.

Can You Keep Both Shopify Stores Running After the Copy?

Yes. Many merchants run regional, wholesale, and DTC stores in parallel with shared or partially shared catalogs. The product copy does not shut down the source.

What you must decide is inventory truth. If both stores sell the same physical stock, a one-time copy will drift the moment either store sells a unit. Either assign separate stock pools, or add an inventory sync app and accept that sync lag is a real risk. For a redesign where the old store will retire, keep the source live only until images finish importing and DNS cuts over, then archive.

Also rewrite descriptions when the destination store has a different audience. A wholesale catalog pasted into a DTC storefront often needs shorter copy, lifestyle images, and different compare-at pricing. The migration tool moves fields. It does not rewrite positioning.