Copy Data Between Shopify Stores (Store Transfer)

Store transfers copy data from one Shopify store into another directly - no export file, no spreadsheet, no import mapping. Typical uses:

• moving a catalog from a development or staging store to production;
• opening a second store (new market, new brand) with the same products and content;
• cloning a store for an agency client or a test environment.

Want to move from WordPress / WooCommerce or Magento instead? See Migrate from WordPress / WooCommerce and Migrate from Magento.

---

Before you start

• DataEase is installed in both stores. Open the app in each store at least once.
• Start from the store that receives the data (the target). The other store (the source) only confirms the request.
• The transfer runs with the target store’s plan and API limits.
• Amounts are copied as-is. If the stores use different currencies, 19.90 stays 19.90 - prices are not converted by exchange rate.

---

Step 1. Request a transfer in the target store

1. In the target store, open DataEase → Store transfers.
2. Choose the From a Shopify store tab.
3. Enter the source store domain, for example my-source-store.myshopify.com.
4. Tick the data you want to copy (see the table below).
5. Click Send request.

The request is valid for 5 minutes.

Step 2. Confirm it in the source store

1. Open DataEase → Store transfers in the source store.
2. The request appears under Incoming requests with the target store name and the list of data.
3. Click Confirm to start, or Reject to decline.

Only the source store can confirm: nobody can copy your data without your approval. A request that is not confirmed in 5 minutes expires - just send a new one.

Step 3. Follow the progress

The transfer runs in the background and appears in the Transfers list of both stores. You can see which entity is being copied right now, and either store can Cancel it.

When it finishes, each entity shows how many records were copied, with warnings and errors (and the reason for the first ones) - for example Products: 120 ✗2.

---

What is transferred

Entities are copied in dependency order, so references between them keep working: products before collections, customers before orders, and so on.

Entity	How it is matched in the target store	Notes
Metafield definitions	namespace + key	Copied first, so metafields of other entities have their definitions.
Products	handle	Variants, options, prices, SKUs, barcodes, weight, cost, media, metafields.
Collections	handle	Manual collections with their products (by handle) and smart collection rules.
Customers	email / phone	Addresses, tags, notes, marketing consent, metafields.
Companies (B2B)	always created	Contacts are linked to the copied customers by email or phone.
Orders	always created	A historical copy: customer, line items (linked to variants by SKU), shipping, transactions. No emails are sent.
Draft orders	always created	Linked to the copied customers and products.
Discounts	always created	Code and automatic discounts with product, collection and customer conditions.
Bundles	always created	Requires Products in the same transfer.
Blogs, articles, pages	always created	Including images and metafields; articles go into the copied blogs.
Menus	handle	Links to products, collections, pages, blogs and articles point to the copied records.
Metaobjects	type + handle	Missing metaobject definitions are created automatically.
Files	always created	Images, videos and documents from Content → Files.
Redirects	always created
Translations	with the entity	Tick Translations to copy translations of the selected products, pages, blogs, articles and metaobjects for languages enabled in both stores.

Not transferred: store settings, themes, sales channel publications, stock quantities, market prices, gift cards, product reviews, blog comments, events and payouts.

Dependencies

The form warns you when an entity depends on another one that is not selected. Bundles cannot be transferred without Products. Other entities are copied anyway, but links to records missing in the target store are skipped - for example, an order line item becomes a custom item if its product was not copied.

---

After the transfer

• Publish products and collections. Sales channel availability is not copied - use a bulk status update or Shopify’s bulk editor.
• Set stock quantities with an inventory import.
• Check prices if the stores use different currencies.

Running a transfer again

Run a transfer once per target store. A second run updates products, collections, customers, menus and metaobjects, but everything marked always created in the table is created again (for example, a second blog “News” with a new copy of the articles), and records with a unique address (pages, redirects, discount codes) fail with “already taken”. To copy more data later, select only the entities you have not transferred yet.

---

FAQ

Does the source store lose anything? No. The source store is only read.

Do customers get emails about copied orders? No. Orders are created without receipts, fulfillment or shipping notifications.

How long does it take? From a minute for a small store to several hours for tens of thousands of products or orders. On some plans Shopify limits how many variants a store can create per day; products over the limit are reported as failed - transfer them again the next day with only Products selected.

Can I copy data between stores of different owners? Yes, as long as someone with access to the source store confirms the request.