Skip to content
Book a build

Free tool

HubSpot property CSV builder: validate a spreadsheet and bulk create properties

Paste rows of property definitions from a spreadsheet. The tool checks each row against HubSpot's documented rules, then gives you batch-create request bodies, a curl script, a clean CSV and a Markdown brief.

Free, no sign-up. Data checked .

Copy the cells from Excel or Google Sheets (tab-separated) or paste CSV. Leave name blank to generate it from the label. Separate options with semicolons, and write value:Label to set an option's internal value.
Download blank template

Runs in your browser. Nothing you paste leaves this page, and the tool never asks for a HubSpot token: the curl script uses a $HUBSPOT_TOKEN placeholder you set on your own machine.

Checks and outputs

Paste your rows (or load the sample) and press Check rows and build. You get each row's errors and warnings, then batch request bodies, a curl script, a clean CSV and a Markdown brief to copy or download.

Columns the tool reads

Headers are matched loosely: internal name, internalName and name all work, as do displayName and isUnique. Columns in any order; others are ignored.

ColumnRequiredWhat to put in it
labelYesWhat users see, e.g. Renewal date.
nameNoInternal name. Leave blank to generate one from the label.
objectYescontacts, companies, deals, tickets, or a custom object ID such as 2-3465404.
groupYesThe group's internal name, e.g. contactinformation or customer_success.
typeYesstring, number, date, datetime, enumeration or bool. A field type name such as "Dropdown select" also works.
fieldTypeNotext, textarea, phonenumber, html, file, number, date, select, radio, checkbox or booleancheckbox. Blank uses the usual one for the type.
descriptionNoHelp text shown in HubSpot.
optionsNoSemicolon-separated. Write value:Label to set an option's internal value, or just Label to generate it.
uniqueNoyes or blank. Sets hasUniqueValue, which can't be changed later.

What the tool checks, and why

"HubSpot docs" rules come from HubSpot's developer reference and Knowledge Base, checked on October 29, 2026. "Safe default" rules fill gaps where HubSpot's docs are silent, so a request doesn't fail on something undocumented.

RuleFlagged asBasis
Every property needs name, label, type, fieldType and groupName. Error HubSpot docs
Batch create reference
type and fieldType must be a valid pair, e.g. enumeration with select, radio, checkbox or booleancheckbox; bool with booleancheckbox; string with text or textarea. Error HubSpot docs
CRM properties guide
Dropdown, radio and checkbox properties (type enumeration) need options, each with a label and a value. Error HubSpot docs
Batch create reference
Internal names are at most 100 characters and can't be edited after creation. Error HubSpot docs
Property editor article
Up to 5,000 options or 512,000 bytes of options per property, whichever comes first, and each option up to 3,000 characters (label, value and description together). HubSpot doesn't say how it counts the bytes, so the tool adds up every option's label and value in UTF-8. Error HubSpot docs
Property field types article
Up to ten unique value properties per object; set only at creation. Your existing unique properties count too. Error HubSpot docs
Validation rules article
Unique values are offered for single-line text, multi-line text, phone number and number properties. Warning HubSpot docs
Validation rules article
object_coordinates and json types are internal only and can't be created. Error HubSpot docs
CRM properties guide
A name that already exists on the object is rejected. The tool knows the default names in HubSpot's object guides and duplicates inside your paste. Error HubSpot docs
Object API guides
Internal names use only letters, numbers and underscores and start with a letter. HubSpot's reference publishes no character rule; this is the format of HubSpot's own names. Error Safe default
Object API guides (examples)
Lowercase internal names and option values; don't reuse the hs_ prefix HubSpot uses for its own properties. Warning Safe default
Naming convention
groupName is the group's internal name, and the group must exist before the batch runs. The curl script creates groups first. Warning HubSpot docs
Property group reference
Calculated properties (calculation_equation) need a formula, which this builder doesn't write. Create them in HubSpot. Error Safe default
Batch create reference
Requests are split into batches of up to 100. HubSpot doesn't state a limit for properties; its object guides limit batches to 100 records. Note Safe default
Contacts API guide

Ways to bulk create HubSpot properties

