Migrations with Data Consistency Score (DCS) – more than you ever wanted to know!

zivrivkis , thank you for the feedback. Here are some answers to the points mentioned by you but this needs a proper analysis, so if you can provide me with the existing case number and optionally your contact details /time zone in a private message so that I can look into it and contact you, that would be great.

1. Correct, DCS is (re)calculated at every incremental sync (including final sync). Since we are migrating from a live mailbox where there are continuous changes and additions, that would explain a change in the DCS score. However, if you think we are recalculating it based on the same data /metadata from a mailbox, we would like to check this.

2. Also, correct, there is no known threshold, but it matters more the type of data that we cannot migrate. However, if you really mean Poor Score (not even Investigate), this should be very rare situation and not based on a single corrupt folder rule. Again, we would need to check it.

3. This would normally happen when Last Skipped Item Encountered was AFTER approval. This means you need to approve the new skipped items encountered (acknowledge them and hence approve it again). If you think this is not the case here, again we would need to look into examples.

4. This should not happen, if you confirm in the migration report metadata (DiagnosticInfo -> SkippedItemCounts section that you only had 2 Corrupt ACLs), we likely need to address this.

We are also open to suggestions on how exactly to improve this feature so that admins can truly benefit from it and would be nice to have a discussion with you.