I'm working for a small webdevelopment company and we want to set up development environments. We'll be using the Laravel framework in combination with Homestead. Now, Homestead has its own database and can work with migrations from Laravel, meaning that any changes to the existing database from previous versions can be updated with a single terminal command. The biggest con to Laravel's migrations is that all the previously stored data in the database will be lost for every migration, meaning you would have to fill it up all over again.
As you might imagine, we don't want to keep refilling our database everytime we change something. So we thought of hosting a single development database instead, but this also comes with cons. Someone in our project might change something in the database, meaning all others in our project may have their code not working on their local development environment, due to the database being changed.
We do have a solid database design, but I'm just worried that something may still go wrong during development. How would we go on about managing our development database properly without loss of data and without the hassle when something changes?