Can You Import Historical Data into Google Analytics 4?

If you've recently made the switch to Google Analytics 4, you might be looking at your new property and asking a very common question: "Where is all my old data?" This article will walk you through why you can't directly import historical data from Universal Analytics into GA4 and, more importantly, what your practical options are moving forward.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The Short Answer: No, You Can't Directly Import UA History

Let's get the main question out of the way first. You cannot directly import your historical website traffic data from a Universal Analytics (UA) property into a Google Analytics 4 property. While this can feel frustrating, it isn't an oversight by Google. The reason is a fundamental difference in how the two platforms are built from the ground up.

Thinking you can merge UA and GA4 data is like trying to combine a movie script with a spreadsheet - they both tell a story, but they're structured in entirely different formats that aren't compatible.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Universal Analytics vs. GA4: A Tale of Two Data Models

To understand why this is impossible, you need to see how differently UA and GA4 measure and record user activity.

The Universal Analytics (UA) Model: Sessions and Hits

Universal Analytics operated on a session-based model. Think of it like a structured report with specific categories. Everything tracked was categorized as a "hit." The main types of hits were:

• Pageviews: When a user loads a page.
• Events: A specific interaction you defined, like a button click or video play, with a Category, Action, and Label.
• Transactions: An e-commerce purchase.

UA would then bundle these hits into "sessions," which are essentially user visits. All its reporting, from bounce rate to pages per session, was based on this session-centric view of the world. It was organized and predictable but could be rigid.

The Google Analytics 4 Model: Events and Parameters

GA4 threw out the session-based playbook and adopted a much more flexible event-based model. In GA4, everything is an event. A pageview is an event called page_view. A purchase is an event called purchase. Clicking a link is an event called click.

Each event can be enriched with "parameters," which are additional pieces of information that describe the event. For example, a page_view event will have parameters like page_title and page_location (the URL). This makes tracking far more versatile and less constrained than UA's strict Category/Action/Label structure.

Because the fundamental building blocks of data (hits in UA vs. events in GA4) are different, there's no way to neatly pour your old UA data into the new GA4 structure. The definitions of core metrics have changed, and the entire data schema is different.

What Should I Do With My Old Universal Analytics Data?

Your UA data might be locked out of GA4, but that doesn't mean it's lost forever. Standard Universal Analytics properties stopped processing new data on July 1, 2023. Google officially began shutting down access to the UA user interface and API starting on July 1, 2024.

Ideally, you already exported your historical data out of the UA platform before this cutoff. If you did, you likely used one of these methods:

• Exporting Individual Reports: Going into UA's standard reports and downloading them as CSV, Excel (XLSX), or Google Sheets files.
• Using the Google Analytics Spreadsheet Add-on: A powerful tool for pulling large amounts of UA data directly into Google Sheets.
• The GA Reporting API: A more technical method for developers to programmatically extract data and send it to other applications or databases.
• BigQuery Export (for UA 360 users): Enterprise users had the option to connect UA to Google BigQuery and export their raw, hit-level data.

Your exported files, whether they are spreadsheets or in a database, now represent your historical source of truth.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Practical Strategies for Analyzing Historical and Current Data

So, you have your old UA data exported and your new GA4 property actively collecting data. How do you see the big picture? Here are three practical approaches, from simple to more advanced.

1. The "Two Timelines" Approach

This is the most straightforward method. You simply accept that you have two separate datasets for two different time periods:

• For any analysis pre-GA4 implementation: You'll refer to your saved UA exports (CSVs, Google Sheets, etc.).
• For any analysis post-GA4 implementation: You'll use the GA4 interface.

This is fine for looking at trends within each period, but it makes direct year-over-year comparisons (e.g., comparing pageviews from May 2023 in UA to May 2024 in GA4) a manual process of looking at two separate reports.

2. The Spreadsheet Solution

For more seamless comparisons, you can bring both data sets together in a spreadsheet tool like Google Sheets or Excel. This is a great middle-ground option that doesn't require deep technical knowledge.

1. Load your historical data: Import the CSV files you exported from Universal Analytics into a Google Sheet. You might have one sheet for traffic sources, another for top pages, etc.
2. Connect to your live data: Use the official Google Analytics Add-on for Google Sheets to pull your GA4 data into the same workbook.
3. Create unified charts: Once both datasets are in the same workbook, you can create a summary tab. Manually align the key metrics (e.g., "Users" from UA and "Total Users" from GA4) side-by-side in a table. Then, you can build a single line chart that visualizes the trend across both time periods. It is manual, but it gets the job done for high-level reporting.

3. The Data Warehouse & BI Tool Approach

This is the most powerful and scalable solution, favored by data-driven companies. It involves sending your data to a central storage location (a data warehouse) and using a business intelligence tool to visualize it.

1. Store your old UA data: Upload your historical UA exports to a data warehouse like Google BigQuery.
2. Set up the GA4 BigQuery Export: Within your GA4 property settings, there is a free, native integration to link your GA4 property to BigQuery. This will automatically start sending all your new raw GA4 event data to the data warehouse daily.
3. Connect a BI Tool: Now, use a visualization tool like Looker Studio (formerly Data Studio), Tableau, or Power BI to connect to BigQuery as its data source.

In this setup, your BI tool can "see" both your historical UA data and your ongoing GA4 data sitting together in the same warehouse. You can then build a comprehensive, automated dashboard that visualizes your key metrics seamlessly over a period of many years, regardless of the analytics platform change. This approach does require more setup and some know-how to blend the two different data structures, but it delivers the most robust result.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What GA4's "Data Import" Feature Is Really For

To add to the confusion, GA4 does have a feature literally called "Data Import." However, it is not used for importing website traffic history from UA.

Instead, GA4's Data Import feature is designed to enrich the data you are already collecting with additional information from outside of Google Analytics. You use a common key (like a User ID, product SKU, or ad Campaign ID) to join offline data with the online data being collected by GA4.

Here are examples of what you can import with this feature:

• Cost Data: Uploading ad spend data from a non-Google network (like Facebook Ads or LinkedIn Ads) so you can analyze ROI inside GA4.
• Item Data: Importing detailed product information (like size, color, or margin) and joining it with your e-commerce events using a product SKU.
• User Data: Uploading user attributes from your CRM (like their loyalty status or LTV) and joining it to their GA4 activity using a User ID.
• Offline Events: Importing data on actions that happened offline (like a CRM lead being marked as qualified) and tying it to an online user.

Final Thoughts

While you can't simply upload your Universal Analytics history into Google Analytics 4, that's by design. The new event-based model in GA4 offers far more flexibility for modern analytics. Your path forward involves embracing this two-source reality, using your exported UA files for historical context, and leveraging your preferred tool - whether it's a simple spreadsheet or a powerful BI platform - to bridge the gap and create a unified view of your business performance.

Manually stitching together historical exports with live data takes time and can be prone to errors, which is where modern analytics platforms come in. To solve this, we built Graphed. It seamlessly connects to your live GA4 and other marketing data sources, but also lets you easily connect Google Sheets containing your historical UA data. This way, you can build dashboards and ask questions about your performance across both eras - all in one place, using simple natural language instead of spending hours wrangling spreadsheets.