I have quite a lot of experience using migrations in Rails, and over time I&#x27;ve become just incredibly suspicious of &quot;down migrations.&quot;<p>I have never once been in a situation where I needed to use one, and even if I did, I&#x27;d have some reason to hesitate. Let&#x27;s say everyone on my team wrote one, and they even tested the &quot;down then up&quot; process to ensure it applied (on their machine), unlike the normal &quot;up&quot; migration, that migration code was probably only executed in a single environment with test data.<p>And even given those two ifs (1 - a down migration exists and 2 - it was tested anywhere), the darn things are still annoying and time consuming to write.<p>I would much rather write another &quot;up&quot; migration in the event that I needed to roll back a change. I guess that would be &quot;rolling forward&quot; a change.<p>All that said, my sphere of influence is pretty small. Has a down migration ever saved your skin? What am I not considering?