Cherry Seed

Can you move a Data Tree to a new website?

data-tree website-migration bigquery data-portability woocommerce first-party-data

Quick Answer

Yes — because the Data Tree lives in your BigQuery warehouse, not on your website. The website is the source of new events, but the accumulated historical data sits in infrastructure you own independently. When you migrate to a new domain, redesign your store, or even switch ecommerce platforms, your BigQuery tables remain intact and queryable. You reconnect the collection pipeline to the new site — new inPIPE install, new server-side tracking configuration — and fresh events begin flowing into the same warehouse alongside your existing history. No data is lost in the transition.

Full Answer

This is one of the core advantages of separating your data asset from your website platform. GA4 ties your analytics to a specific property — change domains, restructure your site, or switch platforms, and your GA4 history either resets or requires complex property migration that rarely preserves everything. Your Data Tree in BigQuery has no dependency on your website's domain, platform, or hosting.

The migration process has two parts. The historical data requires nothing — it already lives in BigQuery tables that you control through your Google Cloud project. Those tables remain exactly where they are, queryable as before, regardless of what happens to the website that generated the original events.

The collection pipeline requires reconnection. On a new WooCommerce site, that means installing the inPIPE plugin, configuring your server-side tracking endpoint, and pointing event output to the same BigQuery dataset. The first event from your new site lands alongside years of historical data from your old site. Attribution queries, cohort analysis, and LTV calculations continue with an unbroken timeline.

If you switch platforms entirely — from WooCommerce to Shopify, for example — the collection mechanism changes but the destination stays the same. Shopify's webhook system feeds the same BigQuery tables through a different pipeline. The schema may need adjustment, but the historical record remains intact.

Data you own in infrastructure you control is portable by default. Data that lives inside a platform is portable only if the platform allows it.

Sources

Programmatic Access

GET https://seresa.io/wp-json/cherry-tree-by-seresa/v1/seeds/891

Cite This Answer

Cherry Tree by Seresa - https://seresa.io/seed/data-trees/can-you-move-data-tree-new-website