GA4 Implementation & UA-to-GA4 Migration
Universal Analytics stopped collecting data in mid-2023. For most teams this is no longer a "migration" in the live sense - it's building a proper GA4 measurement setup, informed by whatever the old UA property can still tell you about what mattered.
What "Migration" Actually Means Now
GA4 and Universal Analytics measure differently at a structural level - UA around sessions, GA4 around events - so there was never a button that moves historical UA data into GA4. Anyone who set up GA4 in the recommended parallel-tracking window (before UA sunset) already has GA4 history running; anyone who didn't is not "behind" on a migration so much as starting a GA4 implementation from the current point forward.
If you still need UA's historical numbers for reporting continuity or year-over-year reference, treat that as an export/archive task - separate from the GA4 implementation work - since Google's own retention timeline for UA data access is finite. We can help identify what's worth exporting before doing the GA4 build.
What a GA4 Implementation Project Involves
| Phase | What happens |
|---|---|
| Measurement planning | Map the business questions ("which channel drives signups") to specific GA4 events and parameters before any configuration starts |
| Property & stream setup | Data streams, cross-domain measurement if you operate multiple domains, timezone/currency/retention settings |
| Event implementation | Built via Google Tag Manager where practical, or direct gtag calls where GTM isn't in use |
| Key events & conversions | Naming and designating the events that represent real business outcomes, not every event GA4 happens to collect |
| Consent & governance | Consent Mode configuration, internal traffic exclusion, naming conventions documented for future maintainers |
| Validation | Every event checked in DebugView and, where possible, cross-checked against a source system (ecommerce platform, CRM) before handover |
Where events are deployed through Google Tag Manager, container build and QA is covered in depth at gtm.webclat.com - this page covers the GA4 side of the same project.
New Build vs. Rebuild
Two different starting points end up at the same place:
- No GA4 property yet, or one that was auto-created but never configured - this is a clean implementation. See our step-by-step setup guide for the sequence, or have us run the whole build.
- A GA4 property exists but wasn't set up carefully - missing key events, no internal traffic exclusion, inconsistent naming. This is closer to an audit followed by targeted fixes than a ground-up rebuild.
Hypothesis, not a guarantee: we can't estimate your specific project's timeline or cost without knowing which of the two starting points you're in and how many domains, platforms, and event types are involved - scoping happens before any number gets quoted.
Frequently Asked Questions
Is Universal Analytics still available to migrate from?
Universal Analytics stopped processing new data in mid-2023. If you still have a UA property, its historical data remains accessible (subject to Google's own retention timeline) but no new data is being collected there - so this is now an export-and-archive project for old data, plus a GA4 implementation project for going forward, not a live migration of an active property.
Can historical Universal Analytics data be moved into GA4?
No, not natively - GA4 and UA use different data models (event-based vs. session-based), so there is no direct import path. The practical approach is exporting UA's historical reports for reference/archive before they become inaccessible, while GA4 collects new data going forward on its own timeline.
What does a GA4 implementation project actually involve?
A measurement plan mapping business questions to specific events and parameters, property and data stream configuration, event implementation (often via Google Tag Manager), key event designation, consent and internal-traffic configuration, and validation against real traffic before handover.
How do you validate an implementation before calling it done?
Every event in the measurement plan is checked in DebugView against a real user action, cross-checked against the source system where one exists (an ecommerce platform's own order count, a CRM's own form-submission log), and documented so the next person maintaining the property understands what each event means and why it exists.
Start With a Measurement Plan, Not a Configuration Screen
Tell us what's in place today (nothing, an unconfigured GA4, or an old UA property) and we'll scope from there.
Scope a GA4 ImplementationScope a GA4 Implementation
Tell us your starting point and what's connected (ecommerce, CRM, ads) and we'll come back with a plan.