Skip to content
Book a build

What are the phases of a HubSpot implementation?

Most HubSpot implementations run in five phases: discovery and goals, data model and account setup, build (pipelines, forms, lists, emails, workflows and reports), migration and integrations, then testing, training and handoff. HubSpot's own onboarding plans follow the same shape, starting with account and tech setup and ending with a transition to a customer success owner. Each phase of a HubSpot implementation needs a sign-off.

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:

PhaseSales Hub planMarketing Hub plan
SetupAccount and tech setup: connect your inbox, invite your team, import data, review your existing CRM, set up external system integrationsAccount and tech setup: invite users, connect domains, install tracking, import data, consider integrations
Core processConnect with prospects: chat, meetings, email toolsCapture and convert leads: personas, qualification, forms, lead scoring, lifecycle stages
AutomationAutomate the sales process: pipeline stages, tasks, lead rotation, workflows, how other tools integrate with HubSpotEngage and nurture: nurture tracks, a first welcome flow
ScalePersonalize outreach: sequences, templates, quotesAutomate and personalize: smart content, social and ad tools, lists
CloseComplete onboarding and transition to a customer success ownerSame

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

PhaseWhat happensSign-off before moving on
1. DiscoveryGoals in priority order, current process, systems, who owns each decisionAgreed scope and goals
2. Data model and account setupUsers and teams, domains, tracking code, objects, properties, lifecycle and pipeline stagesA written schema: internal names, types, option values
3. BuildPipelines, forms, lists, emails, workflows, reports and dashboardsReviewed plan first, then reviewed assets
4. Migration and integrationsTest import, reconciliation, connected apps, final importRecord counts and samples match the source
5. Test, train, hand overTest with real records, switch workflows on in stages, train users, documentAcceptance 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

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 are the phases of a HubSpot implementation?

Most HubSpot implementations run in five phases: discovery and goals, data model and account setup, build (pipelines, forms, lists, emails, workflows and reports), migration and integrations, then testing, training and handoff. HubSpot's own onboarding plans follow the same shape, starting with account and tech setup and ending with a transition to a customer success owner. Each phase of a HubSpot implementation needs a sign-off.

Can phases run in parallel?

Some can. Integration scoping can start during the build, and training material can be drafted while testing runs. The data model is the exception: agree it before building anything that references it.

Where does data migration go?

After the data model and before final testing. Run a test import once properties and pipelines exist, reconcile it, then do the final import close to launch so records don't go stale.

Who should sign off each phase?

The person who owns the business rule, not only the project lead. Sales leadership signs off pipeline stages, marketing signs off lifecycle and lead definitions, and the admin who will run the portal signs off the handoff.