Universal Analytics is gone, but many teams still carry legacy event names, broken ecommerce mappings, and reporting gaps in GA4. A structured migration is not just “install a new snippet”—it is an opportunity to rebuild measurement around events, consent, and the reports your stakeholders actually use.

Why migrations still matter in 2026

Even late adopters discover:

• Historical UA comparisons no longer available in standard interfaces
• Ecommerce reports break when items[], value, and currency are inconsistent
• Paid media teams distrust GA4 because conversions do not match Ads or Meta
• Consent changes reduced visible users without modeling configured correctly

A clean GA4 setup fixes data quality and restores confidence across marketing, product, and leadership.

Migration priorities

1. Audit the UA legacy

• Export UA tags, goals, custom dimensions, and enhanced ecommerce settings from GTM or gtag
• Identify “vanity metrics” you will not recreate in GA4
• List integrations (Looker Studio, BigQuery, CRM) still pointing at old schemas

2. Rebuild the event schema

• Use GA4 recommended events where possible (purchase, generate_lead, sign_up)
• Define a naming convention for custom events and parameters
• Document required parameters per event (avoid free-text PII fields)

3. Recreate business-critical reporting

• Conversions marked in GA4 admin with correct counting method
• Audiences for remarketing and product analytics
• Looker Studio or BigQuery dashboards stakeholders rely on weekly

4. Align consent and modeling

• Enable Consent Mode v2 so opted-out users contribute to modeled data where allowed
• Verify analytics_storage gates GA4 hits appropriately
• Compare user counts pre/post consent banner changes

Ecommerce migration checklist

• view_item, view_item_list, add_to_cart, begin_checkout, purchase fire in order
• Item arrays include item_id, item_name, price, quantity
• Transaction-level value, tax, shipping, currency populated consistently
• Refunds and partial cancellations handled if finance relies on GA4

Test with Tag Assistant and GA4 DebugView using real staging products—not only homepage pageviews.

Rollout checklist

• Parallel run UA and GA4 in GTM (where possible) until KPIs match within agreed tolerance
• Stakeholder sign-off on conversion definitions before switching official reports
• Training for marketing on GA4 explorations vs old UA views
• Post-migration audit two weeks after launch—catch tag drift from campaign pushes
• BigQuery export enabled if you need raw event history beyond GA4 UI retention

Common pitfalls

• Duplicating GA4 (hardcoded gtag + GTM tag) inflating users and events
• Mapping UA “Category/Action/Label” literally instead of redesigning for GA4
• Ignoring session_start vs first_visit confusion in funnel reports
• Setting conversion windows differently in GA4 vs Google Ads

When to get external help

Bring in specialists when ecommerce revenue in GA4 does not match your shop platform, consent rollout broke year-over-year reporting, or multiple brands need a unified schema in one GA4 property.