I did actually mean to, but I then came back and ballsed it up by using the `default_attributes` method. The thinking is that if your migration never relies on models and relationships that change or get removed, the migration will still work. I've just hard coded the hash returned by `default_attributes` instead, and re-tested on a fresh copy of the production database.