Articles on: Onboarding

🚀 Moving your SyncBase setup from a development store to a live store

Moving SyncBase between two different Shopify stores — for example, from a separate development store to your live store — means rebuilding your setup. Here's why, and how to do it cleanly.

Does this apply to you?

Same store going live → nothing to do

If you're trialing SyncBase on the store you'll actually launch — the store goes from development/trial to live, but it's the same Shopify store — your setup stays exactly as-is. Same store means the same Shopify IDs and the same synced base, so SyncBase keeps working and there's nothing to redo. Charges simply begin once the store is live.

👉 Can I try the app with a Development or Partner store?

Two different stores → this guide is for you

If you built your setup on one Shopify store (for example a separate development store) and want it on a different Shopify store (your live store), keep reading.

The rest of this article only applies when you're moving between two different Shopify stores. If it's the same store going live, you're already done.

What carries over — and what doesn't

SyncBase generates a synced Airtable base tied to one specific Shopify store. Two different Shopify stores have different Shopify IDs (Product ID, Variant ID, and the underlying GIDs) and a different synced base.

Because of this, a setup built on one store does not transfer automatically to another. There is no one-click "move to another store" — you set SyncBase up again on the destination store.

⚠️ There's no automatic migration between two Shopify stores. The Shopify IDs and the synced base are different, so the setup has to be rebuilt on the live store.

Recommended approach

Use the development store to learn and finalize how you want everything structured — your tables, metaobject definitions, and the relationships between them. Once you're confident in the structure, do the final build directly on your live store.

Avoid building the "real" version on the development store expecting to copy it across: most of the setup work has to be repeated on the live store either way, so it's more efficient to practice on the dev store, then build for real on the live one.

Step-by-step: going live

1. Finalize your structure on the development store

In Shopify and Airtable, get your metaobject definitions, tables, and relationships right while you're still testing. Treat the dev store as your rehearsal.

2. Install SyncBase on your live store

From your live store's Shopify admin, install SyncBase and select your plan.

👉 How to connect Airtable to Shopify with SyncBase

3. Generate a fresh synced base for the live store

SyncBase creates new synced tables and fields for this store. This base is specific to the live store and uses its own Shopify IDs.

4. Rebuild your structure and data on the live store

Recreate the metaobjects, tables, and links you validated on the development store. Your data will sync using the live store's own IDs.

Good to know

Building on the live store is real work, not a quick copy — plan for it rather than expecting a two-hour job.
If SyncBase already generated a base on this live store from an earlier attempt, watch for table and field name conflicts: SyncBase can't recreate a field or table whose name already exists from a previous generation. Start from a clean base, or cross-reference the existing names before you begin.

To work safely on a live store, test changes on a draft product first so you never touch live customer-facing data before you're sure.

Need help?

A store-to-store rebuild — especially with custom Airtable automations or reference-GID / metaobject-relation work — is usually more than a quick fix. Chat with us and explain your use case, or email support@syncbase.app — we'll guide you, or prepare a custom SyncBase Studio proposal to build it for you.

Updated on: 02/07/2026

Was this article helpful?

Thank you!