Modify migration versions to resolve conflicts

Our migration scheme got messed up when one migration's timestamp put it in the future (2014-11-10 at 22:53:09). I don't know if it's a good idea to fix the issue this way. Without these changes, though, we should be prepared to deal with migration version issues until 2014-11-10 at 22:53:16 (and counting).