Custom Object, Custom Property, or something else?
A branching decision tree that asks up to seven questions about how the data relates to its parent record, how often it changes, and whether you need cross-instance reporting. The tree returns one of five recommendations with the tradeoffs, examples, and tier eligibility you need before building.
Answer up to seven questions about how the data relates to its parent record, how often it changes, and whether you need real reporting on it. The tree branches based on each answer and stops at one of five recommendations: Custom Object, Custom Property, Repurposed Standard Object, HubDB, or Custom Event.
One value per contact, or one row per company. If each parent record holds exactly one of these, answer Yes.
Where the recommendations come from
Tier eligibility. HubSpot product KB (custom object availability article, updated April 28, 2026): Custom Objects require Enterprise on any hub. HubDB requires Content Hub Professional or higher. Behavioral and custom events require Marketing Hub Enterprise or Data Hub Enterprise.
Structural tests. Many-to-many relationships that custom properties cannot support is the test from Hyphadev's Custom Objects walkthrough. The facility_1_address, facility_2_address red-flag pattern is from Set2Close's lead-data structure guide. HubDB as reference/lookup, custom events as immutable and multi-occurrence, are both from ProfitPad's HubSpot data primitives breakdown.
Examples. RevBlack's HubSpot custom object case studies (Licenses, Shipments, Partners, Projects).
Pro-tier workaround. Repurposing standard objects (Companies, Deals, Tickets) is the consensus pattern across HubSpot Community threads from 2025 and 2026. HubSpot has not added Custom Objects to Pro despite repeated requests.
Dunamis model assumptions. Frequently changing = updated more than once per quarter on average. Multiple instances = expecting 3+ instances per parent record on average. Both are heuristics that surface the structural decision; calibrate against your actual usage data once it is in HubSpot.
We'll send the recommendation, your path, the tradeoffs and examples, and the tier-eligibility pointers. Optional.
Reach a recommendation to enable the report.
Answers to the questions we actually get.
What does the decision tree recommend?
One of five HubSpot data structures: Custom Object, Custom Property, Repurposed Standard Object, HubDB, or Custom Event. Each recommendation comes with the tradeoffs (what you gain, what you give up), worked examples from common HubSpot use cases, and tier eligibility (Custom Objects require Enterprise on the affected hub; HubDB requires CMS Hub Pro or Enterprise; Custom Events have their own tier requirements).
What questions does the tree ask?
Up to seven, branching based on your answers. Core dimensions are: how the data relates to a parent record (one-to-one, one-to-many, many-to-many), how often it changes, whether it has its own lifecycle independent of the parent, whether you need to report on it across instances, whether you need it on workflow enrollments, and whether the volume justifies a separate object. The tree stops asking once it has enough information to make a confident recommendation.
Where does the tier eligibility data come from?
HubSpot's public product KB for the platform-level limits (Custom Objects on Enterprise, HubDB on CMS Hub Pro and Enterprise, Custom Events on Enterprise plus the Marketing Hub Enterprise platform fee). For the structural and reporting tradeoffs, we cite Hyphadev, Set2Close, ProfitPad, and RevBlack alongside the HubSpot KB, so you can read the underlying source for the recommendation rather than just trust the output.
What if my use case looks like more than one option?
Common. The tree resolves ambiguity by asking the disambiguating question rather than picking a default. For example, a use case that could fit either Custom Object or Repurposed Standard Object is split by whether you need the data on workflow enrollments and whether the standard object you would repurpose has rules that conflict with your data. The output names both options when the tradeoffs are close, so you can decide based on your team's tier and reporting needs.