How to Bulk Update Properties in HubSpot

At some point, every HubSpot user faces the same problem: you need to change a property value across a large number of records. Maybe your company rebranded and every deal referencing the old product name needs updating. Maybe a new sales territory means reassigning hundreds of contacts. Maybe you just realized that half your contacts have "US" in the country field and the other half have "United States."

HubSpot has several native ways to do this, each with significant limitations. Understanding what's available — and where the gaps are — helps you pick the right approach for your situation.

Method 1: Inline editing in list view

HubSpot lets you edit property values directly in the table view for contacts, companies, deals, and tickets. You can select multiple records using the checkboxes, then use the "Edit" button in the toolbar to change a property value across all selected records.

How it works:

1. Navigate to the object (e.g., Contacts)
2. Apply filters to narrow down the records you want to update
3. Select records using checkboxes (you can "Select all" to grab the entire filtered list)
4. Click "Edit" in the toolbar
5. Choose the property to update
6. Enter the new value
7. Click "Update"

Limitations:

• HubSpot's bulk edit only sets all selected records to the same value — there's no find-and-replace, no regex, and no conditional logic.
• You can only set a property to a single new value for all selected records. You can't conditionally change values (e.g., change "US" to "United States" without also changing "UK" to "United States").
• There's no preview of what will change — you're setting a value, not reviewing current values and proposed changes.
• No undo. Once you click "Update," the old values are gone. If you made a mistake, you'll need to manually correct each record or restore from an export you made beforehand (if you made one).

Best for: Simple, one-value updates across a small number of records. Setting a lifecycle stage for 50 contacts, assigning an owner to a batch of leads, marking a group of deals with a tag.

Method 2: Workflows

HubSpot workflows can update property values based on triggers and conditions. You can create a workflow that enrolls contacts matching certain criteria and sets a property value.

How it works:

1. Go to Automation > Workflows
2. Create a new workflow with enrollment triggers that match the records you want to update
3. Add a "Set property value" action
4. Choose the property and the new value
5. Turn on the workflow

Limitations:

• Workflows process records one at a time, and enrollment can take time for large batches.
• Like inline editing, you set a single value — workflows don't support "find text X and replace it with Y" within a property value.
• Workflow enrollment triggers can be complex to configure correctly, especially if your criteria are nuanced.
• You need to be careful about re-enrollment settings — if the trigger condition is met again later, the workflow might fire again and overwrite values you've since changed.
• Available on Professional and Enterprise tiers. Starter plans have limited workflow capability, and Free plans have none.

Best for: Conditional property updates based on other property values. "If country is US, set region to North America." Updates that should apply to new records going forward as well as existing ones.

Method 3: CSV import and export

The import/export method gives you the most control over the actual values but also carries the most risk.

How it works:

1. Export the records you want to update to CSV
2. Open the CSV in a spreadsheet application
3. Modify the property values (using formulas, find-and-replace, etc.)
4. Save the modified CSV
5. Import the CSV back into HubSpot, mapping columns to properties
6. HubSpot matches records by a unique identifier (record ID or email) and overwrites the specified properties

Limitations:

• High risk of data loss. If you map a column incorrectly, you'll overwrite the wrong property across all imported records. There's no undo, no preview, and no rollback.
• Exports of large datasets take time and can time out or be truncated.
• CSV encoding issues can corrupt special characters (see our guide on fixing special characters).
• You need to include a unique identifier column in both export and import. If the identifier doesn't match — for example, if an email address changed between export and import — the record won't update or, worse, will create a duplicate.
• Managing large spreadsheets is cumbersome and error-prone.

Best for: Complex transformations that require spreadsheet logic. Updating calculated values. Batch changes where you need full control over the before and after.

Method 4: HubSpot API

For developers, the HubSpot API provides complete control over property updates. You can write a script that reads records, applies transformation logic, and writes the updated values back.

How it works:

1. Authenticate with the HubSpot API using a private app token
2. Query records using the search or list endpoints
3. Apply your transformation logic in code
4. Update records using the batch update endpoint (up to 100 records per call)
5. Handle rate limits, errors, and retries

