Steps
- Check the subscription. Custom objects need Enterprise in Marketing, Sales, Service, Data, Content, Smart CRM or Revenue Hub, and there are limits on how many objects and properties you can have.
- Define the object. Give it a primary display property, a unique-value property such as “Source ID”, and its association to Companies (and to Contacts or Deals if needed).
- Load the companies first, with domains, or note their Record IDs.
- Build the file:
| Source ID | Name | Status | Renewal date | Company domain |
|---|---|---|---|---|
| SUB-1001 | Gold plan | Active | 2027-03-01 | acme.com |
| SUB-1002 | Add-on seats | Active | 2027-03-01 | acme.com |
| SUB-1003 | Starter plan | Cancelled | 2025-12-31 | globex.com |
- Import multiple objects in one file: the custom object plus Companies. Map Source ID as the custom object’s unique identifier and Company domain to Company > Company domain name (or Record ID).
- Spot-check a few companies to confirm the custom records show in the association card.
What the native tools do / where they stop
| Tool | Custom objects |
|---|---|
| Smart Transfer | ”The transfer of custom objects isn’t supported” |
| Import tool | Supported in single- and multi-object imports; matches on Record ID or a unique-value property |
| HubSpot paid CRM Data Migration | Bronze: none; Silver: up to 2; Gold: up to 4 |
| APIs | Full support, with the same plan limits |
HubSpot doesn’t give a worked example of linking custom objects to companies. In practice, the problem behind the community thread is identifiers. Companies without domains can’t be matched by domain, so export their HubSpot Record IDs after you load them and join those into the custom object file. And if the source has custom-to-custom relationships, such as a subscription with its invoices, load the parent object first, then the child, with the parent’s unique ID in each row.
Where FlitStack AI fits
FlitStack AI detects custom objects in the source and proposes the HubSpot schema and associations for your review. It then loads them in parent-to-child order. See the HubSpot import guide or HubSpot migrations.