Rant: It's impossible to migrate from MySQL to Postgre

[stuartcusackie]

I tried everything. Went through the official docs. Chatted to different AI bots. Nothing worked.
This is the second time I've had to go through this horrible process. From v1 to v2 and now v2 to v3.
5-6 hours spent on this today. I haven't been this frustrated by software installtion in years.

How the heck am I supposed to get postgres running on an existing Laravel Forge server and run it in conjunction with MySQL? My server is out of date so that seemed like a dead end. Instead, I set up a fresh server with Postgres only dedicated to Umami, and that alone was a problem. The Forge installation docs are not comprehensive and some packages are missing yarn add prop-types react-aria-components

Once I had it my new Umami V3 server up and running I couldn't import my "converted" mysql to postgres. I get all these errors:
ERROR: relation "_event_old" does not exist
ERROR: duplicate keys exist
so on, so forth.

Maybe you could build a simple export / import button in Umami instead of having to go through all this? The installation process is tricky enough without the migration.

Umami is great when it works but don't expect to keep your historical data when updating versions. For the moment I will run v2 and v3 in tandem and recommend to my clients to use another analytics solution.

PS. I appreciate all your work on this :)