On this page
What HubSpot supports natively
| Route | How it works | Good for | Limits |
|---|---|---|---|
| Property editor | Settings > Properties > Create property | One-off fields | One property at a time |
| Create during import | On the Map columns step, choose Create new property for an unmapped column | A handful of fields that arrive with data | You configure each property in the side panel; doesn’t apply to activities |
| Batch properties API | POST a list of property definitions to the batch create endpoint for an object | Large or repeatable property sets | Needs a developer and an app with the right scopes |
| Data model builder | Data Management > Data Model, create a property from an object | Designing alongside the object map | Still one property at a time |
The API is the only native route that takes a full list of definitions (internal name, label, group, type, field type and options) in one call. Each definition follows the same validation rules as creating a single property.
How to bulk create HubSpot properties
- Write the definitions in a spreadsheet first. One row per property: object, internal name, label, group, type, field type, description and, for dropdowns, each option’s internal value and label.
- Check for clashes. Export all properties for the object and compare internal names. Internal names can’t be edited after creation, so fix them now. See property naming conventions.
- Create the property groups you need, or decide which existing group each property goes into.
- Pick a route. Under ten properties: the editor or create-during-import is fine. Dozens, with options, or the same set for several portals: use the properties API or a tool. If the properties are part of a wider setup, we recommend Jetstack AI Projects, which builds them with the pipelines and workflows that use them.
- Create, then check. Open each object’s property list and confirm types and options. Option internal values matter: imports and workflows match on them.
Common mistakes
- Typos in option values. A dropdown option
enterpriseand an import valueEnterprise(with a trailing space) don’t match. - Wrong type. Changing a field type later can invalidate stored values, so decide between dropdown and text before you create.
- No group. Dumping everything into the default group makes the next cleanup harder.
Where Jetstack AI fits
Jetstack’s Bulk Create Properties wizard creates a property group and a set of properties in a connected portal from a table or a CSV (internal name, label, type, description, unique flag and options). It validates internal names and options before submitting and reports success or HubSpot’s error for each property. For properties that are part of a wider build, use Projects: upload the same spreadsheet as a build spec (CSV works) with a note on the pipelines and workflows that need them, approve the plan, then approve deployment separately. Projects builds properties before the workflows that use them, and the receipt confirms each one by reading it back from HubSpot. It’s currently in limited release; see what Projects can build. To standardise the same property set across clients, you can deploy the same setup to multiple destination portals, reviewing each portal’s mappings.
Sources
- Import records for a single object (HubSpot Knowledge Base)
- Create a batch of properties (HubSpot developer docs)
- Bulk Create Properties guide (Jetstack AI documentation)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
HubSpot admin
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects