Skip to main content

Deployments

A deployment applies metadata changes from a source to a target HubSpot portal. Every deployment is reviewed before execution and logged for audit purposes.

Important

Deployments modify live HubSpot data. Always review the diff carefully before confirming a deployment. Changes to properties, pipelines, and workflows can affect active CRM records and automations.

How deployments work​

  1. You select a source (portal or repo) and a target portal
  2. HubSpot Deploy computes the diff between the two
  3. You review the changes in the diff viewer
  4. You confirm the deployment
  5. HubSpot Deploy applies the changes to the target portal via the HubSpot API
  6. The deployment is logged with a full record of what changed

Creating a deployment​

Deployments are initiated from the Comparisons screen:

  1. Open a completed comparison
  2. Review the diff — confirm you understand every change
  3. Click Deploy (visible to workspace admins only)
  4. Select the target portal (if not already set by the comparison)
  5. Confirm the deployment

Deployment status​

StatusMeaning
pendingQueued for processing
in progressApplying changes to HubSpot
completedAll changes applied successfully
partialSome changes applied, some failed
errorDeployment failed — no changes applied

Deployment history​

All deployments are logged and accessible from the Deployments screen. Each log entry includes:

  • Timestamp
  • Source and target
  • Status
  • List of applied changes
  • Any errors

Rolling back a deployment​

HubSpot Deploy does not have a one-click rollback. To revert a deployment:

  1. Find the backup snapshot from before the deployment in your Git history
  2. Create a new comparison using that snapshot as the source and the live portal as the target
  3. Review the diff and create a new deployment to restore the previous state

This approach gives you full control over what gets reverted.

Permissions​

Only workspace admins can create and execute deployments. Members can view deployment history but cannot initiate deployments.

See Permissions for the full permissions matrix.