A practical 90-day HubSpot onboarding checklist

Before day one

Treat onboarding as an operating-model project, not a configuration checklist. Confirm the commercial goals, customer journey, decision owners, systems of record, implementation boundaries, and success measures before building.

• Name the executive sponsor, project owner, Hub owners, and data owner.
• Document the current lead, sales, service, and customer handoff process.
• Inventory data sources, integrations, domains, sending infrastructure, and user groups.
• Agree on the first measurable business outcome and the reports that will prove it.

Days 1 to 30: foundation and usable first release

• Define lifecycle stages, lead statuses, pipelines, ownership, and required transition data.
• Design the property model before importing data or building automation.
• Clean, map, test, and reconcile migration samples before the production import.
• Configure roles, teams, permissions, domains, email, and consent settings.
• Launch one complete path from acquisition to accountable follow-up.
• Train the first user group on the process they will perform immediately.

Days 31 to 60: automation, handoffs, and reporting

• Add automation only after the manual process and ownership rules are accepted.
• Test enrollment, reenrollment, suppression, failure, and rollback behavior.
• Connect required systems with clear source-of-truth and conflict rules.
• Build operational dashboards for managers before executive summary dashboards.
• Review adoption by role and correct process or training gaps early.

Days 61 to 90: hardening and measurable adoption

• Reconcile pipeline, lifecycle, attribution, and customer reporting against source evidence.
• Remove temporary migration access, test assets, and obsolete configuration.
• Document workflows, reports, integrations, owners, and escalation paths.
• Run a portal health review and resolve the highest-risk findings.
• Create a monthly governance rhythm for changes, adoption, data quality, and outcomes.

What a successful day 90 looks like

The portal does not need every requested feature. It needs a trusted data foundation, a complete working journey, accountable owners, useful reports, trained users, and a governed backlog for the next release. That foundation is what makes future automation and AI valuable instead of fragile.