HubSpot custom fields
This article describes working with HubSpot custom fields in LightLead.
Discovering custom fields
Custom fields are loaded from the deal's custom properties. HubSpot properties are filtered by dataSensitivity — fields marked sensitive and highly_sensitive are excluded. The remaining properties are available for use in reports. When a new property is created, it becomes available after the next discovery.
Matching fields
LightLead uses the field identifier (field_id or field_code) for matching. This ensures:
Rename resilience: matching is preserved when a field's name is changed in the CRM
Uniqueness: each field is uniquely identified
Cross-account isolation: fields from different accounts don't overlap
Custom field types
| Field type | Support | Usage |
|---|---|---|
| Text | Full | Grouping, filtering |
| Number | Full | Metrics, range filtering |
| Date | Full | Filtering by period |
| Select | Full | Grouping, filtering |
| Multi-select | Partial | Filtering by membership |
| Checkbox | Full | Filtering (yes/no) |
| Phone | Full | Grouping, filtering |
| Full | Grouping, filtering | |
| File | Not supported | — |
| Image | Not supported | — |
Impact on saved reports
Important considerations when changing custom fields:
Renaming a field: reports keep working, the name updates automatically
Changing a field's type: may cause errors in reports that use this field as a metric
Deleting a field: reports using this field will show an error, the field is marked as unavailable
Adding a field: a new field becomes available after discovery is run again
Recommendations
Plan your custom field structure in advance
Don't change the type of an existing field unless necessary
Before deleting a field, check which reports use it
Use meaningful field names for easier searching in the interface