Data Hygiene
Under Review
February 20, 2026
Hi Team,
The large-scale legacy migration is a critical limitation.
To maintain data and prevent duplicate records, more sophisticated import controls are needed.
Custom Match Keys: Allow users to select a custom field (e.g., MGMT_InternalID) or LinkedIn URL as the primary identifier. I have a data rule...email, LinkedIn, or out.
"Update Only" Mode: A toggle to disable new record creation during bulk updates.
Relying solely on Email for relational data is a significant bottleneck, as LinkedIn URLs are currently a more stable identifier. These enhancements would improve the platform's data hygiene.
A 5000 upload limit override could be password-protected. I began keeping my data in shape by not being afraid to delete except for those with markers like current email or linkedin profiles. At least once a year I've exported the database and cleaned it and then imported it back. I'm having issues with getting my data to "join" home status. What to do with Activities, notes and resume