HubSpot · Data Model · Service Delivery

HubSpot Services Object: A Complete Guide For Service-Based Businesses

What HubSpot's Services object is, when to use it instead of deals, tickets, projects or a custom object, how to activate it and set up its pipeline, and the workflows and reports that turn it into a delivery system from signed deal to renewal.

Key Takeaways

  • The HubSpot Services object is a standard CRM object for the intangible work you deliver to customers, such as onboarding, consulting, maintenance and personal care. Each engagement becomes a record with its own pipeline, properties, associations and activity timeline.
  • It is off by default. A Super Admin activates it under Data Management > Data Model > Manage, and it arrives with a default pipeline of three stages: New, In Progress and Closed.
  • Use it to separate what you sold (the deal) from what you are delivering (the service) and from what went wrong (the ticket). Choose a custom object only when you need something Services cannot model.
  • Custom pipelines need Starter or above, while workflows, custom reports and association labels need Professional or Enterprise. Unlike custom objects, Services does not require Enterprise.
  • The value comes from the build around it: a workflow that creates the service record when a deal closes, stage-based tasks, renewal reminders and a delivery dashboard.

The HubSpot Services object gives service-based businesses somewhere to track the work that happens after the sale. Most HubSpot portals record the deal and the support tickets well, but the delivery in between (the onboarding project, the monthly retainer, the maintenance contract) lives in spreadsheets, project tools or a deal pipeline stretched to cover it. When that happens, nobody can see from the CRM which clients are mid-delivery, which engagements are late, or which ones renew next quarter.

This guide explains what the Services object is and when growing and mid-market companies should use it instead of deals, tickets, projects or a custom object. It covers the subscriptions it needs, how to activate and configure it, how to design the data model around it, and the workflows and reports that make it useful. Every product capability and limit below is checked against HubSpot's own Knowledge Base and developer documentation as of October 2026.

Section 01 · Definitions

What Is The HubSpot Services Object?

The HubSpot Services object is a standard CRM object that stores intangible offerings you provide to customers, such as onboarding and consulting, repairs and maintenance, and personal care. Each service engagement is one record, with properties for its details, a pipeline for its progress, associations to the people and companies involved, and a timeline of meetings, emails and other activity.

HubSpot classifies Services as both a sales object and a service object, which reflects how it is used: it starts where the sale ends and carries the customer through delivery. It is one of the objects HubSpot keeps switched off until a Super Admin activates it, alongside appointments, courses and listings. Services records are deduplicated by Record ID, not by email or domain.

A pipeline

Every service moves through stages. The default service pipeline has three (New, In Progress and Closed), and you can add stages or separate pipelines for different kinds of engagement.

Properties

Default fields such as the service name, pipeline, stage and target end date, plus custom properties for what your business tracks: service type, contract value, start date, renewal date, delivery lead.

Associations

Links to contacts, companies, deals, tickets and other records. Associations in HubSpot are always two-way, so the service shows on the company record and the company shows on the service.

Activity timeline

Meetings, emails, calls, notes and logged SMS or LinkedIn messages sit on the service record itself, so the delivery history stays with the engagement rather than scattered across contacts.

Section 02 · Fit

Who Should Use The Services Object?

Use the Services object when your business delivers ongoing or multi-step work after a sale and you need to see that delivery in the CRM: agencies, consultancies, managed service providers, SaaS onboarding teams, maintenance and field service firms, and clinics or wellness providers. If a sale ends at the invoice, you do not need it.

Services fits your business if a closed deal starts a piece of work with its own stages, owner and end date; if one client can have several engagements running at once; if renewals depend on how delivery went; or if account managers and support need to see what is being delivered without asking the delivery team.

Services is the wrong tool if you sell products that ship and are done, if delivery is a single appointment (the Appointments object fits better), if you need detailed task scheduling with dependencies and resource planning (a project tool fits better), or if the "service" is really a support request (that is a ticket).

For service-led firms the payoff is one connected record of the customer: what they bought, what you are delivering, what is going wrong and when they renew. That is the view account management and leadership usually lack. For firms that book individual sessions, see our guide to HubSpot's Appointments object.

