HubSpot onboarding timeline: what actually happens week by week

Most HubSpot implementations fail on sequencing, not on software. Below is the timeline we use on real projects, from kickoff to a CRM your team actually uses.

Week 1 — Discovery and process mapping

We document how revenue is created today: sources of demand, who touches a deal, where data lives, what reporting leadership needs. Output is a written process map and a target data model — objects, lifecycle stages, pipelines and required properties.

Week 2 — Data audit and cleanup plan

Export every current source (spreadsheets, legacy CRM, mailboxes, eCommerce). Deduplicate, normalise country and phone formats, decide what not to migrate. Bad data migrated on day one becomes distrust on day thirty.

Week 3 — Build

Portal configuration: pipelines and deal stages with exit criteria, custom properties, custom objects if needed, teams and permissions, email sending domain with SPF, DKIM and DMARC, forms and lifecycle automation.

Week 4 — Migration and integrations

Staged import: companies, then contacts, then deals, then activities. Connect the systems that matter — website, eCommerce, ERP, calendars, WhatsApp or telephony. Validate record counts and associations after every load.

Week 5 — Reporting and training

Build the dashboards leadership will open weekly: pipeline by stage, conversion by source, velocity, forecast. Then train by role — reps see their day, managers see their review, marketing sees attribution.

Week 6 — Go-live

Freeze legacy tools, switch demand capture to HubSpot, run daily check-ins for the first week. Everything that breaks in week six is cheap to fix; the same issue found in month six is not.

First 30 days after go-live

Track adoption, not opinions: logged activities, deals with correct stages, forms flowing to the right owner. Adjust automation weekly. A CRM is not a project you close, it is infrastructure you maintain.

Realistic expectations

A focused SMB rollout runs six to eight weeks. Multi-entity, multi-currency or ERP-connected builds run ten to sixteen. Anyone promising two weeks is skipping discovery, migration or training — and you will pay for it later.