Choose a language

Analyst comparing a dashboard on a laptop with a checklist on a tablet

GA4 Migration Checklist: Move Without Losing Data

Published November 5, 2026 · Mis à jour le November 16, 2026 · 15 min read

Migrating to GA4 is not a flick of a switch, it is a project with a beginning, a middle, and a clear end. Get the order wrong and you end up with gaps in your reports, duplicated conversions, or historical data you can no longer open.

This guide gives you the checklist in the order you will actually use it: audit what you have, build the new property, run both tools side by side, validate the numbers, set up Consent Mode v2, archive your old data, and monitor after launch. Each section answers one question and tells you what to decide before moving on.

The path in 7 steps

The steps of this page, in order.

  1. 01 Audit what you have List every UA property, view, goal, and filter you rely on today.
  2. 02 Build the GA4 property Create the property and data streams, and install the new tag.
  3. 03 Run both in parallel Keep UA and GA4 collecting at the same time to compare and catch gaps.
  4. 04 Rebuild goals as events Translate each UA goal into a GA4 event and mark the key ones as conversions.
  5. 05 Validate the data Check numbers before, during, and after the switch against known benchmarks.
  6. 06 Set up Consent Mode v2 Wire consent signals so you do not lose data from users who decline.
  7. 07 Archive and monitor Export your UA history, then watch GA4 daily for the first weeks.

01 / 10

What is the difference between UA and GA4?

GA4 records events instead of sessions, so your old reports will not map one-to-one to the new ones.

In Universal Analytics (UA), the old Google Analytics that tracked sessions and pageviews and no longer collects new data, activity is grouped into sessions. GA4, the current version, records each action as an event, a single action like a click or a purchase.

Because of that, goals, funnels, and bounce rate are defined differently, so your old reports will not map one-to-one. Start with a pre-migration audit of your UA property to list every goal, filter, and custom dimension you rely on.

Core concepts: UA vs GA4

ConceptUniversal AnalyticsGA4
Unit of trackingSessionEvent
PageviewA hit typeAn event with parameter page_view
Goal or conversionGoal (destination, duration, pages/session, event)Conversion (any event marked as conversion)
Bounce rate% of sessions with only one pageview% of sessions with no engagement (not a true bounce by default)

Comparison based on Google Analytics documentation (as of November 2026).

02 / 10

What should I check before I start the migration?

Before touching anything, write down every UA property, goal, and report your team actually uses.

A property is the container in Google Analytics that holds data for one website or app, and each one can have several views with different filters. Screenshot the admin list and note the account owner, editors, and read-only users, because accounts get locked when the owner leaves.

Export your goal list and the ten reports your team opens most. If Google Tag Manager is already installed, the upgrade is simpler: confirm the container ID, then identify which consent tool is running, because that setting must be reproduced in GA4.

List every UA property and view

Open Admin, then Account Settings and Property Settings, and record each ID, site, and view. Views hold the filters and goals you cannot recover after sunset.

Export your goal list

Go to Admin > Goals and download the table as CSV. Each goal name, type, and destination URL becomes your build spec for GA4 events.

Review account access

Open Admin > Account Access Management and list every user with their role. Remove departed contractors now, so the GA4 property is created with the right owners.

Confirm Google Tag Manager

Check whether the site loads from a GTM container and note the container ID. If yes, your GA4 tags will be added there rather than hard-coded on the site.

Record the consent management platform (the banner that collects cookie choices) and where it fires. GA4 consent settings must mirror that behavior to stay compliant.

Save benchmark numbers

Export a 12-month report of sessions, users, and conversions per channel. These numbers are your only baseline for spotting gaps after the switch.

Laptop showing analytics charts next to a checklist notebook

Going further

Show export steps

03 / 10

How do I create the GA4 property and data stream?

Create the property, add a web data stream, and install the Google tag, ideally through Google Tag Manager.

Most small businesses only need one GA4 property per website. It keeps reporting simple and avoids splitting sessions across duplicates. Set it up in the admin panel, then add a web data stream, the connection between your site and the property.

Keep your old Universal Analytics tag running for now. Install GA4 through Google Tag Manager: add a GA4 configuration tag fired on all pages, use Preview to confirm it fires once per page, then publish.

  1. Open Admin

    In Google Analytics, go to Admin and select Create Property.

  2. Name the property

    Use a clear name such as 'Main website, GA4', plus your reporting time zone and currency.

  3. Create a web data stream

    Enter your website URL to generate the stream and its Measurement ID (a code like G-XXXXXXX).

  4. Add the GA4 configuration tag

    In Google Tag Manager, create a Google tag using that Measurement ID, triggered on All Pages.

  5. Preview, then publish

    Use Tag Assistant Preview to confirm the tag fires, then publish the container.

Diagram of the configuration steps of an analytics property

04 / 10

Should I run UA and GA4 at the same time?

Yes. Parallel tracking is the only way to compare old and new numbers while both sources are still reliable.

Parallel tracking means running your old Universal Analytics tag and your new GA4 tag on the same pages. Keep both live for at least four to eight weeks, so you can spot gaps while UA still reports. This overlap is your only reference point before UA data goes away.

Compare key metrics side by side each week, like purchases and form submissions, and note the natural gap between the two models. Use those comparisons to fix tagging problems while you still have a baseline. Once you turn UA off, that safety net is gone.

05 / 10

How do I move my goals to GA4 events?

Each UA goal becomes a GA4 event, and only the events that matter to the business should be marked as conversions.

An event is a single action a user takes, a click, a form submit, a purchase, that GA4 records. Start by listing every UA goal and giving it one event name you will keep stable for years, so reports and audiences do not break when marketing asks for a change.

Mark only events tied to revenue or a lead as conversions; leave the rest unmarked to keep reports clean. Send each event through GTM's preview mode and check it in GA4's DebugView before you trust it.