Section 03 · Comparison

Services vs Deals, Tickets, Projects And Custom Objects: Which Should You Use?

Use deals for what you are selling, Services for what you are delivering, tickets for what has gone wrong, Projects for internal work with planning stages, and a custom object only when none of these can hold your data. Most service businesses need deals, Services and tickets working together, linked by associations.

ObjectTracksDefault pipelineChoose it when
DealsRevenue opportunitiesSeven stages, each with a win probabilityYou are forecasting a sale. Stop using the deal once it is won.
ServicesEngagements delivered to a customerNew, In Progress, ClosedDelivery has stages, an owner and an end or renewal date. Best fit
TicketsSupport requests and issuesNew, Waiting on contact, Waiting on us, ClosedA customer needs help with something. Associate tickets to the service they relate to.
ProjectsPlanned work, often internalPlanning, Execution, Review, Completed, On Hold, CancelledThe work is a time-bound initiative more than a customer engagement.
Custom objectsAnything you definePipelines you build (Enterprise)You need a structure Services cannot model, and you have Enterprise. Enterprise

The commonest mistake is running delivery on the deal pipeline by adding stages such as "Onboarding" and "Live" after Closed Won. It breaks win-rate and forecast reporting, because a won deal keeps moving, and it gives you no way to track two engagements for the same deal. A separate service record solves both. Pipeline stage defaults above are from HubSpot's pipeline documentation.

Against a custom object, Services has two practical advantages: it is already defined and maintained by HubSpot, and it does not require Enterprise. HubSpot's own custom objects guidance asks you to check whether an existing object can hold your data before you create a new one.

Section 04 · Requirements

Which HubSpot Subscription Does The Services Object Need?

HubSpot documents object activation in the data model tool, which is available on all plans. What you can build around the object depends on your tier: extra pipelines need Starter or above, while workflows, custom reports, pipeline cloning and association labels need Professional or Enterprise. Unlike custom objects, Services does not need Enterprise.

What you want to do with ServicesWhat HubSpot requires
Activate the object, use the default pipeline, add records and propertiesA Super Admin; the data model tool is listed for all products and plans
Create additional service pipelinesStarter, Professional or Enterprise. Custom pipelines are shared across all objects: 15 on Starter, 100 on Professional (350 on Flexible Seats & Credits portals), 350 on Enterprise
Clone a pipeline; restrict a pipeline by teamProfessional or Enterprise
Workflows, including creating service records from a deal workflowProfessional or Enterprise
Association labels (for example, Delivery lead or Client sponsor)Professional or Enterprise
Custom reports on services and related objectsProfessional or Enterprise
Manage services through the APIThe object must be activated first

Limits on custom properties, associations and pipelines vary by subscription. Check them in your own portal under Data Management > Data Model > Limits before you design (HubSpot: manage your data model).

Section 05 · Setup

How Do You Activate And Set Up The HubSpot Services Object?

A Super Admin activates Services in Data Management > Data Model: open the Manage tab, select Activate object on Services, and confirm. Then configure its pipeline stages, add the properties you track, turn on the associations you need, and build the record page and automation. The sequence below takes a typical portal from activation to first live record.

1. Activate the object
→ In HubSpot, go to Data Management > Data Model, click the Manage tab, then Activate object on Services (in the graph view, or from the three-dots menu in the table view) and confirm. Services then appears under CRM > Services, and in workflows and segments (HubSpot steps).
2. Shape the pipeline
→ In Settings > Data Management > Objects > Services > Pipelines, rename or add stages to match how you deliver, for example Kickoff, Discovery, Build, Review, Live, Closed. Set each stage as Open or Closed. Create a separate pipeline only when a type of engagement has genuinely different stages.
3. Add the properties you report on
→ Create custom properties for service type, contract value, start date, renewal date, delivery lead and health. Use dropdowns rather than free text for anything you will filter or report on.
4. Require the right data at the right stage
→ Use conditional stage properties to show, and mark as required, the fields a record must have before it enters a stage, such as a kickoff date before In Progress or a completion note before Closed.
5. Turn on associations and the record layout
→ Associate services with contacts, companies, deals and tickets, and add association labels on Professional or Enterprise. Customize the record page and board cards so the delivery team sees stage, dates and owner at a glance.
6. Automate the handoff, then load existing work
→ Build the closed-won workflow in Section 08 first, then import or create records for engagements already in flight, so the board is complete on day one.

