Our application often requires us to often seed data (i.e. populate maintenance tables or other required data) or run scripts to manipulate production data for various reasons. We've been doing this inside of migrations which works, but it destroys the ability for us to run a schema dump and prune our migrations.
Is there a best practice for handling these scenarios? Database seeds do not seem designed for this and migrations appear to be only intended for schema changes.