On this page
What HubSpot supports natively
| Topic | What HubSpot says |
|---|---|
| Where | Data Management > Data Model, graph view, the object’s three-dot menu |
| Permissions | Account access permissions to create, edit and manage custom objects |
| Blockers | You can’t delete a custom object that other tools are using |
| Finding blockers | View object usage in the same menu |
| Confirmation | Tick a box acknowledging the object can’t be restored, then Delete object |
| Restore | Not possible |
| Alternatives | Edit the object’s names, description and display properties instead; the internal name can’t change |
HubSpot’s article doesn’t say what happens to the object’s records, properties and associations, or whether the name can be reused afterwards, so plan as if everything attached to the object goes with it.
How to delete a custom object in HubSpot
- Make sure you mean it. If the object only has the wrong label, edit the singular and plural names instead.
- Find what uses it. In the data model, open the object’s menu and choose View object usage. Note every tool listed.
- Remove each reference. Edit or delete each tool that depends on the object. Check integrations as well; they won’t stop you deleting, but they’ll fail afterwards.
- Export its records. Export the object’s records with all properties and associations, and its property list. A CRM backup includes custom objects too, but not associations.
- Delete it. Open the object’s menu again, choose delete, tick the acknowledgement and click Delete object.
- Check the limits tab. Your custom object count on Data Management > Data Model > Limits should drop.
Common mistakes
- Deleting to rename. The internal name is fixed, but the visible names aren’t; renaming the labels is enough for most cases.
- Deleting during an integration sync. Pause the integration first or it will log errors.
- Building test objects in production. Use a sandbox for experiments so you never need this page. Before creating a new object, check whether you need one at all.
Where Jetstack AI fits
If the custom object came from a Jetstack AI Portal reuse deployment, you can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. See rolling back a deployment.
Sources
- Create custom objects (HubSpot Knowledge Base)
- Back up CRM data (HubSpot Knowledge Base)
- Rolling back a deployment (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