Benefits of using new SERVICES object over a custom object

[Colombo]

Hey there,

We have been developing a custom object to track our client's service inventory and just saw that @hubspot has added a new standard object called SERVICES to the object libary. (See below). Our development team is trying to decide if we should finish developing our custom object or scrap that custom object and customize the new SERVICES object instead. 

Open to any pros, cons or thoughts.

Thank you!

[AllanFormigoni]

Great question! And perfect timing with HubSpot’s new Service object rolling out 😄

The big advantage of using the Service object over a custom object is that it’s already fully supported. You get pipelines, custom properties, reporting, workflows, and associations right out of the box—without the extra setup you usually need for custom objects.

It’s also built specifically for managing service delivery after a deal closes, so if you’re tracking client services or onboarding, it’s probably a much cleaner fit.

Another plus: because it’s a standard object, you won’t hit limits around API access or advanced reporting down the road.

Worth mentioning: the Service object is still pretty new, so there are a few gaps right now (like no timeline events yet if that’s something you use a lot). But HubSpot’s been moving fast to close those.

If your use case is anything like post-sale delivery or ongoing service management, it’s definitely worth switching over. You’ll save a lot of time and headaches compared to maintaining a custom object long-term.

We also recorded a deeper breakdown if you want to dig in:

[JVanpachtenbe]

Hello 

thank you for mentioning the new object.

I don't find a lot of documentation except from the part that it is better to use this object rather than a custom object, which I understand.

But what is the functional part behind this object ?

Anybody has a clue ?

Thy in advance

Jeffrey

[LCunningham1]

I have been searching this morning fro documentation on this object as it's come into our customer success workspace (Beta). We currently use ticket pipelines for managing onboarding, so not sure if we are better to stick with that or overhaul our current process to make use of the service object... anyone any ideas? 

[KhushbooRevOps · Accepted solution]

Hi @Colombo,

Good question! The new service object definitely has some perks over a custom object. Here’s a quick breakdown.

Pros of using the new services object,
Since it’s a standard object, it’ll naturally work better with HubSpot’s built-in tools like reporting, workflows, and lists. 

HubSpot is likely to add more features and improvements to standard objects, so you won’t have to worry about rebuilding custom solutions later. 

Less setup and maintenance using a standard object saves you time configuring and troubleshooting.

Cons of switching to the SERVICES object,

Standard objects might have less flexibility compared to custom objects. So, if you have very specific requirements, you may need to compromise. 

If you already have data and workflows set up for your custom object, migrating everything could be a hassle. 

If the services object covers your main use cases, I’d lean towards switching long-term, it’ll probably save you some headaches! Let me know what your dev team thinks! 

I hope it helps, let me know if you need to talk!

Khushboo Pokhriyal

Growth & Operations

GroRapid Labs

LinkedIn | 9315044754 | Email | Website

[Colombo]

@KhushbooRevOps 

I really appreciate your responce to my post. It was very helpful. My team is wondering if the new SERVICES standard object is considers a Beta solution and they are concerend about bugs. Any thoughts on this?

[TicTacTim]

Hi @Colombo,

We use the new course object. It took some time to get it fully integrated into the portal, e.g. it was not usable in a CRM card on another custom object we created. IMO there's nothing to worry about. I just checked the beta version on the customer portal. It says: release scheduled for 29th October.

Best Tim