Migrating My Web Analytics From Matomo to Umami
Posted9 days agoActive3d ago
stanislas.blogTech Discussionstory
informativepositive
Debate
20/100
Github AnalyticsMatomoUmami
Key topics
Github Analytics
Matomo
Umami
Discussion Activity
Active discussionFirst comment
3d
Peak period
12
60-72h
Avg / period
5
Key moments
- 01Story posted
Dec 24, 2025 at 6:08 AM EST
9 days ago
Step 01 - 02First comment
Dec 26, 2025 at 6:34 PM EST
3d after posting
Step 02 - 03Peak activity
12 comments in 60-72h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 30, 2025 at 7:18 AM EST
3d ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 46374524Type: storyLast synced: 12/27/2025, 4:20:33 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
https://www.goatcounter.com/
> - There will be more bot requests.
> - Some data won’t be available: screen sizes, page titles.
> - It won’t disambiguate to canonical paths from <link rel="canonical">; i.e. /page and /page?x=y will show up as two different paths.
And not a hint on why.
> Matomo has barely evolved in terms of UI, and it feels pretty dated now
It's so sad what my Phillips screwdriver barely evolved in the last 100 years. D'oh!
> It has a few gotchas like this weirdness around updating it in its Docker image.
I'm just clicking the update button in the web UI and waiting a minute.
> Umami is a NextJS app with PostgreSQL
Aaaaand? It would be somewhat understandable if you ran metrics for the hundreds of sites. But you only have two. So - why? Why is this even matters for you?
> no plugins
Ah, the famous 'but I don't need MMS [despite everyone in the world uses them]' line of thinking. BTW you could, you know, just not installing any plugins in Matomo - it would be effectively the same result as not having a plugin support in Umami.
> reduced feature set
Five years ago? Maybe. This is one of the reasons I didn't bother with repairing it when my installation quietly died on itself. But looking at the current list it's hard to say Umami has 'a reduced feature set'.
> that their Cloud hosted version has an import feature, but it’s not open source
And a hard pivot to the 'cloud-first' was another reason why I decided not to bother with Umami anymore. It was heavily advertised as an open source and open source alternative to the other solutions on the market and now you can't even find what you can self-host it on the front page! Of course if don't count . Contribute . as a such description. No mention of self-hosting on Pricing at all.
> Now, I’m free to say goodbye to Matomo, and save resources.
How much resources do you save?
Overall I'm glad what you found a way to preserve the data instead of just throwing it away - and even shared the story and tools to everyone.
Yes, but the screwdriver itself?
The best part here is what if you look at the screenshots of both Matomo and Umami you couldn't distinguish them if you are not explicitly told who is where.
Umami got rooted twice this month because of holes in React, partly because of the enormous complexity of that framework.
Just my two cents.
I’ll pass.