How to Rename HubSpot CRM Objects (Contacts, Deals, and More)

If your teams are calling the same thing by different names, your CRM is working against you.

Maybe Sales tracks “Opportunities” while Marketing logs “Leads” and Operations monitors “Projects”—but under the hood, they’re all “Deals” in HubSpot. These mismatched labels become more than an annoyance. They introduce confusion, stall adoption, and lead to misaligned reporting that wastes time and clouds decision-making.

Fortunately, HubSpot’s CRM now lets you relabel core objects like Contacts, Companies, Deals, and Tickets. This means you can finally match your CRM to the language your teams actually use. When names make sense, data gets entered correctly, users stay engaged, and reporting becomes more meaningful.

This guide walks you through how to rename objects in HubSpot—including what changes (and what doesn’t), real-world use cases, setup steps, and how to measure success. Whether you’re a HubSpot admin or RevOps lead, you’ll find practical tips for creating a CRM your teams are confident using.

What Does “Rename HubSpot CRM Objects” Mean? 

HubSpot allows you to change the visible labels of its default CRM objects across your entire portal. That includes Contacts, Companies, Deals, Tickets, and any Custom Objects you’ve added. It’s a visual update only—the underlying structure and function of each object remain untouched.

You’ll find this feature under Settings: Settings > Data Management > Objects > [Select Object] > Rename Labels

Here, you can edit both the singular and plural versions of any object label. For example, swapping out “Deals” for “Projects” updates all mentions from “Deal Pipeline” to “Project Pipeline” across the interface.

Every user in your portal will see the updated labels in record pages, menus, workflows, reports, and list filters. This change gives your CRM a shared vocabulary that reflects how your team actually talks about customers, sales, and accounts, improving clarity and consistency.

If your portal includes advanced roles, permissions, or custom objects, renamed labels still display correctly across all Hubs—Marketing, Sales, Service, or Operations.

How it Works Under the Hood

Although the visible labels change, the engine underneath remains the same. Think of it like putting new road signs on the same highway. HubSpot still relies on the original object IDs and back-end properties. Automations, workflows, and integrations don’t break—they just reflect your new terminology on-screen.

Once you rename an object like “Companies” to “Accounts,” the system updates labels across:

• Navigation menus and pipelines
• Record headers and property panels
• Workflow tools (triggers, actions, conditions)
• Reports and interactive dashboards
• Filters, saved views, and list builders

You also have granular control: singular and plural labels can be customized separately. That flexibility helps if your internal naming doesn’t neatly match default nouns—for instance, “Person” instead of “Contact,” but you still need the plural “People.”

To recap:

1. You select an object: Contact, Deal, etc.
2. You enter custom singular and plural labels
3. After clicking Save, the changes apply portal-wide instantly

The result is a CRM interface that speaks your team’s language—without interrupting core logic or app integrations.

Main Uses Inside HubSpot

Consistent CRM Terminology for Sales Teams

Sales teams rely on precise pipeline language. If your reps don’t see familiar terms, they hesitate. “Deal” might feel generic to a consulting firm that actually delivers “Engagements” or “Projects.”

By renaming objects to reflect how your team sells, you reduce missteps during data entry and strengthen the connection between what’s in HubSpot and what’s actually happening with clients.

Real-world example: A digital agency changes “Deals” to “Projects.” Overnight, their reports switch from “Open Deals” to “Open Projects.” This simple change helps teams outside of Sales—like Client Services—understand and use the CRM without having to translate in their heads.

Unified Language Between Departments

Label mismatches across departments lead to duplicate efforts, miscommunication, and siloed dashboards. If Sales enters “Deals” while Marketing nurtures “Leads,” it’s hard to connect the dots.

Renaming objects like “Contacts” to “Clients” or “Companies” to “Accounts” allows everyone—Marketing, Sales, Success—to view and work from the same source of truth.

Real-world example: A SaaS company shifts from calling business profiles “Companies” to “Accounts.” Now, Marketing’s MQL handoff triggers to Sales follow the same terminology shown in Sales pipelines. Fewer naming conflicts, cleaner assignment logic.

Simplified Reporting and Training

Training new users is a whole lot easier when your CRM speaks their language. Instead of explaining that “Deals” means “Jobs” in your context, why not just call them “Jobs”? When terms appear as expected, users locate records faster, adopt dashboards more quickly, and submit cleaner data.

Leadership also benefits—executive dashboards labeled with business-relevant terms yield quicker insights and enable better decision-making without CRM translation overhead.

