Open the deals board of a sales team six months after a HubSpot rollout and the picture is often the same. The first stage is crowded with deals nobody has touched. Close dates sit in last quarter. One rep’s pipeline looks suspiciously small, because the real one lives in a spreadsheet. Nobody decided to use the CRM badly. They got a login, a one-hour demo and a quota, and each of them invented a way of working.
This HubSpot onboarding checklist is for the head of sales or founder who wants to avoid that picture, or who has to re-onboard a team that is already in it. It covers the first 30 days, week by week: what the admin prepares, what every rep must be able to do, what the manager inspects, and how to tell at day 30 whether adoption is real.
HubSpot onboarding checklist, before day 1: what the admin prepares
Reps should never log in to a half-configured portal. Everything in this list is finished before the invites go out.
- Write stage definitions before you touch settings. For every deal stage, write one sentence that says what must be true for a deal to be there, in the buyer’s terms. “Buyer confirmed budget and timeline” is a definition. “Proposal” is not. Then build the stages under Settings, Objects, select Deals, Pipelines tab. HubSpot’s pipeline guide notes that the default sales pipeline has seven stages, and that you must keep both a Won and a Lost stage for sales reports to work correctly.
- Keep required properties minimal. On the same Pipelines tab you can attach conditional stage properties to a stage and tick Required. HubSpot is clear about the effect: a user cannot create or update the record until the value is set. Our rule is two or three per stage, and only ones somebody will read. Every extra required field teaches reps to type junk to get past the form.
- Build the views reps will live in. Create saved views on the deals index page, for example “My open deals”, “My deals with no next activity” and “Closing this month”. By default a view is private to its creator and Super Admins, so open the view settings, click Manage sharing and share it with the team or with everyone.
- Set permissions and teams. In user permissions, on the CRM tab, view and edit access for each object can be set to all records, the user’s team’s records or only their own. Bulk delete is a separate switch, and we leave it off for reps. Teams are created under Settings, Users & Teams, Teams tab, and HubSpot lists them as a Professional and Enterprise feature.
- Decide email logging once, for everyone. Under Settings, Objects, select Activities, the Email Log & Track tab lets an admin with account access permissions apply a default log setting for all users. HubSpot also lets you list addresses and domains that should never be logged. Add sensitive ones, such as legal and HR, before the first rep connects an inbox.
- Write a one-page “how we use HubSpot”. Stage definitions, required fields and the rule about next steps. This is what a new hire gets later, when nobody remembers the kickoff.
Week 1: connect the tools and move real deals in
The first session is hands-on, on each rep’s own laptop, with their own deals. By Friday every rep has done the following.
- Connected their individual work email under Settings, General, Email tab, Connect email account. HubSpot’s connection guide says the address should be unique to the user, so no shared mailboxes, and that users on a View-Only seat cannot connect an inbox at all.
- Connected their calendar under Settings, General, Calendar tab. Two details from HubSpot’s calendar sync article are worth telling reps up front: only the primary calendar syncs, and events created before the connection do not appear in HubSpot.
- Installed the inbox extension. For Gmail that is the HubSpot Sales Chrome extension, which tracks and logs emails sent from the inbox. For Outlook, HubSpot offers an Office 365 add-in and a desktop add-in.
- Installed the HubSpot mobile app and logged in. HubSpot lists iOS 17 or later and Android 10 and above as supported.
- Moved every live deal into HubSpot with an amount, a close date and the correct stage. The old spreadsheet gets an archive date, and the date is announced.
What the manager inspects: open a few contact records per rep and confirm that emails and meetings appear on the timeline. Then announce the rule that carries the rollout: from week 2, pipeline reviews run from the HubSpot board and nothing else.
Week 2: build the daily habit
Week 2 is where enthusiasm dips. Logging feels like extra work until reps get something back, so keep the list of skills short.
- Log what happened outside HubSpot. A call from a personal phone, a LinkedIn message, an unplanned meeting. HubSpot supports logging these on the record by hand.
- Create a task with a due date and associate it with the deal. Task defaults for due date, due time and reminder can be set once under Profile & Preferences, Tasks tab.
- Move a deal to the next stage and fill the required properties without asking anyone what they mean.
- Start the day from the saved view, not from the inbox.
The one rule we push hardest: no open deal without a dated next step. HubSpot maintains a deal property called Next activity date, which its deal property reference describes as set automatically from upcoming activity such as a scheduled meeting. A deal where it is empty is a deal nobody plans to touch.
What the manager inspects: run the first pipeline review and every one-to-one from the rep’s own saved view. When a deal sits in the wrong stage, reread the definition together instead of fixing it silently. Keep a friction list of fields reps complain about, and have the admin act on it within days. The payoff reps notice first: the manager stops asking for status updates in chat, because the record already answers.
Weeks 3-4: inspect, fix and remove
By now the portal shows how the team really works, and some of the setup will turn out to be wrong. That is normal. Correct it while the habit is still forming.
- Admin: remove or un-require properties nobody fills honestly, fix the views, clear the friction list. Look for a wall of identical month-end close dates. HubSpot sets the close date to the last day of the month when a deal is created in an open stage without one, so those dates were never chosen by anyone.
- Reps: by day 30 each rep can forecast from their own pipeline. That means close dates they believe, real amounts, and dead deals moved to Closed lost instead of left to age.
- Manager: the weekly review uses the same shared views every time. Run a second, shorter training session built only from mistakes found in the portal.
Day 30 adoption checks
Login counts say nothing. Adoption shows up in the deals, and these five checks read it directly.
| Check | Where to look | Healthy sign |
|---|---|---|
| Open deals have a next activity | Deals view with the Next activity date column, filtered to open deals where it is empty |
Short list, and every deal on it has an explanation |
| Close dates are not in the past | Deals view filtered to open deals with Close date before today |
Empty, or cleared in every weekly review |
| Activities are logged | Last activity date column on open deals, then a few record timelines |
Recent dates across all reps, not just one or two |
| Stages match reality | Five deals per rep, compared against the written stage definitions | Most match, and mismatches are discussed openly |
| No shadow pipeline | The forecast conversation itself | Every deal named in the meeting exists in HubSpot |
If two or more checks fail, do not add features, automation or another hub. Repeat week 2.
Our take
Onboarding is where most of the value of a CRM is lost, and it is rarely lost in the software. The tool side of this checklist is modest admin work. By HubSpot’s own documentation, inbox and calendar connection, saved views, the mobile app and the Chrome extension are available on all products and plans. You are unlikely to need a new purchase to do this well.
The hard parts are the two that are not settings. First, the stage definitions. If leadership cannot agree on what “qualified” means, that is a process problem, and no portal will hide it. Second, the manager’s discipline. Reps use what their manager inspects. If the review still happens from a spreadsheet in week 3, the rollout is over.
So the honest question before kickoff is who owns the 30 days and how many hours they have. It should be one named person with time blocked every week. If nobody has those hours this month, delay the rollout. Repairing a badly adopted portal costs more than starting four weeks later. If you want the setup and the sessions run for you, that is what our HubSpot implementation work covers.
FAQ
How long does it take to onboard a sales team on HubSpot?
Plan for 30 days. For a single pipeline the configuration is the short part. The rest of the month is for habit: reps logging activity and keeping next steps current, and a manager checking every week.
What fields should be required on a HubSpot deal?
As few as you can defend. Amount and close date on every deal, plus two or three conditional stage properties at the stages where the information becomes known.
How do I know if my sales reps are actually using HubSpot?
Look at deals, not logins. Open deals should have a next activity date, close dates should not be in the past, and last activity dates should be recent for every rep. The table above lists all five checks.
Can we re-onboard a team that already uses HubSpot badly?
Yes, and the 30-day plan is the same. The difference is the step before it: close out dead deals, fix the stage definitions and cut the required fields, so reps restart from a board that is true. Our HubSpot audit checklist is a reasonable place to start that cleanup.
This week, do one thing: write your stage definitions on a single page and put the week 1 hands-on session in the team’s calendar. If the definitions take more than an hour to agree on, you have found the real work, and it is better to find it now than at day 30.
Related reading
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.