A bulk update in HubSpot costs about a minute to run and hours to undo. One import with the wrong column, or one bulk edit on the wrong filter, rewrites a field on hundreds of records. Putting it back depends on whether anyone knows what the old values were.
Before you bulk update properties in HubSpot, decide three things: which source wins, what an empty cell means, and how you will get the old values back. This is for the heads of sales and RevOps owners who approve these changes.
What HubSpot actually does with a bulk update
- Import. HubSpot’s guide to formatting import files says the import tool ignores blank cells, so a blank cell will not clear the existing property value. To update records rather than create new ones, the file needs a unique identifier: Record ID, or Email for contacts and Company domain name for companies. Without one, the import creates duplicates.
- Bulk edit in the table view. You select records, click Edit, pick a property and a value, then Update. HubSpot’s bulk edit article notes that for text and single-select properties this overwrites the existing value on every selected record.
So the risk is not where most teams expect it. An empty column in an import does nothing. A filled column with a wrong or outdated value overwrites every matching record, and a bulk edit on a filter that caught too much does the same.
Leave unchanged or clear this field: how to bulk update properties in HubSpot safely
In an import, a blank cell already means “leave unchanged”. It cannot mean “clear”. For clearing values in bulk, the import guide points to the Edit records workflow action instead. Check that your subscription includes workflows before you plan on it.
That gives you a simple rule to write down before anyone prepares a file:
- Every column in the file is a decision that this source wins over what is in HubSpot today. If you are not sure it wins, delete the column.
- Blank means “we do not know”, never “this should be empty”.
- Clearing a field is a separate, deliberate change with its own filter and its own approval.
What to check in your portal before the next bulk update
- Match on Record ID. Export the records you plan to update and keep the Record ID column in the file, as HubSpot’s import guide recommends.
- Save the old values first. Go to Settings, then Properties, choose the object, hover over the property, click More and select Export property history. Tick Include Source Information. This needs the CRM Export and Edit permissions for that object, according to HubSpot’s export article.
- Test on a small sample. Run the same import or bulk edit on five records first. Open each one and check the result.
- Know your undo for a single record. On a record, click Actions in the left sidebar and select View property history. HubSpot’s property history article says Restore appears only when the change came from a CRM UI edit, an import or a workflow.
- Know your undo for hundreds of records. The export article describes it: filter the history by the date of the wrong change, build a file with Record ID and the previous value, and import it. History is limited to 45 revisions for contact properties and 20 for company, deal, ticket and custom object properties, so do not wait months.
Our take
A bulk update is not a data task. It is a decision about which value is true, made once for hundreds of records. The portal will mirror whatever rule your team actually follows, and if there is no rule, it mirrors whoever imported last. That is why cleanups often do not stick: the next file quietly overwrites them.
The fix is cheap. Write a one-page rule per key property: which system or team owns it, which source wins, and who approves a bulk change. Then make the property history export and the five-record test a habit, not a rescue step. In most portals we open, nobody owns that rule, which is the real cost behind a bad import.
Where an agent helps
The manual steps work, but they are easy to skip on a busy week. Alignify agents run in review mode, so an admin approves or rejects each proposed update, and each finding links to the records and activity behind it. Nothing is written to HubSpot until someone on your team says yes.
Private beta
Let an agent run this check in your HubSpot
Alignify agents read the deals, emails and meetings behind every record, show the evidence and wait for your approval before they change anything.
FAQ
Does a blank cell in a HubSpot import clear the property?
No. HubSpot’s import guide says the import tool ignores blank cells and will not clear the existing value. To clear values in bulk, it points to the Edit records workflow action.
Can I undo a bulk update in HubSpot?
Partly. On a single record you can restore a value from property history when the change came from a UI edit, an import or a workflow. For many records, export the property history, build a file with Record ID and the previous values, and import it back.
How do I bulk update properties in HubSpot without creating duplicates?
Include a unique identifier in the file, ideally Record ID from an export. Without an identifier, HubSpot creates new records instead of updating the existing ones.
Before your team’s next import, ask one question: who decided that this file wins? If nobody can answer, export the property history, test on five records, and only then run it. For the wider order of a cleanup, see what to clean first in HubSpot and our notes on duplicate merge rules.
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.