How Salesforce matching works

Salesforce mapping is designed to propose safe matches without creating or changing records during discovery.

Account matching

DOE accounts map to Salesforce Accounts. Mapping discovery compares verified DOE account domains with normalized Salesforce Account.Website values.

Safe account proposals require a unique DOE domain and a unique Salesforce Account match. Ambiguous domains, duplicate candidates, already-mapped records, unverified DOE accounts, and records marked disconnected are excluded from automatic proposals.

Stakeholder matching

DOE stakeholders map to Salesforce Contacts. Stakeholder hints are parent-local: DOE only considers Contacts under the proposed Salesforce Account, and email must be unique enough to be safe.

DOE does not auto-map cross-account contacts. Duplicate emails, ambiguous contacts, already-mapped Contacts, and disconnected mapping markers are skipped.

What mapping start does

Starting mapping is read-only. It queues discovery, calculates proposals, and returns unmatched DOE and Salesforce records. It does not persist mappings. Mappings are persisted only after confirm, manual mapping, import, or export.

When to use manual mapping

Use manual mapping when a business user knows the correct Salesforce Account but automatic discovery could not safely propose it. Manual mapping can also reconnect an explicitly disconnected mapping when the team confirms the relationship is correct.