The only time I&#x27;ve had use for rolling back migrations is when I&#x27;m working on a feature&#x2F;develop branch that have modified existing columns and need to switch back to the master branch to start work on a bug fix.<p>That could potentially be solved in other ways, though - such as keeping separate databases for different git branches, or making database snapshots. Both of those are manual work, though - apart from the upfront effort it takes to write the &quot;down&quot; migration, rolling back migrations seems like the path with least friction.<p>Unless you don&#x27;t need any of the data in your database, or it&#x27;s easily reproducible (database &quot;seeders&quot;), in which case you can just delete the entire database and start from scratch every time.