HubSpot CRM Setup Checklist: Getting Your Revenue Team Operational in 30 Days

HubSpot is one of the most forgiving CRMs to implement — and one of the easiest to implement badly. The defaults are good enough that many teams go live without touching configuration, then spend the next 12 months wondering why their pipeline is inaccurate and their reps aren’t using it.

A proper setup doesn’t take long. It takes a checklist and someone willing to make decisions upfront about how your team will actually work.

This guide covers the core configuration steps to get your HubSpot instance clean, structured, and usable from day one.

Week 1: Account Foundations

Before you touch pipelines or import contacts, get the basics right.

User and team setup:

  • Create user accounts for all team members with appropriate permission sets
  • Set up teams (if you have multiple regions, segments, or pod structures)
  • Configure your default currency and time zone
  • Set up your company domain to auto-associate contacts and companies

Branding and communications:

  • Upload your logo and configure email sending domain (required for deliverability)
  • Set up a connected inbox for each rep who’ll be logging emails
  • Configure your meeting scheduling link (HubSpot Meetings)
  • Verify GDPR/CCPA consent settings match your legal requirements

Property audit:

  • Review the default contact, company, and deal properties
  • Delete or hide properties your team will never use (clutter kills adoption)
  • Create any custom properties you know you’ll need — but keep this minimal at launch

Week 2: Pipeline and Process Configuration

This is where most implementations go wrong. Teams create pipelines that reflect their wishful thinking rather than how deals actually move.

Deal pipeline setup:

  • Define your pipeline stages — aim for 5–8 stages maximum
  • Set stage-level close probability estimates (used in forecasting)
  • Configure required fields at each stage (forces data quality without slowing reps)
  • Set up deal rotation rules if you have multiple reps

Contact and company structure:

  • Define your lifecycle stages (Subscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist)
  • Set up lead status values that match your SDR/AE handoff process
  • Configure company association rules — do contacts auto-associate by email domain?

Activity logging:

  • Decide which activities log automatically (connected inbox, calendar) vs. manually
  • Set up call outcome types and meeting types that match your sales process
  • Configure task queues for your SDR team if applicable

Week 3: Integrations and Data Migration

Core integrations to configure before go-live:

  • Email (Gmail or Outlook) — required for activity logging; do this for every rep
  • Calendar — enables meeting logging and HubSpot Meetings
  • Slack — deal notifications and @mention alerts keep deals moving without log-ins
  • Your marketing automation tool (if separate from HubSpot Marketing Hub)
  • Your billing or ERP system — for deal-to-invoice workflow if applicable

Data migration:

  • Export contacts from your previous CRM or spreadsheet
  • Clean the data before import — deduplicate, standardize formatting, remove invalid emails
  • Map fields from your old system to HubSpot properties before importing
  • Import in test batches first (100 records) to catch mapping errors
  • Validate imported data before full migration

Do not import everything. Old, unengaged contacts dilute your database health and hurt email deliverability. Set a recency threshold (e.g., engaged in the last 18 months) and import only those.

Week 4: Reporting, Automation, and Training

Reports to build before launch:

  • Pipeline by stage (current snapshot)
  • Deal velocity (average days per stage)
  • Activity metrics per rep (calls, emails, meetings booked)
  • Won/lost by reason
  • Forecast by close date

Build these in a shared dashboard your leadership team can check weekly. If you don’t build them before launch, they won’t get built.

Automation to configure:

  • Lead assignment rotation (if not using HubSpot’s built-in round-robin)
  • Deal stage automation (e.g., auto-create a task when a deal enters Proposal Sent)
  • Lead nurturing sequences for MQLs not yet sales-ready
  • Internal notifications for deal inactivity (deals with no activity in 7 days)

Training:

  • Run a 60-minute live session with the full team — not a recording
  • Cover only the workflows that apply to them (reps don’t need admin training)
  • Create a one-page “how we use HubSpot” reference doc for common tasks
  • Set a 30-day check-in to address what’s not working

The 10 Mistakes That Kill HubSpot Adoption

  1. Too many pipeline stages. More than 8 stages and reps start skipping them.
  2. No required fields. “Optional” means “I’ll fill it in later,” which means never.
  3. Importing dirty data. One bad import can take weeks to clean up.
  4. No deal rotation rules. Leads assigned manually create conflict and delay.
  5. Skipping the email integration. If activity doesn’t log automatically, it won’t log.
  6. Building reports no one reads. Build what your manager will actually look at in 1:1s.
  7. Too many custom properties at launch. Start with the minimum; add as you learn what you need.
  8. No data governance rules. Who can create new properties? Who can change stage names? Decide upfront.
  9. Training only power users. Every rep needs to know the basics — not just the admin.
  10. Never revisiting the configuration. Your process will evolve. Schedule a quarterly CRM review.

Get the Full HubSpot Setup Checklist

Our HubSpot CRM Setup Checklist is a 47-point implementation guide organized by week, covering every configuration step from account foundations to reporting — with checkboxes, notes fields, and a common pitfalls callout for each section.

It’s part of the RevOps Toolkit, which includes setup checklists for Salesforce, Gong, and Clari alongside our Sales Forecasting Model, QBR Deck, and Sales Territory Planning Workbook. Everything your revenue operations team needs to build a clean, scalable GTM stack.