Let's face it—words matter. They shape how we think, how we work, and how enthusiastically we adopt new systems. In the HubSpot universe, those default object names like "Deals," "Companies," and "Tickets" have long been non-negotiable fixtures that teams just had to adapt to—regardless of whether those terms aligned with their internal vocabulary.
If you've ever caught yourself explaining to a new hire, "When HubSpot says 'Deals,' what we actually mean is 'Opportunities,'" then the platform's latest Private Beta feature is about to make your day. HubSpot has finally unleashed the power of personalisation where it matters most: the fundamental language of your CRM.
This update does exactly what you've been secretly wishing for: it gives administrators the ability to rename standard HubSpot objects to match your organisation's terminology. No more cognitive dissonance, no more mental translation, and no more explaining why HubSpot's vocabulary doesn't match your sales team's lingo.
The feature allows you to customise the names of:
Once you've made these changes, your custom labels appear throughout most of the HubSpot interface—creating a seamless experience that feels tailor-made for your organization.
At first glance, renaming objects might seem like a superficial change, a mere cosmetic adjustment that doesn't impact functionality. But anyone who's managed CRM adoption knows that terminology alignment is anything but trivial.
When new users encounter familiar terminology, they immediately feel more comfortable. Instead of learning both a new system AND new vocabulary, they only need to focus on mastering the platform itself. This significantly reduces the cognitive load during onboarding.
Every time a user has to mentally translate between HubSpot's terminology and your company's language, it creates friction. These micro-moments of confusion add up, slowing down workflows and increasing the likelihood of errors.
Many organisations use multiple platforms across departments. When HubSpot's language matches your other systems, users can move between tools more fluidly, without the jarring experience of terminology shifts.
When presenting reports to executives or stakeholders, using consistent terminology eliminates confusion and keeps the focus on the insights rather than explaining what each term means in "HubSpot speak."
When sales, marketing, and service teams all speak the same language within the platform, cross-departmental collaboration becomes more natural and effective.
Getting started with object renaming is refreshingly straightforward:
The process takes just minutes, but the impact on your team's experience can be substantial. It's worth noting that as a Private Beta feature, there are still some areas of the platform where the default names might appear, particularly in the mobile app and certain specialised tools. However, the core experience will reflect your custom terminology.
While the ability to rename objects is undoubtedly powerful, it's worth approaching this customisation thoughtfully:
Before implementing changes, ensure you've established a consistent naming convention that truly reflects how your teams communicate. Polling your power users or conducting a quick terminology audit across departments can help identify the most natural language choices.
Remember to update your internal HubSpot documentation, training materials, and onboarding resources to reflect your custom object names. This prevents confusion when new users encounter resources that don't match what they see in the platform.
If you're using HubSpot integrations or APIs, be aware that these connections may still reference the default object names in their documentation and interfaces. Your technical teams should be prepared to maintain this mental mapping when working with integrated systems.
While custom terminology will feel natural to your existing team, new hires who have used HubSpot elsewhere might initially be confused by your renamed objects. A simple reference guide can help bridge this gap during onboarding.
The benefits of terminology alignment extend far beyond making your team feel more at home in HubSpot. Organisations that have implemented similar customisations in other platforms report tangible business outcomes:
New users become productive more quickly when they don't have to learn a new vocabulary alongside new workflows. This accelerates your ROI on both the platform and on new hire training.
When a system speaks your language, it feels more intuitive and user-friendly. This subtle but important factor contributes to overall satisfaction and reduces resistance to adoption.
Clear, consistent terminology reduces confusion and, consequently, the number of internal support requests related to basic platform navigation and understanding.
When users clearly understand what each object represents in their familiar business context, they're more likely to enter data correctly and consistently.
Customer-facing teams can discuss their HubSpot activities using terminology that matches client conversations, eliminating the awkward translation between "HubSpot language" and "client language."
This object renaming capability represents an important step in HubSpot's journey toward greater platform flexibility. While it may not seem as flashy as some feature releases, it signals HubSpot's growing recognition that successful CRM implementation isn't just about functionality, it's about creating an environment where users feel at home.
As the feature moves from Private Beta to general availability, we can expect refinements that extend custom naming to more areas of the platform. The logical next steps might include:
Each of these enhancements would further cement HubSpot's position as a platform that adapts to your business, rather than forcing your business to adapt to it.
If you're ready to bring your organisation's terminology into HubSpot, consider these best practices:
While renaming "Deals" to "Opportunities" might seem like a small change, it represents something much more significant: HubSpot's recognition that the most powerful CRM is one that adapts to how you work, not the other way around.
By aligning HubSpot's terminology with your organisation's natural language, you remove a subtle but persistent barrier to adoption and efficiency. You create an environment where users can focus on their work rather than translating between different vocabularies. And perhaps most importantly, you signal to your team that their experience matters, that the tools they use should conform to their needs, not force them to conform to the tool.
So go ahead, rename those objects. Transform HubSpot from a platform that your team uses into a platform that feels like it was built specifically for them. After all, in the world of CRM adoption, sometimes the smallest changes make the biggest difference.