How to Migrate Products from One Shopify Store to Another (4 Methods, 2026)

To migrate products from one Shopify store to another, export a product CSV from the source admin and import it into the destination, or use an app that reads the source store for you. 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 has no built-in "copy these products to my other store" button, so the real choice is between a free CSV, a URL importer, a bulk spreadsheet app, and a store-to-store sync app.

Each of those four methods moves product titles, images, variants, and prices. They differ on metafields, customers and orders, ongoing sync, and price. This guide covers all four, plus the traps that quietly break imports: dead image URLs, draft vs live status, variant metafields, 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.

Need theme, customers, apps, and settings too? Use the full Shopify store duplicate checklist instead of stopping at the catalog.

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, unless you pay for a store-to-store app built to move them. 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 get only three options per product, and stores that already hold 500,000 or more variants can add only 10,000 new variants a day through apps or CSV unless they are on Shopify Plus.

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.
• Variant metafields and metaobjects. Shopify's product CSV handles product metafields, but variant metafields aren't supported in product CSV import or export. Metaobjects need a bulk app or a manual rebuild.
• 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.

Hot take: 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, all products, selected products, or products matching your search and filters.
4. Pick the CSV format for Excel, Numbers, or other spreadsheet programs, then export. Most files download in the browser. Shopify emails the file instead when a current page or selected export contains a product with more than 100 variants.

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. Left unchecked, products that match an existing handle are ignored.
5. Run the import, then wait for Shopify's confirmation email.

The image trap is the one Shopify documents clearly: images are not inside the CSV file, only their URLs. When you import into a new store, product images are created only if they remain viewable on a publicly accessible website. Keep the source store and its listings live until the destination finishes pulling images. Delete the old products too early and you get blank galleries.

Large exports can also time out when the catalog holds thousands of variants. Shopify's fix is to split the job into smaller filtered exports, for example by vendor or product type, and import them one at a time.

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).
• Variant images need the right image URL on the right variant row, or they land on the wrong option or go missing.
• Variant metafields will not come across, so themes that read them show blanks.

For column-by-column failure modes, use our walkthrough on importing products to Shopify from a CSV without errors, and if photos land on the wrong option, see how to fix missing or duplicated variant images in a Shopify CSV. 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, and it works even when you have no admin access to the source.

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, Daraz, and many other public sites. On the App Store it holds a 4.6-star rating across 58 reviews (checked November 7, 2026). Its plans are Free (up to 5 products in total, not per month), Standard at $14/month for unlimited imports, and Plus at $29/month for heavy Magic Edit use. Paid plans have no free trial.

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; stores on Shopify's trial must upgrade before importing.
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. Migratify shows how many products it found. 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; it does not convert currency), create as active or draft, shipping and 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, 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, weight, SKU, barcode, tags (up to 30), vendor, and product type do come across, per its data list. Metafields are not on that list, so this is the wrong tool if your theme depends on them.

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 and 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, at 4.9 stars from 1,872 reviews on the App Store (checked November 7, 2026). Its pricing page lists a free Demo plan capped at 10 products per job, Basic at $20 per 30 days for 5,000 products per job, Big at $50 for 50,000, and Enterprise at $200 for unlimited. A paid plan can be shared with one additional store, which suits a two-store copy.

Typical steps:

1. Install Matrixify on both stores, or link the second store to your paid plan.
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, such as Metaobjects), 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 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. For a side-by-side of spreadsheet tools, see our bulk product editor app comparison.

Are There Apps That Copy Products and Keep Two Shopify Stores in Sync?

Yes. A newer group of store-to-store apps connects two Shopify admins directly, copies products without a file, and in some cases keeps syncing after the first copy. They cost more than CSV or a URL importer and most are young, so check the review count before you trust one with a live catalog.

Two examples from the App Store, checked November 7, 2026:

• StoreShift (PlanFold) lists products, collections, customers, orders, themes, metafields, metaobjects, discount codes, gift cards, markets, and translations among 25+ data types, with real-time sync on every plan. Pro is about $79 per month for 200 products and 5 destination stores, with a 7-day free trial. It launched July 3, 2026 and has no reviews yet.
• Movely (Tekstur Labs) moves products, customers, orders, collections, and images, and advertises one-click rollback. Its free plan covers 10 products, with paid tiers at 1,000, 5,000, and unlimited products. It launched January 12, 2026 with one review.

The real reason to pay for this lane is ongoing sync. If two stores sell the same physical stock, a one-time copy drifts the moment either store makes a sale. For a one-off catalog copy, the cheaper methods above do the same product work.

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 about 200 products, one-time, no variant metafields: native CSV. Free, transparent, and fine if you keep the source store live for images.
• Public Shopify storefront, no admin access or no wish to touch a spreadsheet: URL importer such as Migratify. Paste a collection or homepage URL and preview before anything is created.
• Metafields, metaobjects, multi-location inventory, or a repeatable pipeline: Matrixify-style bulk spreadsheet. Worth the subscription when fidelity matters.
• Two live stores sharing stock, or customers and orders in the same job: a store-to-store sync app such as StoreShift or Movely, or a dedicated full migration path. Budget for it and test on a handful of products first.

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?

Check prices, images, variants, handles, and publish status on a sample before you touch design or ads. 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.
• Check any theme block that reads variant metafields. Blanks there mean you need a bulk app pass.
• 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 resolve 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 pages that already rank.

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 a 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.