This checklist covers every configuration item that should be complete before a HubSpot CRM implementation goes live. It is organized by category. Every item should have a named owner, a completion date, and a sign-off before the go-live date is confirmed.

Items marked as attribution-critical are the ones most commonly skipped and most expensive to remediate after go-live. Do not skip them.

Category 1: Data Model and Properties

  • ICP documented with firmographic, technographic, and behavioral criteria agreed to by sales and marketing
  • Buying committee personas documented: roles involved in decisions, what each evaluates, at what stage they typically engage
  • All required custom contact properties created with documented name, data type, use case, and owner
  • All required custom company properties created with documented name, data type, use case, and owner
  • All required custom deal properties created with documented name, data type, use case, and owner
  • Contact-to-company association model documented: how contacts will be associated to companies, who is responsible for maintaining associations
  • Duplicate contact detection configured: HubSpot deduplication settings reviewed and enabled
  • Data import templates created for any bulk contact or company imports planned at go-live

Category 2: Lifecycle Stages and Pipeline

  • Each lifecycle stage defined with written entry criteria and exit criteria
  • Lifecycle stage definitions reviewed and approved in writing by both marketing and sales leadership
  • Deal pipeline stages configured to match actual sales process terminology
  • Required fields configured at each deal stage: fields that must be populated before a deal can advance
  • Deal probability weighting configured for each stage
  • Win/loss reason picklist configured with values that reflect actual sales outcomes
  • Deal close date field confirmed as required at deal creation

Category 3: Lead Scoring

  • Lead scoring model designed from current ICP criteria and buying signal data
  • Demographic scoring dimension configured: company size, industry, job title, and other firmographic fit criteria
     
     
     
     
     
  • Behavioral scoring dimension configured: email engagement, page views, form submissions, content downloads
  • Negative scoring configured: unsubscribes, bounces, competitor domain visits
  • MQL threshold set at the score that corresponds to the lifecycle stage entry criteria agreed upon in Category 2
  • Lead scoring model documented: every scoring rule has a name, a value, and a rationale
  • Scoring model validated against a sample of recent closed-won contacts: do high-scoring contacts correspond to buyers who converted?

Category 4: Lead Routing and Assignment (attribution-critical)

  • Lead routing rules configured to match territory and assignment logic agreed with sales leadership
  • Round-robin rotation configured for teams that share lead volume
  • Routing rules tested against sample records before go-live
  • Fallback assignment rule configured: what happens to a lead that does not match any routing rule
  • Routing notification emails configured: sales reps receive immediate notification of new lead assignment
     
     
     
     
     
  • Lead assignment report configured: surfaces unactioned leads that have exceeded SLA window

Category 5: Marketing Hub to CRM Sync (attribution-critical)

  • Marketing Hub to CRM integration enabled and authenticated
  • Field mapping documented for every contact property that needs to sync between Marketing Hub and CRM
  • Bi-directional sync direction confirmed for every field: which system is authoritative when values conflict
  • Sync tested with live test records: verify every mapped field arrives in CRM with correct value
  • Attribution fields confirmed syncing: original source, original source drill-down, first conversion, and recent conversion fields verified in CRM contact records
  • Sync error monitoring configured: alerts fire when sync failures occur rather than accumulating silently

Category 6: UTM Taxonomy and Tracking (attribution-critical)

  • UTM taxonomy standard documented: parameter structure for source, medium, campaign, content, and term
  • UTM taxonomy distributed to every person who creates marketing links: campaign managers, content team, paid media team, agency partners
  • UTM taxonomy enforcement process established: QA check on every campaign link before launch
  • HubSpot tracking code installed on all marketing properties: website, landing pages, blog
  • HubSpot tracking code verified firing correctly on all pages using browser developer tools
  • Cookie consent configuration reviewed for GDPR and CCPA compliance
  • Cross-domain tracking configured if marketing properties span multiple domains

