How a Horticulture Company Differentiated Companies and Properties in HubSpot Without Custom Objects

1. No structural distinction between companies and properties

HubSpot’s standard company record made no default distinction between a business entity and a property tied to it. This made it difficult to track and report on the relationship between the two record types.

2. Manual relationship management

Associating a property with its parent company depended on manual data entry. This increased the risk of error and slowed day-to-day record-keeping.

3. Limited reporting visibility

Without a way to formally categorize records, the client could not build reliable reports or dashboards on company-property relationships. This left the marketing and sales teams without a clear view into their own portfolio structure.

How Campaign Creators Modeled Company-Property Relationships Without Custom Objects

System architecture design

The client’s plan did not include custom objects, so the relationship model was built on HubSpot’s standard company object. Campaign Creators added a “Company Type” property to mark a record as a Company or a Property, and a “Number of Properties” field to track portfolio size at the parent level. Every record, company or property, stays on the object the client’s team already works in day to day.

Association labels

Every company-to-property connection carries an association label describing the relationship. A user on the company record sees its properties. A user on a property record sees its parent company. Neither has to go looking.

Automation and workflows

When a record is set to Property under Company Type, a workflow fills the associated company fields without anyone touching them. The data entry errors that came from manual population were designed out of the process.

Impact: A Structure Built on Standard Objects, Not a Custom One

The company/property distinction lives on HubSpot’s standard objects, not a custom one. The property set, association labels, and automation form a single structure supporting the differentiation the client needed, within the plan tier the client already had.

Solve Record Structure and Reporting Gaps With Campaign Creators

Businesses managing complex relationships between parent accounts and the properties, locations, or entities tied to them often assume a custom object is the only way to model that structure in HubSpot. Native features, combined correctly, can solve the same problem within an existing plan tier. Campaign Creators builds property structures, association models, and automation that hold up under the plan tier a client already has.