Limitations:

• Requires development skills (Python, Node.js, or similar).
• Rate limits: HubSpot allows 100 API calls per 10 seconds for private apps. A batch update of 10,000 records at 100 per batch = 100 API calls, which takes at minimum 100 seconds with rate limit compliance.
• Error handling is your responsibility. Network errors, API changes, malformed data — your script needs to handle all of it.
• No built-in rollback. If your script has a bug and writes incorrect data, you'll need another script to fix it — if you even captured the original values.
• Testing against production data is risky. You need a sandbox or a very careful testing process.

Best for: Large-scale, complex, or recurring updates. Teams with developers who can build and maintain scripts. Integrations that need to update data programmatically.

Method 5: Data Hub (formerly Operations Hub)

HubSpot Data Hub (formerly Operations Hub) adds data quality tools and programmable automation. With Data Hub Professional or Enterprise, you can create custom-coded actions in workflows that transform data programmatically.

How it works:

1. Create a workflow with enrollment triggers
2. Add a custom code action (Node.js)
3. Write transformation logic (e.g., format phone numbers, normalize text)
4. Set property values based on the code output

Limitations:

• Requires Data Hub Professional ($800/month as of early 2026) or Enterprise.
• Custom code actions have execution time limits and memory constraints.
• Still processes one record at a time through the workflow engine.
• Debugging custom code in workflows is limited — logging and error visibility are minimal.

Best for: Teams already on Data Hub who need automated, ongoing data transformations. Formatting rules that should apply to every new record.

Method 6: Third-party bulk edit tools

Purpose-built tools for HubSpot data management fill the gaps that native tools leave. These tools typically offer:

• Search and replace — find a specific value and replace it with another, rather than just setting all records to the same value
• Preview — see exactly what will change before committing
• Rollback — undo a bulk operation if something goes wrong
• Pattern matching — use regex or wildcard patterns to match complex variations

Here's what a bulk property update looks like — in this case, standardizing country name values:

SearchReplace is built specifically for this use case. It connects to your HubSpot portal via OAuth, lets you search across any object type and property using exact match, substring, or regex patterns, shows a full preview of every proposed change, and provides one-click rollback for any operation.

Best for: Find-and-replace operations where you need to change specific values to other specific values. Data standardization (country names, phone formats, company suffixes). Any bulk update where you want to see what will change before it happens and have the ability to undo it afterward.

Choosing the right method

Here's a decision framework:

"I need to set one value across a small batch of records." Use inline editing. It's fast, it's built in, and HubSpot's "Select all" option lets you apply the change to your entire filtered list.

"I need to set values conditionally based on other properties." Use a workflow. Set up enrollment triggers that match your conditions and a property-setting action with the new value.

"I need to change specific text to different specific text." Use a search-and-replace tool. This is the "find US, replace with United States" use case — you're not setting a blanket value, you're transforming existing values.

"I need complex transformations with full control." Use the CSV export/import method or the API. These give you maximum flexibility at the cost of higher risk and more effort.

"I need automated, ongoing data formatting." Use Data Hub or a workflow with a custom code action.

Safety considerations for bulk updates

Regardless of the method you choose, follow these safety practices:

Export before you update. Before any bulk operation, export the affected records with the properties you're about to change. This gives you a backup to restore from if something goes wrong.

Start small. Test your update on a small batch first — 10-20 records. Verify the results before scaling to thousands.

Document what you changed. Keep a log of what was updated, when, by whom, and why. This is invaluable for debugging issues that surface days or weeks later.

Verify after updating. After a bulk update, spot-check records to confirm the values look correct. Don't assume it worked — verify.

Use tools with previews and rollbacks. Whenever possible, choose methods that let you see the impact before committing and reverse it if needed. The few minutes spent previewing can save hours of cleanup from a bad update.

Bulk property updates are one of the most common operations in HubSpot administration. Knowing which tool to reach for — and which risks to watch for — makes the difference between a clean five-minute operation and a multi-day data recovery project.