Disclosure: I build Schemity , a desktop ERD tool - this post is from our blog and uses it for the examples.
TL;DR: Draw a Laravel ERD from the database that php artisan migrate built, not from the migration files. In Invoice Ninja v5.13.47 a fresh migrate loads a squashed schema dump and then runs only 61 of the 317 files, and that dump is 10 tables and 43 columns behind the release that ships it. And neither source shows almost half the relations: the database declares 138 foreign keys, while 131 more live only in column names such as activities.client_id .
A Laravel ERD should be drawn from the database that php artisan migrate built, not from the migration files. The files are a history written in PHP, and the database is the result of running it: what a conditional decided, what a raw SQL string created, what a squashed schema dump replaced.…