Skip to content

GrowthDept Commerce is in build. Brands Growth Dept already runs get it first. Each feature on these pages is marked in testing, in build or planned.

Shopify mirror and migration

Shopify stays in charge until you decide otherwise.

Commerce keeps its own copy of your store, matched to Shopify record by record. Your shop keeps selling on Shopify, and Growth Dept's apps work from the copy. Moving later means changing which side is in charge, not starting over.

StageTakes ordersFinal word on data
MirrorShopifyShopify
Apps on the copyShopifyShopify
Testing the switchShopify, plus test orders on CommerceShopify
After the switchCommerceCommerce
Shopify stays in charge through every stage until the last one.

The mirror

A copy that stays current

The first import

In testing

Commerce reads your products, variants, collections, inventory, orders and the rest of what Shopify lets an app read, in bulk. Each record gets a Commerce ID and keeps its Shopify ID. Customer contact details stay off until they are switched on for your store.

Every change after that

In testing

When Shopify reports a change, Commerce reads the record again rather than trusting the notice alone. Notices can arrive out of order or not at all, so a scheduled check looks for anything that changed since the last pass and fills the gap.

Deletions are confirmed first

In testing

A record that seems to have disappeared is marked, not erased, until Commerce asks Shopify for it directly and Shopify confirms it is gone.

Edits while Shopify is in charge

In testing

Commerce writes to a Shopify store only when write-back is turned on for it. Then an edit made in Commerce goes to Shopify first and is saved from Shopify's reply. If both sides changed the same thing, Shopify's version wins and your edit is kept as a conflict, never dropped without a trace.

Limits

What an ordinary copy can't move

Some things can't move with an ordinary copy: customer passwords, saved payment cards, and subscriptions billed through another app. Each needs its own migration plan, worked out with you before the switch. Themes bought from a theme store, and features that come from Shopify apps, need checking one by one.

The switch

Moving the system of record, on purpose

  1. Mirror

    Commerce imports your store and follows every change. Nothing about how you sell changes.

  2. Apps on the copy

    Attribution, email, testing, reviews and support work from Commerce's copy.

  3. Test the switch

    Your storefront and checkout run on Commerce with test payments until they work the way your live store does.

  4. Switch

    Commerce becomes the system of record. It takes your approval and Growth Dept's, every step is recorded, and it can be undone until your domain points at Commerce.

The switch itself

In build

The approval and the record of each step are built. The storefront and checkout a store needs before it can switch are not built yet.

Connect Shopify and look at your own data.

The mirror only reads from your store until write-back is turned on. The move can wait as long as you like.