UA goal to GA4 event mapping

UA goalGA4 event and conversion status
Newsletter signupgenerate_lead, conversion
Contact form submitform_submit, conversion
Purchasepurchase, conversion
PDF downloadfile_download, no conversion
Outbound link clickoutbound_click, no conversion

Example mapping for a small business. Event names are illustrative; keep your own naming convention consistent.

06 / 10

How do I know the data is correct before I switch off UA?

Compare a handful of known numbers, traffic, sign-ups, revenue, against a fixed reference before you retire the old tag.

Pick one full week that both tools tracked, then pull the same three numbers from GA4, UA, and your own back-end records: sessions, sign-ups, and revenue. A gap of a few percent is normal, because the two tools count sessions and attribute credit differently. A gap of 30 percent or more points to a tagging bug, not a reporting quirk.

Write the result in a validation log: the date, the numbers, the difference, and what you changed. That log shows what changed and when, which matters before you turn the old tag off. Note also your data retention setting, how long Google keeps event-level data before it is removed.

Before the switch: baseline week

Export one week of sessions, conversions, and revenue from UA and your back-end into a single sheet. This is the reference every later number is compared against.

Before the switch: GA4 totals match

Pull the same week in GA4 and compare totals. A few percent of difference is expected; 30 percent means a tagging bug to fix before anything else.

During: debug view on key events

Watch the events fire in real time for one sign-up and one purchase. Confirm each fires once, on the right page, with the value you expect.

During: currency and value check

Open a recent transaction and confirm the currency code and value match your store. A wrong currency inflates or deflates revenue without any visible error.

After: 48-hour reconciliation

Re-run the comparison two days after the switch and log the result. If conversions dropped to zero on one channel, a trigger was lost in the move.

Going further

See the five checks

08 / 10

What happens to my old Universal Analytics data?

UA stopped receiving data, and access to the old interface will not last forever, export what you need now.

Google stopped collecting data in Universal Analytics in 2023 and has since withdrawn access to UA properties. What survives is what you exported yourself: report files, spreadsheets, or a UA dataset in BigQuery if your property had that export switched on. Check your shared drive and your Google Cloud project before buying any migration tool.

GA4 cannot import UA history: the two data models record sessions and events differently, so treat old reports as reference documents, not live data. Store exports with a name like UA-2023-traffic-monthly.csv and note each file's date range and metric definitions. This matters most when a tool asks for last year's totals and you no longer have a dashboard to open.

  1. Find what still exists

    Search your shared drive, email attachments, and Google Cloud project for any UA exports made while the properties were still open.

  2. Export or reconstruct the reports you need

    For reports you can still open, download CSVs for traffic sources, top landing pages, conversions, and audience overview. Where access is gone, rebuild quarterly totals from a BigQuery export if your property had one, or from a third-party tool that imported UA data before the sunset.

  3. Document where the files live

    Create one index file listing each export, its date range, its metric definitions, and the folder path or BigQuery table name. Share it with anyone who reports on marketing performance, so nobody hunts through drives next quarter.

09 / 10

What should I check in the first weeks after the switch?

Treat the first month as a monitoring period, with one named owner checking the numbers each week.

Weekly, compare GA4 against your back-end records: orders, sign-ups, revenue. Pick one person as owner and log every fix, what broke, what you changed, when. Set the data retention period, meaning how long Google keeps event-level data before it is removed, to the longest option your account offers.

Expect a dip right after the switch: consent banners, redirects, and cross-domain tracking are the usual culprits. If validation still fails after you fix the obvious issues, book a few hours with an outside specialist.

10 / 10

Frequently asked questions

Frequently asked questions
The Web Insider editorial team
About the author The Web Insider editorial team

Web Insider is a practical magazine for people who build, run or grow a website. Every fact is checked against its official source, and every test shows its proof.

Your feedback

Was this page helpful?

Share

Could this page help someone?

Related reading

Read next

Web analyst setting up analytics on a laptop with a notebook
Data & Analytics

GA4 Setup Tutorial: Live and Verified in 30 Minutes

A copy-along GA4 setup that ends with proof: your property created, your tag live, and traffic confirmed in Realtime and DebugView before you touch a single report.

·17 min
Laptop showing a tag debugging panel on a desk with a coffee mug
Data & Analytics

Best GTM Chrome Extensions for Testing Tags

Tag Assistant Legacy is gone, and the current crop of GTM Chrome extensions splits into three jobs: debugging tags, inspecting the dataLayer, and validating pixels. This guide maps each extension to the task you're actually doing.

·17 min
Laptop on a desk showing an analytics dashboard and code next to sticky notes
Data & Analytics

What Is Google Tag Manager? A Plain-English Guide

Google Tag Manager (GTM) is a free tool that lets you add and manage marketing and analytics tags on a site without touching code. This guide explains tags, triggers, and variables, how GTM works with GA4, and whether you need it.

·13 min
Abstract tag management interface on a laptop, with no logo visible
Data & Analytics

Google Tag Manager Logo: What the Icon Means

The GTM logo is the interlocking double-diamond mark for Google's tag management product. It proves Tag Manager is attached, not that your tags work. Here's how to read it.

·13 min
Explore the topicData & Analytics

Audience measurement, Google Analytics 4 and Google Tag Manager: set them up, check them and keep your data reliable.

Explore the topicWebsites & Platforms

WordPress, Shopify, PrestaShop and WooCommerce: run, integrate and maintain a site without making it fragile.

Explore the topicGuides & How-Tos

Methods, training and practical benchmarks to scope a web project, test a site and make better decisions.

Explore the topicSecurity & Compliance

Backups, updates, GDPR, cookies and audience measurement: keep a site safe and compliant.