On this page
What HubSpot supports natively
| Change | Allowed? | What HubSpot says |
|---|---|---|
| Label | Yes | Edit any time |
| Internal name | No | Can’t be edited after creation |
| Object type | No | Can’t be edited after creation |
| Field type | Yes, with care | Can invalidate current values; export your data first |
| To or from Score / Calculation | No | Those types can’t be converted in either direction |
| Text to dropdown | Yes | Each unique text value becomes an option |
| Dropdown options | Yes | Options can be edited after creation |
| Properties in use | Limited | Some edits are blocked on certain default properties and on properties used in records or tools |
Field type changes can take up to 30 minutes to show everywhere in the account.
How to change a HubSpot property’s internal name
Because the internal name is fixed, “renaming” means replacing:
- Export the old property’s definition (More > Export property definition). The usage file lists every tool that uses it, with links.
- Create the new property with the right internal name, the same type and the same option values.
- Copy the values. Export records with the old property and Record ID, then import them into the new property. For live data, a workflow that copies the value on change can bridge the gap.
- Repoint every asset: workflows (triggers, branches and actions), forms, segments, reports, property cards and views.
- Update integrations that read or write the old internal name. They may not appear in HubSpot’s usage list.
- Archive the old property once nothing blocks it. See deleting a property that’s in use.
How to change a field type safely
- Export the property’s values first, or its property history.
- Normalise the values if you’re moving to a dropdown, so you don’t create near-duplicate options.
- Check workflows and filters that compare values; a number filter won’t work on a text field.
- Make the change and check a sample of records after 30 minutes.
Common mistakes
- Creating
lead_source_2. A replacement with a numbered name causes the confusion you were fixing; follow a naming convention. - Forgetting integrations. External systems break silently when an internal name disappears.
- Changing types in a production portal first. Try it in a sandbox or on a test property.
Where Jetstack AI fits
Jetstack AI can’t rename internal names either, since HubSpot doesn’t allow it. When Portal reuse deploys a property and the destination already has one with the same internal name but a different type, it doesn’t overwrite it: it creates a separately named property and logs a warning so you can reconcile them. See how properties are deployed. For steps 2 and 4, Projects (currently in limited release) can build the correctly named property and corrected replacement workflows from a brief, with the workflows created switched off; copying the values stays an export and import you run, and you retire the old assets in HubSpot.
Sources
- Create and edit properties (HubSpot Knowledge Base)
- Organize, archive and export properties (HubSpot Knowledge Base)
- Properties (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
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse