HubSpot implementation guide

HubSpot implementation: the guide and checklist

A HubSpot implementation is more than turning on features. It is deciding how your business will run inside the CRM: the data model, the pipelines, the automation, the integrations and how your team will use it every day. This guide walks through each phase, with the checklist we use on real projects.

Before you start

Why implementations succeed or stall

Most HubSpot problems start on day one. A portal set up in a hurry, or by someone learning HubSpot while building it, ends up with duplicate properties, pipelines nobody trusts and workflows that fight each other. The team stops using it, and the subscription keeps being paid.

Implementations that work have three things in common: the business process is agreed before anything is configured, the data model is designed once and shared by every hub, and adoption is planned as carefully as the setup. The checklist below follows that order.

If you are still evaluating the platform, start with What is HubSpot. If you are comparing HubSpot's own onboarding with a partner, see HubSpot onboarding vs Solutions Partner onboarding.

In this guide

  1. The implementation checklist, phase by phase
  2. What to set up in each hub
  3. The mistakes that cost the most
  4. After go-live: running and governing the portal
  5. Common questions

The implementation checklist

Seven phases, in this order.

Each phase depends on the one before it. Building automation before the data model is right is the most common reason projects need to be redone.

  1. 01 · Scope

    Map the process and goals

    Document how leads become customers today, which teams use the CRM, which reports leadership needs and which systems must connect. Agree on what is in the first release.

    Done when: a signed scope with goals, users and success metrics.

  2. 02 · Data model

    Design objects, properties and associations

    Contacts, companies, deals, tickets and custom objects where needed, with naming rules, required fields and ownership. Every hub will read this model.

    Done when: a data dictionary the whole team can read.

  3. 03 · Migration

    Clean and import the data

    Map fields from the old system or spreadsheets, deduplicate, keep history and associations, and test with a sample before the full import.

    Done when: records in HubSpot that match the source.

  4. 04 · Process

    Build pipelines and lifecycle

    Deal and ticket pipelines with stage rules, lifecycle stages, lead status, routing and the handoffs between marketing, sales and service.

    Done when: a process every rep follows the same way.

  5. 05 · Automation

    Automate and integrate

    Workflows for routing, follow-up and alerts, then integrations with email, calendar, billing, ERP or product data. Keep each workflow with one clear job.

    Done when: manual work removed without side effects.

  6. 06 · Reporting

    Build the dashboards

    Dashboards for leadership, sales managers and reps, built on the definitions agreed in scope, so every number has one meaning.

    Done when: reports the leadership uses in its meetings.

  7. 07 · Adoption

    Train, launch and support

    Role-based training with the team's own data, a launch date, office hours in the first weeks and a short list of what each role must do in HubSpot every day.

    Done when: the team works in HubSpot, not around it.

More detail on the process in CRM implementation process.

Hub by hub

What to set up in each hub.

One portal, several hubs, one data model underneath. These are the essentials of each.

  • Smart CRM

    Objects, properties, associations, permissions, teams and data quality rules. The foundation every other hub reads.

    Data quality alerts
  • Marketing Hub

    Forms, lead capture, lifecycle stages, lead scoring, email, nurturing and campaign attribution.

  • Sales Hub

    Deal pipelines and stage rules, routing, sequences, meetings, quotes and forecasting.

    Sales automation done right
  • Service Hub

    Ticket pipelines, help desk, SLAs, knowledge base and customer feedback.

  • Content Hub

    Website and blog on a theme marketing can edit on its own, with languages, SEO and tracking set up from the start.

    Launching a Content Hub website
  • Breeze AI

    AI agents and assistants turned on only where the data and playbooks are ready, with permissions and credits under control.

    See AI Agent Hub

The mistakes that cost the most

Five things to get right before go-live.

Each of these is cheap to avoid during the implementation and expensive to fix a year later.

  • 01

    Configuring before agreeing

    Building pipelines before marketing, sales and leadership agree on the stages and what each one means.

  • 02

    Importing dirty data

    Migrating duplicates and empty fields from the old system and promising to clean them later.

  • 03

    Too many properties

    Creating a field for every request instead of designing the data model, until nobody knows which one to use.

  • 04

    Workflows that overlap

    Several workflows changing the same property, with no naming rules or owner, until the results become unpredictable.

    Workflow troubleshooting
  • 05

    Training as an afterthought

    One generic session at launch, with no role-based training or support in the first weeks.

After go-live

Running and governing the portal

Go-live is the start, not the end. The business keeps changing, new people join, new tools get connected and requests for fields and workflows keep coming. Without someone owning the portal, quality drifts back to where it started.

Three habits keep a portal healthy: a monthly data quality review, rules for who can create properties and workflows, and a backlog where requests are prioritized instead of built on demand. Our articles on workflow governance and the data quality command center show how we run it.

If you would rather have a senior team look after the portal every month, see HubSpot Managed Services.

From the blog

Latest articles on HubSpot implementation.

See all HubSpot implementation articles

Common questions

HubSpot implementation, answered.

How long does a HubSpot implementation take?

In our projects most portals go live in about 30 days: a week each for discovery and data model, migration and integrations, automation and reporting, and training and go-live. Portals with several hubs, a large migration or custom integrations can take six to eight weeks. Scoping first is what keeps the timeline honest.

What should a HubSpot implementation checklist include?

Scope and goals, the data model, data migration, pipelines and lifecycle stages, automation and integrations, dashboards, and training and adoption, in that order. The checklist on this page details each phase.

Can we implement HubSpot ourselves?

Yes, for a simple setup with one hub and little data. As soon as there is a migration, several teams, custom objects or integrations, mistakes in the data model become expensive, and an experienced partner usually pays for itself.

What is the difference between HubSpot onboarding and a partner implementation?

HubSpot onboarding teaches your team the tools. A Solutions Partner designs and builds the portal around your process, migrates your data and connects your systems. See HubSpot onboarding vs Solutions Partner onboarding.

Can we migrate from another CRM during the implementation?

Yes, and it is the best moment to do it, because the data model is being designed anyway. History, associations and owners can be kept when the migration is planned field by field. See CRM Migration.

How do we make sure the team uses HubSpot after launch?

Train by role with real data, define the few things each role must do in HubSpot every day, give support in the first weeks and use HubSpot reports in the team meetings. When leadership runs the meeting from HubSpot, the team keeps it up to date.

Want it done right the first time?

A HubSpot portal your team will actually use.

Implementation across every hub by a Diamond partner, on clean data, with your team trained.

See HubSpot Implementation