Short answer
Create HubSpot properties with a clear label, a permanent internal name that says what the field holds, the right field type, a description and a property group. Check for an existing property first, and document who owns each custom property so the portal doesn't fill up with duplicates nobody trusts.
Before you create a property
- Search existing properties, including HubSpot's default ones. Duplicates such as "Industry", "Industry (new)" and "Industry 2" are the most common cleanup job we see.
- Decide which object it belongs on: contact, company, deal, ticket or a custom object. Firm-level facts go on the company, person-level facts on the contact.
- Decide whether it must sync to Salesforce or another system, and map it there at the same time.
Naming rules
- Label: plain words a user understands, for example "Custodian".
- Internal name: lowercase with underscores, describing the content, for example
custodianoraum_band. HubSpot doesn't let you change an internal name after the property is created, and integrations and workflows refer to it, so get it right the first time. - No dates or people in names. "2024 webinar source" becomes useless next year; use a general property and a value instead.
Field types
- Use dropdowns, radio buttons or checkboxes for anything you'll report or segment on. Free text can't be grouped reliably.
- Use number and date fields for numbers and dates, so filters and calculations work.
- Use a single checkbox only for true yes or no facts.
Governance
- Fill in the description: what it means, where the value comes from and who owns it.
- Put custom properties in named property groups by team or process.
- Review unused properties each quarter. Archive the ones with no values and no references in workflows, lists, reports or forms.
- For regulated firms, mark properties that hold sensitive data and restrict who can view or edit them with field-level permissions where your subscription supports it.
Official documentation
Frequently asked questions
Can you rename a HubSpot property's internal name?
No. You can change the label at any time, but the internal name is fixed once the property is created. To change it you create a new property, move the data and update every workflow, form, list and integration that used the old one.
Should a property go on the contact or the company?
Put it where the fact lives. Facts about a firm, such as AUM band or custodian, go on the company. Facts about a person, such as role or consent, go on the contact.
Salesforce, HubSpot, Anthropic and OpenAI change their products often. Check the official documentation before you rely on a specific setting, limit or price.