Custom Property vs. Custom Object? What to choose?

Smart CRM & Sales Hub Tips, Tricks & Best Practices
1

My company is a private aviation company. We sell co-ownerhsip shares into private jets. This allows the customer a certain number of flights per year. We want to add into hubspot some information that will tell us what shares they own and what plane. Each share has a start date and expiration date. The planes are ultimately sold after 5 years of purchase which would be the expiration. The start date could be different for each shareholder.

My problem is whether to create a custom property or an object to allow us to track this. Each plane number would have 16 shares. My thought is a custom property with the Plane number-serial number would be selected, and another field for 01, 02, 03 (share number) etc. Each Share Record could be associated with a contact right?
Mainly we want to allow for said information to pop up when someone calls in to us via Talk Desk. So we can see which planes they own, what shares and how many, and how many days are left until their expiration.

Any ideas?

2

Hi @Stacks42,

Do you have any additional information on top of start date and end date per share? Die ach additional field means 16 additional properties. Start and end date alone are 32.

To me it sounds like custom objects are the way to go. This would also allow you to build reports that show how many shares are currently within the start and end date range, for example, and easily add additional criteria without drowning in Neely created custom properties.

Best regards!

3

@Stacks42 - Karsten’s on the right track! A Custom Object for “Shares” seems perfect. With 16 shares per plane, custom properties might get messy. This way, you can manage all the details for each share and easily connect them to contacts in HubSpot and Talk Desk.