I&#x27;ve had similar problems with FluentMigrator, even though it orders things nicely using an attribute on the migration class that has a long value representing the order things should run in.<p>I just use timestamps for when the migration was created, like 201509010034, and for the most part, things are great. Until we got a high priority ticket, and a migration with a later timestamp got pushed ahead of an earlier one, so it never gave us the option to migrate the earlier one.<p>Easy fix was just to update the timestamp of the earlier migration when it finally got through QA, since they weren&#x27;t dependent on each other, but things could&#x27;ve gotten really messy, so I&#x27;m not 100% happy with the way migrations currently work.