Evaluate ISN import identity mapping beyond email

Teams need safer identity matching for ISN imports than email-only matching. The transcript raised concern about duplicate agent/contact records and poor downstream CRM mapping when importing historical data or syncing to external systems like HubSpot.

While reviewing the new ISN integration and historical data imports, Sarah Kreidel specifically raised concerns about how agents were being mapped to avoid duplicate records. Benjamin Eberle explained that the system currently relies primarily on email addresses for identity matching; it looks at the client on the ISN inspection, checks if they exist in Attic, and applies an "ISN import tag" to prevent doubling up.

Sarah pushed back against this email-only method, pointing out that mapping by email often creates dirty data because multiple people might share the same email address, or conversely, different individuals might use a generic office email.

To ensure clean data and proper downstream CRM syncing, she suggested mapping historical imports using unique identifiers like the ISN ID and the HubSpot ID. Her goal is to have these unique IDs connected so that when historical inspections come through, they automatically map to the correct existing profiles in HubSpot without generating duplicate agent records. The team planned to follow up later to collaborate on exactly how to implement this cleaner mapping strategy for HubSpot.