---
title: HubSpot Custom vs Standard Objects for Portals
description: Choose the right HubSpot records for your customer portal with a simple example, decision checklist and clear guidance on when custom objects are useful.
---

[Skip to content](https://woodsportal.digitalwoods.io/en/resources/articles/hubspot-custom-vs-standard-objects-for-portals#main-content)

[![WoodsPortal](https://woodsportal.digitalwoods.io/hs-fs/hubfs/woodsportal-2026/v3234/assets/woodsportal-logo.png?width=393&height=50&name=woodsportal-logo.png)](https://woodsportal.digitalwoods.io/)

[Product](https://woodsportal.digitalwoods.io/product) Use Cases

[Customer Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Vendor Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Dealer Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Membership Portal](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) 

[Pricing](https://staging.woodsportal.digitalwoods.io/pricing) Resources

[Browse all resources](https://woodsportal.digitalwoods.io/resources) [Documentation & help](https://woodsportal.digitalwoods.io/resources/docs) [Developer resources](https://developer.dev.woodsportal.com/) [Open-source frontend](https://github.com/Digital-Woods/WoodsPortal-Frontend) 

[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo) 

Menu

[Product ↗](https://woodsportal.digitalwoods.io/product) Use Cases

[Customer Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Vendor Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Dealer Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Membership Portal↗](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal) 

[Pricing ↗](https://staging.woodsportal.digitalwoods.io/pricing)

Resources

[Browse all resources↗](https://woodsportal.digitalwoods.io/resources) [Documentation & help↗](https://woodsportal.digitalwoods.io/resources/docs) [Developer resources↗](https://developer.dev.woodsportal.com/) [Open-source frontend↗](https://github.com/Digital-Woods/WoodsPortal-Frontend) [Get Started with WoodsPortal ↗](https://app.woodsportal.com/login/sso) [Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo)

[Resources](https://woodsportal.digitalwoods.io/resources)/Articles/Should Your Customer Portal Use Standard or Custom HubSpot Records?

ARTICLE

# Should Your Customer Portal Use Standard or Custom HubSpot Records?

Choose the right HubSpot records for your customer portal with a simple example, decision checklist and clear guidance on when custom objects are useful.

**[WoodsPortal Editorial Team](https://woodsportal.digitalwoods.io/en/resources/author/woodsportal-editorial-team)**ArticleOctober 14, 2026

On this page

A customer portal is easier to build when your information is organized well in HubSpot. The first question is simple: do you need a new kind of record, or can the existing ones do the job?

## Start with records you already have

Think about a company that repairs restaurant equipment. A customer wants to check a repair request, see the related company and find the machine involved.

**HubSpot plan note.** WoodsPortal's nested relationships between HubSpot objects use GraphQL. GraphQL is available with HubSpot Sales Hub Enterprise, Service Hub Enterprise, or Content Hub Professional or higher. Many other portal use cases can use WoodsPortal's REST API implementation on HubSpot plans including Free; supported features depend on the configuration.

One customer's work, three types of information

Company

Who needs the service?

Ticket

What needs fixing?

Equipment

Which machine is involved?

Company and Ticket are familiar standard HubSpot objects. The equipment information might fit an existing supported object or need its own type, depending on what the business tracks. There is no need to create a new object just to give a standard Ticket a different name in the portal.

## What is a standard object?

Standard objects are built-in record types such as Contacts, Companies, Deals and Tickets. Use them when they naturally match the work. A repair request is often a Ticket; a customer organization is usually a Company.

## What is a custom object?

A custom object is a new type of record your business defines. If you maintain a separate history for each machine—serial number, installation date and related repairs—a dedicated Equipment object may make sense.

HubSpot requires an eligible Enterprise subscription to create custom objects. The connected WoodsPortal experience must also support the specific object and its relationships.

## A quick way to choose

Which way should you go?

Use a standard object

It already describes the work clearly

Add properties first

You only need a few more details on an existing record

Consider a custom object

The item has its own history, owner or many related records

In our example, a customer's repair requests belong in Tickets. If the team just needs a model number on each Ticket, a property may be enough. If the same cooler has dozens of requests across several years, a dedicated equipment record may become useful.

## Keep the customer's screen simple

Your internal HubSpot setup can be detailed while the portal stays straightforward. The customer might see 'My equipment,' 'Open repairs' and 'Documents,' rather than internal CRM object labels.

What the customer could see

My equipment

Cooler C-14

Open repairs

Cooling issue — being checked

Documents

Approved instructions and service files

The actual screens depend on the supported objects and fields you configure. Linking two records in HubSpot does not automatically give an external user permission to view both.

## Four questions before you decide

1\. Does an existing HubSpot object already match this work?

2\. Does the information need a separate history or its own relationships?

3\. Does your HubSpot subscription support the record type you want?

4\. Can your portal show the record and restrict it to the right customer?

Try one real-life task with a few sample records. If the customer can complete it without confusing fields or duplicated records, your model is likely heading in the right direction.

## Frequently asked questions

### Should every customer portal use custom objects?

No. Begin with standard HubSpot records where they fit the customer's task. Add custom objects when the business needs a genuinely different kind of record.

### Can I show Tickets and Companies in one portal?

Yes, when the relevant standard objects are included and configured in a supported WoodsPortal experience.

### Does a custom object cost extra?

Creating custom objects requires an eligible HubSpot Enterprise subscription. Check your account's limits and WoodsPortal configuration.

### Can I just add a property to a Ticket?

Often, yes. If you only need to record an extra detail such as an asset serial number, a property may be simpler than a new object.

### Can customers edit these records?

Only for supported actions and fields that you allow for their role. Reading a record does not automatically grant editing permission.

### Can two objects be linked together?

HubSpot supports associations between eligible object types. Check the selected object pair and configure the external portal's access separately.

### What should I do before building the portal?

Write down the questions customers ask, map each answer to a HubSpot record, and test one complete customer journey.

## Start with the customer's question

A good portal makes work clear. Choose the simplest HubSpot record structure that supports the customer journey, then build a WoodsPortal experience around it.

[Choose and sync HubSpot objects](https://woodsportal.digitalwoods.io/resources/docs/choose-and-resynchronize-hubspot-objects) · [Customer portal example](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal)

KEEP EXPLORING

## Related resources

[Browse all resources ↗](https://woodsportal.digitalwoods.io/resources)

## On this page

[All resources ↗](https://woodsportal.digitalwoods.io/resources)

A connected experience

## Turn your HubSpot data into a customer workspace.

Explore how WoodsPortal presents connected records and relevant actions to external users.

[Explore the product ↗](https://woodsportal.digitalwoods.io/product)[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo)

A CONVERSATION ABOUT YOUR PORTAL

## Book a meeting.

Choose a convenient time to discuss your HubSpot portal.

×

Prefer to open the booking calendar in a new tab? [Open meeting calendar ↗](https://digitalwoods.io/meetings/woodsportal/demo)

×

COMING SOON

## This resource is in preparation

We are preparing this resource for the WoodsPortal library. Explore other topics in the collection, or talk with our team about your portal plans.

Return to resources ↗

[![WoodsPortal](https://woodsportal.digitalwoods.io/hs-fs/hubfs/woodsportal-2026/v3234/assets/woodsportal-logo.png?width=393&height=50&name=woodsportal-logo.png)](https://woodsportal.digitalwoods.io/)

Your HubSpot. Their experience.A complete portal, ready to make your own.

[Book a Meeting ↗](https://digitalwoods.io/meetings/woodsportal/demo)

## Product

[Overview](https://woodsportal.digitalwoods.io/product) [Pricing](https://staging.woodsportal.digitalwoods.io/pricing)

## Solutions

[Customer Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-customer-portal) [Partner Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-partner-portal) [Dealer Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-dealer-portal) [Vendor Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-vendor-portal) [Member Portals](https://woodsportal.digitalwoods.io/use-cases/hubspot-membership-portal)

## Resources

[Blog](https://woodsportal.digitalwoods.io/en/resources) [Knowledge Base](https://woodsportal.digitalwoods.io/resources/docs) [Developer Documentation](https://developer.dev.woodsportal.com/)

## Company

[DigitalWoods](https://digitalwoods.io) [Trust Center](https://trust.digitalwoods.io/) [HubSpot Marketplace](https://ecosystem.hubspot.com/marketplace/listing/woodsportal)

[Privacy policy](https://digitalwoods.io/privacy-policy)[Terms of service](https://digitalwoods.io/terms-of-service)[Frontend license](https://github.com/Digital-Woods/WoodsPortal-Frontend/blob/main/LICENSE.txt)

© 2026 DigitalWoods Technologies Inc.WoodsPortal is a DigitalWoods product.

Northstar, Horizon and Riverside scenarios and portraits are illustrative, not customer testimonials.

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "WoodsPortal Editorial Team",
    "url" : "https://woodsportal.digitalwoods.io/en/resources/author/woodsportal-editorial-team"
  },
  "dateModified" : "2026-10-16T10:36:44.310Z",
  "datePublished" : "2026-10-14T18:30:00.000Z",
  "headline" : "HubSpot Custom vs Standard Objects for Portals",
  "mainEntityOfPage" : {
    "@id" : "https://woodsportal.digitalwoods.io/en/resources/articles/hubspot-custom-vs-standard-objects-for-portals",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://woodsportal.digitalwoods.io/hubfs/digitalWoods%20logo.png"
    },
    "name" : "DigitalWoods Technologies Inc"
  }
}
```