The old instruction to look under "Settings > Objects" for an enable switch is out of date: activation now lives in the data model tool, and pipelines and properties are configured afterwards in object settings (HubSpot: set up pipelines).

Section 06 · Architecture

How Should You Design The Data Model Around Services?

Create one service record per engagement, not per customer and not per task. Associate it with the deal that sold it, the company and contacts it serves, and the tickets raised during delivery. Keep revenue on the deal, delivery status on the service, and issues on tickets, so each pipeline answers one question.

Deal Closed won creates Service Pipeline stage · owner Start, target end, renewal Contract value · health Company Contacts Sponsor · Delivery lead Tickets Meetings · emails renewal date opens the next deal
A service-delivery data model in HubSpot: the deal records the sale, the service record carries delivery, and tickets and activities attach to the engagement they belong to.
Property on the serviceTypeWhy it earns its place
Service typeDropdownFilters the board and splits reports by offering (onboarding, retainer, maintenance)
Start date and target end dateDateDrives overdue views and the "ending soon" workflow
Renewal dateDateTriggers renewal tasks and the next deal
Contract valueNumber (currency)Shows the revenue under delivery, copied from the deal at creation
Delivery healthDropdown (On track, At risk, Off track)Gives account managers an early warning before renewal
External IDSingle-line textMatches records to a project or billing tool if you sync one, since Services deduplicate only on Record ID

Keep the property list short. Every field you add is one more thing the delivery team must fill in, and fields nobody reports on are quickly left blank.

Section 07 · Use Cases

6 Ways Service-Based Businesses Use The Services Object

The Services object fits any engagement that has a start, stages and an end or renewal. These six patterns cover most service businesses. Each lists the pipeline stages to start from and the one thing that makes the build work; adjust both to how your team actually delivers.

1. Client Onboarding

SaaS · Agencies

Best for: teams whose new customers wait weeks for kickoff because nobody owns the handoff from sales.

Pipeline: Kickoff scheduled, Discovery, Configuration, Training, Live. A workflow creates the onboarding service when the deal closes, assigns the onboarding lead, and creates a task at each stage. Book the kickoff meeting from the service record so it sits on the engagement's timeline.

What makes it work: a target end date on every record and a view of onboardings past that date, reviewed weekly.

2. Retainers and Managed Services

Recurring

Best for: agencies, IT providers and consultancies billing monthly for ongoing work.

Pipeline: Active, Review due, Renewal in progress, Renewed, Ended. Store the term start, term end and monthly value. A workflow moves the record to Review due ahead of the quarterly review and to Renewal in progress a set number of days before term end.

What makes it work: one service per retainer, so a client with two retainers shows two records with their own dates and values.

3. Maintenance and Repair Contracts

Field service

Best for: firms that service equipment or properties on a schedule and need proof each visit happened.

Pipeline: Scheduled, Visit booked, Completed, Follow-up required, Closed. Associate each visit's tickets and notes with the contract's service record, so the whole maintenance history is in one place for the account manager.

What makes it work: a next-visit date property that the completion step updates, so the schedule cannot drift.

4. Consulting and Professional Services Engagements

Consulting

Best for: consultancies and professional services firms running several engagements per client.

Pipeline: Scoping, In delivery, Client review, Complete. Use association labels (Professional or Enterprise) to mark the client sponsor and the engagement lead, and log the steering meetings on the service. Our guide to HubSpot for management consulting firms covers the sales side of the same model.

What makes it work: keeping detailed task planning in your project tool and using the service record for status, dates, value and relationships.

5. Implementation Programmes

B2B software

