Do we lose years of historical conversion and revenue-attribution data when migrating a custom platform's tracking setup to Shopify?
Short answer
Historical revenue survives a move to Shopify; session attribution does not. Imported orders can keep the date Shopify's reports use (Shopify developer docs, October 2026). Sessions stay behind because Shopify counts them only on its storefront (Shopify Help Center, October 2026). Google Analytics 4's standard properties cap event-level data, not aggregated reports, at 14 months (Google Analytics Help, October 2026).
- Imported order dates
- Can keep the original processed dateShopify says the processed date is the one used in the analytic reports, and an import can set it in the past to match the original order (October 2026).Source: Shopify developer docs (OrderCreateOrderInput)
- Channel on imported orders
- The import app, not the original channelMatrixify says the order channel shown in Shopify's admin and analytics will always be Matrixify; a custom source is saved behind the scenes (October 2026).Source: Matrixify (Import and Export Orders from Shopify in bulk with Matrixify)
- Shopify session history
- 1 October 2022 at the earliestShopify counts sessions with cookies on its own online store, so the old site's sessions never appear in Shopify's reports (October 2026).Source: Shopify Help Center (Acquisition reports)
- GA4 event data retention
- 2 or 14 months; up to 50 on Analytics 360Key events keep the 2 or 14 month user-level limit, and standard aggregated reports aren't affected. Universal Analytics data went from July 2024 unless exported (October 2026).Sources: Google Analytics Help (Data retention, Google Analytics 4 has replaced Universal Analytics)
Deploi’s call
The order data is not at risk and the schema continuity is. We front-load one deliverable on every replatform that has an analytics dependency: a written event and identifier schema, agreed before build starts, that the new site is implemented against. Everything else that breaks at cutover can be recovered, or exported in time. A schema decided implicitly by a new theme cannot.
CustomizeWrite the event and identifier schema before build when
- Anyone will compare the year after cutover with the year before, in Google Analytics or an ad platform.
- The new theme or pixel will rename events, parameters or product IDs, because a renamed event splits every year-over-year chart.
- Three or more tools read your storefront events, the case Deploi's tracking-plan record scores CUSTOMIZE: buy the plan tool, build the schema and the pixel that obeys it (October 2026).
WaitLeave old analytics history where it is when
- Nobody has opened the report in a year.
- The metric is a rate computed on the old site's tracking.
- Keeping it means standing up a warehouse you don't have, while Deploi's historical order export record scores a build only when a warehouse is the destination (October 2026).
Basis: Build or Buy Event Tracking-Plan Governance on Shopify?, our Build vs. Buy decision record, scored CUSTOMIZE.
Which historical data survives a move to Shopify?
Order facts survive a move to Shopify, and order-level attribution survives in part. Session data never moves, because it lives in your analytics platform.
| Data | Where it lives | What a move to Shopify keeps |
|---|---|---|
| Order facts: revenue, units, customer, date, discount | The order record | Revenue, units, customer and date, with the original processed date; one discount code per order at most |
| Order-level attribution: referring site, channel, campaign tags | Fields on the old order | The referring site. Campaign tags belong in an order metafield, and the channel shows the import app |
| Session and behavioral data: sessions, bounce, funnel steps, assisted paths | Your analytics platform | Nothing moves, and nothing is deleted |
Shopify's order import has a field for the referring site but none for campaign tracking (UTM) values (Shopify developer docs, October 2026). An order's customer journey comes from visits to Shopify's own online store (Shopify developer docs, October 2026), so imported orders arrive without one. Matrixify, a bulk import app, says the order channel in Shopify's admin and analytics "will always be “Matrixify”" for its imports (Matrixify, October 2026). So if anyone will report on old channel and campaign values, keep them in order metafields, not custom attributes. Shopify can filter and report on metafields whose definitions allow it (Shopify developer docs, October 2026).
What attribution history is already gone before you migrate?
Much of the attribution history people fear losing was already gone, or reduced to aggregates, before anyone drew a migration plan, because three limits apply whether you migrate or not.
- Shopify starts counting sessions at your launch. Shopify bases sessions on cookies set by its own online store, and its history for session-based metrics goes back only to 1 October 2022 (Shopify Help Center, October 2026). The old site's sessions never enter Shopify's reports.
- Google Analytics 4 (GA4) deletes event-level data on a schedule. Standard properties keep event data for 2 or 14 months, and Analytics 360, Google's paid tier, for up to 50. Key events, GA4's conversions, keep only the 2 or 14 month user-level limit. Expired data is deleted "automatically on a monthly basis", but the retention setting "does not affect standard aggregated reports", and Google Ads data in GA4 covers a rolling 36-month window (Google Analytics Help, October 2026).
- Universal Analytics history is gone unless you exported it. Standard Universal Analytics properties stopped processing hits on 1 July 2023, and from the week of 1 July 2024 Google ended access to all Universal Analytics data (Google Analytics Help, October 2026).
So the multi-year history still at stake is mostly GA4's aggregate reports, which the move doesn't touch, and the old platform's own reports, which go when it's switched off.
Why do year-over-year comparisons break at cutover?
Year-over-year comparisons break at cutover because the new site sends different events and identifiers, even though both sides of the seam have data.
- Event schema discontinuity. A new theme and pixel change event names, parameters and product identifiers. Google says even moving a Shopify store's Analytics tag into a custom pixel can change reported data "due to differences in event measurement and tag behavior" (Google Analytics Help, October 2026). Fix: freeze and document the event schema before cutover, and build the new site against it. Renaming an event after launch "splits your history in every downstream tool at once", as Deploi's tracking-plan record puts it (October 2026).
- Identifier changes. Product IDs, variant IDs and stock keeping units (SKUs) often change in a replatform, so every product-level report keyed on the old ID stops joining. Fix: keep the legacy ID as a product metafield and carry it into the analytics payload.
- A new analytics property. A fresh Google Analytics 4 (GA4) property at launch splits the history by design. Fix: keep the existing one, which Shopify's Google & YouTube app lets you pick "from the dropdown" (Google Analytics Help, October 2026).
Shopify treats its own seams the same way: across its 21 to 23 September 2026 session measurement rollout, it tells merchants to "treat the update as a measurement change" (Shopify Help Center, October 2026).
What else breaks at cutover besides the event schema?
Besides the event schema, two things break at cutover: ad platforms recalibrate on new conversion data, and the old platform's own reports go when it's switched off. Those reports are the one item with a deadline.
- Ad platform learning. A new domain, pixel or conversion action gives automated bidding new data to learn from. Google's advice: "After you set up conversion tracking, wait for a few conversion cycles before implementing a new bid strategy" (Google Ads Help, October 2026). Fix: sequence the changes and hold a stable measurement window on either side, so you can tell a platform reset from a performance change. How long to hold structural changes after a tracking change has its own answer. For the attribution ad platforms lose from now on, see what server-side tracking can recover and whether it pays at $10M a year.
- The old platform's own reports. A custom platform's reports go when the platform does. Fix: export them before switch-off, not after.
When should you not pay to preserve old analytics history?
Don't pay to preserve old analytics history when nobody reads it, when it's a rate, or when keeping it needs a warehouse you don't have.
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- Migration vendors answer this question by selling more data migration. The honest answer is that the expensive part of the loss is not historical, it is prospective: the comparability of the next twelve months against the last twelve. That is fixed with a schema document and instrumentation discipline, not with a larger import.
- Our judgment on post-launch complaints
- In our judgment, the reporting complaint after a launch is rarely missing history. It's that the new site emits different events under different names, so the two periods won't sit in the same chart.
- What this page adds
- that imported orders keep their dates but report under the import app's channel, that Shopify counts sessions only on its own storefront and from 1 October 2022 at the earliest, and that GA4 standard properties cap event-level data, not aggregated reports, at 14 months while Universal Analytics data went in July 2024 unless exported, so much of the multi-year attribution history in question was already gone or reduced to aggregates.
Decision records behind this answer
When this answer changes
- Shopify adds an order-import field for campaign tracking (UTM) values, the landing page or the customer journey.
- Shopify lets imported orders keep their original sales channel in reports instead of the import app's.
- Google changes GA4's event-data retention options, the key events limit or the 36-month window for Google Ads data.
- Shopify changes how it measures sessions again, as it did from 21 to 23 September 2026.
- Shopify extends session-based history before 1 October 2022, or opens a way to import sessions.
Related questions
- Does moving to server-side tracking actually recover the ad-attribution accuracy lost to iOS App Tracking Transparency and third-party cookie blocking?
Server-side tracking recovers ad-blocked events (Shopify, October 2026), some attribution lost to cookie blocking and none lost to App Tracking Transparency.
- Is server-side tracking overkill for a mid-market Shopify brand doing $10M/year, or is it only worth it above a certain ad-spend threshold?
Server-side tracking is not overkill at $10M a year, because paid spend decides it, not revenue.
- Should marketing pause paid-spend optimization decisions for a period after the Aug 26 migration until reporting numbers are re-validated?
Marketing keeps paid spend on after the 26 August 2026 non-Plus script-tag cutoff (shopify.dev, October 2026) and pauses only structural changes.
- What order-level custom fields (gift messages, engraving instructions, delivery-date selections) need special handling during an order-history migration?
Engraving instructions and delivery-date selections need special handling; gift messages need only consistent keys.
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Shopify developer docs, OrderCreateOrderInput
- Shopify Help Center, Acquisition reports
- Google Analytics Help, Data retention
- Google Analytics Help, Google Analytics 4 has replaced Universal Analytics
- Google Analytics Help, Update your Google Analytics integration on Shopify with the Google & YouTube app
- Shopify developer docs, CustomerJourneySummary
- Matrixify, Import and Export Orders from Shopify in bulk with Matrixify
- Google Ads Help, How our bidding algorithms learn
- Shopify developer docs, orderCreate
- Shopify developer docs, Use metafield capabilities
- Deploi Build vs. Buy, Build or Buy Event Tracking-Plan Governance on Shopify?
- Deploi Build vs. Buy, Should You Build or Buy a Historical Order Export Tool?