On this page
What HubSpot’s onboarding plans cover natively
HubSpot’s sample onboarding plans are organized in phases. They are a good reference for the first part of any implementation:
| Phase | Sales Hub plan | Marketing Hub plan |
|---|---|---|
| Setup | Account and tech setup: connect your inbox, invite your team, import data, review your existing CRM, set up external system integrations | Account and tech setup: invite users, connect domains, install tracking, import data, consider integrations |
| Core process | Connect with prospects: chat, meetings, email tools | Capture and convert leads: personas, qualification, forms, lead scoring, lifecycle stages |
| Automation | Automate the sales process: pipeline stages, tasks, lead rotation, workflows, how other tools integrate with HubSpot | Engage and nurture: nurture tracks, a first welcome flow |
| Scale | Personalize outreach: sequences, templates, quotes | Automate and personalize: smart content, social and ad tools, lists |
| Close | Complete onboarding and transition to a customer success owner | Same |
The plans focus on up to three goals, and HubSpot designs each one around your current tech stack and how it integrates with HubSpot. Integrations sit inside onboarding: Sales Hub Onboarding lists turning on standard App Marketplace and native integrations and consulting on migrating data from your CRM. The guidance is remote, so your team or a partner does the hands-on work, and HubSpot points a highly customized setup to a Solutions Partner. That’s why the project phases below keep migration and integrations as their own phase, with their own sign-off.
The phases of a HubSpot implementation project
| Phase | What happens | Sign-off before moving on |
|---|---|---|
| 1. Discovery | Goals in priority order, current process, systems, who owns each decision | Agreed scope and goals |
| 2. Data model and account setup | Users and teams, domains, tracking code, objects, properties, lifecycle and pipeline stages | A written schema: internal names, types, option values |
| 3. Build | Pipelines, forms, lists, emails, workflows, reports and dashboards | Reviewed plan first, then reviewed assets |
| 4. Migration and integrations | Test import, reconciliation, connected apps, final import | Record counts and samples match the source |
| 5. Test, train, hand over | Test with real records, switch workflows on in stages, train users, document | Acceptance by the people who will run it |
Two rules keep the phases honest. First, nothing in phase 3 should reference a property or stage that phase 2 hasn’t agreed. Second, “built” and “working” are separate checks: an asset can be saved correctly and still enroll the wrong records.
Common mistakes
- Skipping the schema sign-off. Workflows and reports built on provisional properties get rebuilt later.
- Migrating before the build. Imports into properties that later change need cleanup or a second import.
- Ending at “deployed”. Without testing and a handoff, the next admin inherits assets nobody can explain. The handoff guide lists what to leave behind.
Where Jetstack AI fits
Jetstack AI covers the build phase and its record. With Projects, the phase 2 schema and the agreed build scope go into a brief. Jetty turns them into a plan you review, generates the supported assets after that approval and deploys them after a second one, in dependency order so properties come before the workflows that use them. Each asset is read back from HubSpot and recorded in a receipt, and workflows are created switched off so phase 5 testing stays in your hands. Projects is currently in limited release; see deployment and receipts and how Projects compares with building by hand.
Sources
- Sales Hub sample onboarding plan (HubSpot)
- Marketing Hub sample onboarding plan (HubSpot)
- HubSpot onboarding services (HubSpot)
- Sales Hub Onboarding (HubSpot)
- Projects deployment and receipts (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