Best for: software and technology firms whose implementation fees and go-live dates are sold on the deal but tracked nowhere after it.

Pipeline: Planning, Build, Testing, Go-live, Hypercare, Closed. Associate support tickets raised during hypercare to the service, so the customer success team sees the issues tied to the rollout rather than to the general queue.

What makes it work: a delivery health property that a weekly review updates, and an alert to the account owner when it turns At risk.

6. Care and Wellness Programmes

Personal care

Best for: clinics, coaching and wellness providers selling a course of sessions rather than a single appointment.

Pipeline: Enrolled, In programme, Programme complete, Follow-up. Track each session with the Appointments object and associate it with the programme's service record, which holds the package, sessions remaining and end date.

What makes it work: keeping clinical or sensitive information out of general CRM properties; check what your regulations allow before storing health data in HubSpot.

Section 08 · Automation

Which Workflows Should You Build Around The Services Object?

Build four workflows first: one that creates the service record when a deal is won, one that creates tasks as the service changes stage, one that warns the owner before the target end or renewal date, and one that alerts the account owner when delivery health drops. Workflows need a Professional or Enterprise subscription.

Workflow 1 · Handoff

Closed-won deal creates the service

A deal-based workflow, triggered when the deal stage becomes Closed won, uses the Create record action, which supports Services. Set the name, pipeline and first stage, copy the contract value and service type from the deal, assign the delivery lead, and associate the new service with the deal's company and contacts.

Workflow 2 · Stage tasks

Each stage creates the next piece of work

A service-based workflow enrolls when the pipeline stage changes and branches by stage: a kickoff checklist task at Kickoff, a review task at Client review, a close-out and feedback-request task at Closed. Keep each task's due date relative to the stage change.

Workflow 3 · Dates

Target end and renewal reminders

A workflow on the service enrolls a set number of days before the target end date or renewal date, notifies the owner and creates a renewal task for the account manager. For renewals, it can create the renewal deal so the forecast picks it up early.

Workflow 4 · Risk

Delivery health alerts

When delivery health changes to At risk or Off track, the workflow notifies the account owner and the delivery lead's manager, so problems reach sales before the renewal conversation rather than during it.

One guardrail from HubSpot's documentation: when a workflow creates records of its own object type, make sure the new records cannot meet the workflow's enrollment triggers, or you create an endless loop. For setup rules that apply to every workflow, see our HubSpot workflow best practices.

Section 09 · Reporting

Which Services Reports Matter Most?

Report on delivery the way you report on sales: how many engagements sit in each stage, which are past their target end date, how much contract value is under delivery, which renew in the next 90 days, and which are at risk. Custom reports on Professional or Enterprise can combine services with deals, companies and tickets.

ReportBuilt fromWho uses it
Services by stage and ownerServices, grouped by pipeline stage and ownerDelivery managers, for weekly stand-ups
Overdue engagementsServices where the target end date has passed and the stage is openDelivery managers and leadership
Value under deliverySum of contract value on open services, by service typeFinance and leadership
Renewals in the next 90 daysServices by renewal date, with delivery healthAccount managers
Tickets per engagementServices joined to associated ticketsCustomer success, to spot troubled rollouts

Custom report builder reports refresh about every two hours, which suits weekly delivery reviews. For the live state of one engagement, use the service board or the record itself.

Section 10 · Pitfalls

What Mistakes Should You Avoid With The Services Object?

Most Services builds that fail do so on design, not on the feature. These are the patterns to avoid before go-live.

1. One service record per customer. It cannot show two engagements at once, and its dates are overwritten each time new work starts. Create one record per engagement.
2. Copying the deal pipeline. Delivery stages are not sales stages. Map the stages to how your team actually delivers, and remove any no one moves records through.
3. A pipeline for every client. HubSpot recommends separate pipelines only for processes with genuinely different stages, and custom pipelines count against a limit shared by every object.
4. Relying on manual creation. If someone must remember to create the service after a deal closes, some will be missed. Automate the handoff on Professional or Enterprise.
5. Importing without a matching ID. Services deduplicate only on Record ID, so importing the same spreadsheet twice creates duplicates. Keep an external ID and update existing records rather than creating new ones.
6. Turning it into a project tool. The Services object tracks the engagement, not every task in it. Keep detailed scheduling where it already works, and sync only status and dates if you need them in the CRM.
Section 11 · Partner

