Skip to content

Moving from Umami to Statsdot

Updated October 19, 2026

Umami is a fine piece of open-source software, and many developers run it on their own server. The usual reason to leave is not Umami itself but the server: updates, database, backups and uptime for a tool that should just work.

When switching makes sense

  • You self-host Umami and would rather not maintain it.
  • You want the visitor code to change every day. Umami rotates its salt monthly by default; Statsdot rotates it daily, so a visitor cannot be followed from one day to the next.
  • You need a non-English dashboard for clients or colleagues.

When to stay with Umami

For user journeys, retention cohorts and identifying users across devices, Umami does more. Those features need a way to recognise a person over time, which Statsdot deliberately does not have.

What you keep

Statsdot imports the daily totals of an Umami website: visitors, visits, pageviews, bounce rate and visit duration; pages, entry and exit pages; referrers with their channel; countries, regions and cities; devices, browsers and systems; and events.

How to do it

  1. Add your site to Statsdot and install the script alongside Umami for a week or two.
  2. Get access for the import: an API key on Umami Cloud, or the address and a view-only login of your own Umami.
  3. Import: Statsdot site settings, Import > Import from Umami. Umami's API has no daily breakdowns, so Statsdot imports the days with visits one by one; a busy year takes a few minutes. Details in Import from Umami.
  4. Move your events: umami.track('Signup') becomes statsdot.track('Signup'), or use data-statsdot-event where you had data-umami-event.
  5. Remove the Umami script. If you self-hosted, keep a database backup before you shut the server down.