Magento to Shopify Migration: The Conversion Tracking Checklist

TL;DR

Migrating from Magento to Shopify does not automatically carry your conversion tracking over. Your GA4 property ID can be reused, but every tag, pixel, and consent configuration needs to be rebuilt from scratch on the Shopify side. The biggest risk is a gap period where you lose attribution data right when your new store goes live. This checklist covers what transfers, what you have to redo, and exactly when to cut over tracking versus keeping both setups running in parallel.

What Actually Transfers During a Magento to Shopify Migration?

Not much, when it comes to tracking. The data layer, custom events, and tag manager setup are all Magento-specific and will not follow you.

Here is what each tracking component looks like on both sides:

The property and pixel IDs are just identifiers. They survive the migration. Everything that wraps around them, the code that fires them, the events that trigger them, and the consent logic that controls them, is platform-specific and has to be rebuilt.

How Do You Rebuild GA4 Tracking on Shopify After Migrating?

You keep your existing GA4 property and add a new web data stream pointed at your Shopify domain. This preserves historical data and keeps reporting continuity.

The practical steps:

1. Go to your GA4 property and create a new web data stream under the same property.
2. Note the new Measurement ID (format: G-XXXXXXXXXX).
3. Install your Shopify tracking app and enter this Measurement ID.
4. Map the standard Shopify events (view_item, add_to_cart, begin_checkout, purchase) to GA4 recommended events.
5. If you were using Enhanced Ecommerce in Magento, confirm the same parameters (item_id, item_name, value, currency) are firing on Shopify.
6. Verify in GA4 DebugView before you go live.

One thing I see merchants miss: the old Magento data stream will still exist in the same property. That is fine. It just goes quiet after cutover. Do not delete it right away because you may need to compare pre/post migration metrics.

If you used our WeltPixel GA4 extension on Magento, you already know what proper Enhanced Ecommerce event coverage looks like. The Shopify equivalent is the WeltPixel Conversion Tracking app, and it maps the same events with the same parameters so your historical and new data stay comparable in the same property.

What Has to Be Rebuilt from Scratch?

Consent Mode, custom funnels, and any non-standard events are a full rebuild. Do not assume anything Magento-side carries over automatically.

Consent Mode: Magento's consent banner integration is separate from Shopify's. Shopify has its own consent API [1]. You need to connect your CMP (OneTrust, Cookiebot, or native Shopify consent) to your tracking app's consent mode implementation. If you skip this, you will likely fire tags without consent on markets where that creates legal exposure (EEA, UK, California).

Custom events: If you tracked custom Magento events like loyalty point redemptions, wishlist adds, or configurator interactions, those need to be re-implemented on Shopify. There is no migration path. You are writing new code or using a new app.

Google Tag Manager: A Magento GTM container has Magento-specific triggers and data layer variables. Shopify's data layer is structured differently [2]. You can import your old container as a starting point, but every trigger and variable will need review. In practice, I have found it faster to build a clean Shopify GTM container than to fix an imported Magento one.

Server-side tagging: If you ran server-side tagging in Magento, the setup does not transfer. You need to reconfigure your server container with Shopify as the data source.

When Should You Cut Over Tracking, and When Should You Dual-Run?

This is the question most migration guides skip. The answer depends on your traffic volume and how much data loss you can tolerate.

Dual-running (both Magento and Shopify tracking active at the same time) makes sense if:

• You are running a phased migration with some traffic still going to Magento.
• You want to validate Shopify tracking accuracy before fully switching.
• You are migrating close to a high-traffic period (holiday, sale) and cannot afford attribution gaps.

During dual-run, you will see inflated event counts in GA4 if both streams fire for the same session. Keep your data streams separate and use the stream ID filter in GA4 reports to isolate traffic.

Cut over immediately if:

• Your Magento store goes fully offline on migration day.
• You have validated Shopify tracking in a staging environment beforehand.
• You are using server-side forwarding on Shopify, which makes dual-run validation much cleaner anyway.

The recommended sequence:

1. Set up Shopify tracking in staging, validate all events.
2. On go-live day, confirm Shopify tracking fires on the live domain.
3. Disable or archive the Magento GTM container / tracking extension.
4. Monitor GA4 DebugView and real-time reports for the first 48 hours.
5. Check for zero-value purchase events (a common Shopify data layer bug) within the first week.

How Does Server-Side Tracking Change the Migration Picture?

Server-side forwarding is worth setting up during the migration rather than bolting on later. It improves data quality and reduces the number of browser-side tags you have to maintain.

On Magento, most server-side setups ran through GTM server-side containers with a custom data layer. On Shopify, the approach is different. Shopify's server-side events come from the Shopify webhooks or the Conversions API (for Meta) and Enhanced Conversions (for Google Ads), either through a native integration or a third-party app. We migrated weltpixel.com itself from Magento to Shopify in April 2026 and rebuilt our own tracking through this exact approach, which is one reason this article is more specific than most migration guides. The deeper architecture trade-offs sit in our server-side GA4 article.

Benefits of migrating with server-side tracking already in place:

