HubSpot Configuration Glossary
Template Manager introduces a layer of configuration management on top of HubSpot. These definitions explain what the terms mean and how they relate to each other.
-
Template
- A saved snapshot of a single HubSpot object — a property, workflow, segment, custom object, or form. A template stores the full configuration exactly as it existed in the source portal, including all settings and metadata, ready to deploy to any other portal on demand. When you save a template, Template Manager also detects which other objects it depends on so nothing gets left behind.
-
Bundle
- A named, ordered collection of templates grouped for deployment together. Bundles let you package a complete HubSpot configuration — all the properties, workflows, segments, and forms for a given use case — and push the whole set to a new portal in a single step. Templates within a bundle deploy in dependency order automatically.
-
Blueprint
- A named specification built from one or more bundles, representing your ideal HubSpot instance. Blueprints are the basis for gap analysis: connect any portal and Template Manager compares it structurally against the blueprint to show which components are present, partially matched, or missing entirely.
-
Deployment
- The process of pushing one or more templates or bundles to a target HubSpot portal. Template Manager resolves all dependencies and deploys objects in the correct order — custom objects first, then property groups, properties, segments, workflows, and forms last. Internal IDs from the source portal are remapped to their equivalents in the target portal automatically, so cross-object references (workflow → segment, workflow → pipeline stage) resolve correctly.
-
Gap Analysis
- A structural comparison between a blueprint and the current state of a connected portal. Template Manager fingerprints each object by its structure — field types, filter logic, action sequence — not by name. This means an object renamed or slightly reconfigured in the target portal can still be matched against the blueprint. The result is a line-by-line report of what is in place, what is missing, and what needs attention.
-
Sync
- The process of pulling live objects from a connected HubSpot portal into Template Manager's local cache. Synced data is the raw material for saving templates and running analysis. Syncs can be triggered manually from the portal detail page, scheduled to run automatically at a set interval, or triggered via the API or MCP. Each sync type (properties, workflows, segments, forms) runs independently.
-
Property Group
- A HubSpot label that organises related properties together in the CRM record view. In Template Manager, property groups can be saved and deployed as their own template type, ensuring the correct groupings exist in the target portal before properties are created — since HubSpot requires the group to exist before a property can be assigned to it.
-
Portal
- A connected HubSpot account. Template Manager connects to portals via HubSpot OAuth and syncs their objects into a local cache. A single Template Manager account can connect multiple portals — useful for agencies managing configurations across many client accounts. Portal limits depend on your plan.
-
MCP (Model Context Protocol)
- An open standard that lets AI assistants interact with external tools through a structured interface. Template Manager's MCP server lets you use Claude, Cursor, Windsurf, or any compatible AI assistant to list portals, save templates, create and update bundles, trigger syncs, and deploy configurations — all through natural language, without opening a browser. Connect via Settings → API Keys.
Something unclear or missing? Request access and ask →