HubSpot Implementation & Onboarding
HubSpot onboarding gets you configured. Implementation gets you a system your team actually uses. They are not the same project.
Book a callHubSpot’s own onboarding is product training. It shows your team where the buttons are, configures the defaults, gets the tracking code live and hands over a working portal. It is competent, and it is not the same project as an implementation.
What it does not do is decide what a qualified opportunity is at your company, who owns a record after the handoff, or what has to be true before a deal moves stage. Those are the decisions that determine whether anyone trusts the pipeline in six months.
That gap is the whole point of a HubSpot CRM implementation: design the revenue process first, then build the portal to encode it. Most implementation services skip to configuration instead, because configuration is easy to quote and process design is not.
HubSpot onboarding vs implementation
These get used interchangeably and they buy you different things. Both can be worth having. Only one of them changes how your company sells.
| HubSpot onboarding | A third-party implementation | |
|---|---|---|
| Sold by | HubSpot, as a fee attached to the licence | A partner, agency or consultant, scoped to the work |
| Covers | Product training, technical setup, default configuration | Revenue process design, then configuration built to it |
| Stage definitions | You bring them | The first two weeks of the engagement |
| Data migration | Guidance on how to import | Done for you — mapped, deduplicated, reconciled |
| Adoption | Enablement sessions | Working in live deals with reps until usage holds |
| Ends with | A configured portal | A documented system with a named internal owner |
If you have already paid for onboarding, none of it is wasted. It covers the product layer properly, and an implementation starts a level above it.
How a HubSpot implementation runs
Stage definitions, exit criteria, ownership at each handoff, and what has to be true before a deal moves. Nothing gets configured yet.
Objects, properties, pipelines, lifecycle stages, automation, permissions and teams — each one mapped to a decision made in the phase above.
Migration, deduplication, reporting, and sitting with reps in their live deals until the portal is the system of record rather than an afterthought.
Documented configuration, a named internal owner and a change process, so the portal does not quietly drift back within two quarters.
The order matters more than the duration. Configuring before the process is defined means building automation around decisions nobody has made yet, and every one of those becomes a rebuild later. Half of what looks like an implementation delay is a decision the business has been deferring for a year and now has to make in week one.
What a HubSpot implementation covers
| Area | What gets done |
|---|---|
| Process design | Stage definitions with exit criteria, ownership, handoff rules |
| Configuration | Objects, properties, pipelines, lifecycle stages, automation, permissions, teams |
| Data migration | Mapping, deduplication, normalisation, owner assignment, closed history |
| Integrations | The systems that must agree with the CRM — billing, quoting, support, finance |
| Reporting | Dashboards finance and sales both trust, built on defined stages |
| Adoption | Working with reps until the portal is the system of record |
| Handover | Documented configuration, so the next person inherits a system rather than a mystery |
The last two are the ones commonly dropped when a project runs late, and they are the two that decide whether the first six weeks survive contact with the sales team.
Which Hubs, and what implementation means in each
Most engagements at this size start with Sales Hub and add one more. The work is different in each, and buying all of them at once is usually how a portal ends up half-configured.
| Hub | What the implementation is actually about |
|---|---|
| Sales Hub | Pipelines, stage exit criteria, quoting, sequences, and forecasting people believe |
| Marketing Hub | Lifecycle stages, lead scoring and routing, and an attribution model sales agrees with |
| Service Hub | Ticket pipelines, SLAs, and the handoff from closed-won into delivery |
| Operations Hub | Two-way sync, deduplication and data quality rules — usually bought after a messy migration, occasionally worth buying before one |
Migrating onto HubSpot
Migration is part of the implementation, not a separate engagement. The work is rarely the import itself — it is deciding what each field means, which record wins on a duplicate, and how much history has to come across for reporting to be comparable year on year.
| Moving from | What tends to break |
|---|---|
| Salesforce | Custom objects and record types with no clean HubSpot equivalent, plus validation rules encoding process nobody ever wrote down |
| Pipedrive or Zoho | Flat deal data with little stage history, so velocity and conversion reporting restarts from zero unless it is reconstructed |
| Spreadsheets | Duplicate companies and free-text owner fields — cheap to fix before import, expensive afterwards |
| Another HubSpot portal | Portal-to-portal moves after an acquisition: associations, workflow dependencies and reporting history do not travel cleanly |
One thing we do not do is website migration onto HubSpot CMS. That is a web build with a different skill set, and pairing it with a CRM migration is how both slip.
Where this sits
If you have not chosen a platform yet, start at CRM consulting. If HubSpot is already in place and the question is what to do about it, that is HubSpot consulting — usually a portal audit first, which tells you whether this is an implementation or a repair.
Where deal approval and non-standard pricing are part of the problem, the implementation needs a deal desk defined alongside it, or the approval logic has nowhere to live. And where the underlying issue is that nobody has defined how the company sells, the honest framing is a revenue operations engagement that happens to end in HubSpot.
Scope an implementation
We map your revenue process first and quote against that, so the number reflects the actual work rather than a per-seat guess.
Book a callCommon questions
- What is the difference between HubSpot onboarding and implementation?
- Onboarding is HubSpot getting you configured and trained on the product — it is about the tool. Implementation is designing the revenue process the tool should encode, then building to it. Onboarding alone leaves you with a correctly configured portal that does not match how you sell, which is the most common reason a portal is abandoned in year two.
- Is HubSpot onboarding mandatory, and do we still need it?
- HubSpot attaches a one-off onboarding fee to Professional and Enterprise purchases, sold as Guided Onboarding at Professional tier and a heavier package at Enterprise. Where it is mandatory you pay it regardless. It is product training rather than process design, so it duplicates very little of an implementation — we work alongside it rather than repeat it, and we do not ask you to buy it where it is optional.
- How long does a HubSpot implementation take?
- Six to eight weeks for a company at $5M–$20M with one or two pipelines, plus a handover period after go-live. Data cleanup is the variable — a clean starting point is faster, and years of drift across two or three source systems can add several weeks before anything is imported.
- What does a HubSpot implementation cost?
- We quote fixed-price against the mapped process rather than per seat or per hour, so the number is known before the build starts. Three things move it: how many pipelines you run, how many systems the data is arriving from, and whether the sales process is already defined or has to be defined first. HubSpot licence and onboarding fees are separate, set by HubSpot, and scale with the tier you buy.
- Do we need a certified HubSpot implementation partner?
- Partner tier tells you how much software an agency has resold, not how well it designs a revenue process. It is worth asking any implementation partner or agency whether they hold reseller margin on your licence, because that shapes which tier they recommend. We do not, so a cheaper tier is a live option in every conversation.
- Can you migrate us from Salesforce, Pipedrive or a spreadsheet?
- Yes — migration is part of the implementation rather than a separate project. Records are deduplicated, normalised and mapped before anything is imported, including closed-won history so the first quarter of reporting is comparable to the last. Importing dirty data into a clean portal is how a new CRM inherits the credibility problem of the old one.
- What do we need to prepare before it starts?
- Less than most implementation checklists suggest. An export of every system currently holding customer data, a list of who owns which accounts, and two hours each from the people who actually run deals. We do not ask you to document your process first — mapping it is the first phase of the work.
Related
- HubSpot ConsultingHubSpot is only as good as the revenue process it encodes. Most portals we inherit are configured for how the company sold three years ago.
- Deal DeskWhen every large deal becomes a bespoke negotiation routed through the founder, you need a deal desk. It is a process, not a department.
- CRM ConsultingA CRM is only as good as the process it encodes. Most of what looks like a CRM problem is an undefined process problem.