HubSpot has no import for a file of property definitions: its import tool imports records. These are the routes that work:

RouteHow it worksBest for
Property editorSettings > Properties > Create property, one at a timeA few one-off fields
Create during an importOn the mapping step, create a new property for an unmapped column, set up by handA handful of fields that arrive with data
Batch APIPOST /crm/v3/properties/{objectType}/batch/create with an inputs list, one object per requestDozens of fields, or the same set in several portals
Jetstack AI Bulk Create PropertiesA wizard that takes a table or CSV upload, creates the group, then each property, and reports HubSpot’s result for eachOne object and group at a time, no code
Jetstack AI ProjectsUpload a build spec (Markdown, CSV and others) and Jetty plans the properties alongside pipelines and workflowsProperties that are part of a wider build
Portal reuseCopies property sets from one connected portal to anotherFields that already exist somewhere else

This tool writes the batch API requests. The Markdown brief works as a Projects build spec, and the answer on bulk creating properties compares the routes in more detail. For the request fields and scopes, see creating a property with the HubSpot API.

Copying properties from another portal

If the properties already exist in a client’s portal, start from HubSpot’s export of all properties: it lists each property’s internal name, type, group and options. Copy those columns into the blank template to recreate the set in a new portal. With Portal reuse, Jetstack AI creates missing groups, reuses properties with the same internal name, adds missing dropdown options without removing existing ones, and creates a suffixed copy with a warning when types clash. It also copies calculated properties, remapping each formula to the destination’s property names and creating its inputs first, and supported rollups (count, sum, min, max, average, earliest and latest date), stopping with an explicit error on a rollup it can’t copy. Score properties are mapped to an existing score in the destination. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. More in importing custom properties from another portal.

Naming before you create

Internal names can’t be edited after creation, so the batch is the last cheap moment to get them right:

  • Lowercase words joined by underscores, at most 100 characters: renewal_date, cs_health_score.
  • A short team or source prefix if many people create fields. Not hs_, which HubSpot uses for its own properties.
  • The same field gets the same internal name on every object and every portal.
  • Option values in lowercase too (multi_year), because imports and workflows match on values, not labels.

The full scheme is in HubSpot property naming conventions.

Choosing type and field type

type is how HubSpot stores the value; fieldType is how it’s edited.

  • Text: string with text (single line) or textarea (multi-line). Use these for IDs from other systems; only text, phone number and number properties offer unique values, up to ten per object.
  • Choices: enumeration with select, radio or checkbox (multiple). These need options: up to 5,000, or 512,000 bytes of options, whichever is reached first.
  • Yes or no: bool with booleancheckbox.
  • Dates: date or datetime, both with fieldType date.
  • Numbers: number with number. A number that’s really a code, like a ZIP code, belongs in text.

Changing a type later can affect stored values, filters and workflows, so settle it in the sheet. If you’ll load data next, build the import file from HubSpot’s import templates and match dropdown columns to the option values listed here.

HubSpot property CSV builder

Questions about this tool.

Can I import a CSV of property definitions straight into HubSpot?

Not as definitions. HubSpot's import tool imports records. While mapping an import you can create a new property for an unmapped column, but you set each one up by hand. For a whole file of definitions, use the properties batch create endpoint (this tool writes the requests for you) or a tool that reads a CSV, such as Jetstack AI's Bulk Create Properties wizard.

How many properties can one batch request create?

HubSpot's reference for the properties batch create endpoint doesn't state a maximum. HubSpot's CRM object guides limit batch operations to 100 records at a time, so the tool splits each object's list into requests of up to 100 properties. If HubSpot rejects a request for its size, split it further.

Why does the tool flag an internal name HubSpot might accept?

Some checks come straight from HubSpot's documentation: the required fields, valid type and field type pairs, the 100-character internal name, ten unique value properties per object, and 5,000 options or 512,000 bytes of options per property. HubSpot's API reference doesn't publish an allowed character set, so the tool also holds names to lowercase letters, numbers and underscores starting with a letter, the format HubSpot's own internal names use. The rules table shows which check is which.

Sources

HubSpot changes often. Spotted something out of date? Tell us at team@jetstack.ai.

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