Can You Run Customer Onboarding in HubSpot? (2026)
Yes, with limits. HubSpot's Projects object, deal-to-project workflows, the customer success workspace, and the Onboarding Plans beta can run a linear onboarding pipeline, but every piece that automates it requires Service Hub Professional at $90 per seat per month billed annually plus a $1,500 setup fee. It fits teams already on that tier running fewer than about five concurrent, mostly internal onboardings. It breaks when customers own the tasks, projects run out of stage order, or everyone who needs visibility needs a paid seat.
Yes, you can run customer onboarding in HubSpot, and in 2026 it is a better fit than it used to be: the Projects object, deal-to-project workflows, the customer success workspace, and a new Onboarding Plans beta give you a real project pipeline inside the CRM. The catch is where those pieces sit. Workflows, pipeline rules, the customer success workspace, and Onboarding Plans all require Service Hub Professional, which starts at $90 per seat per month billed annually plus a $1,500 setup fee. And even fully configured, HubSpot tracks the stage a project is in, not the work the customer still owes you.
The practical rule: HubSpot is the right onboarding tool when you already pay for Service Hub Professional, you run fewer than about five concurrent onboardings, the process is linear, and most of the work is on your side. It stops being the right tool when customers own tasks, when projects run out of stage order, or when everyone who touches a project needs a paid seat to see it. This guide covers what HubSpot gives you, what it costs, how to set it up, where it breaks, and how it compares to dedicated onboarding software and to running the work in Slack.
Can you run customer onboarding in HubSpot?
You can, and for a specific kind of team you should. Three conditions make HubSpot the right call:
- You already have Service Hub Professional or Enterprise. The features that make onboarding workable are gated there. If your only paid hub is Sales Hub, you are looking at a second subscription, and at that point the comparison with dedicated tools is a fair fight.
- Onboarding is short, linear, and mostly internal. A pipeline stage is one state. It works when a project moves kickoff, configuration, training, go-live in that order and your team does most of the configuring.
- Your team is small enough that seats are cheap. Two or three implementers on Professional is a few thousand dollars a year. Fifteen implementers plus solutions engineers plus executives who want visibility is a different conversation.
Three conditions push you the other way:
- The customer owns a large share of the tasks. Data exports, credentials, SSO configuration, UAT sign-off. HubSpot has no customer-facing task list for onboarding; its customer portal exists for support tickets and a knowledge base.
- Projects run in parallel workstreams. Data migration and training happening at the same time do not map to a single stage, and the pipeline rule that stops projects skipping stages makes it worse.
- The real record lives in Slack and on calls. If decisions, blockers, and commitments are made in customer channels and kickoff calls, HubSpot only knows about them when someone types them in. The HubSpot Slack app helps at the edges; it does not read the channel for you.
The rest of this guide shows how to tell which side you are on, with 2026 numbers.
What does HubSpot actually give you for onboarding in 2026?
More than most teams realize, and most of it arrived recently. Here is the inventory, with the minimum tier each piece needs.
| Building block | What it does for onboarding | Minimum tier |
|---|---|---|
| Projects object | A first-class CRM record for a delivery project, with its own pipelines, properties, tags, and associations to deals, contacts, and tasks. Activated from Data Management > Data Model. | All plans; project tags need Starter; pipeline rules need Professional |
| Deal-based workflow that creates a project | When a deal hits Closed Won, HubSpot creates the project record automatically with the deal owner and dates carried across. | Professional (workflows) |
| Customer success workspace | A dedicated view for CSMs with Customers, Projects, and Revenue tabs, health scores, and up to five pinned dashboards. One workspace on Professional, up to five on Enterprise. | Service Hub Professional, with an assigned Service seat |
| Onboarding Plans (beta, May 2026) | A default "Onboarding" project pipeline, a "Service - Onboarding" project type, and five out-of-the-box reports: projects per stage, time in each stage, planned versus actual timeline, status distribution, engagement distribution. | Service Hub Professional or Enterprise |
| Gantt index view (beta) | Timeline view of projects and their tasks. | Only Free and Starter accounts created after March 30, 2026, enrolled in the Streamlined Index public beta |
| Slack integration | Create a HubSpot task, ticket, or note from any Slack message; search records with slash commands; link previews for records. | All plans |
| Custom objects | Model anything the standard objects do not cover, such as a "Deliverable" the customer owes you. | Enterprise only |
The Projects object is the piece that changed the calculation. HubSpot's own projects documentation walks through exactly the onboarding use case: a company whose sales team had been tracking delivery in a post-Closed-Won deal stage, which "created issues with data quality", moves that work into a dedicated project pipeline with stages for kickoff and final sign-off, restricts projects from skipping stages, and builds a quarterly report on average time in each stage by owner. That is a workable onboarding tracker, and two years ago it did not exist in the product.
The customer success workspace is where the projects become visible to the people who care. You choose which object represents customers (contacts, companies, or on Enterprise a custom object), which represents projects, and which represents revenue, then CSMs get a single screen with their accounts, their projects filtered by pipeline, and a health score. Onboarding Plans, announced as a beta in a HubSpot product update in May 2026, layers a standard onboarding pipeline and five reports on top of that, so a Professional account no longer has to build "time in stage" reporting by hand.
How much does running onboarding in HubSpot cost?
For a four-person onboarding team on Service Hub Professional, plan on $5,820 in year one and $4,320 a year after that, before credits or limit increases. That is more than the smallest Rocketlane contract and less than most quote-only tools, and it buys a CRM as well as an onboarding tracker.
The numbers come from HubSpot's Service Hub pricing guide, updated June 30, 2026. HubSpot moved Service Hub to seat-based pricing for new customers on March 5, 2024, so every implementer who needs the workspace needs a paid seat:
| Service Hub tier | Price | Setup fee | What you get for onboarding |
|---|---|---|---|
| Free | $0, up to 2 users | None | Projects object, tasks, ticket pipeline, Slack app. No workflows, no workspace. |
| Starter | From $7 per seat per month, billed annually | None | Adds project tags, multiple ticket pipelines, branding removed. Still no workflows. |
| Professional | From $90 per seat per month billed annually ($100 monthly) | $1,500 | Workflows, pipeline rules, customer success workspace, health scores, Onboarding Plans beta, customer portal for tickets, 3,000 HubSpot Credits. |
| Enterprise | From $150 per seat per month | $3,500 | Adds custom objects, up to five CS workspaces, conditional SLAs, journey analytics, 5,000 credits. |
Worked examples for the same four-person team:
- Professional, annual: 4 seats x $90 x 12 = $4,320, plus the $1,500 setup fee = $5,820 in year one.
- Professional, monthly: 4 x $100 x 12 = $4,800 a year, plus setup.
- Enterprise, because you need a custom "Deliverable" object: 4 x $150 x 12 = $7,200, plus $3,500 = $10,700 in year one.
- Rocketlane Standard, for comparison: $49 per team member per month billed annually with a five-member minimum, so $2,940 a year is the floor, with the HubSpot integration included on that tier. GUIDEcx is quote-only on all three tiers.
Two costs hide behind the seat price. First, seats scale with visibility: the solutions engineer who joins three projects, the VP who wants the dashboard, and the support lead who inherits the account at go-live all need Service seats if they are going to work inside the workspace. Second, HubSpot's own guide lists onboarding, integrations, HubSpot Credits for usage-based features, and paid limit increases as additional costs to budget for. If you are already paying for Sales Hub, the marginal decision is whether the Service seats are worth it, which is a much easier case than buying HubSpot for onboarding from scratch. The customer onboarding software cost guide has the full market picture.
How do you build an onboarding pipeline in HubSpot?
Use the Projects object, not a ticket pipeline and not a post-Closed-Won deal stage. Tickets are built for support conversations and deals are built for revenue; both get misused for onboarding because they were there first. Here is the build, in order:
- Activate Projects. As a Super Admin, go to Data Management > Data Model, find Projects, and click Activate object. Projects then appear under CRM in the navigation.
- Rename the pipeline stages to your milestones. Settings > Objects > Projects > Pipelines. A typical B2B SaaS pipeline is Kickoff scheduled, Configuration, Data migration, Training, UAT, Go-live, Hypercare. Keep it to six or seven stages; you are tracking phases, not tasks.
- Decide whether to restrict stage skipping. HubSpot's pipeline rule "Restrict projects from skipping stages" keeps reporting clean. Turn it on only if your process is truly sequential. If migration and training overlap, leave it off and track the parallel work with tasks.
- Create the deal-to-project workflow. Build a deal-based workflow with the trigger Deal stage is Closed Won and the action Create record > Project. Map deal owner to project owner and close date to project start. The project now exists before anyone on your team has to remember to create it.
- Add task templates per stage. Tasks associated to the project carry the internal checklist. HubSpot is testing subtasks with projects in beta, which helps for anything with more than one level.
- Configure the customer success workspace. Set Projects as the project object, pick the onboarding pipeline as the default, and choose the user property that represents project ownership. Add one dashboard with time-in-stage and projects-per-stage reports.
- Connect Slack. Once connected, anyone on your team can hover over a customer message in Slack, click the three-dot menu, and create a HubSpot task or note from it. Note the limits in HubSpot's Slack documentation: it only works in public channels or private channels where the HubSpot app is invited, and the Create a ticket action supports at most 10 fields.
- Build the two reports that matter. Average cumulative time in each stage, by owner, filtered to this quarter; and projects by status (On Track, Delayed, On Hold). If you are on the Onboarding Plans beta, the planned-versus-actual timeline report is the third.
Feed the pipeline properly from the front. The sales to onboarding handoff checklist lists what the deal record should contain before the workflow fires, and the customer onboarding plan template covers what each stage should mean.
Where does HubSpot break down for onboarding?
It breaks at the same four places every CRM does: non-linear work, customer-owned work, seat economics, and the gap between what happened and what got typed in.
Onboarding is not a pipeline
A June 2024 thread on the HubSpot community, still active in 2026, describes the problem exactly. An onboarding lead using Service Hub wrote that their clients do not complete onboarding steps in order, sometimes never finish all of them, and would "flip back and forth between stages", so the pipeline could not tell them which steps were actually done. Their proposed fix was to collapse the pipeline to In Progress and Complete and track everything else as tasks. That is the honest end state for most teams: the pipeline becomes a status label and the real tracking happens somewhere else.
The customer's work has nowhere to live
Every task in HubSpot is an internal task. The customer portal in Service Hub Professional is a place for customers to view and reply to support tickets. There is no shared plan where the customer's IT lead sees "SSO metadata due Thursday" with their name on it. So the customer-owned deliverables, which are the ones that slip, get chased by email and logged after the fact. GUIDEcx's State of Customer Onboarding 2026, a survey of 200 B2B onboarding professionals run April to June 2026, found that 48% call keeping customers engaged their biggest challenge and 62% have lost at least one customer to a poor onboarding experience. The same report notes that most teams, even those with dedicated onboarding software, still piece the process together across CRMs, email, spreadsheets, and project tools. HubSpot alone does not close that gap; it is one of the pieces. The customer deliverables tracking guide covers what does.
Seats scale with visibility
The workspace is the useful part, and it needs a Service seat per person. That is fine for three implementers. It is a budget line when the solutions engineers, the support lead, the account executives who want to see their deals delivered, and the CEO all want in. Most teams solve this by exporting a dashboard to a weekly email, which puts you back to writing status updates by hand.
Reporting on stages is not reporting on risk
Time in stage tells you a project is slow. It does not tell you why: the customer's data lead went on leave, the integration scope grew on a call nobody summarized, the champion changed. Only 9% of onboarding teams say they have real-time visibility into the health of their portfolio, and stage reporting is a big reason the other 91% think they do. The onboarding health score guide explains what a risk signal looks like when it is built from evidence rather than from a stage field.
Sales owns the CRM
Every property, pipeline, and workflow you add is a negotiation with RevOps, and the reporting you build competes for attention with pipeline reviews. HubSpot's own documentation example started from delivery work polluting deal data. Moving to a projects pipeline fixes the data, but not the ownership question. That is part of why Zylo's 2026 SaaS Management Index finds business units now control 81% of SaaS spend: teams whose work does not fit the central system buy their own tool. The same report finds 36% of licenses go unused, which is the risk on the other side of that purchase.
What about Salesforce?
The same logic applies with higher prices and less out of the box. Salesforce's Service pricing page, as of September 2026, lists Starter Suite at $25, Pro Suite at $100 (billed annually, contract required), Core at $195, Advanced at $395, and Max at $550 per user per month. Service Cloud has no standard project object for post-sale delivery the way HubSpot now does, so onboarding in Salesforce usually means one of three things: an admin builds custom objects and flows, you buy a Salesforce-native delivery app such as Precursive, or you sync an external tool through the AppExchange.
The integration tiers tell you how vendors see the two CRMs. Rocketlane includes its HubSpot integration on the $49 Standard tier and its Salesforce integration on the $69 Premium tier. Rocketlane's HubSpot integration is a good model for what a CRM should do in onboarding regardless of which tool runs the project: a deal-based workflow fires on Closed Won or Contract Sent, creates the project from a template with the deal name, owner, and close date mapped in, and syncs fields both ways afterwards. The CRM stays the system of record for the account; the project runs where projects run.
HubSpot vs dedicated onboarding software: how do you choose?
Choose on three questions: where does the customer do their part, how linear is the work, and who keeps the record current. Here is how the options line up for a team of four implementers.
| Question | HubSpot Service Hub Pro | Rocketlane or GUIDEcx | Slack-native intelligence layer |
|---|---|---|---|
| Where the customer works | Email and calls; portal is for tickets | Branded customer portal with their tasks | The Slack Connect channel they already use |
| Customer-owned tasks | Internal tasks only | Assigned to customer contacts with reminders | Extracted from messages and calls, tracked as deliverables |
| Non-linear projects | One stage at a time | Task dependencies and parallel phases | Tracks commitments, not stages |
| Year-one cost, 4 implementers | $5,820 (Pro, annual, plus setup) | $2,940 floor (Rocketlane 5-seat minimum); GUIDEcx quote-only | Free plan for one active engagement; Pro $249/mo, no per-user fees |
| Who keeps it current | Your team, by hand | Your team plus customer check-offs | AI reads the channel and transcripts; you confirm |
| Best for | Teams already on Service Hub Pro with short, linear, internal onboardings | Teams with heavy customer-side work and a portal the customer will adopt | Teams whose customer conversations already live in Slack |
A few decision rules that follow from the table:
- If you already pay for Service Hub Professional and run fewer than five onboardings at a time, build the projects pipeline first. It costs nothing extra and you will learn exactly where it falls short before spending on a second tool.
- If customer-side work is the bottleneck and your customers will log into a portal, dedicated software earns its price. The GUIDEcx vs Rocketlane comparison covers that choice.
- If you are choosing between HubSpot and a generic project tool, the Asana, monday.com, and ClickUp guide applies: the same customer-adoption ceiling shows up, just with different guest pricing.
- If you are weighing HubSpot's customer success workspace against a full CS platform, that is a different decision; the CS platform vs onboarding software guide separates the two.
One more data point on the market: Arrows, for years the best-known HubSpot-native onboarding add-on, now describes its pricing as scoped per engagement on the deal work it takes on rather than on seats or onboarding plans. The "just add onboarding to HubSpot" category is thinner than it was, which is one reason HubSpot built Onboarding Plans itself.
A different approach: HubSpot as system of record, Slack as the workspace
Most of the friction above comes from asking a CRM to be the place where onboarding work happens. It does not have to be. Keep HubSpot as the record of the account, the deal, the contacts, and the renewal. Run the project where the conversation already is, and let a tool that reads that conversation keep the record.
That is what Stipulate does. It reads your customer Slack channels and call transcripts and builds a record of every commitment: decisions, risks, blockers, requirements, stakeholders, and open action items, each linked to its source message. Customer deliverables are tracked from the moment a customer says "we'll send the export Friday" rather than from the moment someone creates a task. Leads get a live health read per engagement built from the evidence in the channel, which is the risk signal a stage field cannot give you. The free plan runs one active engagement with every core feature and the full manager dashboard, with no per-user fees, so the solutions engineer and the VP can look without a seat conversation. Pro removes the engagement limit at $249 per month billed annually.
The guide to running customer onboarding in Slack lays out the channel structure that makes this work, and the decision tracking guide covers how commitments stay findable without anyone retyping them into a CRM.
Next steps
If you are on HubSpot today and onboarding is running on deal stages, spreadsheets, or memory, do these in order:
- Check your tier. Free or Starter gets you the Projects object and nothing that automates it. Professional is where onboarding in HubSpot becomes real; price the seats before you design anything.
- Activate Projects and move delivery out of the deal pipeline. Even if you later buy a dedicated tool, cleaning delivery work out of deal data is worth doing now.
- Build the Closed Won workflow. Every project should exist the moment the deal closes, with owner and dates filled in.
- Run five projects through it. Count how many customer-owned tasks you chased by email and how many times a project sat in the wrong stage. Those two numbers tell you whether HubSpot is enough.
- Add the layer you are missing. If the problem is customer-side tasks, look at a portal-based tool. If the problem is that the truth lives in Slack and calls, add an intelligence layer that reads them, and keep HubSpot for what it is good at.