How to migrate from Google Analytics to Plausible without losing data

by

TL;DR

You can migrate from Google Analytics to Plausible and keep your historical data visible inside Plausible’s dashboard using their built-in GA import feature. The whole process takes about two to four hours depending on your site’s complexity and how much historical data you have. You need a Plausible account (free 30-day trial, then starts at $9/month), access to your GA4 property, and either Google Tag Manager or your site’s HTML.

What You Need Before You Start

  • A Google Analytics 4 (GA4) property with admin access. Universal Analytics (UA) data requires a separate export step covered in Step 2.
  • A Plausible Analytics account – sign up at plausible.io. The trial is 30 days with no credit card required.
  • Access to your website’s code or Google Tag Manager (any version).
  • Your site’s domain verified in Plausible before the import will work.
  • Google Search Console linked to your GA4 property if you want keyword data preserved (optional but recommended).
  • A CSV export tool if you want raw UA data saved locally – the free GA Exporter Chrome extension works fine for this.
  • About 30 minutes of uninterrupted time for the tracking switch. Do it during a low-traffic window.

Step 1: Export and Archive Your Universal Analytics Data

GA4 replaced Universal Analytics in July 2023, and Google deleted UA properties in 2024. If you never exported your UA historical data, it is gone. But if you are still sitting on a GA4 property with imported UA data, or you have a backup, this step matters.

Open Google Analytics, go to your GA4 property, click Reports, then Acquisition, then Traffic acquisition. Use the date picker to set the range from your earliest date to today. Click Share this report (the export icon, top right), then Download file, and choose CSV.

Repeat this for Engagement, Monetization, and any custom reports you rely on. Store them in a folder labeled ga-export-YYYY-MM-DD.

If you have a UA property still accessible via a shared link or backup account, install the GA Exporter Chrome extension, navigate to your UA reports, and use the extension to pull dimension-level CSVs.

You should now see a folder of CSV files covering your most important metrics. These won’t import directly into Plausible but they serve as your permanent archive and source of truth for year-over-year comparisons.

Step 2: Create Your Site in Plausible

