---
title: "Change a HubSpot property internal name or field type"
description: "Whether you can change a HubSpot property internal name or field type, what breaks when you do, and how to replace a property without losing its data."
url: "https://jetstack.ai/answers/change-hubspot-property-internal-name/"
---

# Can I change a HubSpot property's internal name or field type?

You can't change a HubSpot property's internal name or object type after it's created; only the label and settings are editable. You can change the field type, but HubSpot warns it can invalidate stored values and score or calculation types can't be switched. To change the internal name, create a new property, copy the values across, repoint every asset that uses the old one, then archive it.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

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:

1. **Export the old property’s definition** (More > Export property definition). The usage file lists every tool that uses it, with links.
2. **Create the new property** with the right internal name, the same type and the same option values.
3. **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.
4. **Repoint every asset**: workflows (triggers, branches and actions), forms, segments, reports, property cards and views.
5. **Update integrations** that read or write the old internal name. They may not appear in HubSpot’s usage list.
6. **Archive the old property** once nothing blocks it. See [deleting a property that’s in use](https://jetstack.ai/answers/delete-hubspot-property-in-use).

## How to change a field type safely

1. **Export the property’s values** first, or its [property history](https://jetstack.ai/answers/export-hubspot-property-history).
2. **Normalise the values** if you’re moving to a dropdown, so you don’t create near-duplicate options.
3. **Check workflows and filters** that compare values; a number filter won’t work on a text field.
4. **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](https://jetstack.ai/answers/hubspot-property-naming-conventions).
- **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](https://jetstack.ai/roll-out) 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](https://jetstack.ai/docs/implementations/asset-types/properties). For steps 2 and 4, [Projects](https://jetstack.ai/build) (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)](https://knowledge.hubspot.com/properties/create-and-edit-properties)
- [Organize, archive and export properties (HubSpot Knowledge Base)](https://knowledge.hubspot.com/properties/organize-and-export-properties)
- [Properties (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/asset-types/properties)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

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](https://jetstack.ai/roll-out)

On this page

HubSpot admin

## Related questions.

Can I change a HubSpot property's internal name or field type?

You can't change a HubSpot property's internal name or object type after it's created; only the label and settings are editable. You can change the field type, but HubSpot warns it can invalidate stored values and score or calculation types can't be switched. To change the internal name, create a new property, copy the values across, repoint every asset that uses the old one, then archive it.

Why can't HubSpot let me rename the internal name?

Imports, workflows, integrations and the API refer to properties by internal name. HubSpot keeps it fixed so those references don't break. Change the label instead if only the wording is wrong.

What happens if I change a text property to a dropdown?

HubSpot creates an option for each unique text value, so variations like LinkedIn and linkedin become separate options. Clean the values before you switch.

How long does a field type change take?

HubSpot says it can take up to 30 minutes for the change and your data to be fully reflected across the account.
