Move an entire Shopify store, one file at a time.

Data types

Everything the app moves is grouped into selectable data types. You choose which ones to include in every job.

• Products & variants
• Collections
• Customers
• Companies
• Orders & Draft Orders
• Discount codes
• Pages & Blog posts
• URL redirects
• Navigation menus
• Metaobjects
• Metafields & definitions
• Files & media

Dependencies

Some data types depend on others. Product exports automatically include variants, images, and metafields. Metafield definitions are bundled with the collections and pages that use them. Metaobject file-reference fields point at your Files library, so if you export metaobjects without Files, those fields come in empty on the destination.

Bulk operations

Large jobs run through Shopify's Bulk Operations API in the background, so a store with 100k+ records won't time out. Progress shows on the Dashboard and the job's status page; you can close the tab and come back.

The standard store-to-store migration, end to end.

1. 1

   Install on both stores

   Add Transfer Store to the source store and the destination store, and subscribe to a plan on each (there is no free tier). The plan you need depends on record counts; see Plans & limits.

2. 2

   Select your data

   On the source store, open Export → New Export. Tick the data types you need. Pick a format: Excel (.xlsx), with one sheet per data type, or CSV (.zip), with one CSV per type in an archive.

3. 3

   Run the export

   Click Start export. The job processes in the background. When it finishes it appears under Recent Exports on the Dashboard and on the export access card.

4. 4

   Download the file

   Download the .xlsx or .zip from the Dashboard. Files are hosted on cloud storage behind time-limited signed links and are purged automatically after the job expires.

5. 5

   Import to the destination

   On the destination store, open Import Data, drop the file, and click Start Import. Metafield Definitions, Metaobject Definitions, Metaobject Entries and Navigation Menus are recreated in dependency order, with no manual setup.

6. 6

   Verify

   Check the Import Log for skipped or failed rows. Re-run with a corrected file if needed; imports match on handle/key and update in place rather than duplicating.

From Export → New Export, choose one or more data types and a format, then start the job. The Export Summary lists what will be included, including dependencies the app adds for you.

Formats

What's always bundled

• Products → variants, images, SEO fields, metafields.
• Collections & Pages → the metafield definitions they reference.
• Metaobjects → entries and definitions (add Files for reference fields).

Export status

The Sync Status view and the Dashboard's Export Activity panel show counts for In progress, Completed, and Failed jobs. A failed job reports the error on its status page; fix the cause and start a new export.

Open Import Data, drop in a .xlsx or .zip produced by Transfer Store, and click Start Import.

What gets imported

• Metafield Definitions: owner types, validations, namespaces.
• Metaobject Definitions: schemas, field configs, types.
• Metaobject Entries: all records and their field values.
• Navigation Menus: menu items and nesting.
• Products, Collections, Customers, Pages, Blog posts, Redirects, Discounts, where present in the file.

Ordering & idempotency

The importer creates definitions before the records that depend on them, so a single file imports cleanly in one pass. Re-importing the same file updates matched records in place (by handle or key) rather than creating duplicates.

Import order

1. 1

   Metafield Definitions: Owner types, validations, namespaces.

2. 2

   Metaobject Definitions: Schemas, field configs, types.

3. 3

   Metaobject Entries: All records and their field values.

4. 4

   Navigation Menus: Menu items and nesting.

5. 5

   Records: Products, Collections, Customers, Pages, Blog posts, Redirects, Discounts, wherever present in the file.

Import Log

Every run writes a log listing created, updated, skipped, and failed rows with reasons. Check it before assuming a migration is complete.

Move data straight from a source store to a destination store with no download in between. Requires a plan that includes Link a Store on both.

1. 1

   Generate a link code

   On the destination store, go to Link a Store and click Generate code. Codes such as 4G7WQ9ZX expire after 15 minutes and are single-use.

2. 2

   Enter it on the source

   On the source store's Transfer page, paste the code to connect the two stores. Once linked, the pair shows under Linked stores on both sides.

3. 3

   Choose data and run

   Select data types and start the transfer. It runs entirely server-side using Bulk Operations, resuming automatically across batches for large datasets.

Use Export Files (from the Dashboard) to pull your Shopify Files library (images, videos, and documents) as a downloadable archive. This is the same mechanism the app relies on when importing metaobject and product reference fields.

• Files are staged in cloud storage during an active job and deleted when it completes or expires.
• Download links are signed and time-limited.
• For migrations, prefer including Files in the main export or transfer so references resolve automatically.

A subscription is required; there is no free tier. Limits are per-store record ceilings for a single job. A coupon can be applied on the subscribe screen.

For a two-store migration, both stores need an active subscription. Direct transfer additionally requires Grow or Enterprise on the destination.

Transfer Store reads store data only for jobs you start, and does not sell data or use it for advertising.

• Session data. Shopify tokens; stored while the app is installed and removed on uninstall.
• Transfer files. Staged in cloud storage during an active job and deleted automatically afterward.
• Subprocessors. Shopify (platform & data source), a cloud web host, and cloud object storage (transient staging).
• The app implements Shopify's mandatory compliance webhooks (customers/data_request, customers/redact, shop/redact).

Full text: Privacy Policy. Data questions: support@speedyapps.in.