# Protect HubSpot data

HubSpot is a comprehensive customer platform that unifies marketing, sales, and customer service operations. This workload protects HubSpot CRM (contacts, companies, deals, tickets, leads, appointments, courses, services, custom objects, properties, pipelines, associations), Marketing (emails, forms, events, campaigns), Content/CMS (website and landing pages, blog posts, HubDB tables, files, URL redirects), Sales (target accounts, meeting links, sequences), Commerce (quotes, products, invoices, payments, subscriptions, line items, credit memos, properties, associations), Service (feedback submissions), Automation (workflows, sequences), Data Management (events), and Reporting (goals).

## What's supported

### HubSpot requirements

- Service key (created in Hubspot -> development -> keys -> service keys) The service key must be granted all required scopes for CRM, Marketing, Content, Sales, Commerce, Service, Automation, Data Management, and Reporting APIs
- API access must be enabled (not available on all free-tier plans)

### Supported resources and data

HubSpot protection covers a nine-hub hierarchy organized by product area:

- CRM — Contacts, companies, deals, tickets, leads, orders, projects, appointments, courses, services, listings, carts, custom objects, properties, pipelines, association records, and segments (lists)
- Marketing — Marketing emails, forms, events, campaigns, and their associations
- Content (CMS) — Website pages, landing pages, blog posts (with authors and tags), HubDB tables and rows, File Manager files, and URL redirects
- Sales — Target accounts (ABM), meeting links (scheduler definitions), and sales sequences
- Commerce — Quotes, products, invoices, line items, payments, subscriptions, credit memos, discount/fee/tax properties, and commerce associations
- Service — Feedback submissions (NPS/CSAT/CES survey responses)
- Automation — Workflow definitions (v4 graph and v3 legacy workflows) and automation sequences
- Data Management — Custom behavioral event definitions
- Reporting — Customer success KPI goals

## Backup and restore capabilities

Capability | Details
--- | ---
Backup levels | Full and Incremental.
Incremental backups | Supported by all objects and is filtered on `lastmodifieddate >= timestamp`.
Restore granularity | Hub, object type, or individual object level.
Restore destinations | In-place restore to the same HubSpot account. Cross-account restore is not supported.
Restore method | Create if not exists, update if exists (upsert). Objects are restored in dependency order (schemas and properties first, then records, then associations).

### Data flow and storage

Commvault access nodes connect to the HubSpot API endpoints to download backup data. The access node serializes CRM, marketing, content, sales, commerce, service, automation, data management, and reporting objects as JSON and stores them in the configured backup storage destination. Since HubSpot is a global SaaS service, neither the access node nor the backup storage has regional placement requirements.

## What isn't supported

- Workflow execution history — Only workflow definitions are backed up, not workflow run history or execution state.
- Meeting links — Meeting link definitions are backed up but not fully restorable (the HubSpot API does not support upsert for meeting links).
- Sales sequences — Sales sequence definitions are backed up but not fully restorable (sequence enrollment requires live user context and cannot be automated via API).
- Cross-account restore — Out-of-place restore to a different HubSpot account is not supported.

## Limitations

- Schema and configuration objects always perform full backup — Properties, pipelines, associations, segments (lists), sequences, meeting links, HubDB tables, URL redirects, service feedback submissions, data management events, commerce objects, and marketing events do not support incremental backup. These objects are small and lack reliable API-level modification timestamps.
- API rate limits — HubSpot enforces a 10 requests/second rate limit. The workload automatically applies a 100ms delay between API calls, and the HubSpot SDK handles 429 (rate limit exceeded) responses with automatic retry. Full backups of large accounts may take longer than other SaaS workloads.

×

Loading...