How to Clean Up Contact Properties in HubSpot

Contact properties are the foundation of everything you do in HubSpot. They power your lists, drive your workflows, populate your email templates, and feed your reports. When the properties are clean and consistent, the entire system works. When they are messy, every downstream process is unreliable.

The problem is that contact properties get messy by default. Every form submission, import, integration, and manual edit is an opportunity for inconsistency to enter the system. Over months and years, you end up with job titles in 40 different formats, phone numbers with no consistent pattern, and custom properties that nobody remembers creating.

This guide covers how to audit your contact properties, identify the most common problems, and clean them up at scale.

Here's what a contact property cleanup looks like — in this case, standardizing phone number formatting:

Understanding your contact properties

HubSpot contacts come with a large set of default properties — first name, last name, email, phone number, job title, lifecycle stage, and dozens more. On top of these, most portals have custom properties created by admins, integrations, and app installations.

To see all your contact properties, go to Settings > Data Management > Properties and filter by Object Type: Contact. Sort by "Created" to see the newest properties, or by "Contacts with a value" to find the most (and least) populated ones.

Default vs. custom properties

Default properties are created by HubSpot and cannot be deleted (though some can be hidden). They include essentials like Email, First Name, Last Name, Lifecycle Stage, and Lead Status. These properties have standard internal names that integrations and workflows reference.

Custom properties are created by your team. They include everything from "Preferred Language" to "NPS Score" to "T-Shirt Size (Event 2023)." Custom properties are where the most cleanup opportunity exists, because they are created ad hoc and often without a naming convention.

Property groups

Properties are organized into groups: Contact Information, Email Information, Conversion Information, Social Media Information, and custom groups your team has created. Check your property groups for organization — a well-organized property set is easier to maintain.

Auditing your contact properties

Step 1: Export the property inventory

Go to Settings > Properties > Contact Properties. HubSpot does not have a native "export all properties" button, but you can use the Properties API (GET /crm/v3/properties/contacts) to pull a complete list with metadata: name, label, type, group, description, field type, and options (for dropdown/multi-select).

If the API route feels heavy, a manual review works for smaller portals. Page through the property list and take notes on anything that looks problematic.

Step 2: Identify unused properties

Sort your properties by "Contacts with a value" (ascending). Properties with data in less than 1% of contacts are usually candidates for deletion. They might be:

• Properties created for a one-time campaign that ended months ago
• Properties from a deactivated integration
• Properties created by a former team member for a purpose nobody remembers
• Duplicate properties that track the same data as another property

Before deleting, check for dependencies. Is the property used in any workflow, list, report, form, or integration? HubSpot will warn about some dependencies when you try to delete, but it does not catch everything. Search for the property's internal name in your workflows and list criteria manually.

Step 3: Find redundant properties

Look for properties that overlap in purpose. Common duplicates:

• "Company Size," "Number of Employees," and "Employee Count"
• "Phone," "Phone Number," and "Mobile Phone"
• "Source," "Lead Source," and "Original Source"
• "Tags," "Contact Tags," and "Labels"

For each set of redundant properties, choose the canonical one (usually the one with the most data and the most references in workflows/lists). Plan to migrate data from the redundant properties to the canonical one, then delete the extras.

Step 4: Check property types

Verify that each property's type matches the data it holds:

• Phone numbers should use the "Phone number" field type, not "Single-line text"
• Dates should use the "Date picker" type, not text
• Yes/no values should use "Single checkbox," not text
• Fixed-option values should use "Dropdown select" or "Radio select," not free text
• Numbers should use the "Number" type, not text

Wrong property types cause problems downstream. A phone number stored as text cannot be formatted by HubSpot's phone formatting. A date stored as text cannot be used in date-based workflow conditions. A number stored as text cannot be summed in reports.

Changing a property type in HubSpot can cause data loss — HubSpot may clear values that do not match the new type. The safe approach is:

1. Create a new property with the correct type
2. Migrate data from the old property to the new one (using a workflow or import)
3. Update all references (workflows, lists, forms, reports) to point to the new property
4. Delete the old property

Step 5: Audit property values

For each important property, check the actual values stored across your contacts. Export a list of unique values and look for:

• Formatting inconsistencies — "United States," "US," "USA," "U.S.," "united states"
• Spelling errors — "Markeitng," "Mangaer," "Develoepr"
• Case variations — "CEO," "Ceo," "ceo," "Chief Executive Officer"
• Whitespace issues — Leading spaces, trailing spaces, double spaces
• Encoding artifacts — Strange characters from CSV imports or API issues
• Obsolete values — Dropdown options that are no longer relevant

Cleaning up property values

Job titles

Job titles are notoriously messy. People enter them in dozens of variations:

