HubSpot field mapping

When you import from HubSpot into TalkValue, the integration pulls in two layers: your portal and every contact inside it. Your portal becomes a channel, and your contacts become people. Here’s how each field maps.

​

Portal mapping

Your HubSpot portal becomes a channel in Path. The channel name is HubSpot (<portal ID>). Every contact imported through that channel is attributed to it, so the Attribution model works without extra setup.

​

Contact mapping

Every HubSpot contact becomes a Person. People are matched by email within your workspace, so a contact that already exists is updated in place instead of duplicated. A contact must have an email to be imported.

​

Re-import behavior

You can re-import the same HubSpot portal. TalkValue updates existing people in place by email, adds new contacts, and refreshes the channel. TalkValue never deletes people.

​

What is not imported

• Archived contacts. Only active contacts are pulled in.
• Contacts without an email. Email is the identity key, so a contact with no email is skipped.
• Address.
• HubSpot deal, lifecycle-stage, marketing, or list data. TalkValue reads only the contact fields listed above.

​

Related

• HubSpot integration. Connection model, status states, reconnect, disconnect.
• Import a channel from HubSpot. Connect HubSpot and start the channel import.
• Import a CSV. Manual import path with explicit column mapping.
• Column mapping. The CSV-side counterpart for picking which columns map to which fields.
• People, companies, channels, events. The Path entity model the import lands in.