HubSpot properties are the fields that store data on contact, company, deal, and ticket records. Every piece of information in HubSpot – a contact’s lifecycle stage, a deal’s close date, a company’s industry – is stored in a property. Understanding the difference between default properties and custom properties, and knowing how to create and manage them correctly, is fundamental to building a HubSpot CRM that your team actually uses and trusts. This guide explains HubSpot’s property system, the available field types, and best practices for property governance.
That makes property planning one of the most important parts of a clean setup.
HubSpot properties are useful when a team needs to store the right mix of custom and default fields on records. They shape how the CRM captures information, which means they have a direct effect on reporting, workflow logic, and data quality.
Default Properties vs Custom Properties
Default properties are created by HubSpot and cannot be deleted. They include universally useful fields like email address, first name, last name, company name, phone number, lifecycle stage, lead status, original source, and hundreds more. HubSpot populates some default properties automatically – Original Source is set when a contact is first created based on how they came into the system; Last Activity Date updates every time a new interaction is logged. Default properties are consistent across all HubSpot accounts.
Custom properties are fields you create to store information specific to your business. If you sell software and need to track which product tier a contact is interested in, or which CRM they’re currently using, or whether they’ve completed an onboarding call – those require custom properties. Custom properties can be created on contact, company, deal, and ticket objects, and are only visible in your account (not shared with other HubSpot users).
Property Types Available in HubSpot
When creating a custom property, choose the field type that matches the data you’re storing:
- Single-line text: Free-text entry, one line. Use for names, IDs, short text values.
- Multi-line text: Free-text entry, multiple lines. Use for notes, descriptions, longer text inputs.
- Dropdown select: One selection from a fixed list of options. Use for controlled vocabularies (industry, company size range, product interest) where consistency matters for segmentation and reporting.
- Multiple checkboxes: Multiple selections from a fixed list. Use when a contact can belong to multiple categories (e.g., interested in multiple products).
- Radio select: One selection displayed as radio buttons. Functionally similar to dropdown but displayed differently in forms.
- Date picker: Stores a date value. Use for milestones – contract start date, renewal date, trial end date.
- Number: Stores a numeric value. Use for quantities, scores, revenue amounts.
- Boolean (yes/no): A true/false toggle. Use for binary states – is this contact a decision-maker? Has this company signed an NDA?
- Calculated: A field whose value is computed from other property values using a formula. Available on Professional and above. Use for calculated scores, margin percentages, or time-difference calculations.
Property Groups
Properties are organised into groups – logical sections visible on the record view. Default groups include Contact Information, Company Information, Email Information, Social Media Information. Create custom property groups to organise your custom properties: for example, a “Sales Qualification” group containing ICP score, budget range, decision timeline, and primary competitor. Organised property groups make the record view easier to navigate for reps.
Creating a Custom Property
Go to Settings ? Properties ? select object (Contacts, Companies, Deals, etc.) ? Create property. Fill in: object type, group, field type, internal name (a unique identifier, auto-generated from the label, used in API calls and Workflow references), label (what’s shown in the UI), description (helps team members understand what to enter), and for dropdown/checkbox/radio types, the list of options. Once saved, the property appears on all records of that object type and can be added to forms, used in Workflow conditions, and included in custom reports.
Property Governance: Avoid Property Sprawl
The most common HubSpot data problem is property sprawl – dozens or hundreds of custom properties that overlap, are poorly named, are no longer used, or capture the same information in different formats across objects. Symptoms of property sprawl: reps are confused about which field to fill in, the same value is captured in two different properties, reports can’t be built because the relevant data is spread across inconsistent fields.
To prevent property sprawl: designate one person as the HubSpot property owner responsible for approving new property requests. Before creating a new property, check if an existing property already serves the purpose. Use a naming convention (e.g., prefix all sales qualification properties with “SQ_”) to make properties easy to find and group. Audit unused properties quarterly – any property with zero or near-zero usage that is more than 6 months old should be evaluated for deletion or consolidation.
Using Properties in Segmentation and Automation
The primary value of well-designed properties is their use downstream in segmentation, automation, and reporting. A dropdown property with clean, consistent values (e.g., Company Size with options “1-10”, “11-50”, “51-200”, “201-500”, “500+”) can drive: list segmentation (all contacts at companies with 51-200 employees), Workflow automation (if company size is 500+, enroll in the enterprise nurture sequence), and custom reporting (average deal size by company size bucket). A free-text property with no controlled vocabulary – “how did you hear about us” as a text field – cannot be segmented or automated against without manual cleanup. Match property type to intended downstream use.
Sources
HubSpot, Properties Documentation (2026)
HubSpot, Custom Properties Setup Guide (2026)
HubSpot Academy, CRM Data Management Best Practices (2025)
HubSpot, Calculated Properties Documentation (2025)
HubSpot, Property Group Organisation (2025)
Is HubSpot easy to learn for beginners?
HubSpot has a learning curve, but its official free training platform HubSpot Academy provides structured paths from beginner to advanced. Most users handle day-to-day tasks within 2-4 weeks. Admin and developer skills take 3-6 months to develop proficiently.
What are the biggest HubSpot mistakes to avoid?
Top mistakes include: over-customizing before understanding your process, skipping user training, importing dirty data without cleansing, and not establishing naming conventions. Avoid these four and your implementation will be significantly more successful.
How often does HubSpot release new features?
HubSpot releases major updates quarterly. HubSpot also ships smaller updates continuously to all tiers.
Does HubSpot offer customer support?
Yes. Support is available via chat, email, and phone depending on your plan tier. Enterprise plans include dedicated customer success managers. HubSpot Academy and the HubSpot Community are excellent free support resources.
Can HubSpot integrate with other business tools?
Yes. HubSpot App Marketplace has 1,500+ integrations including Gmail, Slack, Zoom, Shopify, and WordPress.
The best property setup is the one that collects only what the team can use. If fields multiply without purpose, the CRM becomes harder to maintain.
Common Challenges with HubSpot Properties and How to Solve Them
Problem: Getting Your Team to Consistently Use HubSpot
Adoption gaps occur when teams revert to old habits after initial training. Fix: Identify the 2-3 daily workflows where HubSpot adds the most value for your specific role. Focus training on those workflows first. Use HubSpot in-app guidance to provide contextual help at the moment of need rather than relying solely on one-time classroom training.
Problem: CRM Data Quality Degrading Over Time
CRM data decays at approximately 30% per year as contacts change roles and companies. Fix: Schedule a quarterly data quality audit. Use HubSpot deduplication tools to merge duplicate records. Establish data entry standards enforced through validation rules. Consider a data enrichment tool like Clearbit or ZoomInfo to update stale records automatically.
Problem: HubSpot Reports Not Matching Actual Business Results
Reports are only as accurate as the data entered. Discrepancies between CRM reports and actual revenue indicate data entry gaps. Fix: Audit closed-won records against actual invoices monthly. Make CRM data the source of truth for commission calculations so reps have a direct incentive to enter accurate data.