Good practice is to describe the database in code so that it can be recreated at any time and you can apply changes in a controlled manner to other copies such as production.
If you inherit a database, you can run php artisan schema:dump against an existing database and this will create a baseline of all the existing tables. You can then add migrations from that point on.
@Snapey Yes, I know that the best solution is to describe the database in code but I don't wanna really use it because I am working on an online shop where need to add some relationships. That shop has 358 tables with millions of products so I don't wanna accidentally delete some data from the database.