How Twopir Consulting Helps You Build On The Services Object

Twopir Consulting is a Salesforce Partner and HubSpot Partner. We implement, rescue, optimize, and integrate complex CRM and revenue systems, and we help growing and mid-market companies solve complex CRM, integration, and business system challenges. For service-based businesses on HubSpot, that means designing the deal-to-service-to-ticket model, configuring the pipelines and properties, and building the handoff, renewal and reporting automation on top.

Our HubSpot Service Hub practice starts with a free five-day portal audit, so the build begins from what your portal already has. Our wider HubSpot implementation team covers Sales Hub, Marketing Hub and migrations, and where delivery data also lives in Salesforce, our Salesforce and HubSpot integration work decides which system owns each object and field.

Ready to Start

Design Your Service Delivery Model In HubSpot

In a 30-minute discovery call, we review how you deliver today, check what your HubSpot subscription supports, and outline the Services pipeline, properties and workflows to start with.

Schedule a Discovery Call
Section 12 · Bottom Line

The Bottom Line

The HubSpot Services object closes the gap between the sale and the support desk. It gives each engagement a record, a pipeline and a place in the data model, without the Enterprise subscription a custom object needs. The feature is simple; the value comes from the design: one record per engagement, delivery stages that match your work, and automation that creates, advances and renews services without anyone having to remember.

  1. 1

    Activate Services in Data Management > Data Model as a Super Admin.

  2. 2

    Keep the sale on the deal, delivery on the service and issues on tickets, all associated.

  3. 3

    Reshape the default New, In Progress, Closed pipeline to your real delivery stages.

  4. 4

    Automate the closed-won handoff and renewal reminders on Professional or Enterprise.

  5. 5

    Report on stage, overdue work, value under delivery and upcoming renewals.


FAQ

Frequently Asked Questions

It is a standard HubSpot CRM object for intangible offerings you deliver to customers, such as onboarding, consulting, maintenance and personal care. Each engagement is a record with properties, a pipeline, associations to contacts, companies, deals and tickets, and an activity timeline. A Super Admin must activate it before use.

As a Super Admin, go to Data Management > Data Model, open the Manage tab, select Activate object on Services and confirm. Services then appears under CRM > Services and becomes available in workflows and segments. Configure its pipeline and properties afterwards in Settings > Data Management > Objects.

No. Unlike custom objects, Services does not require Enterprise. Additional pipelines need Starter or above, and workflows, custom reports and association labels need Professional or Enterprise. Check your portal's limits under Data Management > Data Model before designing.

A service tracks an engagement you are delivering, such as an onboarding or a retainer, from start to finish. A ticket tracks a support request or issue. Most service businesses use both: tickets raised during delivery are associated with the service they relate to, so the engagement's history is complete.

Start with Services when you are tracking engagements delivered to customers. It is already defined, includes a pipeline, and does not need Enterprise. Choose a custom object only when you need a structure Services cannot represent, and you have an Enterprise subscription.

The default service pipeline has three stages: New, In Progress and Closed. You can rename, reorder, add or delete stages, set each as Open or Closed, and add conditional stage properties so required fields appear when a record enters a stage.

Yes, on Professional or Enterprise. A deal-based workflow triggered by the Closed won stage can use the Create record action to create a service, set its pipeline and stage, copy values from the deal, assign an owner, and associate it with the deal's company and contacts.

Yes, once the object is activated. HubSpot's Services API supports creating, reading, updating, upserting, merging, associating and deleting service records, individually or in batches, which lets you sync services with a project management or billing system.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting implements, rescues, optimizes, and integrates complex CRM and revenue systems. We work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges, including service-based businesses running delivery and renewals on HubSpot and Salesforce.