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.
Umami got rooted twice this month because of holes in React, partly because of the enormous complexity of that framework.
Just my two cents.