How to Customize Contacts and Companies in HubSpot

Out of the box, a CRM tracks a generic version of a contact and a company. Your business isn't generic. The difference between a CRM your team actually uses and one they quietly avoid usually comes down to a single question: does it capture the information you care about, in a form that's easy to enter and easy to trust?

That's what customizing your core objects and properties is really about. It's the step where the CRM stops being a generic database and starts reflecting how your business understands its contacts and companies.

Here's what's involved, why the details matter more than they seem, and where we focus.

Start with properties, not screens

A property is a single piece of information you track — an industry, a role, a status, a source. Before you arrange anything on a screen, the real work is deciding which properties your business needs on its contacts and companies (and any core custom objects), and how each one should behave.

The best source for that list is evidence you already have: the columns in your current CRM, the fields in the spreadsheets your team maintains, the data in the reports you rely on. We mine those, then talk through the gaps, and end up with a deliberate set of properties rather than a pile of fields nobody remembers creating.

Properties specific to deals, projects, and tickets are handled in their own steps — deal pipeline, onboarding, and support setup — so this work stays focused on the core objects: contacts, companies, and the custom objects that anchor your model.

The details that make properties trustworthy

A property list is only half the job. How each property is built determines whether the data stays clean.

Format and rules. Is it a dropdown, a multi-select, a date, a number? What are the allowed values? Should it require a unique value, or be hidden from certain teams? These choices are the difference between tidy, reportable data and a free-text field full of ten spellings of the same thing.

Conditional logic. Some properties should only appear when another one has a certain value — dependent fields that keep records relevant and uncluttered instead of overwhelming.

Syncing between objects. Often you want the same information to live on both a company and its contacts. HubSpot can sync a value from one to the other, but there's a catch worth knowing: a straight sync is one-directional — you can only edit it from the controlling side. When a business genuinely needs to edit the value from either record, that calls for matching properties kept in step through automation. Knowing which pattern a given property needs is exactly the kind of judgment that keeps a CRM from quietly corrupting its own data.

Then shape what people see

Once the properties exist and behave correctly, the CRM gets tailored to how your team works: the form people fill out when creating a contact or company, the list views they scan, the quick preview they glance at, and the full record they open.

Add the account-level behaviors that keep data associating correctly — how companies attach to contacts, how unknown senders are handled, which domains to keep out of automatic association — and the CRM starts doing sensible things on its own.

Why this pays off

When your core objects and properties are customized properly, the benefits show up in daily use:

Your team captures the information the business actually needs — nothing critical missing, nothing pointless in the way
Data stays clean and reportable, because properties are structured with rules instead of left as free text
Records are easy to read and fast to work, because views and layouts match how each team operates
Segmentation and reporting are precise, because the distinctions you care about are captured as real, structured data
The CRM behaves predictably — associations and defaults handled once, so nobody has to think about them again

Where teams go wrong

Creating fields with no plan. Properties multiply when everyone adds their own. The result is a bloated, confusing record where no one trusts the data. A deliberate, sourced property list beats an organic sprawl every time.

Free-texting things that should be structured. A dropdown you can report on is worth ten open text boxes you can't. The moment of creating a property is the moment to decide this — and it's easy to get wrong in a hurry.

Forgetting the sync direction. Two-way editability is a common, reasonable need that a simple sync quietly can't deliver. Not knowing that is how "the numbers don't match between the company and the contact" becomes a recurring mystery.

How we approach it

We treat this as an information-design exercise, not a field-creation chore. We start from the evidence of what you already track, shape a deliberate property set with the right formats and rules, work out the conditional and syncing logic so the data stays clean and consistent, and then tailor the forms, views, and records so each team sees what's relevant to them.

The aim is a CRM that captures what matters, keeps it trustworthy, and feels built for your business — because it is.

Common questions

Do you customize deal or ticket properties here too? No — those are handled in their own steps (deal pipeline, onboarding, and support), so each stays focused. This step is about your core objects: contacts, companies, and the custom objects central to your model.

We have hundreds of fields in our old system — do they all come over? Not automatically, and usually not all of them. Part of the value here is deciding what's genuinely worth keeping, restructuring what should be structured, and leaving behind what was only ever clutter.

Can we add more properties later? Of course. The point of doing it deliberately now is that later additions fit a clean, intentional structure instead of adding to a mess.

Get your contacts and companies right

If you want to learn more about how to customize your contacts and companies in HubSpot the right way, contact The Gist.