Log into your Plausible account and click Add a website. Enter your domain exactly as it appears in your browser bar (for example: yourdomain.com, no https://, no trailing slash). Plausible is case-sensitive about this.

Choose your reporting timezone and your business category. Neither setting affects data collection but they do affect how your dashboard displays.

Click Start collecting data. Plausible will show you your unique tracking snippet:

<script defer data-domain="yourdomain.com"
  src="https://plausible.io/js/script.js"></script>

Copy this and keep the tab open. You will need it in Step 3.

You should now see your site listed in the Plausible dashboard with a banner saying Waiting for first page view. That means the site is created but not yet receiving data.

Step 3: Install the Plausible Tracking Script

If you use Google Tag Manager:
Open GTM, go to Tags, click New, choose Custom HTML, paste the Plausible snippet, and set the trigger to All Pages. Name it Plausible Analytics. Submit and publish the container.

If you use WordPress:
Install the free Plausible Analytics WordPress plugin. Go to Settings > Plausible Analytics, enter your domain, and save. The plugin inserts the script automatically and excludes logged-in admins from tracking.

If you edit HTML directly:
Paste the snippet inside the <head> tag of your base template or layout file, before the closing </head> tag.

<head>
  <!-- your other tags -->
  <script defer data-domain="yourdomain.com"
    src="https://plausible.io/js/script.js"></script>
</head>

You should now see the Waiting for first page view banner disappear within a few minutes of visiting your own site. Open your Plausible dashboard and confirm you see at least one real-time visitor (yourself).

Step 4: Verify Data Is Flowing Correctly

Before you touch anything in GA, spend 24-48 hours running both scripts in parallel. This overlap period is critical. It tells you whether Plausible numbers are in the right ballpark compared to GA.

Open Plausible and check the Live counter. Then open GA4 and check Reports > Realtime. Plausible typically shows 10-30% fewer sessions than GA4 because it does not count bot traffic and does not use cookies, so bounced sessions from bot crawlers disappear. That is expected and correct.

Check that your top pages match between the two tools. Go to Plausible’s Top Pages and compare against GA4’s Pages and screens report. The ordering should be roughly the same even if absolute numbers differ.

You should now have confidence that Plausible is tracking real human visitors correctly before you kill the GA script.

Step 5: Import Your GA4 Historical Data into Plausible

This is the step most people miss. Plausible has a native GA4 import feature that pulls your historical data directly via the Google API.

In your Plausible dashboard, go to Site Settings > Import & Export, then click Import from Google Analytics. Click Continue with Google and authenticate with the Google account that owns your GA4 property.

Select your GA4 property from the dropdown. Choose the date range you want to import. Plausible recommends starting from your GA4 launch date (usually July 1, 2022 or when you set up GA4).

Click Confirm import. Depending on your site’s traffic volume, this takes anywhere from a few minutes to a few hours. Plausible sends you an email when it is done.

Once complete, your Plausible dashboard will show historical bars going back to your import start date. The data is labeled as imported and shown in a slightly lighter color to distinguish it from natively collected data.

You should now see months or years of historical traffic data inside Plausible, letting you compare current performance against historical baselines.

Step 6: Recreate Your Goals and Custom Events

GA4 uses events and conversions. Plausible calls them Goals. You need to manually recreate the ones that matter to you.

Go to Site Settings > Goals, click Add goal. For pageview goals (like a /thank-you confirmation page), choose Pageview and enter the URL. For custom events (like button clicks or form submissions), choose Custom event and name it.

To fire a custom event from your site, add this snippet where the action happens:

window.plausible('FormSubmit', {props: {plan: 'pro'}});

The props object is optional but useful. It lets you segment conversions by properties, similar to GA4’s event parameters.

For e-commerce sites, check Plausible’s revenue tracking docs before you go further, as the revenue goal setup requires a slightly different event structure.

You should now see your goals listed in Site Settings > Goals and they should start registering conversions as visitors complete those actions.

Step 7: Update Your Privacy Policy and Cookie Banner

Plausible does not use cookies and does not collect personal data. That means you no longer need a cookie consent banner for analytics purposes under GDPR, CCPA, or PECR.

Update your privacy policy to reflect the change. Replace any mention of Google Analytics with Plausible. Plausible provides a data processing agreement you can reference. Add a line like:

This site uses Plausible Analytics, a privacy-first analytics tool that does not use cookies and does not collect personally identifiable information. See Plausible’s data policy.

If you have a cookie consent tool like Cookiebot or OneTrust managing your GA script, update it to remove the analytics category from consent requirements. If analytics was the only reason you had a cookie banner, you may be able to remove the banner entirely.

Check your site’s compliance against the privacy-compliance tools overview to see if any other tracking scripts need attention.

You should now have an updated privacy policy and a simplified (or removed) cookie consent flow.

Step 8: Remove Google Analytics From Your Site

Wait until you have at least seven days of clean Plausible data before doing this. Then:

GTM users: Open Tag Manager, find your GA4 configuration tag, and set it to Paused first (not deleted). Publish the container. Confirm Plausible data still flows. Then delete the GA4 tag and publish again.

WordPress users: Go to your GA plugin settings and deactivate or delete the plugin.

Direct HTML users: Delete the gtag.js or GA4 snippet from your <head> tag.

Also remove the GA4 property from your Google account if you want a clean break: GA4 Admin > Property Settings > Move to Trash. Note that Google holds deleted properties for 35 days before permanent deletion, giving you a recovery window.

You should now see zero GA4 hits in your Google Analytics Realtime report, confirming the script is gone.

Step 9: Set Up Plausible Sharing and Alerts

GA4 has robust email reporting. Plausible keeps it simple but covers the basics.

Go to Site Settings > Visibility and toggle on Public dashboard if you want to share your stats with a team or embed them publicly. You get a shareable link with no login required.

For email digests, go to Site Settings > Email reports. You can set up weekly or monthly reports delivered to your inbox.

For spike alerts (traffic surges), go to Site Settings > Spike notifications. Set a threshold, for example 10x your average hourly traffic, and Plausible will email you when you hit it.

You should now have a Plausible setup that matches or exceeds the day-to-day reporting you relied on in GA, without the data privacy overhead.

Common Mistakes To Avoid

  • Deleting GA before the import completes. The Plausible GA import pulls data from your live GA4 property via API. If you delete the GA4 property first, the import fails and you lose access to that historical data permanently.
  • Ignoring the parallel tracking window. Skipping the 24-48 hour overlap means you have no baseline to verify Plausible is working correctly. Spend the time.
  • Expecting identical numbers. Plausible counts unique visitors differently from GA4. GA4 inflates session counts with bot traffic. A 15-25% difference in total sessions is normal and does not mean something is broken.
  • Forgetting subdomains. If your blog lives on blog.yourdomain.com and your app on app.yourdomain.com, you need separate Plausible sites or use their rollup reporting feature to combine them. One script on one domain will not automatically track the others.
  • Not updating the WordPress plugin after a theme switch. If you switch WordPress themes and your new theme has a hardcoded GA snippet in header.php, you will run both tracking scripts at once. Always check the page source after theme changes.
  • Recreating every single GA4 event. Most sites have hundreds of auto-tracked GA4 events they never look at. Audit your actual GA4 conversions before rebuilding goals in Plausible. Copy only the ones you act on.

When To Level Up

The Plausible approach works well for content sites, SaaS marketing pages, and small e-commerce stores with straightforward funnels. It starts to show limits when you need multi-touch attribution across paid channels, server-side event tracking for SPAs with complex state, or raw event-level data exports for your data warehouse.

If you are running significant paid media budgets and need impression-to-conversion attribution across Google Ads, Meta, and LinkedIn in a single view, Plausible’s dashboard will not give you that. You are looking at a tool like Segment combined with a warehouse-native BI layer.

If you are processing more than a few million monthly page views and need granular cohort analysis or custom SQL queries against your analytics data, Plausible’s export options (CSV only, no direct database access) become a bottleneck.

That is the point where you should look at the privacy-compliant analytics tools compared section of this site, where we cover server-side alternatives and hybrid setups that keep you GDPR-clean while giving you the query depth that a growing operation needs.

Frequently Asked Questions

Does Plausible import Universal Analytics data, not just GA4?
Plausible’s native import only supports GA4. For UA data, you need to export it as CSVs first using the GA UI or a tool like GA Exporter. You can then keep those CSVs as an archive. There is no way to import UA data directly into Plausible’s dashboard.

Will I lose data during the switchover?
If you run both scripts in parallel for at least 24 hours before removing GA, you will not lose any data collected after Plausible is installed. Historical data from GA4 comes in via the import step. The only data at risk is UA historical data if you did not export it before Google deleted those properties.

Does Plausible work with single-page applications (SPAs)?
Yes, with a small modification. Add data-spa="auto" to your script tag and Plausible will listen for browser history changes automatically. For frameworks like Next.js with custom routing, check Plausible’s SPA guide for router-specific event binding.

Can I share Plausible data with my team without giving everyone a login?
Yes. Plausible lets you make your dashboard public via a unique URL with no authentication required. You can also add team members to your Plausible account as viewers or admins through Site Settings > People.

What happens to my Google Search Console data?
Search Console is separate from GA4 and stays unaffected. Plausible can connect to Search Console to show keyword data in its dashboard. Go to Site Settings > Search Console, authenticate with Google, and select your property.

Bottom Line

Migrating from Google Analytics to Plausible is a four-step core process: export your GA4 historical data via Plausible’s import tool, install the lightweight Plausible script, run both in parallel long enough to verify accuracy, then remove GA and update your privacy docs. The entire workflow takes a few hours and leaves you with a GDPR-compliant setup that requires no cookie consent banner for analytics. Your historical data lives inside Plausible’s dashboard, your goals carry forward as custom events, and your privacy policy becomes significantly simpler. For most content sites and small SaaS products, Plausible covers 90% of what you actually used in GA4, without the compliance overhead. If your analytics needs grow past what Plausible handles, the privacy-compliance tools section has a full comparison of the next-tier options worth considering.