Real-world example: A construction firm renames “Deals” to “Jobs” and begins tracking “Jobs Won This Month.” This more accurately reflects internal operations and makes it easier to reconcile job records with accounting software and service delivery tools.

Common Setup Errors and Wrong Assumptions

Renaming CRM objects is straightforward—but it’s easy to miss how deep the change goes. Here are frequent mistakes you can avoid:

• Expecting property names to change
  Labels change, but internal property identifiers like dealstage remain unchanged. If you want UI consistency, you’ll need to manually edit field labels.
• Assuming workflows update references invisibly
  The automation logic still functions, but visual labels in actions and conditions reflect new terms. Skim through core workflows post-renaming to ensure team clarity.
• Renaming without consulting stakeholders
  Unilateral changes confuse users who rely on default terms. Before launching a rename, sync with the department leads to validate terminology.
• Forgetting to update both singular and plural labels
  Leaving one form blank results in mismatched phrases such as “Add new Client” and “View Contacts.” Always complete both forms.

A quick review after renaming can save hours of explanation later. Focus on workflows, reports, and forms where misunderstanding tends to ripple outward.

Step-by-Step Setup or Use Guide

If you’re ready to rename core CRM objects in your portal, follow this step-by-step approach. You’ll need Super Admin or CRM customization rights.

1. Log in to your HubSpot account
2. Click the gear icon in the top right to open Settings
3. In the left menu, navigate to Data Management > Objects
4. Choose the object to rename (Contacts, Companies, Deals, or Tickets)
5. Click on the Rename Labels tab
6. Enter your new singular and plural terms
7. Preview how these will display across the portal
8. Click Save to apply the changes immediately
9. Check your dashboards, pipelines, workflows, and list views for visual consistency

If you’re using Custom Objects, follow the same steps in the Custom Objects section of the menu.

To avoid internal confusion, notify users proactively. Update your training documents, onboarding sessions, and SOPs to reflect the new terms used across the system.

Measuring Results in HubSpot

Changing labels won’t feel like much on its own. But over the following days and weeks, you should notice patterns: users clicking more confidently through records, fewer naming questions during onboarding, and more consistent pipeline use.

Since HubSpot doesn’t offer a built-in report titled “Label Change Effectiveness,” you’ll need to track these metrics manually or build custom dashboards:

• Record creation volume: More objects being created suggests users better understand where data should go.
• Required field completion: If the object’s purpose is more explicit, you’ll see stronger completion rates for mandatory fields.
• Workflow executions involving your renamed object: If those counts remain steady or rise, renaming didn’t disrupt automation flows.
• Internal dashboard activity: Increased traffic on renamed-object dashboards means users are engaging with reports again, now that labels make sense.

To keep an eye on adoption and make course corrections, set up a “Change Management Dashboard” with filters for:

• Weekly new records per object
• Property updates by team
• Stage or pipeline transitions
• Active users engaging with renamed records

These KPIs show whether users embraced the new labels—and whether those tweaks translated to stronger CRM participation across the business.

Short Example That Ties It Together

A software consulting firm has used HubSpot for years, but friction keeps cropping up. Sales tracks “Opportunities,” yet HubSpot still labels them as “Deals.” New hires miss updates, and duplicate reports emerge.

One admin takes five minutes to fix it. From Settings > Data Management > Objects > Deals, they rename the object to “Opportunities.”

• Now, Sales sees “Opportunity Pipeline” and enters updates with confidence
• Reports flow with terms like “Opportunities Won”
• Marketing workflows referencing deals now read correctly, reducing follow-up errors

Over four weeks, internal reviews show a 20% increase in Opportunity entry accuracy. Cleaner data. Fewer questions. More confident users. All from a simple language alignment.

How INSIDEA Helps

Getting object names right is just one step in building a CRM your teams will actually use—and trust. INSIDEA helps businesses shape their entire HubSpot environment to mirror how their teams sell, serve, and grow. That means everything from object naming to automation alignment, onboarding guides, reporting views, and governance frameworks.

If you’re planning to customize object labels, we can help you go deeper. Our HubSpot consulting services include:

• HubSpot Onboarding: Configure object pipelines and naming from the start
• HubSpot Management: Keep object usage aligned and clean post-launch
• Workflow Optimization: Ensure automations reflect label changes clearly
• Reporting Alignment: Build dashboards with your terms, not HubSpot’s defaults

Your CRM should sound like your company—not a software manual. Visit INSIDEA to get started with a portal audit or talk to our team about renaming and CRM governance.