Metadata Types
HubSpot Deploy supports the following HubSpot metadata types for backup, comparison, and deployment.
Beta
Additional metadata types are being added. Request a type if you need something not listed here.
Supported types
| Type | Backup | Compare | Deploy | Notes |
|---|---|---|---|---|
| Contact properties | ✓ | ✓ | ✓ | |
| Contact property groups | ✓ | ✓ | ✓ | |
| Deal properties | ✓ | ✓ | ✓ | |
| Deal pipelines & stages | ✓ | ✓ | ✓ | |
| Company properties | ✓ | ✓ | ✓ | |
| Ticket properties | ✓ | ✓ | ✓ | |
| Ticket pipelines & stages | ✓ | ✓ | ✓ | |
| Custom objects (schema) | ✓ | ✓ | ✓ | Requires HubSpot Enterprise |
| Custom object properties | ✓ | ✓ | ✓ | Requires HubSpot Enterprise |
| Workflows | ✓ | ✓ | — | Deploy coming soon |
| Forms | ✓ | ✓ | — | Deploy coming soon |
| Email templates | ✓ | ✓ | — | Deploy coming soon |
| Lists | ✓ | ✓ | — | |
| Owner records | ✓ | ✓ | — | Read-only in HubSpot |
| Teams | ✓ | ✓ | — |
How metadata is stored in Git
Each metadata type is stored as a JSON file in a structured directory layout:
hubspot-metadata/
├── contacts/
│ ├── properties.json
│ └── property-groups.json
├── companies/
│ ├── properties.json
│ └── property-groups.json
├── deals/
│ ├── properties.json
│ ├── property-groups.json
│ └── pipelines.json
├── tickets/
│ ├── properties.json
│ └── pipelines.json
├── custom-objects/
│ └── {object-name}/
│ ├── schema.json
│ └── properties.json
├── workflows/
│ └── workflows.json
├── forms/
│ └── forms.json
└── ...
HubSpot plan requirements
Some metadata types require specific HubSpot plans:
| Metadata type | Minimum plan |
|---|---|
| Custom objects | Enterprise |
| Workflows | Professional or Enterprise |
| All other types | Starter or above |