HubSpot Property Groups: How to Organise Your CRM Properties

HubSpot stores a lot of data. Every contact, deal, and company record carries dozens of properties. Without a clear structure, your CRM quickly becomes a wall of unlabelled fields that no one knows how to use efficiently.

Property groups are how HubSpot organises those fields. Grouping your properties correctly makes your team’s work faster, reduces data entry errors, and keeps your CRM readable over time.

This guide covers what property groups are, how to create and manage them, and the patterns that work well for teams across Southeast Asia.

What Are HubSpot Property Groups?

A property group is a label that clusters related properties together. When you open a contact, company, or deal record in HubSpot, the properties panel displays your data organised by group.

Groups are a display-layer setting only. They do not affect how properties behave, what data they hold, or how they appear in filters or workflows. Their job is to keep your CRM readable.

HubSpot ships with default groups:

• Contact Information — name, email, phone, website
• Social Media Information — LinkedIn, Twitter, Facebook handles
• Email Information — email status, opt-in data
• Analytics History — original source, latest source
• Conversion Information — form submissions, first conversion

You can add your own groups and reassign properties between them at any time. For most teams, the defaults need restructuring once you start adding custom properties at volume.

Why Property Groups Matter for SEA Teams

Teams in Thailand, Vietnam, the Philippines, and across Southeast Asia often work with contact data that does not fit the default HubSpot structure. LINE IDs, local province and region fields, language preference fields, and intake-cycle properties for education clients are common additions.

When these properties accumulate in a single catch-all group, finding the right field takes longer. Sales reps skip filling in data they cannot find quickly. Reports become unreliable. A deliberate group structure surfaces the right data in the right context.

How to Create a Property Group in HubSpot

Property groups are managed per object type. You set up separate structures for contacts, companies, deals, and tickets.

1. Go to Settings (gear icon, top right)
2. Under Data Management, select Properties
3. Choose the object: Contact, Company, Deal, or Ticket
4. Click Groups in the tab row
5. Click Create group, name it, and save
6. Assign properties to the new group by editing each property and updating the Group field

Renaming and moving properties between groups does not change the underlying data. It is safe to restructure at any stage of your setup.

A Practical Group Structure for Most Teams

The right structure depends on your business, but most teams in Southeast Asia work well with something like this for contacts:

• Contact Information — keep the default; holds name, email, phone
• Regional Data — country, city or province, LINE ID, preferred language
• Lead Source and Attribution — original source override, campaign, referral partner
• Qualification — lead score, ICP fit, company size band, lifecycle stage override
• Communication Preferences — opt-in consent date, preferred channel, contact frequency preference
• Engagement History — last contacted date, next follow-up date, number of calls logged
• Internal — assigned region, account manager override, internal tier

For deals, a lean structure covers most needs:

• Deal Details — value, close date, pipeline, stage
• Qualification — deal type, inbound vs outbound, source
• Scope and Product — service type, contract length, renewal date
• Forecast — confidence level, forecast category, priority flag

Naming Conventions That Reduce Confusion

Group names should be specific enough that a new team member can navigate them without asking. Avoid generic names like “Custom Fields” or “Miscellaneous”.

Prefer:

• Regional Data over Extra Info
• Lead Attribution over Marketing Data
• Qualification over Sales Fields

Use title case consistently. HubSpot displays group names exactly as written on every record, and inconsistent casing looks unprofessional over time.

How Property Groups Connect to the Rest of HubSpot

Property groups affect only the display layer — how fields appear on records. They have no impact on filters, workflows, or reports. When you build contact segments and views, you filter by property values, not by group membership.

Where group structure helps indirectly: when team members are setting up workflows or building reports, a clean group structure makes it faster to find the right property in the dropdown lists. In a portal with 150 or 200 properties, searching a flat list is much slower than navigating by group.

When you create custom properties, assign them to the right group immediately. Properties created without a deliberate group assignment default to a catch-all bucket and accumulate there over time.

When to Restructure Your Property Groups

Most teams restructure once: after their initial CRM setup has been live for three to six months and data quality problems become visible. A restructure does not delete or change property data. You can safely rename groups and reassign properties at any time.

If you are doing a larger cleanup that combines removing duplicate properties, standardising naming, and reorganising groups, let your team know before you start so that people are not referencing old field names in reports during the process.

FAQ

Can I delete a default HubSpot property group?
Default groups cannot be deleted. You can rename some of them and move properties out of them, but the group itself remains in the portal.

Can a property belong to two groups?
No. Each property belongs to one group. If a property fits logically in two places, choose the primary context and document the decision in your CRM setup notes.

How many groups should I have?
As few as needed to keep records readable. Most teams work well with four to seven groups per object. More than ten groups tends to produce the same confusion as having no groups at all.

Do property groups affect HubSpot reports?
No. Reports filter and aggregate by property values, not by group membership. Groups are purely a display-layer setting.

Does moving a property to a different group affect automation or workflows?
No. Workflows reference individual properties directly. Moving a property between groups has no effect on existing automation.

What happens to properties that have no group assigned?
They fall into a system default, typically “Contact Information” or a general catch-all. Assigning new properties to a meaningful group at creation time prevents this accumulation.

---

This article is produced by an independent informational resource by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.