• Cookie-based signal loss from browsers (Safari ITP, Firefox ETP) affects client-side tags more than server-side events [3].
• Conversion rates reported in Meta and Google Ads tend to be higher with server-side because deduplication catches events blocked client-side.
• You avoid the gap where client-side tags get blocked by ad blockers right after launch when your new store is getting crawled and reviewed.

Public vendor data quantifies the gap: Stape's published case studies report event recovery of up to 40% when adding server-side forwarding to a previously browser-only setup, and Elevar customer studies have shown recovery in the 10-36% range. Exact numbers vary by audience, device mix, and geography, but the directional gain is consistent across vendors.

What Is the Full Pre-Launch Tracking Checklist?

Use this before you cut over your DNS or announce the new store.

Before launch:

• [ ] GA4 new web data stream created under existing property
• [ ] New Measurement ID entered in Shopify tracking app
• [ ] All standard ecommerce events verified in GA4 DebugView (view_item, add_to_cart, begin_checkout, purchase)
• [ ] Purchase event includes correct value, currency, transaction_id
• [ ] Meta Pixel re-linked to Shopify store via app
• [ ] Meta CAPI token configured (server-side)
• [ ] TikTok Pixel ID entered, events mapped
• [ ] Google Ads conversion actions remapped to Shopify purchase event
• [ ] Consent Mode configured and tested for EEA/UK traffic
• [ ] GTM Shopify container published and verified

After launch (first 48 hours):

• [ ] Real-time GA4 report shows sessions and events
• [ ] No duplicate purchase events firing
• [ ] No zero-value purchase events
• [ ] Meta Events Manager shows purchase events with healthy match quality (Meta's EMQ scale; aim for "Good" or higher)
• [ ] Google Ads shows conversion data within expected delay window (up to 3 days for view-through)
• [ ] Consent Mode logs show correct granted/denied signals

Key Takeaways

• Your GA4 property ID survives the migration. Create a new data stream under it rather than a new property, so historical data stays in one place.
• Meta, TikTok, and Google Ads pixel/tag IDs are reusable, but every implementation detail has to be redone in Shopify's environment.
• Consent Mode does not migrate. Rebuild it explicitly on Shopify, especially if you serve EEA or UK traffic.
• Dual-running both tracking setups is worth it during a phased migration or when you want to validate before full cutover.
• Server-side forwarding is easier to set up correctly during the migration than to retrofit later.
• Custom Magento events (loyalty, configurator, wishlist) require custom re-implementation on Shopify. There is no automated transfer.
• Validate in GA4 DebugView and Meta Events Manager before your store goes live, not after.

FAQ

Can I keep the same GA4 property when migrating from Magento to Shopify?

Yes. You keep the same GA4 property and add a new web data stream for your Shopify domain. This means your historical Magento data and new Shopify data sit in the same property, making year-over-year comparison possible without data stitching.

Will my Meta Pixel lose its training data when I switch to Shopify?

No. Your Meta Pixel ID is an account-level identifier, not tied to your platform. Re-link the same Pixel ID in your Shopify tracking setup and the event history stays. The Pixel's optimization model continues building on past purchase signals.

How long does the Shopify tracking setup take after a Magento migration?

For a standard setup (GA4, Meta, Google Ads) using a dedicated tracking app, most merchants can complete configuration in a few hours. Validation and consent mode tuning generally adds another day. Custom event tracking, if you had complex Magento-specific events, can add several days depending on development resource.

Do I need a new Google Ads account when I migrate to Shopify?

No. Your Google Ads account and conversion actions transfer over. You will need to update the tag implementation to fire from Shopify, and remap conversion actions to the new purchase event source, but the account history, quality scores, and audience lists are not affected by the platform change.

What happens to my Shopify tracking if I had server-side tagging on Magento?

Your Magento server container configuration does not transfer. On Shopify, you set up server-side tracking through Conversions API (for Meta) and Enhanced Conversions (for Google Ads), either natively or via an app. The concept is the same but the implementation is a fresh setup.

Migrate Your Tracking the Right Way with WeltPixel Conversion Tracking

If you used our WeltPixel GA4 extension on Magento, you already know what complete ecommerce event coverage looks like. WeltPixel Conversion Tracking is the Shopify equivalent, and it was built specifically so merchants can replicate that same level of tracking on Shopify without starting from zero.

It handles GA4 Enhanced Ecommerce, Meta Pixel with CAPI server-side forwarding, TikTok Pixel, and Google Ads conversion tracking from a single app. Consent Mode is built in, not bolted on. And the event parameter mapping is designed to match what our Magento extension outputs, so your GA4 data stays comparable across the migration.

If you are in the middle of a migration or planning one, install the app and configure your tracking in staging before launch.

Install WeltPixel Conversion Tracking on Shopify

Sources

1. Shopify Developer Documentation, Customer Privacy API: https://shopify.dev/docs/api/customer-privacy
2. Shopify Developer Documentation, Web Pixels API and Data Layer: https://shopify.dev/docs/api/web-pixels-api
3. Apple ITP and Firefox ETP impact on cookie-based tracking, documented by IAB Tech Lab and browser vendor release notes: https://webkit.org/blog/9521/intelligent-tracking-prevention-2-3/