<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1094218042721276&amp;ev=PageView&amp;noscript=1">
Skip to content

Architecture Entry 4 of 11

Do nonprofits need to upgrade every HubSpot user to access custom objects?

Not necessarily. Custom objects require an eligible HubSpot Enterprise subscription, but subscriptions, seats, and permissions are separate parts of the setup. The right configuration depends on your nonprofit's account, users, requirements, and contract.

What does this mean?

HubSpot lets organizations purchase different products, or Hubs, at different subscription levels. A nonprofit might use Marketing Hub Professional, Sales Hub Starter, Service Hub Enterprise, Smart CRM, and free tools in the same account.

The organization does not always need the same edition of every Hub. Because custom objects are included with several Enterprise products, a nonprofit may be able to choose the Enterprise product that best fits its needs instead of upgrading every part of its HubSpot account.

Purchasing an Enterprise subscription and assigning user access are still separate decisions. The organization needs to understand:

  • Which Enterprise product unlocks the required feature
  • How many seats are included or required
  • Which users need specialized seats
  • Which users need Core or View-Only access
  • Who needs permission to create or manage custom objects
  • What onboarding and contract requirements apply

Why does this matter for nonprofits?

Nonprofits often assume that advanced CRM architecture automatically requires an expensive account-wide upgrade. That assumption can lead a team to:

  • Rule out custom objects too quickly
  • Build awkward workarounds
  • Store complex information in spreadsheets
  • Overload contact or company records
  • Purchase another system without reviewing HubSpot's options
  • Pay for more access than staff actually need

Reviewing the nonprofit's real requirements can reveal a more practical setup. Some staff may need advanced tools, while others may only need to view or update records. A thoughtful subscription and seat plan matches access to each person's role.

A nonprofit example

A nonprofit needs a custom object for grant applications. It wants to track the grant name, funder, deadlines, requested and awarded amounts, reporting dates, status, and associated contacts and organizations.

The development team initially assumes that every employee needs an Enterprise-level seat. Before purchasing, the nonprofit reviews its current Hubs, seat types, user roles, and permissions with HubSpot and its implementation partner.

The review may show that:

  • One eligible Enterprise subscription provides custom-object functionality at the account level
  • Only certain administrators need permission to create or configure the object
  • Other staff can work with records using their assigned seat type and permissions
  • Some employees only need View-Only access
Maya Santos: Primary Household Member and Primary Donor
Maya Santos: Primary Household Member and Primary Donor
Maya Santos: Primary Household Member and Primary Donor
Maya Santos: Primary Household Member and Primary Donor

The final setup depends on HubSpot's current packaging and the nonprofit's contract, so the organization confirms the details before moving forward.

Important architecture note

Subscription strategy should follow the nonprofit's architecture and user requirements.

Choosing an Enterprise Hub only because it appears to be the least expensive route can create problems if the team ignores which tools staff need, how records will be maintained, which workflows and reports will use the object, who needs editing access, how integrations connect, and what happens as the team grows.

The goal is to purchase the right structure for the nonprofit - not to chase a clever workaround that may not fit the organization long term.

Confirm before purchasing

Do not treat a single Enterprise seat as a guaranteed shortcut.

HubSpot currently lists custom-object creation with several Enterprise products. However, the exact claim that one Service Hub Enterprise seat unlocks full custom-object access for every user should be confirmed with HubSpot for the specific account.

Packaging, minimum seats, onboarding, permissions, limits, pricing, and contract terms can vary. Accounts created before and after March 5, 2024 may also follow different seat models.

Requirements and limitations

HubSpot currently requires an eligible Enterprise subscription to create custom objects. Account Access permission is required to create, edit, and manage custom objects, and object limits can vary by subscription.

Before purchase, confirm:

  • The Enterprise subscription being purchased
  • The minimum seat commitment
  • Included seat types
  • Who can view, create, or edit records
  • Who can create and configure the object
  • Required onboarding fees or services
  • Current custom-object limits
  • Contract and renewal terms
  • Legacy or current seat-based pricing
  • Whether the proposed setup provides the required access