When to remove old migrations

I’m on a large scale enterprise product and our liquibase changelogs have reached a very large scale and running changesets is starting to take a long time for our multi-tenancy system. Is it appropriate or at what point should you snapshot the current database and start fresh in your migrations with your current schema. I would love to know if anyone else has run into issues like this and what solutions worked.

Many of our early migrations are deprecated and create tables that have their rows updated or even dropped. This feels like a waste of compute time to create a table only to drop it in a later changelog.

Happy Coding!

This page has information on trimming changelog files:

https://docs.liquibase.com/workflows/liquibase-community/trimming-changelogs.html