@Ryan Along the same line as @Ibad Shaikh question a few minutes ago. Is there a way to mark a migration as completed successfully, other than just the finished_at date ? I have a couple of migrations that were run in production, but subsequently had to be slightly modified. The database had to be tweaked to match by hand in production, as the only way to execute the migrations is with a new deployment. It keeps complaining about the migrations having changed, and locally will not create a new migration without completely resetting the database. Even bringing the database locally, and trying to get it synchronized by hand doesn't solve the problem, because of the migration checksums. Couldn't the reset only be applied to tables that changed or preferably allow the creation of new migrations since there is no way to recalculate the migration checksum ?