Skip to content

Deploying assets

Deploying writes assets into a portal through its Private App Token. You can deploy from a snapshot (the selected items, or the whole snapshot) or from a recipe. Either way the app runs a preflight first and shows you the plan before anything is queued.

The deploy dialog asks for the target portal under To, then shows:

LineMeaning
SummaryWhat goes in, e.g. “3 workflows and the 2 lists they need. Anything already in Acme is left as is.”
Missing scopesWrite scopes the target’s Private App Token lacks. Scan scopes re-reads them from HubSpot. Deploy is blocked until this clears.
Can’t be deployedAsset types with no write API, with the reason.
Associated records not in this deployLinks to records you did not choose are skipped unless those records already exist in the target.
Not in this snapshotThings the chosen items refer to that were never captured. Leave them as they are, or Map them onto something the target already has.

Under Advanced:

  • If it already exists there: Leave it alone (skip) or Create a copy (rename). A copy is named “<name> (copy)”, then “(copy 2)” and so on, up to five. Records are matched by email, domain or SKU and are never copied.
  • Bring what they depend on (on by default): a workflow’s lists and emails, a form’s properties, a property’s group, and so on. A dependency that already exists in the target is always reused as-is.
  • Map to existing: for anything not in the source, pick the matching asset in the target. Filters inside lists and workflows have their list, form, pipeline and stage IDs swapped for the target’s.

Assets go in dependency order: a property group before its properties, a list before the workflow that enrols from it. Each one ends as:

OutcomeMeaning
CreatedNew in the target.
SkippedAlready there and left alone, or a record matched by email, domain or SKU.
MappedA dependency you pointed at an existing asset.
FailedHubSpot refused it. The log has HubSpot’s detail lines and the request that was refused.
UnsupportedThe type cannot be written through the API.

The job’s page on Activity lists every item with its outcome and a link to it in the target portal.

Custom objects, property groups, properties, association labels, pipelines, lists, forms, marketing emails, HubDB tables, custom events, campaigns, workflows, records (contacts, companies, deals, tickets, custom objects), products, line items, quotes and activities.

Two safety defaults:

  • Workflows are created switched off. Review them in HubSpot and turn them on yourself.
  • Marketing emails are created as drafts.

Not deployable: dashboards (HubSpot has no API to create reports), sequences (need user-level access, which a Private App Token does not have), lead scores and knowledge base articles (beta APIs). Owners are assigned by matching email; unmatched records are left unassigned.

Date and date-time properties on records, activities and commerce objects move forward by the number of days between the capture and the deploy. Sample data deployed a month after it was captured looks a month fresher, not a month staler.

Deploy on a recipe queues one asset job plus one install job per app in the recipe. Dependencies always come along. The target needs a Private App Token for the assets and a Personal Access Key for the apps; the dialog says which is missing. An app that is already installing in that portal is left alone.

Once a recipe has been deployed, the portal appears under Deployed to. If the recipe changes afterwards, that entry shows Update, and the portal’s page offers Update all for every recipe and app that is behind.