Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 37 ยท CRM Basics

HubSpot CRM Objects and Records

Learn HubSpot's data model: contacts, companies, deals, tickets and other objects, what a record is, how records are identified, and how to create and manage them.

Everything in HubSpot's CRM is organized as objects and records. An object is a type of thing you track (a contact, a company, a deal). A record is one specific instance of an object (the contact Ana Lopez). If you know spreadsheets or databases: an object is a table, a record is a row, and a property is a column.

The standard objects

HubSpot ships with a set of standard objects:

Object What it represents Typical unique identifier
Contact A person Email address
Company An organization Company domain name
Deal A potential sale or revenue opportunity Record ID
Ticket A customer support request Record ID
Product Something you sell (a catalog item) Record ID / SKU you define
Line item A product attached to a deal or quote with a quantity and price Record ID
Quote A priced proposal sent to a customer Record ID

Other standard objects include calls, emails, meetings, notes and tasks (the activities), and in some editions leads, orders, invoices, subscriptions, listings or courses. Enterprise accounts can also define custom objects for things like "Project", "Property" or "Subscription" (see the API chapter later).

Every record, of every object, also has an internal Record ID, a number HubSpot assigns that never changes. It appears in the record's URL and is what the API uses.

Contacts

A contact is a person. Its most important property is email address, which HubSpot treats as the unique identifier: you cannot create two contacts with the same primary email, and imports use it to decide whether to create or update. A contact can have additional emails too.

Contacts have a lifecycle stage, a lead status, a contact owner, and hundreds of possible properties (name, phone, job title, country, original source and so on). HubSpot also records tracking data when a known person visits your site.

Companies

A company is an organization. The company domain name is the unique identifier, so bluefin.example appears once. When a contact is created with an email on a domain that matches a company, HubSpot can automatically associate them (a setting you control).

Deals

A deal tracks a possible sale. It lives in a pipeline at a stage, has an amount, a close date and an owner. See deals and pipelines.

Tickets

A ticket is a support issue, living in a ticket pipeline with its own stages such as New, Waiting on contact, Waiting on us and Closed. See Service Hub.

Creating records

You can make records in several ways:

  1. Manually: the Create contact (or company, deal, ticket) button in the CRM.
  2. Forms: a form submission creates or updates a contact (see forms and landing pages).
  3. Imports: a spreadsheet loaded through the import tool (see importing data).
  4. Integrations: apps that sync with HubSpot.
  5. API: your own software posts records programmatically.
  6. Email and meetings: logging an email with an unknown address can create a contact.

Working with a record

Each record page has:

  • Properties on the left (editable).
  • Activity timeline with notes, emails, calls, meetings and tasks.
  • Associations on the right (the company, the deals, tickets).
  • Actions to merge, clone, delete, or manage consent.

Important actions:

  • Edit in bulk. Select several records in a table view, then use Edit to change a property for all of them.
  • Merge. Combine duplicates into one record, keeping chosen values. Merges cannot be undone, so check the selection carefully (see data quality).
  • Delete. Deleted records go to a recoverable state for a limited time; after that they are gone.

Modeling objects in code (stand-in)

A tiny model helps you reason about unique identifiers and upsert behaviour. This stand-in is not HubSpot; it applies the same rule HubSpot uses for contacts.

JS Stand-in: contacts keyed by email

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

No output.

JS Stand-in: domain matching to a company

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

No output.

The second example shows why auto-association skips public webmail domains: gmail.com is shared by millions of unrelated people, so it must not be treated as a company.

Records versus activities

Records are things (people, organizations, opportunities). Activities are events attached to records: a call, an email, a meeting, a note, a task. When you "log a call" you create an activity linked to the contact (and often the company and deal). Reports can use activities to measure effort, such as calls per rep per week.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the unique identifier for contacts?

    Contacts are unique by email address, which is also how imports decide between create and update.
  2. 2. What is the difference between an object and a record?

    Contact is an object; Ana Lopez is a record of that object.
  3. 3. Why is a gmail.com address not used to associate a contact with a company?

    Public mail domains do not identify an organization, so matching on them would wrongly merge people.
  4. 4. Which are activities?

    Activities are events logged against records, such as calls and meetings.

Summary

  • Objects are record types; records are individual entries with a stable Record ID.
  • Contacts are unique by email, companies by domain name; deals and tickets live in pipelines.
  • Records are created by hand, forms, imports, integrations, email logging or the API.
  • Activities are events attached to records.

Next: Properties and fields