Before
Export in a supported format and keep an untouched copy.
- Check the limits
- Umami: confirm the three columns
- Pick the right destination site
Move your history in
Import Plausible ZIPs or Umami CSVs, then swap one script tag.
Import formats
Daily aggregates only, not raw events.
| Source | Export | Limits |
|---|---|---|
| Plausible | ZIP of export CSVs. Matched by file-name prefix; unknown files and columns are ignored. | 512 MiB upload, 1,000 entries, 2 GiB per entry, 8 GiB total. |
| Umami | website_event CSV with session_id, created_at, event_type. | 512 MiB upload, 2,000,000 sessions. |
What carries over
| Data | Result |
|---|---|
| Daily metrics | Imported as aggregates, bucketed by the local day of the site. |
| Raw events | Not imported. |
| Historical sessions | Used to compute aggregates, not recreated. |
| New traffic | Collected once the Supermetry tracker replaces the old one. |
How imported and live data merge in each report is not verified. Check the migration docs first.
Before and after
After
Swap the tracking script and check new traffic apart from history.
- No Plausible API compatibility
- No wire compatibility
- One-line script change
Export
- Report CSV
- Every report streams as CSV.
- API CSV
- Accept: text/csv or format=csv.
- Site export
- supermetry-site-<id>-<from>-<to>.zip, needs data-export permission.