Plan how Commvault protects your HubSpot data. In most environments, you can start with recommended defaults and adjust only if your environment requires it.
Start with your HubSpot environment
One HubSpot configuration protects one HubSpot portal (identified by a numeric hub_id). If your organization operates multiple HubSpot portals — for example, separate portals for different regions, business units, or environments (production, staging, sandbox) — configure each portal as a separate HubSpot instance in Commvault.
Align storage with your HubSpot region
HubSpot is a global SaaS service, and the access node downloads API data as JSON payloads and file attachments. Neither the access node nor the backup storage has a regional requirement. You can place the access node and storage in any region that meets your organization's cost, latency, and compliance requirements.
Network requirements
Access node and network requirements are the same as described in Configure network connectivity for HubSpot.
Understand backup behavior
HubSpot supports both Full and Incremental backups. Incremental backups are supported for CRM standard objects, engagement activities, marketing objects (emails, forms, campaigns), content pages, and automation workflows. These objects filter on API-level modification timestamps (lastmodifieddate >= timestamp for CRM objects, hs_lastmodifieddate >= timestamp for engagement activities, and updated_after parameters for marketing and content objects).
Schema and configuration objects always perform full backup even in incremental mode. These include properties, pipelines, associations, segments (lists), HubDB tables, URL redirects, meeting links, sales sequences, service feedback submissions, data management custom events, commerce objects, and marketing events. These objects are small and lack reliable API-level modification timestamps, so they are always backed up in full.
Decide how to scope your data
HubSpot backup content is scoped at the portal level. One HubSpot configuration backs up all hubs and all object types in the account. Commvault does not support per-hub or per-object-type content scoping for HubSpot. If you need to protect only a subset of your HubSpot data, configure separate HubSpot portals for different environments or business units and protect each portal as a separate instance.
Organize backups logically
Use subclients to organize the backups based on how your organization manages HubSpot data. Common approaches include grouping by environment (production, test, or development), business unit or application, or data sensitivity or compliance requirements — whichever helps you apply consistent policies and simplifies monitoring and reporting.
Plan for performance
Backup and restore performance depends on data size, change rate, and HubSpot 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. Schedule backups to avoid peak workload periods, and avoid running multiple concurrent backup jobs for the same HubSpot portal.
Confirm permissions early
Make sure the required HubSpot permissions are in place before configuring protection. For details, see Configure HubSpot user and permissions.
Understand key limitations
- Schema and configuration objects always perform full backup, even in incremental mode.
- Workflow execution history is not backed up.
- Meeting links and sales sequences are backed up but not fully restorable.
- Cross-account restore is not supported.
For complete details, see Protect HubSpot data.