Seean
Sign inStart free for 15 daysTry free

Import from Umami

Bring Umami Cloud history into your Seean website. Umami exports raw events rather than daily reports, so Seean rolls the event file up into daily totals during validation. You must own the Seean website; live events, orders, tracking token and saved reports stay intact and the import modes (fill gaps, source-day selection, replace) apply.

Export from Umami Cloud

  1. In Umami Cloud, open the profile menu, then Settings → Data → Export.
  2. Choose the website and date range, then start the export. Umami processes it in the background and emails a download link.
  3. Download the file and keep your own copy. Exports contain website_event.csv (page views and events with their session and visit ids) and may include session_data.csv and event_data.csv.

See Umami’s export guide. Self-hosted Umami has no export tool; a CSV of the website_event table with the same columns can be uploaded instead.

Upload in Seean

  1. Open your website, then Settings → Data → Import history.
  2. Select Umami as the source; Seean also detects it when the file contains website_event.csv or its session_id/visit_id columns.
  3. Choose the ZIP from the email, or website_event.csv on its own, or a .csv.gz copy of it.
  4. Umami timestamps are UTC. Select the Export timezone whose calendar days you want on the dashboard, usually the website’s own timezone. Later imports must use the same timezone as earlier ready imports.
  5. Upload and import, wait for ready, then review days added and skipped. View rows shows one row per source day.

The limits from the Plausible guide apply: ten imports per website, one active import per website, three starts per hour and no demo websites.

What is imported

For each calendar day in the chosen timezone Seean stores:

  • visitors: distinct session_id values
  • visits: distinct visit_id values
  • pageviews: events with event_type 1
  • events: all other event types, as a daily total under View rows and, when the export carries event_name, as a daily count per event name in the custom_events table

Accepted complete days contribute to the main unfiltered KPIs and chart, and the imported custom-event counts appear in the Overview Events card and its event-type total for the same days (up to 1,000 event names per day; further names are summed as (other); the day rows and event-name rows together count toward the 200,000-row limit). They are daily counts per name, not activity-log records, funnels or conversion goals. Bounce rate and duration are not reconstructed; full-period values show - when Umami days are included. Visitors are Umami’s daily sessions, summed into the selected period without cross-day deduplication. Pages, referrers, countries, devices and event data (properties) are not imported. See shared history behavior for filters, reports and API scope.

Limits and validation

  • Up to 25 MiB uploaded, 100 MiB expanded, 1,000,000 events and 3,660 calendar days. Export a shorter date range in Umami if a file is larger.
  • website_event.csv must contain session_id, visit_id, created_at and event_type; additional Umami columns are accepted and ignored. Other files in the ZIP are skipped without being read.
  • created_at must be YYYY-MM-DD HH:MM:SS, optionally with fractional seconds and a Z or ±HH:MM offset; values without an offset are treated as UTC.
  • Encrypted or unsafe ZIP entries, corrupt checksums, malformed timestamps and files without the event file fail validation. A failed import contributes nothing to the dashboard.

Something unclear? Contact support.