Skip to content
Book a build

What should a HubSpot implementation checklist include?

A HubSpot implementation checklist should include the goals and decision owners, the data model (objects, properties, lifecycle and pipeline stages), account setup (users, teams, domains, tracking code), the build list (pipelines, forms, lists, emails, workflows, reports), migration and integrations, testing with real records, training and a handoff record. Give every item an owner and a definition of done.

On this page

What HubSpot provides natively

HubSpot’s sample onboarding plans work as a starting checklist. HubSpot designs each plan around your goals and your current tech stack, including how it integrates with HubSpot. The first phase, account and tech setup, lists inviting users, connecting email and domains, installing the tracking code, importing data and integrations: the Sales Hub plan includes reviewing your existing CRM and setting up external system integrations, and the Marketing Hub plan says to consider integrations. Sales Hub Onboarding also lists consulting on migrating data from your CRM and turning on standard App Marketplace and native integrations. Later phases cover forms, lead scoring and lifecycle stages (Marketing Hub) or pipeline stages, lead rotation and workflows (Sales Hub). If you have a sandbox, HubSpot lets you build there and deploy supported changes to production.

The onboarding is remote guidance; your team or a partner does the work, and for a highly customized setup HubSpot points you to a Solutions Partner. What the plans can’t give you is your own rules: what a qualified lead means for you, who gets which deal, and which records stay out of automation.

What a HubSpot implementation checklist should include

AreaItemDone when
GoalsTwo or three launch goals, rankedSigned off by the budget owner
OwnershipA named owner for each business ruleEvery open question has a name next to it
Data modelObjects, properties (internal names, types, options), associationsWritten down and reviewed before any build
DefinitionsLifecycle stages, lead status, pipeline stages with entry and exit rulesSales and marketing agree in writing
Account setupUsers, teams, permissions, domains, tracking code, email connectionEach user can log in and see what they should
BuildPipelines, forms, lists, emails, workflows, reports, dashboardsEach asset reviewed against the data model
MigrationField mapping, test import, final importRecord counts and spot checks match the source
IntegrationsConnected apps and their field mappingsTest records sync both ways as expected
TestingWorkflows tested with real records, switched on in stagesEnrollment and actions checked in HubSpot
TrainingSessions by role, short written guidesUsers can do their daily tasks unaided
HandoffAsset register, open items, who maintains whatThe next admin can explain every workflow

The detailed version of the build and verification steps is in the HubSpot implementation guide.

Common mistakes

  • Ticking “properties created” without recording internal names and option values, which workflows depend on.
  • Treating “deployed” as “done”. A saved workflow can still enroll the wrong records; check behavior separately.
  • No owner for open questions, so generated or default settings quietly become policy.

Where Jetstack AI fits

Jetstack AI covers the build rows of the checklist. Put the data model and definitions rows in a Projects brief and Jetty turns them into a plan you review; approving it generates supported properties, pipelines, lists, forms, emails, workflows and more, and deployment is a separate approval. The receipt records what was created, checked by reading it back from HubSpot, and workflows arrive switched off for the testing row. Anything it can’t do, such as users, data imports or integrations, appears as a “You do this” step; see what Projects can build and how Projects compares with building by hand. Projects is currently in limited release.

Sources

Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Implementation & onboarding

Turn the brief into approved HubSpot assets.

Projects plans the build against the client portal, generates the assets and deploys them only after you approve.

Explore Projects

Implementation & onboarding

Related questions.

What should a HubSpot implementation checklist include?

A HubSpot implementation checklist should include the goals and decision owners, the data model (objects, properties, lifecycle and pipeline stages), account setup (users, teams, domains, tracking code), the build list (pipelines, forms, lists, emails, workflows, reports), migration and integrations, testing with real records, training and a handoff record. Give every item an owner and a definition of done.

Is HubSpot's onboarding checklist enough?

It's a strong start. HubSpot builds each plan around up to three goals and your tech stack, and the guidance covers account setup, importing data and setting up integrations. It's remote guidance: your team or a partner does the hands-on work, and your own business rules and definitions of done are yours to add.

Should we test in a sandbox first?

If your subscription includes sandboxes, build and test risky changes there and deploy the supported changes to production. Otherwise test in production with workflows switched off and a small set of test records.

What's the most common missing item?

A written definition for each lifecycle stage and pipeline stage. Without it, workflows and reports encode different people's assumptions.