.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
TLDR
- HubSpot doesn't offer a ready-made customer onboarding process. Teams build one by tracking onboarding through Projects, Services, a ticket pipeline or a custom object, with a new record created when a deal closes.
- The key decision is where onboarding lives. Accounts created on or after December 1, 2025 can show only Projects or custom objects in the Customer Success Workspace.
- Service Hub Professional is needed for several key tools, including workflow-created tickets, the Customer Success Workspace, health scores, feedback surveys, the customer portal and the knowledge base.
- Agree on the stages, exit criteria and sales handoff fields before you build. HubSpot supports the process, but it cannot design it for you.
- Elefante RevOps builds onboarding and customer success processes in HubSpot, starting with a 45-minute assessment and a written scope.
Good onboarding carries the context of the sale into delivery, makes ownership clear and shows whether customers are reaching the outcomes they bought. HubSpot can support that process, but it can't design it for you.
The contract is signed on Friday, and sales moves the deal to closed won. On Monday, the onboarding lead hears about the new customer through Slack and opens a HubSpot record with a few notes. There is no clear record of what was promised, who the sponsor is or what success should look like at 90 days. By the kickoff call, the customer is repeating information they already gave sales.
The problem goes beyond a frustrating first meeting. In Bain's 2024 technology report, software buyers ranked help with technical implementation and deployment as their top post-sale priority, while customer success teams ranked it sixth. When those priorities don't line up, customers spend their first weeks waiting for answers instead of getting value from what they bought.
This guide explains how CS and RevOps leaders can run customer onboarding in HubSpot: choosing the right object, automating the sales handoff and measuring progress without relying on spreadsheets and Slack threads. If you're setting up HubSpot for your own team, see our HubSpot onboarding guide instead.
What HubSpot offers for customer onboarding
HubSpot provides the building blocks for customer onboarding across its CRM and Service Hub, but the features available depend on your subscription.
| Feature | What it does for onboarding | Subscription needed |
|---|---|---|
| Custom pipelines | Stages for each onboarding step, marked open or closed | Starter or higher. The limit is shared across all objects: 15 on Starter, 100 on Professional (350 on Flexible Seats & Credits pricing) and 350 on Enterprise |
| Projects object | Tracks each onboarding as a project with associated tasks, deals and contacts | All plans. Pipeline rules need Professional or Enterprise |
| Services object | Tracks onboarding sold as a defined service, which HubSpot describes as built for offerings "such as onboarding and consulting" | All plans |
| Ticket pipeline automation | Creates tasks, sends internal notifications or edits properties when a ticket enters a stage | Sales Hub or Service Hub Starter or higher |
| Workflows that create records | Creates the onboarding record automatically when a deal closes | Professional or Enterprise. Creating tickets needs Service Hub Professional or Enterprise, and custom objects need Enterprise |
| Customer Success Workspace | One place for a CSM's customers, projects, revenue records, tasks, health score alerts and dashboards | Service Hub Professional or Enterprise, with an assigned Service seat |
| Health scores | Scores companies or contacts on engagement, tickets, sentiment and other signals | Service Hub Professional or Enterprise. Multiple scores need Enterprise |
| Playbooks | Guides the kickoff call with set questions and logs the answers on the record | Sales Hub or Service Hub Professional or Enterprise, with a Sales or Service seat |
| Feedback surveys, customer portal and knowledge base | Collects feedback, lets customers follow their tickets and gives them self-serve help | Service Hub Professional or Enterprise |
A basic pipeline can run on Starter. For an automated closed-won handoff, you'll need Professional workflows, while the Customer Success Workspace and health scores require Service Hub Professional.
HubSpot is also testing HubSpot Work, a public beta for managing cross-functional projects that uses client onboarding as one of its examples. It is worth watching, but this guide focuses on the CRM objects and features you can rely on today.
Which HubSpot object to use for customer onboarding
Before building the workflow, decide where you'll track each onboarding. The object you choose affects how your team manages delivery, what it can automate and how onboarding appears in reports.
Start with what onboarding actually is for your team:
- Delivery work with tasks and milestones, such as a software rollout: use Projects.
- A defined service you sell, such as a fixed-scope onboarding package: consider Services.
- Requests handled by a service team that already works in tickets: use a separate ticket pipeline.
- A complex data model, such as several sites or product modules per customer: use a custom object.
Next, check the subscription requirements and the restrictions tied to when your HubSpot account was created.
| Object | Good for | Watch out for |
|---|---|---|
| Projects | Most teams, and the safe default on newer accounts. Built for delivery work, with associated tasks, and usable in the Customer Success Workspace on every account | Some views and subtasks are still in beta. Pipeline rules need Professional |
| Services | Onboarding sold as a defined package, tracked alongside the other services you deliver | Accounts created on or after December 1, 2025 cannot use it in the Customer Success Workspace |
| Ticket pipeline | Older accounts already running service in tickets, and teams that want ticket automation and the customer portal | Onboarding tickets mix with support tickets in reports unless you separate pipelines. Accounts created on or after April 1, 2025 cannot use tickets in the Customer Success Workspace |
| Custom object | Complex onboarding with its own data model | Needs Enterprise, and someone has to maintain the data model |
| Deal pipeline | Rarely the right choice | Onboarding "deals" inflate deal counts and break deal-based workflows and forecasts |
Your account creation date affects which onboarding records appear in the Customer Success Workspace. HubSpot's workspace settings guide says accounts created before April 1, 2025 can use Projects, Services, Tickets or custom objects. Accounts created from April 1 through November 30, 2025 can use Projects, Services or custom objects, while those created on or after December 1, 2025 can use only Projects or custom objects. Tickets and Services may still work elsewhere in HubSpot, but they won't appear in the workspace on accounts where they're unsupported. For a new portal, Projects is the safer default.
Keep the sales deal as the record of the sale, and create a separate record for onboarding. As one HubSpot Community member warned in 2022: "Whatever you do, do not move a sales deal from one pipeline into another."
How to set up customer onboarding in HubSpot
To set up customer onboarding in HubSpot, agree on the onboarding milestones and the information sales must pass to CS before configuring anything. The steps below assume Professional-level workflow access.
1. Define the stages and what "done" means
Define the stages and what must happen before an onboarding can move forward. A typical B2B process goes from handoff received to kickoff, configuration, training, first value and account management. These labels only help if each has an exit criterion. For example, a kickoff isn't complete until the customer and CSM agree on a success plan and record it.
Define "first value" in terms the customer would recognize, such as first report delivered, first live integration or first team trained. It becomes the milestone you measure onboarding against.
2. Decide what sales must hand over
Decide what CS needs to know before sales marks a deal closed won, and make those fields required. They typically include the executive sponsor, day-to-day contact, products sold, promised go-live date, customer goals and commitments made during the sale. Without that information, even a well-built pipeline leaves the CSM chasing sales for context.
If your team qualifies with SPICED, the handoff fields map cleanly: the customer's Situation, Pain, Impact, Critical Event and Decision. A Critical Event, such as a renewal of the old system or a board deadline, tells onboarding which date actually matters to the customer.
HubSpot is also testing a beta called Automated Sales to CS Handoff, which generates an AI summary of key contacts, goals and concerns in the Customer Success Workspace. It is opt-in, so treat it as a supplement to required fields, not a replacement.
3. Build the onboarding pipeline
Build a pipeline on your chosen object using the stages you've defined. Mark stages as open or closed so completed onboardings don't clutter active views, and use pipeline rules where available to prevent stages from being skipped.
4. Create the onboarding record automatically from closed won
Set up a deal-based workflow triggered by closed won, then use Create record to generate the project, service, ticket or custom object record you've chosen. Ticket creation requires Service Hub Professional or Enterprise, and custom objects require Enterprise. HubSpot's workflow guide also describes how to:
- Copy deal properties to the new record, such as the go-live date or products sold, as long as the field types are compatible.
- Keep the association to the deal, which HubSpot adds by default, and add the deal's company and contacts with "+ Add another association".
- Copy timeline activity from the deal, which defaults to the last 30 days, so the onboarding team sees the recent conversation history.
- Check the owner. The new record can default to the sales rep who owned the deal, so assign the onboarding owner or use a rotation instead.
Test the workflow on a test deal before you turn it on, and make sure one closed won deal creates exactly one onboarding record.
5. Automate the work inside each stage
Use stage-based automation or workflows to assign tasks, notify the right people and update properties as onboarding progresses. Entering "Kickoff", for example, could create a task for the CSM, while reaching "First value" could alert the account manager.
6. Guide the kickoff with a playbook
Use a playbook to guide the kickoff and log answers on the customer record. That helps CSMs follow a consistent process while confirming the context supplied by sales, rather than making customers repeat their earlier conversations.
7. Set up health scores and the workspace
In the Customer Success Workspace, build a health score from the signals that predict trouble during onboarding, such as missed meetings, open support tickets, low product engagement or CSM sentiment. HubSpot creates Health score and Health status properties automatically, and the workspace shows an alert when a customer's health status changes. Alerts expire after 14 days.
8. Ask for feedback at the end
Send a short survey when onboarding closes, while the experience is fresh, and route poor scores to the CS lead.
Example: a B2B SaaS onboarding project
This is an illustrative setup, not a documented client result. It shows how the steps above fit together on a newer account using the Projects object.
| Setting | Example |
|---|---|
| Trigger | Deal moves to closed won with every required handoff field filled |
| Record | A new project, associated with the deal, the company and the main contacts |
| Handoff | The CSM receives the products sold, goals, sponsor and promised go-live date, copied from the deal |
| Stages | Handoff, Kickoff, Configuration, First value, Complete |
| Automation | Each stage creates the next task for the right owner |
| Success measure | Days from closed won to first value |
Planning how onboarding fits the full customer journey?
Our free Bowtie Funnel and Buyer Journey Template lays out the bowtie and the buyer journey stages, so you can see where onboarding sits between the sale and expansion.
Customer onboarding metrics to track in HubSpot
To measure customer onboarding in HubSpot, track customer progress, not just completed tasks. Bain found that net revenue retention fell for 75% of the software companies it surveyed, even as nearly 60% increased customer success spending. That doesn't prove onboarding caused the decline, but it reinforces why teams should measure whether their work helps customers reach value. Put these metrics in the reports leadership already uses.
| Metric | How to track it in HubSpot | What it tells you |
|---|---|---|
| Time to first value | Date property set when the record reaches "First value reached", compared with the closed won date | How quickly customers reach the outcome they bought |
| Handoff completeness | Share of closed won deals with every required handoff field filled | Whether onboarding gets what it needs to start without chasing sales |
| Time in each stage | Pipeline stage duration reports on the onboarding object | Where onboarding stalls, and whether the delay sits with the customer or your team |
| Onboardings at risk | Health status at day 30, 60 and 90 | Which accounts need help before renewal is in sight |
| Onboarding feedback | Survey responses on the onboarding record | How customers rate the experience, in their own words |
| Early retention | Renewal and expansion outcomes compared by onboarding completion and time to first value, over at least one renewal cycle | Whether customers who finish onboarding well actually stay and grow |
As renewal data accumulates, compare retention and expansion across customers with different onboarding outcomes. If faster time to first value aligns with stronger retention, your milestone may be meaningful. If it doesn't, revisit the definition and consider differences between customer segments before drawing conclusions.
What to test before launching customer onboarding in HubSpot
Run each scenario on test records before the first real customer enters the pipeline.
| Test | What to check | Why it matters |
|---|---|---|
| Closed won trigger | One closed won deal creates exactly one onboarding record | Catches duplicate records and enrollment loops |
| Copied properties | Go-live date, products and goals arrive on the new record | Confirms the handoff data actually transfers |
| Associations | The record links to the deal, company and the right contacts | Lets CSMs see the full account history in one place |
| Ownership | The onboarding owner is assigned, not the sales rep | Stops new customers waiting for the wrong person |
| Stage tasks | Entering each stage creates the right task for the right person | Shows whether automation follows the process you defined |
| Workspace visibility | The onboarding appears in the Customer Success Workspace | Confirms you chose an object your account can use there |
| Reporting | Onboarding records stay out of support and sales reports | Keeps ticket volumes and deal counts accurate |
Common customer onboarding mistakes in HubSpot
Running onboarding in the sales pipeline
Moving won deals into an onboarding stage, or adding onboarding stages to the sales pipeline, mixes two jobs in one record. Forecasts, win rates and deal counts become harder to trust, and deal-based workflows start firing on customers.
Mixing onboarding with support tickets
If you use tickets for onboarding, keep them in a separate pipeline. Otherwise onboarding work can distort support volume and response-time reporting, making it harder to assess the service team's actual workload.
Trusting data nobody checks
Even a well-designed health score can mislead a CSM if the underlying data isn't maintained. Validity's 2025 State of CRM Data Management report found that 76% of CRM users said less than half of their organization's CRM data was accurate and complete. Give someone ownership of onboarding data and review incomplete handoffs regularly.
Treating training as the finish line
A training session is not the end of onboarding. Onboarding is finished when the customer has reached the first value you defined together and their team can handle the next problem without you.
How Elefante RevOps helps with customer onboarding in HubSpot
We help B2B companies with $10 million to $500 million in revenue build onboarding and customer success processes in HubSpot. As a HubSpot Diamond Partner, we account for the features and object restrictions in each portal instead of forcing every team into the same setup.
Our customer success enablement work uses Winning by Design's SPICED framework to connect what customers expected during the sale with what they need after signing. We help teams track progress toward first value, identify accounts that need attention and build consistent processes for onboarding and renewals.
For Synthflow AI, a Berlin-based AI phone agent company that grew to 60 people in under two years, we launched Sales Hub, Marketing Hub and Service Hub Professional together. The Service Hub build included a ticket pipeline with custom stages, feedback surveys, SLAs and a dedicated team inbox, and the same project rebuilt lead qualification, deal progression and the customer handoff. Read the Synthflow case study.
We begin with a 45-minute assessment and a written, fixed-price scope. Together, we define the stages, handoff fields and exit criteria before building in two-week sprints, with documentation your team can use afterward. If you're setting up Service Hub for the first time, our HubSpot implementation services cover the broader rollout.
Losing new customers between sales and success?
Book a call with our team to map your onboarding stages, handoff fields and health signals before you build them in HubSpot.
FAQ
Can HubSpot be used for customer onboarding?
Yes. HubSpot has no ready-made onboarding process, but you can run customer onboarding with the Projects object, the Services object, a ticket pipeline or a custom object, created automatically when a deal closes. Service Hub Professional adds the Customer Success Workspace, health scores, feedback surveys and the customer portal.
Should onboarding be a deal pipeline or a ticket pipeline?
Keep onboarding out of the deal pipeline. Onboarding records in a deal pipeline inflate deal counts and interfere with deal-based workflows and forecasts. Use a separate record instead. For accounts created on or after December 1, 2025, the Projects object or a custom object is usually the better choice, because those are the only objects the Customer Success Workspace can use on those accounts.
How do I create an onboarding ticket automatically when a deal is closed won?
Build a deal-based workflow that enrolls deals when they reach closed won, then add the Create record action and choose ticket. Set the ticket name, pipeline and status, copy the deal properties you need and add associations to the deal's company and contacts. Creating tickets with workflows needs Service Hub Professional or Enterprise.
How do I track customer onboarding progress in HubSpot?
Give onboarding its own pipeline with a stage for each step, then report on stage duration, time to first value and the share of onboardings at risk. On Service Hub Professional, the Customer Success Workspace shows each CSM's customers, projects, tasks, health score alerts and dashboards in one view.
Does HubSpot have customer health scores?
Yes. Health scores are part of the Customer Success Workspace in Service Hub Professional and Enterprise, and creating one needs a Service seat. You build a score from groups of events or properties, set thresholds with labels, and HubSpot creates Health score and Health status properties automatically. Multiple scores need Enterprise.
How do I hand off a customer from sales to customer success in HubSpot?
Define the fields onboarding needs, such as the sponsor, products sold, promised go-live date and customer goals, and make them required at closed won. Then use a workflow to create the onboarding record, copy those properties across and associate the deal, company and contacts, so the customer success team starts with the full context.
What is the difference between HubSpot onboarding and customer onboarding in HubSpot?
HubSpot onboarding usually means setting up HubSpot for your own team, often with HubSpot or a partner. Customer onboarding in HubSpot means using HubSpot to onboard your own customers after they buy from you, with pipelines, automation and health tracking.