Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 37 ยท CRM Basics

HubSpot Properties and Field Types

Create and manage HubSpot properties: field types, internal names, dropdowns, calculated and rollup properties, groups, required fields and naming best practices.

A property is a field on a record: first name, deal amount, ticket priority. Properties are how HubSpot stores facts, and they are what you filter, segment, report on and automate with. Designing them well is one of the highest-leverage skills in HubSpot administration.

Default and custom properties

HubSpot ships with many default properties for each object (for contacts: First name, Last name, Email, Phone number, Job title, Lifecycle stage, Lead status and so on). You can add custom properties in Settings > Data Management > Properties (older layouts say "Properties" directly under Settings). Choose an object, then Create property.

When you create one you set:

  • Object. Contact, company, deal, ticket or another.
  • Group. A folder used for tidying (for example "Contact information", "Sales info").
  • Label. The display name, such as "Preferred language".
  • Internal name. The programmatic name used in the API and in imports, for example preferred_language. HubSpot suggests it from the label; it is lower-case with underscores and cannot be changed after creation.
  • Field type. How the value is entered and stored (see below).

Field types

Field type Stores Use for
Single-line text Short text Names, codes
Multi-line text Longer text Notes, descriptions
Number Numeric value Seats, score
Date picker A date Contract end date
Dropdown select One choice from a list Industry, plan
Radio select One choice (all visible) Yes/no questions
Multiple checkboxes Several choices Interests
Single checkbox True/false Consent given
Calculation Result of a formula Margin = price minus cost
Score Points from rules Lead score
Rollup Summary of associated records Total deal value on a company
Unique ID, File, Rich text, Phone, and others Specialized Varies

Type matters because it is mostly permanent: a number property can support sums and averages in reports, while the same value stored as text cannot. A dropdown keeps data consistent, while a free-text field invites "USA", "U.S." and "United States" all at once.

Choosing between text and dropdown

Use a dropdown (or radio/checkbox) whenever the set of valid values is known. It makes reporting reliable and lets workflows branch on exact values. Use text only for truly free input. Keep dropdown lists short; a hundred options is a sign you need a different structure, such as a company property or custom object.

Calculated and rollup properties

  • Calculation properties compute a value from other properties on the same record: for example amount - cost or a date difference like days until renewal. They update automatically.
  • Rollup properties summarize across associated records: the sum of all won deal amounts on a company, the count of open tickets on a contact, the most recent activity date. They are powerful for account-level reports without manual maintenance. Availability depends on edition.
  • Score properties add and subtract points based on conditions (covered in lead scoring).

Required fields, conditions and validation

  • Required creation fields force a value when someone makes a record manually. Use sparingly; too many required fields push people to type "n/a".
  • Property rules and validation (edition dependent) restrict formats, such as a number range or a pattern.
  • Conditional properties can show a field only when another has a certain value (set in the record or form layout).

Property best practices

  1. Check before you create. Search existing properties; duplicates split your data across two fields.
  2. Name consistently. Labels in sentence case, internal names in snake_case, and a short prefix for custom groups.
  3. Use help text on the property so users know what to enter.
  4. Archive instead of delete for properties you no longer need, to protect reports and workflows that reference them.
  5. Limit the properties shown on the record sidebar to what users need.

Internal names and the API

When you import data or call the API, you use internal names, not labels. A property labelled "Preferred language" with internal name preferred_language is set in an API request like:

JSON
{ "properties": { "email": "[email protected]", "preferred_language": "Spanish" } }

For dropdowns, you send the internal value of the option, which can differ from its display label. Mismatches here are a common cause of failed imports.

Validating property values (stand-in)

The stand-in below models the validation rules a property type implies. It is not HubSpot's validator, just the same idea you can reuse before an import.

JS Stand-in: validate values against property definitions

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Stand-in: calculation and rollup

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Groups and views of properties

Property groups only organize the settings and record pages. They do not affect reporting. You can reorder properties on the left sidebar and create different record views for different teams (for example, a lean layout for support agents).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which part of a property cannot be changed after creation?

    The internal name is used by the API and imports, so HubSpot fixes it when the property is created.
  2. 2. When should you prefer a dropdown over text?

    Dropdowns prevent variants like USA, U.S. and United States, making filters and reports reliable.
  3. 3. What does a rollup property do?

    Rollups aggregate across associations without manual maintenance.
  4. 4. Why use number fields for amounts rather than text?

    Reports can only do arithmetic on numeric properties.

Summary

  • Properties are record fields with a label, an immutable internal name and a field type.
  • Pick dropdowns for known value sets and numbers for amounts.
  • Calculation and rollup properties compute values automatically.
  • Search before creating, name consistently and archive rather than delete.

Next: Importing data