What are CRM custom objects and custom properties, and when do you need them?
Properties describe a record. Custom objects are for things that are not contacts or deals.
A custom property is a field you add to describe a record. A custom object is a whole new record type, and it only earns its place when something in your business has its own lifecycle and its own relationships to other records. Most companies that ask for custom objects need two properties and a second pipeline instead.
Property types, and picking the right one
The type matters more than people expect, because it determines what reporting you can do later and how dirty the data gets.
- Dropdown or radio for anything you will group a report by. Industry, lead source, closed lost reason.
- Multiple checkboxes when a record can genuinely be several things at once, such as products of interest. Harder to report on, so use it deliberately.
- Number for anything you will sum or average. Never store a number as text.
- Date for anything you will measure elapsed time from. Contract end date, renewal date, first contacted date.
- Single line text for genuinely unique values only, like an account number. If you are tempted to report on it, it should have been a dropdown.
- Calculated properties for anything derived from other fields, so it cannot drift out of sync.
Name fields so the owner is obvious, and resist creating a second field for something that already exists under a different name. Property sprawl is how reporting dies.
The test for a custom object
Ask three questions. Does this thing have its own lifecycle, meaning it changes state over time independently of the contact or deal? Does it need its own relationships to multiple other records? And do you need to report on it as a population, not just as a field on something else?
Three yeses and you probably need a custom object. Genuine examples: a fleet of vehicles a dealer services, individual properties a management company operates, policies at an insurance agency, enrolled students at a school. Each of those has a life of its own.
False alarms we see constantly: products, which are usually a line item feature that already exists; locations, which are usually companies; and projects, which are usually a second pipeline.
The honest trade-off
Custom objects add real capability and real weight. More to maintain, more to train on, more that integrations must understand, and reporting that is less convenient than it is on standard objects. Build one when the business genuinely needs it, not to make the data model feel complete.
See our custom development work, our integration services, and how the data model spans departments.
Related: Can LevelUp Digital build custom HubSpot integrations? | What is a HubSpot Private App? | What is a custom API integration?