Architecture | Entry 2 of 11
Yes. HubSpot allows organizations to create custom properties, also called fields, to store information specific to their work. Nonprofits can use them to track details about donors, volunteers, members, programs, grants, events, households, and other records.
HubSpot comes with standard properties, such as a contact’s name, email address, company, or record owner.
Those standard fields may not cover every detail a nonprofit needs to manage. Custom properties allow the organization to add its own fields to a record.
For example, a nonprofit might create properties for:
These properties give staff a consistent place to enter and find information.
When the CRM does not have the right fields, staff usually create workarounds.
Important information may end up buried in notes, added to spreadsheets, stored in someone’s inbox, or tracked differently by each department. That makes the data harder to search, segment, report on, and use in automations.
Custom properties help nonprofits store information in a structured format. Once the information is stored consistently, teams can use it to:
A nonprofit runs several volunteer programs and needs to know when volunteers are available.
The organization creates custom properties for:
Instead of keeping this information in a separate spreadsheet, staff can view it directly on the volunteer’s record.
The nonprofit can then create a list of volunteers who are available on Saturdays, have completed orientation, and are approved for a specific program.
Before adding a property, decide what information it will store, which object it belongs on, who will update it, and whether staff should choose from set options or enter free text.
Also consider whether the property will support reporting, forms, segmentation, or automation, and whether similar information already exists elsewhere in the CRM.
Too many unnecessary or overlapping properties can make records confusing and create inconsistent data. The goal is not to create a field for every possible detail. The goal is to create fields that support real work and clear reporting.
Property options and limits may vary depending on the HubSpot subscription, object type, and user permissions.
Before publication or implementation, confirm:
Review sensitive information carefully before adding it to any CRM property. Also check whether a new field could affect existing integrations, workflows, forms, or reports.