Skip to main content
You can import your Umami history into tinyanalytics by uploading a Umami export file. tinyanalytics reads your past events from the export and stores them as its own events, so your Umami history appears in every report alongside your new tinyanalytics data.

How to import from Umami

1

Export your data from Umami

Export your website data from Umami for the period you want to keep.
2

Upload the file to tinyanalytics

In your site’s import settings, choose Umami and upload the export file. tinyanalytics parses it in your browser and imports the events.
3

See it in your dashboard

When the import finishes, your Umami history is live across your reports.
The import worked when your Umami history appears in your tinyanalytics reports, and the import summary shows how many events imported, skipped, or were invalid.

What carries over from Umami

A Umami export contains individual events, so more detail survives the move than with an aggregate export. tinyanalytics translates Umami’s browser, OS, and device labels into its own taxonomy so they line up with your native traffic: Channels are re-derived by tinyanalytics from the referrer and campaign data, so imported Umami traffic is classified by the same rules as your live traffic.

Good to know

  • One import runs at a time per organization.
  • Rows dated in the future are skipped, and malformed rows are dropped and counted, so you’ll see how many events imported, skipped, or were invalid.
  • Re-running adds the data again — to redo an import, delete the previous one first (deleting removes all of that import’s data).
  • Imported data is stored as ordinary events, so it flows through every report, including funnels, retention, cohorts, and period comparison.

Frequently asked questions

Yes. A Umami export contains individual events, so pageviews and sessions keep their own timestamps and event-level timing is preserved. That’s more detail than survives an aggregate export.
Pageviews and sessions with their timestamps; countries, regions, and cities where present; referrers and query strings, with referrers reconstructed to full URLs; and browsers, operating systems, and devices, normalized to tinyanalytics’ device labels with screen size preserved.
Delete the previous import first, then run it again. Re-running an import adds the data a second time rather than replacing it, and deleting an import removes all of that import’s data. Only one import runs at a time per organization.
Rows dated in the future are skipped, and malformed rows are dropped and counted. tinyanalytics reports how many events imported, skipped, or were invalid, so you can see exactly what happened to your export.

Switch to tinyanalytics

The full migration overview.

Import from Plausible

Coming from Plausible instead.

Import from Simple Analytics

Coming from Simple Analytics instead.

Quickstart

Install the script to start collecting new data.