title: Recommended / Standard handling of Laravel Data Migrations
body: <p>Laravel ships with database migrations for managing CRUD operations regarding the <em>structure</em> of a database, but what is the appropriate/recommended/standardized way to handle migration of actual data?</p>
  <p>My question is, should the <em>data</em> migration take place directly inside the <em>database</em> migration file? Should it be a seeder? Should it be a job that is dispatched from within the database migration? Where should such logic go. Sometimes these data migrations can become incredibly complex depending on what the database migration does, and in the spirit of maximizing readability and keeping responsibilities separate, I <em>feel</em> like the logic belongs somewhere else.</p>
  <p>This question, I suppose, is more attributable to OOP programming structure and practice as a whole, rather than laravel specific, but Laravel is the framework I'm working in right now so framing my question in that regard.</p>