Migration field guide
Google Analytics to Plausible: import and verify
Preserve a dated historical reference while validating new collection separately. The two products do not count every metric the same way.
Edited by Clinton Feyisitan · Documentation checked
Review scope: Official documentation and field mapping reviewed. The steps below are a proposed validation procedure, not a completed native migration or a measured completion-time claim.
What the documented route supports
Plausible imports aggregated GA4 reports through its Imports & Exports settings. It adjusts historical date ranges to avoid overlap with native collection, but cannot recover missing data. The documented import cannot split a GA property by hostname. Goals need configuration, and ecommerce revenue, exit pages and scroll depth are not imported.
Map before importing
| Source | Destination | Check |
|---|---|---|
| GA4 property | One Plausible site import | A multi-host property cannot be split by hostname in this importer. |
| Daily aggregates | Historical reference | Multi-day unique counts are not equivalent to GA4 deduplicated users. |
| Conversion events | Configured goals | Check event names and which goals appear after import. |
| Ecommerce revenue / scroll depth | Not imported | Retain the source reports if these are needed. |
A controlled migration
- List the websites, GA4 properties, required events and reporting dates. Save baseline reports with their filters and definitions.
- Create the intended Plausible site and install its supported tracking snippet through the official setup. Validate consent and privacy requirements for your actual configuration.
- In site settings, open Imports & Exports, connect the authorized Google account and select the correct GA4 property. Review the property scope before confirming.
- Recreate the goals you need, then review imported coverage and native traffic separately. Keep GA available during a measured overlap period.
Acceptance checks
Record the result and evidence for each check. Stop the cutover if a required check fails.
- Check date coverage and compare a single-day report with identical filters.
- Trigger an authorized test event and verify it is collected once.
- Record expected metric differences rather than forcing totals to match.
Budget for overlapping plans, required features, seats, storage or usage, and the time to reconcile exceptions. Check the current provider quote; this guide does not reuse historical subscription prices.
Keep a way back
Keep the original GA4 property and report exports. If the wrong property was imported, pause reporting on the mixed dataset and review the documented removal/re-import controls. Do not reset native stats simply to make totals align.
Official sources
Source availability and account UI can change. Native account execution remains untested in this guide.
Earlier editorial risk estimate
This historical rating has not been recalculated by this documentation review.