Everyone obsesses over field mapping and workflows, but I kept my eye on the integrity of the access control layer. My primary KPI was record parity, but not just the raw counts. A record that migrated but is now visible to unauthorized users due to broken permission inheritance is a compliance event waiting to happen.
I built a dashboard to track three core metrics across all major objects (Accounts, Contacts, Opportunities):
* **Gross Record Count:** Simple pre- and post-migration totals. Any delta here is a critical data loss/gain incident.
* **User-Scoped Record Count:** The count of records visible to a sample set of users (Sales Rep, Sales Manager, Sys Admin) post-migration, compared to their visible count from a pre-migration log extract. This catches broken role hierarchies and sharing rules.
* **Sensitive Field Completion Rate:** For fields like `AnnualRevenue` or `ContractNumber`, the percentage populated post-migration. A drop indicates ETL pipeline failures or data truncation.
The findings were revealing. Gross counts matched exactly, which the migration vendor celebrated. However, the user-scoped analysis showed:
* Sales reps gained visibility to 15% more Contact records due to a misconfigured "Team-Based" sharing rule in the new CRM.
* The "Private" flag on certain Opportunities did not translate, making them globally visible.
This wasn't just a data migration. It was an access control migration. The dashboard provided the audit trail to force the vendor to remediate the sharing model before go-live. Without tracking visibility, we would have had a massive segregation of duties violation on day one. Always audit the permissions, not just the data.
Where is your SOC 2?