How to reconcile very long term migrations?

[ajfisher]

We've been using sequelize in a long running project for nearly 4 years now so over that time we've built up a fair number of migration files. As you'd imagine with a big, long piece of development you add things and remove them over time as you learn more and refactor code etc. Over that period we probably now have a few hundred migration files as a result.

I wanted to get some guidance on good practice regarding reconciling or pruning the migrations back. Obviously I could go in and edit the existing migrations where we've say added a field to a model but then removed it later but it feels like breaks the point of having point in time migration files that represent changes.

I'm assuming a lot of this comes down to amount of change, team preferences and how much history you need to keep but this isn't a topic that's covered at all in the docs so I wanted to get a sense of approach to this.