How to Update Product Names Across HubSpot

Product renames happen more often than full rebrands — and they're almost as disruptive to your HubSpot data. Maybe you're consolidating two product lines into one. Maybe marketing decided that "Enterprise Suite" should become "Business Platform" because the word "enterprise" intimidates mid-market buyers. Or maybe your product simply outgrew its original name.

Whatever the reason, the old name is now everywhere: deal records, blog posts, email templates, knowledge base articles, landing pages, form dropdown options, pipeline stages, and probably a few places you haven't thought of yet. Unlike a rebrand where the company name changes in a predictable way, product renames often involve changes to related terminology too — tier names, feature names, acronyms, and URL slugs.

This guide covers how to systematically update a product name across your entire HubSpot portal without spending a week on it.

Here is what renaming a product across deal records and CMS content looks like in a single operation:

Map the blast radius

Before you change a single record, map out everywhere the old product name appears. This is the step most teams skip, and it's why they're still finding references to the old name six months later.

CRM objects

Deals. Deal names frequently include product names: "Acme Corp - Pro Plan" or "Widget Co - Enterprise Suite Annual." If you have hundreds of open and closed deals, that's hundreds of records to update.

Line items. HubSpot's product library and associated line items will contain the old product name. Update the product in the product library first, but existing line items on closed deals will retain the old name.

Custom properties. If you created dropdown properties like "Product Interest" or "Subscription Type" with the old product name as an option, those need updating. HubSpot lets you edit dropdown options in property settings, but existing records that already have that value selected will need to be updated to the new value.

Contacts and companies. Contact records may have properties like "Current Product" or custom fields that reference the product name.

Tickets. Support tickets often reference product names in the subject or description. Historical tickets probably shouldn't be changed (they're a record of what happened), but open tickets and any auto-populated fields should reflect the new name.

CMS content

Blog posts. Product-focused content, comparison articles, and how-to guides will all mention the product name — often multiple times per post.

Landing pages. Product landing pages, pricing pages, and demo request pages are usually the most concentrated sources of product name references.

Knowledge base. Your documentation and help articles are likely full of references to the product by name, especially in titles and headings.

Email templates. Marketing emails, sales sequences, and transactional email templates may all reference the product name.

Automations and settings

Workflows. Enrollment triggers, branch conditions, and internal email notifications may reference the product name in their criteria or text.

Lists. Active and static lists may be named after the product or use product-name-based filter criteria.

Pipeline stages. If you have product-specific deal stages, those names may need updating.

Start with CRM properties

Before touching individual records, update the source of truth:

1. Product library: Go to Settings > Objects > Products and rename the product. Update the description, price points, and any associated images.

2. Dropdown properties: Go to Settings > Properties and find every dropdown or radio select property that includes the old product name as an option. In each property, add the new name as an option, then use a bulk update to change all records from the old value to the new value, and finally remove the old option.

3. Pipeline stages: If any deal pipeline stages reference the product name, rename them under Settings > Objects > Deals > Pipelines.

Update CRM records in bulk

With properties updated, you now need to update the actual data stored on individual records.

Deal names are typically the biggest job. If you have 2,000 closed-won deals from the last three years and half of them include the product name, that's 1,000 records to update. HubSpot's native bulk edit lets you select records from a list view and set a property to a single value — but it doesn't support find-and-replace. You'd need to manually type the new deal name for each record, which defeats the purpose.

The alternative is a tool that can search for a pattern within a property value and replace just that portion. For example, search for "Enterprise Suite" in the Deal Name field across all deals, and replace it with "Business Platform." A tool like SearchReplace handles this in a single operation: search across all deals, preview the changes, apply them, and roll back if needed.

Contact and company properties follow the same pattern. Search for the old product name in relevant properties and replace it with the new name.

Update CMS content

CMS content requires a separate pass because the product name appears in different contexts:

Body text is the most straightforward — find the old name and replace it. Be mindful of contexts where the old name should remain, like a blog post titled "Announcing the rename from Enterprise Suite to Business Platform."

Page titles and meta descriptions need special attention because they affect SEO. Update the title tags and meta descriptions, but also set up URL redirects if you change any URL slugs.

Images and graphics that contain the product name (screenshots, feature diagrams, hero images) need to be re-created. A text replacement tool can't modify images, so flag these for your design team.

Structured data and JSON-LD on your pages may contain the product name. If your pages include schema markup, check that it's been updated too.

Handle the tricky cases

Partial matches

If your product was called "Pro" and you're renaming it to "Professional," a naive search for "Pro" will match "Product," "Profile," "Process," and dozens of other words. Use exact matching or word-boundary-aware patterns to avoid this. If your tool supports regex, a pattern like \bPro\b will match the standalone word "Pro" without matching it inside other words.

Multiple product tiers

If you're renaming the entire product line, you might have "Pro," "Enterprise," and "Starter" all changing at once. Run these as separate operations, starting with the most specific names first. "Enterprise Suite" is safe to replace without false positives. "Pro" requires more care.

Historical records

Decide upfront whether to update historical data. Closed deals from two years ago, resolved support tickets, and published case studies are all historical records. Changing them might cause confusion if someone cross-references an old invoice with a deal record that now shows a different product name. In most cases, it's fine to update historical records for consistency, but it's worth noting the decision.

Acronyms and abbreviations

If your product was commonly abbreviated (e.g., "ES" for "Enterprise Suite"), search for those abbreviations too. They tend to show up in internal notes, deal descriptions, and team communication channels.

Verification checklist

After completing the bulk updates, verify:

• Product library shows the new name and description
• All dropdown properties use the new name as options
• Pipeline stages reflect the new product name
• A sample of deal names has been updated correctly
• Blog post titles and body text show the new name
• Landing pages and pricing page are updated
• Email templates and sequences use the new name
• Knowledge base articles are updated
• Chatflow messages reference the new product
• Google search results are updating (use Search Console)

Keep it consistent going forward

After the rename, the biggest risk is inconsistency creeping back in. New team members might use the old name out of habit. Sales reps might duplicate an old email template that still has the old name. Document the change clearly, update your internal style guide, and consider setting up a quarterly check where you search for the old product name across your portal to catch any stragglers.

A product rename doesn't have to be a month-long project. With a clear plan and the right tools, you can update thousands of references in a day and move on to the work that actually matters.