> ## Documentation Index
> Fetch the complete documentation index at: https://tinyanalytics.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Import Umami Analytics Data

> Move your Umami history into tinyanalytics by uploading a Umami export file. Your past pageviews, sessions, devices, and referrers flow into every report.

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

<Steps>
  <Step title="Export your data from Umami">
    Export your website data from Umami for the period you want to keep.
  </Step>

  <Step title="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.
  </Step>

  <Step title="See it in your dashboard">
    When the import finishes, your Umami history is live across your reports.
  </Step>
</Steps>

<Check>
  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.
</Check>

## 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:

| Carries over                                 | Notes                                                                |
| -------------------------------------------- | -------------------------------------------------------------------- |
| Pageviews and sessions with their timestamps | Event-level timing is preserved                                      |
| Countries, regions, and cities               | Where present in the export                                          |
| Referrers and query strings                  | Referrers are reconstructed to full URLs                             |
| Browsers, operating systems, devices         | Normalized to tinyanalytics' device labels; screen size is preserved |

**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

<Note>
  * **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](/docs/analytics-period-comparison).
</Note>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does a Umami import keep the original event timestamps?">
    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.
  </Accordion>

  <Accordion title="What carries over from a Umami 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.
  </Accordion>

  <Accordion title="How do I redo a Umami import?">
    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.
  </Accordion>

  <Accordion title="Why did some rows get skipped during my import?">
    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.
  </Accordion>
</AccordionGroup>

## Related

<Columns cols={2}>
  <Card title="Switch to tinyanalytics" icon="right-left" href="/docs/migrate-analytics-data-to-tinyanalytics">
    The full migration overview.
  </Card>

  <Card title="Import from Plausible" icon="file-import" href="/docs/import-plausible-analytics-data">
    Coming from Plausible instead.
  </Card>

  <Card title="Import from Simple Analytics" icon="file-import" href="/docs/import-simple-analytics-data">
    Coming from Simple Analytics instead.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/docs/tinyanalytics-quickstart">
    Install the script to start collecting new data.
  </Card>
</Columns>


## Related topics

- [Import Plausible Analytics Data](/docs/import-plausible-analytics-data.md)
- [Import Simple Analytics Data](/docs/import-simple-analytics-data.md)
- [Import Google Analytics 4 Data](/docs/import-google-analytics-4-data.md)