# Client onboarding process: what sales must record in HubSpot before the deal moves to Closed Won

https://salesbond.app/blog/hubspot-closed-won-onboarding-handoff/
Published: 2026-10-20 · Updated: 2026-10-26

A client onboarding process works when sales hands over everything the customer already said: who the contacts are, what was promised, the scope and the dates. In HubSpot that means a short set of deal properties required at the Closed Won stage and, if you run onboarding in HubSpot too, a ticket in an onboarding pipeline created from the deal.

Below: the twelve properties, the setting that makes HubSpot ask for four of them, and the line where the deal stops and the ticket starts.

## Where onboarding really starts (before the signature)

Most client onboarding guides begin on signing day: welcome email, kickoff call, training. From the sales side, the process started three weeks earlier, on the second call, when the customer said two people in finance will use the product daily and it has to be live before their fiscal year turns over in February.

If that sentence lives in the rep’s head, onboarding starts from zero.

Sit in on a kickoff call and count the questions the customer has already answered: who the day-to-day contact is, which modules they bought, when they need to be live, what the rep agreed to that is not in the contract. The customer rarely complains about being asked again. They just quietly lower their opinion of how well your company talks to itself.

We think the handoff is a sales deliverable, not a courtesy. The rep is the only person who heard the whole story, and Closed Won is the last moment anyone can ask for it without chasing. So we treat Closed Won as a gate with a form. We wrote the [Pipedrive version of that gate](https://salesbond.app/blog/closed-won-handoff-pipedrive/) earlier; in HubSpot the parts are deal properties, conditional stage properties and tickets with their own pipelines.

## Sales-to-onboarding handoff: the deal properties

Here is the list we would put on a deal before it is allowed to win. Four are HubSpot default deal properties ( [HubSpot: default deal properties](https://knowledge.hubspot.com/properties/hubspots-default-deal-properties)). The other eight are custom properties you create yourself; HubSpot does not ship them, and the names are ours, so use whatever your team actually says on a call.

Who:

- **Deal owner** (default). Stays the rep, even after the win.
- **Day-to-day contact.** A person at the customer; on Professional or Enterprise use an association label on the contact ( [HubSpot: associate records](https://knowledge.hubspot.com/records/associate-records) ), below that a single-line text property.
- **Executive sponsor.** Same mechanics, for the person who approved the budget.
- **Onboarding owner.** A HubSpot user property, set before the win so the customer never belongs to nobody.

When:

- **Close date** (default). HubSpot sets it to today’s date when the deal moves into a closed stage, unless you turn that automation off in pipeline settings.
- **Target go-live date.** A date picker, because a date you can filter on is a date you can report on.

What:

- **Deal type** (default), New Business or Existing Business.
- **Scope purchased.** Multiple checkboxes for modules or tiers, plus a number property for seats if that matters.
- **Promised during the sale.** Multi-line text for the custom report, the extra training session, the integration “we’ll sort out”; onboarding reads this one first.
- **Data and integrations.** Multiple checkboxes for the systems the customer named.

What to watch:

- **Known risks.** Multi-line text, often empty: “Champion leaves in March”, “procurement still reviewing the DPA”.
- **Closed won reason** (default). Not for onboarding as such, but this is the only moment anyone fills it in.

![Diagram: twelve deal properties in four groups, with an arrow to the ticket "Onboarding: Acme Ltd" at Kickoff scheduled](https://salesbond.app/wp-content/uploads/2026/10/hubspot-closed-won-onboarding-handoff-2.png)

Twelve looks like a lot. In practice the rep fills in five during the sale, and the Closed Won form catches the rest. The other side of the same idea is the [closed lost reason](https://salesbond.app/blog/hubspot-closed-lost-reason/), a required dropdown that shows why HubSpot deals are lost.

## Required properties at the Closed Won stage

Require four of the twelve: Day-to-day contact, Target go-live date, Scope purchased and Onboarding owner. Those are the ones the onboarding owner cannot start without. Add Promised during the sale if your contracts are loose, and leave Known risks optional (but read it anyway).

Don’t require all twelve. A form with twelve blanks at the moment of winning teaches reps to type “TBC” into every one.

The setting is called conditional stage properties, and you need Edit property settings permissions. Go to Settings, then Data Management, then Objects, select Deals, open the Pipelines tab and click the pipeline. In the Closed Won row, hover over the Conditional logic rules column and click **Add rule**. Add the four properties under Dependent properties, select the **Required** checkbox for each, and click **Save logic** ( [HubSpot: set up and customize pipelines](https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines)). From then on a user who moves a deal into Closed Won by hand can’t save it until those properties have values.

The caveat is in the words “by hand”. The form appears when a user manually creates a deal in the stage or moves one into it, so deals that reach Closed Won some other way can skip it. We went through where the rule does and does not reach in [required properties at a HubSpot deal stage](https://salesbond.app/blog/hubspot-stage-required-properties/). The short version: add Record Source as a column to your Closed Won view and look at any deal that did not arrive by hand.

## Deal to ticket: an onboarding pipeline for a small team

There is no ready-made onboarding pipeline. Tickets come with a default Support Pipeline and four statuses (New, Waiting on contact, Waiting on us, Closed), and ticket stages are called statuses by default. An onboarding pipeline is one you build, which needs a Starter, Professional or Enterprise subscription ( [HubSpot: set up and customize pipelines](https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines)).

The build, for a team of two to eight people:

1. **Create a ticket pipeline named Onboarding.** Statuses are delivery phases, not support states: Kickoff scheduled, Data loaded, Users trained, Live and a closed status. If you can’t say what happens in a status, you don’t need it.
2. **Decide what crosses from deal to ticket.** Default ticket properties include Ticket name, Ticket description, Pipeline, Ticket status, Owner and Priority ( [HubSpot: default ticket properties](https://knowledge.hubspot.com/properties/hubspots-default-ticket-properties) ). Scope purchased, Promised during the sale and Known risks go into Ticket description, in that order, and the Onboarding owner becomes Owner. Give the go-live date its own custom date property on the ticket so the board can be sorted by it.
3. **Create the ticket at Closed Won.** By hand: open the won deal, go to the Tickets card in the right sidebar, click the Create new tab and fill it in, and the ticket is associated with the deal from the start ( [HubSpot: associate records](https://knowledge.hubspot.com/records/associate-records) ). By workflow: a deal-based workflow with a Create record action, where “by default, records created by a workflow will be associated with the record that was enrolled in the workflow”. You set the pipeline and status in the action, assign the deal’s existing owner, a specific user or no one, and copy deal properties into ticket properties as long as their field types are compatible ( [HubSpot: create records with workflows](https://knowledge.hubspot.com/workflows/create-records-with-workflows) ).
4. **Check the subscription before you promise automation.** Workflows need a Professional or Enterprise tier of Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM or Revenue Hub ( [HubSpot: create workflows](https://knowledge.hubspot.com/workflows/create-workflows) ). Creating tickets with the Create record action is Service Hub Professional and Enterprise only ( [HubSpot: choose your workflow actions](https://knowledge.hubspot.com/workflows/choose-your-workflow-actions) ). So a team on Sales Hub Professional alone creates the ticket by hand, which is quick precisely because the deal is already filled in.
5. **Draw the boundary.** The deal holds what was sold and is not edited after Closed Won. The ticket holds what is being delivered and changes every day; when someone wants to “update the deal” with progress, the answer is the ticket.

If you are weighing workflows against sequences for the sales side, we compared them in [HubSpot workflows vs sequences for a sales manager](https://salesbond.app/blog/hubspot-workflows-vs-sequences-sales-manager/).

## Who owns what in the first 30 days

Two records, two owners, even when its the same person. The deal owner answers one question in the first month: what did we promise? The ticket owner answers the other: where are we against the go-live date? The rep books one check-in call for the second week before the win and answers fast when asked “did we agree to the custom report?”, and the onboarding owner keeps the status honest. A ticket sitting in Kickoff scheduled for three weeks is information. So is a failed first payment, which we covered in [failed payments and renewals at risk](https://salesbond.app/blog/failed-payment-subscription-renewal-at-risk-hubspot/).

## Weekly check: won deals with an empty handoff

Required properties catch the deal at the door. The weekly check catches what got through anyway, “TBC” included.

Build one saved view on the Deals index: Deal stage is Closed won, Close date in the last 30 days, with Day-to-day contact, Target go-live date, Scope purchased, Onboarding owner and Promised during the sale as columns. Sort by Close date. Any blank cell, or one that reads like a placeholder, is a two-minute conversation with the rep on Monday while they still remember the customer. Then switch to the Onboarding ticket pipeline and look for tickets that have not changed status since the the week before.

A disclosure, since this is where a tool would help: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It reads deal fields and flags the deals that need attention, which is one way to get that Monday list without maintaining the view yourself. The saved view is the free version of the same habit. [Check your CRM with SalesBond](https://salesbond.app/) if you want the list waiting for you.

## When onboarding outgrows a HubSpot pipeline

A ticket is one card with one status. That is enough when onboarding means four or five things done by one or two people over a few weeks. It stops being enough at fifteen tasks across three people with dependencies, when the ticket says Data loaded and nobody can tell which data task is stuck. The signs are easy to spot: a spreadsheet next to the ticket, a checklist growing in the description, two onboarding owners asking each other in chat what’s done.

Then move delivery into a project tool your team already pays for and keep the ticket as the one-line status sales and management look at; we built that version in [a client onboarding checklist in Pipedrive Projects](https://salesbond.app/blog/pipedrive-projects-client-onboarding-checklist/). The deal doesn’t move, though. Wherever delivery lives, the properties on the deal at Closed Won are what it opens first. So set up the required-property form this week, and let the pipeline wait until the first customer has gone live without being asked thier go-live date twice.