Field mappings decide what each lead writes to HubSpot. Connecting HubSpot creates a sensible default set; edit them on the Field Mapping tab (contacts) and Company Mapping tab (companies).
Write modes
Every mapping has a write mode that controls what happens when the HubSpot property already has a value:
| Mode | Behavior |
|---|
| Overwrite | Always set the property to the Caard value |
| Complete if missing | Only write when the HubSpot property is empty |
| Append | Add the Caard value to the existing text instead of replacing it |
| Caard field | HubSpot property | Write mode |
|---|
| First name | First name | Overwrite |
| Last name | Last name | Overwrite |
| Email | Email | Overwrite |
| Phone | Phone | Overwrite |
| Company | Company name | Overwrite |
| Job title | Job title | Overwrite |
| Industry | Industry | Complete if missing |
| Company website | Website URL | Complete if missing |
| LinkedIn URL | LinkedIn URL | Complete if missing |
| Notes | Message | Append |
| Owner | Contact owner | Overwrite |
How notes sync
Smart-capture questions and answers come first, followed by freeform notes oldest-first, combined into the mapped property as one text block. The default target is HubSpot’s Message property; remap it to any text property you prefer.
Default company mappings
Used when company sync is enabled. All default to Complete if missing, so existing HubSpot company data is never overwritten:
| Caard field | HubSpot property |
|---|
| Company name | Name |
| Domain (derived) | Company domain name |
| Company website | Website URL |
| Company size | Number of employees |
| Industry | Industry |
| Company address | Street address |
| Company about | About us |
| Company LinkedIn | LinkedIn company page |
Customizing mappings
On either mapping tab you can:
- Enable or disable individual mappings
- Change the target property — any property on the contact or company object, including custom properties
- Change the write mode
- Add new mappings — map a custom field from Caard, or set a fixed value that’s written to every synced contact
- Reorder mappings
- Reset to defaults to start over
When mapping to a custom HubSpot property, use the property’s internal name (for example lead_source_detail), not its display label. Caard validates mapped property names against your HubSpot account before each sync and reports any that don’t exist.
Per-team and per-event mappings
Like other HubSpot settings, mappings can be overridden per subteam or per event with the scope switcher — useful when one event needs leads tagged differently or written to different properties. See per-team and per-event settings. 