* Hopefully fixes spec failures in which the table doesn’t exist
* Decouples the background migration from the post-deploy migration, e.g. we could easily run it again even though the table is dropped when finished.
I believe the field only needs to fit 519 at the moment but I’m rounding up to be a little safer.
See the migration spec for more detail on the magic number 519.