Cleaning up Historian data after an Ignition migration

When migrating an older Ignition system to a new Ignition 8.1 platform pointing to the existing database (to maintain access to all the historical data) we have some overlapping data timeframes between the previous scan classes and drives and the newer ones with the result that we find gaps in our trending unless we turn off scan class validation. Has anyone else had to solve this kind of conflict before?

In our case there is just over an hour of time where we have data from both the old partition and the two newer partitions. I believe the biggest thing we need to do is retire tags pointing to the older partitions but I'm not certain if there are other necessary steps to get things working correctly.