Category 7: Attribution and Reporting (attribution-critical)

  • Multi-touch attribution model selected and documented: linear, U-shaped, W-shaped, full-path, or time-decay
  • Attribution model rationale documented: why this model fits this sales cycle length and buying process
  • Marketing-sourced pipeline dashboard built and validated against test data before live data loads
  • Marketing-influenced pipeline dashboard built and validated
  • Channel attribution report built: first-touch and last-touch breakdown by channel
  • Lead funnel report built: contact volume at each lifecycle stage with conversion rates
  • Reporting permission structure configured: defined who can create and modify dashboards

Category 8: SLA Workflows

  • MQL handoff workflow built: trigger condition, notification to sales rep, task creation, SLA window definition
  • SQL acceptance workflow built: how a sales rep marks a lead as SQL and what happens next
  • Lead rejection workflow built: how a sales rep rejects a lead, what reason is captured, where the lead goes next
  • Lead recycling workflow built: how rejected leads re-enter nurture and under what conditions they re-qualify
  • SLA enforcement alert configured: fires when a lead has been in MQL status beyond the defined SLA window without sales action
  • All SLA workflows tested with live test records before go-live

Category 9: Integrations

  • Integration dependency map complete: every system connecting to HubSpot documented with data flow direction and method
  • Each integration configured and tested in sandbox environment
  • Each integration tested with live data before go-live
  • Integration data flow documentation complete: what fields sync, in which direction, on what trigger
  • Integration error monitoring configured for each integration

Category 10: Sales Team Readiness

  • Sales team training completed before go-live: not scheduled after go-live
  • Training content is role-specific: covers daily workflow tasks, not just platform features
  • Sales team has logged into HubSpot and completed at least one end-to-end workflow test before go-live
  • Sales leadership has reviewed and approved the pipeline dashboard they will use post-go-live
  • HubSpot mobile app installed on sales team devices where mobile CRM use is expected

Category 11: Pre-Go-Live Validation

  • Data association validation: contact-to-company association rate at or above defined threshold
  • Workflow trigger validation: all SLA workflows tested and confirmed firing on correct conditions
  • Attribution field validation: marketing touchpoints visible on test contact records in CRM timeline
  • Pipeline dashboard validation: dashboard produces expected output against test data
  • Integration validation: all integrations verified live and syncing correctly
  • Routing validation: test lead records route to correct sales rep in each territory scenario

Category 12: Go-Live and Hypercare

  • Go-live date confirmed with all stakeholders: marketing, sales, and IT
  • Parallel running period defined: if running Salesforce and HubSpot simultaneously, end date and cutover criteria documented
  • 30-day hypercare monitoring protocol assigned: named owner reviews attribution data daily for 30 days post-go-live
  • Escalation path documented: who is contacted and within what timeframe when a configuration issue is discovered post-go-live
  • Post-go-live attribution baseline measurement scheduled: Day 30 and Day 90 pipeline attribution reviews on calendar

Frequently Asked Questions

How long does it take to complete this checklist? Categories 1 through 6 run concurrently and take 3 to 4 weeks in a well-resourced implementation. Categories 7 through 9 run concurrently with Categories 4 through 6 and add 1 to 2 weeks. Categories 10 through 12 run in the final week before go-live. Total elapsed time for a standard implementation is 6 to 8 weeks.

Which items are most commonly incomplete at go-live? Category 6 (UTM taxonomy distribution) and Category 5 (Marketing Hub to CRM sync testing) are the most common incomplete items. UTM taxonomy documents are created but not distributed to agency partners and paid media vendors who also create marketing links. Sync testing is performed for primary fields but not for attribution-specific fields like original source and recent conversion. Both gaps produce attribution data problems that surface 30 to 60 days post-go-live.

What is the consequence of going live before Category 7 (attribution dashboards) is complete? Campaign data that runs through HubSpot before the attribution dashboards are built still generates attribution data, but the dashboards need to be built against data that has already accumulated. In most cases this works without issues. The risk is that data quality problems in the first 30 to 60 days are not visible because no one is monitoring the attribution report. Build the dashboards before go-live so monitoring can begin from day one.

The Pedowitz Group has been implementing HubSpot for enterprise and mid-market B2B organizations since 2007. If you are approaching a go-live and want an independent validation against this checklist, we can complete it in a single review session. Talk to TPG.