Correct workflow when working with migrations and data in a team?

Question

Yii

I'm trying to use migrations, but so far I can't conceptually fit them into the development process in a team using VCS.
In particular, it is not clear how the data should be added.
In migration? If so, then it turns out that during testing (not automatic), with each sneeze (data change), you will have to create a new migration.
In a dump? If yes, then it is not at all clear how to apply data from dumps and migrations in parallel. Although everything seems to be logical - migrations contain a structure, a dump contains data, but it seems to me that there will be so many pitfalls when developers start changing the structure and data of one table in parallel, for example ...
Maybe in fixtures? And what, I created them and voila, everyone has the same data for testing. I downloaded the code from the VCS, loaded the fixtures and tested, either manually or automatically.
All my reasoning is hypothetical, since I have no experience and I just want to find out for myself how to do it right.

Answer 1

The organization depends on the team in which you work, or rather on the agreements between its members. But in general:
migrations - database structure + basic data that almost never change (for example, a list of countries)
fixtures - data for tests and development