• "VP of Marketing" / "Vice President of Marketing" / "VP Marketing" / "VP, Marketing"
• "CEO" / "Chief Executive Officer" / "Founder & CEO" / "Co-founder/CEO"
• "Director of Sales" / "Sales Director" / "Dir. of Sales" / "Dir Sales"

Complete standardization is usually impractical — there are too many variations and many are legitimately different. Focus on the highest-impact normalizations:

1. Standardize abbreviations: decide whether you use "VP" or "Vice President" and apply it consistently
2. Fix clear typos and misspellings
3. Remove garbage entries ("test," "asdf," "N/A")
4. Standardize separator characters: decide whether you use "/" or "&" or "and" between multiple titles

A bulk find-and-replace handles the most common variations. Search for "Vice President of" and replace with "VP of." Search for "Dir." and replace with "Director." Run each as a separate operation with preview to catch false positives.

Phone numbers

Phone number formatting is a universal CRM headache. Your database probably has:

• (555) 123-4567
• 555-123-4567
• 555.123.4567
• 5551234567
• +1-555-123-4567
• +15551234567

Pick a format and standardize. E.164 format (+15551234567) is the most universally compatible — it works with HubSpot calling, Twilio, and most telephony integrations.

Regex-based find-and-replace is the most efficient approach for phone number standardization. A regex pattern can match multiple input formats and output a single consistent format. For example, \(?(\d{3})\)?[\s.-]?(\d{3})[\s.-]?(\d{4}) matches most US phone number formats, and the replacement +1$1$2$3 produces E.164 output.

Country and state values

Geographic properties are riddled with variations. For countries: "United States," "US," "USA," "U.S.," "United States of America," "America." For states: "California," "CA," "Calif," "Ca."

Standardize to the shortest unambiguous form (ISO country codes and state abbreviations) for consistency and to match HubSpot's default dropdown options.

Run a find-and-replace for each known variation. Start with the most common ones — typically, "United States" to "US" and full state names to abbreviations cover 80% of the inconsistencies.

Email addresses

Email cleanup focuses on formatting rather than standardization:

• Remove leading and trailing whitespace
• Lowercase the entire address (email delivery is case-insensitive)
• Fix common domain misspellings (@gmial.com to @gmail.com)
• Remove invalid characters (spaces in the middle, double dots)

See our detailed guide on fixing email formatting issues for the complete approach.

Lifecycle stage and lead status

These properties drive your marketing-to-sales handoff and are critical for reporting. Check for contacts in the wrong stage:

• Contacts at "Lead" who have closed-won deals (should be "Customer")
• Contacts at "Customer" who have churned (should have a specific churn stage or be marked accordingly)
• Contacts at "MQL" who have been there for 6+ months without activity (may need to be moved back to "Lead" or disqualified)

Lifecycle stage changes should usually be done through workflows rather than bulk edit, because HubSpot's lifecycle stage has progression rules that bulk edit can bypass.

Preventing property data from getting dirty again

Tighten form fields

Replace free-text fields with dropdowns wherever you have a fixed set of acceptable values. Job title is hard to constrain (too many valid values), but country, state, industry, and company size can all be dropdowns.

For fields that must be free text, add help text that shows the expected format. "Phone number: +1-555-123-4567" as placeholder text guides correct entry.

Add validation workflows

Create workflows that flag or fix common data quality issues:

• A workflow that lowercases email addresses on creation
• A workflow that sets lifecycle stage based on deal status
• A workflow that flags contacts with missing critical fields (sends a notification to the record owner)

HubSpot Data Hub (formerly Operations Hub) Professional gives you custom code actions, which enable sophisticated validation logic — phone number formatting, name capitalization, and field normalization.

Restrict property creation

Limit who can create new contact properties. In HubSpot, this is controlled through user permissions. Restrict property creation to admins or a designated data steward. This prevents the property sprawl that makes cleanup necessary in the first place.

Document your properties

Maintain a living document that lists every custom property, its purpose, acceptable values, and which team owns it. When someone wants to create a new property, they check the document first to see if one already exists.

HubSpot's property description field is underused. Add a clear description to every custom property explaining what it is for and who should populate it. This description appears in the property settings and helps team members understand the data model.

Schedule recurring cleanup

Property cleanup is not a project — it is a habit. Schedule a monthly check of the most critical properties (email, phone, lifecycle stage, lead source) and a quarterly deep audit of all custom properties. The monthly check takes 30 minutes. The quarterly audit takes 2-3 hours. Both are far less work than a crisis cleanup after months of accumulated data quality issues.

---

Need to standardize contact property values across your HubSpot CRM? SearchReplace lets you find inconsistent values and fix them in bulk, with a full preview before any changes are applied.