HubSpot Objects, Records and Properties Explained: How the CRM Data Model Works

Every report you trust, every automation that fires correctly and every clean handover between sales and service rests on one thing: how your CRM stores data underneath the surface. In HubSpot, that structure comes down to three concepts. Objects, records and properties. Get them right and the system scales with you. Get them wrong and you spend the next two years fighting duplicate data, broken reports and workflows that misfire.

This is a plain explanation of how the HubSpot data model works, and why it matters more than most teams realise when they first set up the CRM.

The three building blocks

If you have ever worked in a spreadsheet, the model will feel familiar. The easiest way to map it:

• Object = a sheet (a type of thing you track)
• Record = a row (one specific instance of that thing)
• Property = a column (a single field of information about it)

The whole CRM is the workbook. Each object holds many records, and each record is described by its properties.

Objects

An object is a category of data. HubSpot ships with a set of standard objects that cover most B2B sales and service motions:

• Contacts are individual people, for example a buyer, a champion or an end user.
• Companies are the organisations those people belong to.
• Deals are revenue opportunities moving through a pipeline.
• Tickets are support or service requests.
• Activities are the interactions logged against records, such as emails, calls, meetings and notes.

On paid tiers you can also create custom objects: a type of record that is specific to how your business actually operates. A logistics firm might model Shipments, a SaaS business might model Subscriptions, a recruiter might model Placements. This is where the model stops being generic and starts reflecting your operation.

Records

A record is a single entry within an object. One contact is one record. One company is one record. Every record has its own timeline, its own associations and its own set of property values. When someone says the data is messy, they almost always mean the records are: duplicates, half-filled fields, the same company entered three different ways.

Properties

Properties are the individual fields that describe a record. First name, last name and email on a contact. Industry, employee count and annual revenue on a company. Amount, close date and pipeline stage on a deal. HubSpot provides default properties for every standard object, and you can create your own.

Each property has a field type that controls what data it can hold and how it behaves: single-line text, number, date picker, dropdown select, multiple checkboxes, calculated values and more. The field type matters far more than it looks. A dropdown with fixed options keeps your reporting clean. A free-text field where a dropdown belonged is how you end up with "UK", "U.K.", "United Kingdom" and "england" all describing the same thing, and reports you cannot trust.

Associations: how records connect

The real power of the model is that records do not sit in isolation. Associations link records across objects so you can see the full picture.

Take a simple B2B example. You have a contact, a sales lead at a manufacturing firm. You associate that contact with their company record and with the open deal. Now anyone in the business can open the company and see who the contacts are, which deals are live, what tickets are open and the full history of activity. Nothing is hidden in one person's inbox.

HubSpot also supports association labels (for example marking a contact as the decision maker or billing contact) and many-to-many relationships, so one company can hold many contacts and one contact can be linked to several deals. Modelling these relationships correctly is what makes pipeline reporting, attribution and account-based views actually work.

Why the data model is the foundation, not an afterthought

Most CRM problems are not tooling problems. They are data model problems that were set in the first few weeks and never revisited. A few patterns we see again and again with mid-market teams:

• Everything forced onto the contact. Data that belongs on the company or deal gets crammed into contact properties, so it cannot be reported on properly and goes stale fast.
• Free text where a dropdown belonged. Inconsistent values quietly break segmentation and reporting.
• Custom objects bolted on too late. By the time the business realises it needs to model its core entity, thousands of records already live in the wrong place.
• Associations that do not reflect reality. Contacts and deals are not linked the way the business actually sells, so forecasts and account views are misleading.

The fix is to design the model around how your business operates before you load it with data. Which objects do you genuinely need. Which properties drive decisions and reports. Which field types protect data quality. How records associate to match your real sales and service motion. That groundwork is unglamorous, and it is the difference between a CRM that runs your business and one your team works around.

Getting the foundation built right

You can learn the data model from a page like this. Architecting it for a real operation, migrating existing data into it without carrying the mess across, and keeping it clean as the business grows is a different job.

That is where a structured HubSpot CRM implementation earns its keep: defining the objects, properties and associations around your processes from day one. If you are moving from another system, a careful data migration maps your old fields onto a clean model rather than copying old problems across. And once the foundation is solid, well-designed integrations with the rest of your stack keep records accurate without manual re-keying.

Build the data model deliberately and everything downstream, from automation to reporting to the customer experience, gets easier.

Want your CRM built on the right foundation?

If your HubSpot setup grew organically and the data model is fighting you, we can help you architect it properly around how your business actually works.

Explore our CRM implementation service