Import your data

Bring Plausible, Fathom, Umami or DataFast daily history into Seean while preserving your live analytics.

Assisted import

Contact hello@seean.io with your Seean site domain and the source tool to ask whether your export can be supported. Import compatibility and a transfer process must be confirmed before you send data; starting a trial does not guarantee an import. Keep an original copy of your export and continue collecting in your existing tool until a migration has been verified.

Self-serve availability

Open Settings → Data → Import history and pick the Source. File imports require the export and its timezone, and offer an optional source-day selection and a Replace previously imported days mode (import modes). DataFast uses a read-only website API key and UTC date range. Accepted complete days contribute to the main Overview KPIs, chart and supported breakdowns; unavailable full-period metrics show -. Each imported day keeps its source calendar date: on the chart it sits on that date in your display time zone, and it counts only when the whole source day lies inside the selected period. Each provider guide covers setup and verification.

Seean skips a source day if it overlaps collected live events, using the export timezone and its daylight-saving boundaries. Overlap checks use the current analytics store, request an immediate transfer of queued visits and wait for earlier accepted visits to become available. If preparation or storage is unavailable, the import fails with a retry message instead of accepting an unchecked day. Keep the original file and retry after collection has caught up.

Source availability

A source tool’s export button does not establish compatibility with Seean. Do not send an archive to the tracker collector or order endpoint; neither is a historical analytics importer.

Moving from another tool

Keep collecting in your existing tool while you install Seean on the same website. Export from the source tool as its guide describes, then select the same source timezone in Seean: Plausible (full Settings ZIP, not the chart export), Fathom (custom daily export, not the dashboard ZIP) or Umami (Cloud export; timestamps are UTC).

Historical daily aggregates are different from individual browser events. Seean preserves source totals without inventing visitor identities or sessions. Daily visitors are summed into the selected period, without cross-day deduplication; source definitions apply. Unfiltered Roll-up, shared dashboards, widgets, PDF/email reports and analytics API/MCP Overview results use the same aggregates. Saved results remain unchanged; start a new calculation after an import finishes to include its accepted days. Session filters, realtime, funnels, campaign analysis, revenue attribution and raw-event exports continue to use original Seean records.

Before considering a transfer complete

Replacing or restoring imported days can invalidate an older analysis’ on-demand breakdown before the import finishes. Refresh the analysis after completion or rollback; Seean refuses mismatched details instead of combining old totals with changed history. Previously saved result summaries and report files remain unchanged.

Check accepted/skipped days, the source timezone, representative daily pageview totals and the source rows. Existing Seean events must remain intact. Keep your own original export and compare metric definitions before retiring your old setup. Failed imports do not appear in dashboard totals; their uploaded original remains available until you remove the import. A refused start shows the server’s reason, including the seconds to wait when the hourly import limit was reached.

Export from Seean

Exporting out of Seean uses Settings → Data. See CSV exports for supported files and account-access requirements.

Something unclear? Contact support.