Migrate Custom Objects Into HubSpot Without Breaking Associations

How to Migrate Custom Objects Into HubSpot Without Breaking Associations

A migration can pass every count check and still fail the people who use it. The deals are all there, with none of them showing which company they belong to. The loans landed in HubSpot, and service reps can’t see which loan a ticket is about. Reports built on those links come back empty, and workflows that depend on an associated record never fire.

Records and the links between them travel separately. A source system stores a relationship as an ID on one record pointing to another. HubSpot stores it as an association between two record IDs it assigns when the records arrive. With nothing connecting the old ID to the new one, the records make it across and the relationship does not.

What You’ll Find Inside

You finish knowing how to move custom objects into HubSpot so every record lands connected to the right contacts, companies, deals, and other records from the first day. A 10-step method covers it, from checking what your portal can hold through building the matching keys that rebuild every association, loading parents before children, and reconciling both directions before anyone signs off. Each step ends with a checkpoint and comes with a worksheet, and a fillable workbook of all 10 arrives with the download.

What is a custom object in HubSpot?
Do I need HubSpot Enterprise to use custom objects?

Yes. Custom objects and custom object pipelines both require an Enterprise subscription. Access depends on the account’s subscription, so one Enterprise hub covers custom objects across the whole account. On Starter or Professional, your data lands in standard objects, properties, and associations. Professional accounts can create custom association labels, which carry a lot of relationship detail with no custom object involved.
How many custom objects can I create?

Enterprise accounts have a limit on custom objects and custom properties, and you can see where you stand under Data Management, then Data Model, then the Limits tab. HubSpot publishes the current numbers in its Products & Services catalog. A connected integration can carry a cap of its own, and HubSpot’s knowledge base lists the native Salesforce integration at up to 10 custom objects per account. A one-time load through CSV or the API counts only against your portal limit.
What is the difference between a custom object and a custom property?

A property holds one value about one record, like a status or a category from a lookup list. A custom object holds many related records, each with its own fields, dates, and history. The test is how many exist per parent record. One value points to a property. Many records with their own detail point to a custom object. Our decision framework guide walks through nine questions for the cases that could go either way.
What should we document before connecting HubSpot to another system?

Start with how each piece of data moves today. A data flow matrix gives each data element one row and follows it through three states: how it moves now including manual steps, what changes once the team works in HubSpot with nothing connected, and what the integration automates. Record the integration point as a yes or no with the reason, plus the owning system. A no is as useful as a yes, and any row with no owner needs settling before mapping starts.

Who This Is For

RevOps and CRM teams planning a migration from Salesforce, Zoho, Podio, or another system holding custom data
HubSpot admins deciding which source objects become custom objects and which belong on standard ones
Teams facing a portal custom object limit or an integration sync cap they have to design around
Anyone who has migrated before and arrived with records in place and relationships missing
Operations leads scoping a migration ahead of a source system contract ending

Download Now