UA to GA4 After the Shutdown: What You Can Still Set Up

A late move from Universal Analytics to GA4 involves two separate questions: whether historical data still exists and how to establish useful measurement now. As of October 2026, deleted, unexported UA data cannot be recovered or newly exported from UA. You can still audit an inherited GA4 setup, create one where needed, and improve the measurement specification.

What the UA shutdown means for historical data

The official shutdown timeline distinguishes Standard UA from eligible UA 360 properties. UA 360 did not universally stop measurement in October 2023. Also distinguish the retired UA 360 product from the current GA4 version of Analytics 360.

Restoring a Google login or administrator access does not restore UA data deleted through the shutdown. Identify saved report dates, definitions, filters, and storage locations. Do not fill an unavailable period with estimates and describe it as recovered history.

Audit existing GA4 properties and connected tags first

An earlier owner may have created GA4, or an automatically created property may already exist. Missing access does not prove that collection is absent. Check properties, website streams, recent receipt, and the team responsible for the implementation before creating another property.

A legacy site tag may have been reused for GA4. Removing everything that looks old can therefore stop current collection. Audit connected destinations and dependencies before replacing code.

Create a GA4 property only when a new setup is needed

When no suitable property exists, follow the current Analytics setup process. Do not make access to a retired UA Setup Assistant the required starting point.

1. Choose a business-managed Analytics account and accountable owners.
2. Create a GA4 property with the appropriate reporting time zone and currency.
3. Create the website stream and record its measurement ID.
4. Choose a supported CMS integration, direct Google tag, or GTM installation.
5. Record the collection start date and verify the intended production environment.

Existing GA4 can often be repaired without duplicating properties. For GTM implementations, use the current Google-tag instructions rather than assuming that older GA4 Configuration tag terminology describes the present workflow.

Validate events, key events, and domain handoffs

A visit appearing in Realtime establishes only a limited observation. Test page loading, unsuccessful submissions, accepted success, and reloads against the business specification. Verify the destination, production hostname, consent behavior, authentication or app journey, and duplicate handling.

Review the key-event counting method. Event-based and session-based counts are neither verified registration headcounts. Website and app data also require an appropriate reporting identity design; placing them in a single property does not automatically establish every person’s cross-device identity.

Compare saved UA reports with GA4 using explicit definitions

A matching metric name does not guarantee matching definitions. Before comparing saved UA totals with GA4, document acquisition conditions, dates, time zone, host coverage, and event meanings. A difference alone does not establish an installation failure or a business decline.

For example, a monthly UA all-channel report cannot directly establish a change against a GA4 organic-only 30-day report. Preserve definition gaps and establish a consistent forward-looking baseline when historical reconciliation is impossible.

Document retention, ownership, and measurement decisions

Data retention controls do not mean that every standard report disappears after 14 months. User-level and key-event retention have 2- or 14-month options; other event data has additional 360 options. Standard aggregated reports and Explorations are affected differently. Extending retention does not recover already deleted records.

Choose settings for the analysis need and organizational policy, then document owners, streams, tag routes, success definitions, collection dates, and unresolved questions. The useful outcome of a late migration is a clear account of what current measurement can support, rather than an unsupported claim that the old environment has been recreated.

Continue with the relevant guide

• How to Install GA4 with the Google Tag or GTM and Check Duplicates
• Google Analytics Login: Fix Sign-In and Missing GA4 Access
• How to Use Tag Assistant to Debug GA4 and Google Tag Manager