HubSpot is a cloud-based customer relationship management (CRM) platform that unifies marketing, sales, and customer service operations into a single ecosystem. It combines foundational CRM functionality (contact management, deal tracking, reporting) with advanced marketing automation, content management, and AI-powered tools — all designed to support inbound methodology where businesses attract, engage, and delight customers. What sets HubSpot apart is its freemium model and deeply integrated architecture: every email sent, form filled, or page visited automatically enriches CRM records, creating a unified view of each customer relationship. This interconnected approach means marketers can trigger personalized workflows based on sales activity, sales reps can see which content a prospect viewed, and service teams inherit complete context from prior interactions. Understanding how HubSpot's objects, properties, and automation work together is key to scaling efficiently — the platform rewards thoughtful setup with compounding gains in productivity and insight.
What This Cheat Sheet Covers
This topic spans 30 focused tables and 322 indexed concepts, 162 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Core CRM Objects and Data Structure
HubSpot's data model revolves around six standard objects (Contact, Company, Deal, Ticket, Custom Object, and Activity) plus the properties and associations that link them. Everything else in the platform — automation, reporting, AI — is built on top of this object graph, so understanding it well is the single highest-leverage investment when setting up HubSpot.
| Object | Example | Description | |
|---|---|---|---|
john.smith+1-555-0123 | • Represents an individual person • stores email, phone, lifecycle stage, and engagement history. | ||
Acme CorpIndustry: SaaSRevenue: $5M | • Represents an organization • associates multiple contacts and tracks firmographic data like industry, size, and revenue. | ||
Deal: Q1 Enterprise RenewalAmount: $50,000Stage: Negotiation | • Tracks a revenue opportunity through pipeline stages • each deal belongs to a pipeline and has an amount, close date, and deal owner. | ||
Ticket #1234: Login issuePriority: HighStatus: In Progress | • Tracks customer support requests • moves through a support pipeline with status, priority, and assigned owner. | ||
ProjectLocationEvent | • User-defined object to track business-specific data like projects, inventory, or events • requires Professional or Enterprise tier. | ||
Lead Source: WebsiteLast Meeting Date: 2026-03-15 | • A field on an object that stores a specific data point • can be default (built-in) or custom. | ||
Contact → CompanyDeal → Ticket | • Defines relationships between objects • multiple association types allowed (e.g., primary contact, billing contact). | ||
John Smith (Contact)Deal #5678 (Deal) | • A single instance of an object • each record has a unique ID and timeline of activities. | ||
Email sentCall loggedMeeting scheduled | • An engagement event logged to a record's timeline • can be manual or automatic. | ||
Lifecycle Stage: Lead → MQLChanged by: Workflow | Audit trail showing all changes to a property value, including who made the change and when. |