Ordinarily I would agree, but in this case, the poster said that there's not a lot of data yet so it would be easier to migrate. Choosing a database is a pretty major decision with long-term impact that might not be obvious now, so it's worth exploring a few options if you have that luxury.
I think there are two times when it makes sense to consider a DB migration: (1) early on, when it's easy; (2) if you are in major trouble with your existing DB.
> Some people have quite a dependency on Postgres
Our dependency on Postgres is more to do with it being a lot safer with our data. It doesn't silently fail, the transactions have a better failure mode, and as previously pointed out it handles ALTER in production a LOT better than MySQL.
The combination of safety, speed/efficiency in schema/index alteration, and its increasingly good performance are why we depend on it. The rest is just gravy.
If MySQL works for you, there is no reason to change. Some people have quite a dependency on Postgres (hstore, JSON, transactional DDL, pubsub, PLPGSQL etc.)