Architecture | Entry 1 of 11
Yes. HubSpot allows organizations to rename default objects so the visible terminology reflects how their teams work. The internal object value used by integrations and APIs stays the same.
HubSpot organizes information using objects such as Contacts, Companies, Deals, and Tickets.
Those default labels may not match the terms a nonprofit uses every day. A development team may talk about donations, gifts, grants, or sponsorships rather than deals.
Renaming the visible object gives staff terminology they already understand without requiring the organization to build a new custom object solely for the name.
Unfamiliar CRM language creates small moments of confusion throughout the day.
Staff may pause to remember what a term means, put information in the wrong place, or explain the same terminology every time a new person is trained.
Clear labels give the organization a shared vocabulary and make the CRM feel connected to the work staff are already doing.
A nonprofit uses HubSpot’s Deal object to manage major gifts.
Instead of asking the development team to work inside a Deals pipeline, the organization renames the object Donation. Staff could then see labels such as:
Mandy’s original example also suggests renaming Companies to Households.
Changing the name does not change how the object works.
For example, renaming Companies to Households does not automatically create a complete household model. The nonprofit still needs to decide how household members, addresses, donations, and relationships should connect.
The naming decision should support the architecture plan.
HubSpot’s documentation states that default objects can be renamed. The object’s internal value remains unchanged, which matters when working with integrations and APIs.