How to Bulk Edit Deals in HubSpot

Deal records carry some of the most important data in your HubSpot portal. They represent revenue, pipeline, and the work your sales team does every day. When deal data needs to change at scale — after a product rebrand, during pipeline restructuring, or following a messy migration — the stakes are higher than with almost any other object type.

HubSpot's native tools for bulk editing deals have the same core constraint as contacts and companies: they can only set properties to a single value, with no find-and-replace capability, no preview, and no undo. For deals specifically, these limitations create unique risks because deal data feeds directly into forecasts, commission calculations, and executive reporting.

What you can do natively with deal records

In the HubSpot Deals list view (Sales > Deals, then switching to the table view), you can:

• Filter deals by any property, pipeline, or deal stage
• Select deals using the checkboxes (including a "Select all" option)
• Click Edit to set one property to one value across all selected deals
• Use "Select all" for larger lists, but only for uniform value assignment

The board view (the Kanban-style pipeline view) does not support bulk editing at all. You can drag individual deals between stages, but there is no multi-select in the board view. For bulk operations, you must switch to the table view.

What native editing cannot handle

Deal records have a particular challenge: many of the properties that need bulk updating contain contextual text. Deal names often follow a convention like "CompanyName - ProductName" or "Q1-2026 | AccountName | Tier." Descriptions reference products, pricing, or terms that change. These are substring-level changes that HubSpot's "set property to value X" bulk edit cannot do.

For example, if your company renames a product from "ProSuite" to "Enterprise Platform," every deal whose name includes "ProSuite" needs updating. With HubSpot's native tools, you would need to:

1. Filter deals by name containing "ProSuite"
2. Open each one individually
3. Edit the name, carefully replacing only the "ProSuite" portion while preserving the rest
4. Save and move to the next one

That is workable for 10 deals. For 300 deals across multiple pipelines, it is a full day of mind-numbing work with a high probability of typos.

When bulk deal editing is necessary

Product or service rebranding

When a product name changes, it ripples through your entire sales pipeline. Deal names, descriptions, and custom properties that reference the old product name all need updating. The change affects not just open deals but also closed-won deals that appear in reports and dashboards.

If you leave old product names in historical deals, anyone pulling a report on "Enterprise Platform" revenue will miss all the deals closed under the "ProSuite" name. Your reporting becomes fragmented across the old and new naming.

Pipeline restructuring

Sales teams regularly restructure their pipelines — merging stages, renaming them, or splitting one pipeline into two. While stage changes themselves happen at the pipeline configuration level, the deal properties that reference stage-specific language often need updating too.

If your deals have a "Current Status" text property or notes that reference stage names like "Contract Sent" and you rename that stage to "Agreement Review," the text properties do not update themselves. They still say "Contract Sent" even though that stage no longer exists under that name.

Fiscal year and quarter updates

Some organizations include time references in deal names: "Q4-2025 Renewal" or "FY26 Expansion." When the naming convention changes — perhaps switching from fiscal year to calendar year, or updating the year reference — all those deals need updating.

This is a textbook substring replacement: find "FY25" and replace with "FY26," or find "Q4-2025" and replace with "Q4-2026."

Owner reassignment text cleanup

When a sales rep leaves or territories are reassigned, deal ownership gets transferred. But deal descriptions, next steps, or custom text fields may reference the old owner by name. "John will follow up on pricing" needs to become "Sarah will follow up on pricing" across all reassigned deals.

This is easy to miss because it is buried in text fields, not structured property values. But it confuses the new deal owner and looks unprofessional if a customer ever sees old rep names in shared deal documents.

Post-import correction

Migrating deals from Salesforce, Pipedrive, or another CRM into HubSpot often produces deals with artifacts from the source system. Deal names might include Salesforce opportunity IDs, descriptions might contain Markdown formatting that HubSpot does not render, or currency values might include symbols that HubSpot does not expect in number fields.

Cleaning these up post-import with a targeted find-and-replace is faster and safer than trying to transform the data during the import itself.

Bulk editing deals with SearchReplace

Select Deals as your object type in SearchReplace, choose the property to update, and enter your search pattern and replacement. Here's an example of renaming a product across your pipeline:

For deal name updates, the substring search mode is usually what you want. If you are renaming "ProSuite" to "Enterprise Platform" in deal names, enter "ProSuite" as the search and "Enterprise Platform" as the replacement. The preview will show every deal that contains "ProSuite" in its name, with the full updated name displayed so you can verify that the replacement looks correct in context.

For more complex patterns, regex mode lets you handle variations. If deal names use inconsistent capitalization — "Prosuite," "ProSuite," "PROSUITE" — a case-insensitive regex match catches all of them in one pass.

Every operation is logged with the full list of affected deal IDs, original values, and new values. If the replacement introduces an unintended change (say, a deal name that coincidentally contained "ProSuite" as part of a different word), you can roll back the entire operation and try again with a more specific pattern.

Protecting your pipeline during bulk changes

Deal data feeds into forecasting, so bulk edits require some extra care:

Avoid editing amount-related fields with text replacement. While SearchReplace works on text properties, using it to modify deal amounts by replacing dollar signs or decimal points is risky. Use HubSpot's native bulk edit or a workflow for numeric changes.

Check for active workflows triggered by deal properties. If a workflow fires when the Deal Name changes, a bulk update to 500 deal names triggers it 500 times. Review and pause any workflows that should not fire during the update.

Time your updates around reporting cycles. If your team pulls pipeline reports on Monday mornings, do not run a bulk deal name update at 8am on Monday. Run it during a low-activity window and verify the results before the next reporting pull.

Update one property at a time. If you need to update both deal names and descriptions, run them as two separate operations. This gives you granular rollback — if the description update goes wrong, you revert just that operation without touching the correctly updated names.

Deal data is too important for the CSV-export-and-hope approach. Preview every change, keep a full audit trail, and have one-click rollback ready. That is the minimum bar for making bulk changes to the records that represent your revenue.