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
| Area | Item | Done when |
|---|---|---|
| Goals | Two or three launch goals, ranked | Signed off by the budget owner |
| Ownership | A named owner for each business rule | Every open question has a name next to it |
| Data model | Objects, properties (internal names, types, options), associations | Written down and reviewed before any build |
| Definitions | Lifecycle stages, lead status, pipeline stages with entry and exit rules | Sales and marketing agree in writing |
| Account setup | Users, teams, permissions, domains, tracking code, email connection | Each user can log in and see what they should |
| Build | Pipelines, forms, lists, emails, workflows, reports, dashboards | Each asset reviewed against the data model |
| Migration | Field mapping, test import, final import | Record counts and spot checks match the source |
| Integrations | Connected apps and their field mappings | Test records sync both ways as expected |
| Testing | Workflows tested with real records, switched on in stages | Enrollment and actions checked in HubSpot |
| Training | Sessions by role, short written guides | Users can do their daily tasks unaided |
| Handoff | Asset register, open items, who maintains what | The 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
- Marketing Hub sample onboarding plan (HubSpot)
- Sales Hub sample onboarding plan (HubSpot)
- HubSpot onboarding services (HubSpot)
- Sales Hub Onboarding (HubSpot)
- Create a sandbox and deploy changes to production (HubSpot Knowledge Base)
- What Jetty can build (Jetstack AI documentation)
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