Summary

An iPaaS.com Company can be transferred to HubSpot as a HubSpot company, either automatically when the iPaaS.com event system is configured to send company changes, or on demand from the iPaaS.com Manual Sync page. Company creation and company updates are handled by two separate collections, and which one runs is decided by whether the iPaaS.com Company is already linked to a HubSpot company. The company's relationships travel with it as HubSpot associations.

ID Format

Manual Sync ID Format

Enter the iPaaS.com Company id on the iPaaS.com Manual Sync page to transfer that company to HubSpot.

External ID Format

The HubSpot company id assigned when the company is created is recorded as the external-id link on the iPaaS.com Company. That link is what routes every later change to the Update HubSpot Company FROM iPaaS.com collection instead of creating a second company.

Deleted Record Support

Outbound delete is not supported. Deleting a company in iPaaS.com does not delete or deactivate the company in HubSpot, delete mappings are not included in the default templates, and deletions do not propagate in any form. Removing a company in HubSpot is a manual action performed under a supervised process.

Custom Field Support

Custom fields are not supported in this direction. At the time this documentation was written, an iPaaS.com Company custom field is not written to a HubSpot company property, so adding a custom field mapping to this collection does not populate a property on the HubSpot company. See Additional Notes.

Two custom fields are read by the default template mappings as a source for standard HubSpot properties: HubSpot Owner Email, used to resolve the company owner, and HubSpot LifeCycleStage Name, used to resolve the lifecycle stage. Both are empty by default, so neither the owner nor the lifecycle stage is set until the corresponding custom field carries a value. These two mappings target standard HubSpot properties rather than custom properties.

Mapping Collection Status

Status: Enabled. Both company collections and both association collections are enabled.

Trigger Events: These are FROM iPaaS.com collections, so they are driven by iPaaS.com outbound triggers, which subscribers or their MiSP enable under Outbound Data Flows in the subscription configuration. Subscribe to the iPaaS.com Company create and update events that should dispatch a transfer. No automatic transfers occur until those subscriptions are enabled. Manual Sync is available on the parent collections regardless. Whether a given transfer runs as an Add or an Update is decided by the external-id link, not by which event was raised.

Duplicate or Conflicting Mappings

No duplicate check is performed when a company is transferred to HubSpot, because names, email addresses, and website addresses are used inconsistently across HubSpot company records.

HubSpot does not deduplicate companies created through an API, including companies created by an integration. A company transferred from iPaaS.com is therefore created in HubSpot even when a similar company already exists there. Where similar companies exist on both platforms, this can produce two HubSpot records for one business. If a merge is performed in HubSpot to resolve this, the resulting record should be the one linked to iPaaS.com so it remains usable for future transfers.

The other collection that operates on the same entity is Add/Update HubSpot Company TO iPaaS.com, the opposite-direction collection. Review the filters and Add/Update settings across all three collections, and decide which system is the source of truth for a given field, before enabling a bi-directional company sync.

Supported Child Collections

Add HubSpot Company Association FROM iPaaS.com: creates the company's HubSpot associations from the iPaaS.com company relationships when the company itself is being created. It runs under Add HubSpot Company FROM iPaaS.com.
Update HubSpot Company Association FROM iPaaS.com: maintains the associations of a company that is already linked, and carries associations added in iPaaS.com after the company was created. It runs under Update HubSpot Company FROM iPaaS.com.

Which child runs follows the parent that ran, which in turn follows the link state of the iPaaS.com Company. Each association is linked back through the related record's own external-id link, so an association is only written once both ends of the relationship exist in HubSpot.

System Caveats

HubSpot Caveats

Owner and lifecycle stage are opt-in: both are resolved from iPaaS.com custom fields that are empty by default, so neither is set unless the corresponding custom field carries a value. Either mapping may be changed to a static value if the owner id or stage id is known.
Owner email lookup: resolving an owner by email address costs an additional lookup against HubSpot. Setting the owner id directly performs better than searching by email.
Company category property: the property named in the Company Category Field Name setting must exist in HubSpot beforehand as a Dropdown select property on the Company object, with at least one option defined.
Rate limiting: at the time this documentation was written, the integration does not wait and retry when HubSpot throttles it. A throttled transfer fails and must be re-run. The failure is reported under Dashboard, Integration Monitoring, Error Logs.

iPaaS.com Caveats

One address is sent: the address mappings read the iPaaS.com Company's primary billing address, because standard HubSpot company fields hold a single address entry. An iPaaS.com company with no address flagged as primary billing sends no address to HubSpot. Change these mappings if a different address should populate the HubSpot address.
Parent company: a HubSpot parent company is set from a relationship record with type Parent Company whose related id is the iPaaS.com company. It is not set from the company's own field mappings.
Categories are opt-in: the company's category assignments transfer only when the Company Category Field Name subscription setting names a HubSpot property. Leaving that setting empty disables company category processing entirely, and no error is raised.

Setup Requirements

iPaaS.com Configuration

Enable the iPaaS.com Company create and update outbound triggers under Outbound Data Flows on the subscription. No automatic transfers occur until they are enabled.
Create the HubSpot Owner Email and HubSpot LifeCycleStage Name custom fields on the Company module if the owner or lifecycle stage should be set.
Populate the Company Category Field Name subscription setting if company categories should transfer.

HubSpot Configuration

Create the company category property named in Company Category Field Name as a Dropdown select property with at least one option defined.
Confirm the connected HubSpot account can create and edit companies.

Authentication and connection setup are covered in HubSpot Installation Instructions and HubSpot Connections and Settings.

Integration Flow

An iPaaS.com company create or update, or a manual sync, dispatches the company transfer.
The integration resolves whether the iPaaS.com Company is already linked to a HubSpot company. When there is no link, the Add HubSpot Company FROM iPaaS.com collection runs; when a link exists, Update HubSpot Company FROM iPaaS.com runs instead.
The mapped company properties are assembled, including any custom field values.
When the iPaaS.com Company carries category assignments and the Company Category Field Name setting is populated, each category value is added to the HubSpot company category property first, so the value exists before the company references it.
On Add, the HubSpot company is created from the assembled properties and the new HubSpot company id is saved as the external-id link. On Update, the linked HubSpot company is updated in place.
The company's relationships are written to HubSpot as contact and company associations through the association child collections.
Only the values the transfer actually has are sent. Properties that are not mapped are never blanked.

Mappings

Add HubSpot Company FROM iPaaS.com (Parent)

iPaaS.com data type: Customer Company

This collection creates a new company in HubSpot from an iPaaS.com Company. It runs only when the iPaaS.com Company has no HubSpot company linked to it yet, so it maps no id field and lets HubSpot assign the new company id.

Mapping Type	Source Field (iPaaS.com)	Destination Field (HubSpot)	Description
Field	Name	Name	Recommended. The iPaaS.com Company Name, written to the HubSpot company name. HubSpot advises including at least one of name or domain when a company is created. The iPaaS.com Company name always carries a value — iPaaS.com requires it — so this mapping is the reliable way to satisfy that guidance for every company.
Field	Url	Domain	Recommended. The iPaaS.com Company website address, written to the HubSpot company domain. HubSpot treats the company domain as the primary unique identifier for avoiding duplicate companies and recommends always including it, so populating the website address on the iPaaS.com Company makes the resulting HubSpot record easier to recognise and merge if needed. This value is empty when the iPaaS.com Company has no website address, in which case HubSpot receives only the name.
Field	PhoneNumber	Phone	Optional. The iPaaS.com Company phone number, written to the HubSpot company phone number.
Dynamic Formula	`var value = GetCustomFieldValue(CustomFields, "HubSpot LifeCycleStage Name"); if(value!=null && value!=""){ return await GetLifeCycleStageIdByName(value); } return null;`	Lifecyclestage	Optional. Sets the lifecycle stage of the new HubSpot company. The formula reads the iPaaS.com Company custom field named HubSpot LifeCycleStage Name; when it holds a stage name, the matching HubSpot lifecycle stage id is resolved and set. When the custom field is empty, no stage is set and HubSpot applies its own default. To use this mapping, create a Company module custom field in iPaaS.com named HubSpot LifeCycleStage Name and provide the stage name on the company. To place every new company at the same stage instead, replace the formula with one that resolves a fixed stage name such as Customer, or set a known stage id as a static value. Because this mapping runs only when a company is created, a stage set here is a starting point: later edits in HubSpot are not undone by this collection.
Dynamic Formula	`var value = GetCustomFieldValue(CustomFields, "HubSpot Owner Email"); if(value!=null && value!=""){ return await GetOwnerIdByEmail(value); } return null;`	HubSpotOwnerId	Optional. Sets the owner of the new HubSpot company.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Address1")`	Address	Optional. Finds the first address on the iPaaS.com Company that is flagged as the primary billing address and returns its Address1 value for the HubSpot company address. Standard HubSpot company fields hold a single address entry, which is why the template selects one specific iPaaS.com address rather than sending them all. If the iPaaS.com Company has no address flagged as primary billing, this mapping returns empty. Change the filter condition if a different address should populate the HubSpot address.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Address2")`	Address2	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its Address2 value — the second address line, such as a suite or unit number. Empty when the iPaaS.com address has no second line, or when no address is flagged as primary billing.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "City");`	City	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its City value for the HubSpot company city.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Region");`	State	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its Region value for the HubSpot company state. The iPaaS.com field is named Region because it holds states, provinces, and equivalent divisions; HubSpot stores it as State.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "PostalCode");`	Zip	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its PostalCode value for the HubSpot company postal code.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Country");`	Country	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its Country value for the HubSpot company country.
Field	Description	AboutUs	Optional. The iPaaS.com Company description, written to the HubSpot About Us property.
Dynamic Formula	`return await GetHubSpotCategoryValuesFromCategories(Categories);`	CompanyCategories	Optional. Combines the iPaaS.com Company's category assignments into a list of HubSpot category values and supplies them to the company. Only categories that have been transferred to HubSpot and carry a link contribute a value. The categories reach the HubSpot company property named in the Company Category Field Name subscription setting. That property must be created in HubSpot beforehand as a Dropdown select property on the Company object. Leaving the setting empty disables company category processing entirely. Important: HubSpot holds a single property for the category designation, so when the iPaaS.com Company carries several category assignments, only one of them appears in HubSpot — the last one processed becomes the final property value. This functionality is best suited to a single category assignment per company.

HubSpotOwnerId

Optional. Sets the owner of the new HubSpot company. The formula reads the iPaaS.com Company custom field named HubSpot Owner Email; when it holds a value, the owner is resolved by that email address and the resulting owner id is set on the company. When the custom field is empty, no owner is set.

To use this mapping, create a Company module custom field in iPaaS.com named HubSpot Owner Email and provide the owner's email address on the company. Resolving an owner by email costs an extra lookup against HubSpot on every transfer, so if the owner id is already known, replacing this formula with a static owner id performs better.

Update HubSpot Company FROM iPaaS.com (Parent)

iPaaS.com data type: Customer Company

This collection maintains a company that is already linked to a HubSpot company. It resolves that HubSpot company id first, then applies the mapped values to the existing record.

Placeholder value — replace during implementation: the Update collection ships with the same field set as the Add collection, so every mapped field is re-applied each time the record is updated. Subscribers or their MiSP should adjust the mappings in this collection to match their operations — for example, by removing fields that should be set only when the record is first created.

Mapping Type	Source Field (iPaaS.com)	Destination Field (HubSpot)	Description
Field	Name	Name	Recommended. The iPaaS.com Company Name, written to the HubSpot company name. HubSpot advises including at least one of name or domain on a company. The iPaaS.com Company name always carries a value — iPaaS.com requires it — so this mapping is the reliable way to satisfy that guidance for every company. Because this mapping runs on every update, a company renamed in HubSpot is renamed back to the iPaaS.com value on the next transfer. Remove this mapping if HubSpot should own the company name.
Field	Url	Domain	Recommended. The iPaaS.com Company website address, written to the HubSpot company domain. HubSpot treats the company domain as the primary unique identifier for avoiding duplicate companies and recommends always including it. This value is empty when the iPaaS.com Company has no website address. An empty value is not sent, so a domain already present on the HubSpot company is left as it is rather than being cleared.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "City");`	City	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its City value for the HubSpot company city.
Field	PhoneNumber	Phone	Optional. The iPaaS.com Company phone number, written to the HubSpot company phone number.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Region");`	State	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its Region value for the HubSpot company state. The iPaaS.com field is named Region because it holds states, provinces, and equivalent divisions; HubSpot stores it as State.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Address1");`	Address	Optional. Finds the first address on the iPaaS.com Company that is flagged as the primary billing address and returns its Address1 value for the HubSpot company address. Standard HubSpot company fields hold a single address entry, which is why the template selects one specific iPaaS.com address rather than sending them all. If the iPaaS.com Company has no address flagged as primary billing, this mapping returns empty and the HubSpot address is left as it is. Change the filter condition if a different address should populate the HubSpot address.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Address2");`	Address2	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its Address2 value — the second address line, such as a suite or unit number. Empty when the iPaaS.com address has no second line, or when no address is flagged as primary billing.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "Country");`	Country	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its Country value for the HubSpot company country.
Dynamic Formula	`var value = GetCustomFieldValue(CustomFields, "HubSpot Owner Email"); if(value!=null && value!=""){ return await GetOwnerIdByEmail(value); } return null;`	HubSpotOwnerId	Optional. Sets the owner of the HubSpot company.
Dynamic Formula	`var value = GetCustomFieldValue(CustomFields, "HubSpot LifeCycleStage Name"); if(value!=null && value!=""){ return await GetLifeCycleStageIdByName(value); } return null;`	Lifecyclestage	Optional. Sets the lifecycle stage of the HubSpot company. The formula reads the iPaaS.com Company custom field named HubSpot LifeCycleStage Name; when it holds a stage name, the matching HubSpot lifecycle stage id is resolved and set. When the custom field is empty, no stage is sent and the HubSpot stage is left unchanged. To use this mapping, create a Company module custom field in iPaaS.com named HubSpot LifeCycleStage Name and provide the stage name on the company. Because this mapping runs on every update, a stage advanced in HubSpot is reset to the iPaaS.com value on the next transfer whenever the custom field holds a value. Leave the custom field empty if HubSpot should own the lifecycle stage after a company is created.
Dynamic Formula	`return FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "PostalCode");`	Zip	Optional. Finds the first address on the iPaaS.com Company flagged as the primary billing address and returns its PostalCode value for the HubSpot company postal code.
Dynamic Formula	`var ExternalId=await GetExternalIdAsync(Id, "Company", SpaceportSystemId); return ExternalId;`	Id	Required. Identifies which HubSpot company this update targets. The formula takes the iPaaS.com Company id and returns the HubSpot company id linked to it, so the update reaches the company that was previously created or matched rather than any other record. This is the mapping that makes this an update rather than a create, and it is the reason company creates and company updates are separate collections: the Add HubSpot Company FROM iPaaS.com collection has no HubSpot company id to resolve, so it carries no equivalent mapping. If an iPaaS.com Company has no HubSpot company linked to it, there is nothing for this mapping to return and the record is handled by the Add collection instead.
Field	Description	AboutUs	Optional. The iPaaS.com Company description, written to the HubSpot About Us property.
Dynamic Formula	`return await GetHubSpotCategoryValuesFromCategories(Categories);`	CompanyCategories	Optional. Combines the iPaaS.com Company's category assignments into a list of HubSpot category values and supplies them to the company. Only categories that have been transferred to HubSpot and carry a link contribute a value. The categories reach the HubSpot company property named in the Company Category Field Name subscription setting. That property must be created in HubSpot beforehand as a Dropdown select property on the Company object. Leaving the setting empty disables company category processing entirely. Important: HubSpot holds a single property for the category designation, so when the iPaaS.com Company carries several category assignments, only one of them appears in HubSpot — the last one processed becomes the final property value. This functionality is best suited to a single category assignment per company.

HubSpotOwnerId

Optional. Sets the owner of the HubSpot company. The formula reads the iPaaS.com Company custom field named HubSpot Owner Email; when it holds a value, the owner is resolved by that email address and the resulting owner id is set on the company. When the custom field is empty, no owner is sent and the HubSpot owner is left unchanged.

Because this mapping runs on every update, an owner reassigned directly in HubSpot is overwritten on the next transfer whenever the custom field holds a value. Leave the custom field empty if HubSpot should own the company owner.

Add HubSpot Company Association FROM iPaaS.com (Child)

iPaaS.com data type: Company Relationship

This collection writes the iPaaS.com Company's relationships to HubSpot as associations when the company is being created. It runs as part of the company's own transfer and cannot be triggered directly.

Mapping Filter

if (string.IsNullOrEmpty(RelatedToId))
  return false;var customerId = await GetExternalIdAsync(RelatedToId.Split("|")[0], "Customer", SpaceportSystemId);
if(customerId != null){
return true;
}
else{
var companyId = await GetExternalIdAsync(RelatedToId.Split("|")[0], "Company", SpaceportSystemId);
if(companyId != null)
    return true;
}
return false;

Filter Description. The filter decides whether a relationship is worth sending to HubSpot, and it lets through only relationships whose other end already exists in HubSpot. A relationship with no RelatedToId is skipped immediately. Otherwise the filter takes the first segment of RelatedToId — the iPaaS.com id of the record at the other end, before any appended HubSpot association tag — and looks for a Customer in iPaaS.com linked to a HubSpot contact. If it finds one, the relationship passes. If it does not, it looks for a Company linked to a HubSpot company, and the relationship passes if that is found. If neither exists, the relationship does not pass and is skipped. A skipped relationship is not an error and produces no entry in the Error Logs: it simply means the record at the other end has not reached HubSpot yet, and the association is written once it does.

Mapping Type	Source Field (iPaaS.com)	Destination Field (HubSpot)	Description
Dynamic Formula	`var customerId = await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Customer", SpaceportSystemId); if(customerId != null){ return "Customer"; } else{ var companyId= await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Company", SpaceportSystemId); if(companyId!=null){ if(Type == "Parent Company"){ return "ParentCompany"; } return "Company"; } }`	ReadOnlyRelationshipType	Required. HubSpot must know what kind of record it is associating before it can create the association, and this mapping determines that.
Dynamic Formula	`var customerId = await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Customer", SpaceportSystemId); if(customerId != null){ return customerId; } else{ return await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Company", SpaceportSystemId); }`	ReadOnlyRelationshipId	Required. HubSpot must be given the id of the record being associated, and this mapping supplies it.

ReadOnlyRelationshipType

Required. HubSpot must know what kind of record it is associating before it can create the association, and this mapping determines that. It takes the first segment of the relationship's RelatedToId — the iPaaS.com id of the record at the other end, before any appended HubSpot association tag — and looks for a Customer in iPaaS.com that is linked to a HubSpot record. If one is found, the relationship is to a contact and the mapping returns Customer.

If no linked customer is found, the formula looks for a linked Company instead. Where the relationship's type is Parent Company, it returns ParentCompany, which is how a HubSpot parent company is set from iPaaS.com; otherwise it returns Company for an ordinary company-to-company association. In HubSpot a child company can be associated with only one parent company, so a second Parent Company relationship does not add a second parent.

This mapping works together with ReadOnlyRelationshipId in this table, which resolves the same related-to-id to the HubSpot id of that record. It is not advised to alter this mapping, as it is required to support the HubSpot associations.

ReadOnlyRelationshipId

Required. HubSpot must be given the id of the record being associated, and this mapping supplies it. It takes the first segment of the relationship's RelatedToId and resolves it to the HubSpot id of the linked Customer; if there is no linked customer, it resolves the HubSpot id of the linked Company instead. The result is the HubSpot record that the newly created company is associated with.

If the related-to-id resolves to neither a linked customer nor a linked company, the collection's mapping filter skips the relationship before this mapping runs, so no association is attempted and no error is raised. It is not advised to alter this mapping, as it is required to support the HubSpot associations.

Update HubSpot Company Association FROM iPaaS.com (Child)

iPaaS.com data type: Company Relationship

This collection maintains the associations of a company that is already linked to HubSpot. It carries the same filter and the same two mappings as Add HubSpot Company Association FROM iPaaS.com, and runs as part of the company's own transfer. Its field notes are specific to this collection: it also carries associations added in iPaaS.com after the company was first created.

Placeholder value — replace during implementation: the Update HubSpot Company Association FROM iPaaS.com collection ships with the same field set as Add HubSpot Company Association FROM iPaaS.com, so every mapped field is re-applied each time the association is updated. Subscribers or their MiSP should adjust the mappings in this collection to match their operations — for example, by removing fields that should be set only when the association is first created.

Mapping Filter

if (string.IsNullOrEmpty(RelatedToId))
  return false;var customerId = await GetExternalIdAsync(RelatedToId.Split("|")[0], "Customer", SpaceportSystemId);
if(customerId != null){
return true;
}
else{
var companyId = await GetExternalIdAsync(RelatedToId.Split("|")[0], "Company", SpaceportSystemId);
if(companyId != null)
    return true;
}
return false;

Filter Description. This collection carries the same filter as Add HubSpot Company Association FROM iPaaS.com, and it behaves identically: a relationship with no RelatedToId is skipped immediately; otherwise the first segment of RelatedToId is resolved to a linked HubSpot contact, or failing that to a linked HubSpot company, and the relationship passes if either is found. If neither exists, the relationship is skipped. A skipped relationship is not an error and produces no entry in the Error Logs.

Mapping Type	Source Field (iPaaS.com)	Destination Field (HubSpot)	Description
Dynamic Formula	`var customerId = await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Customer", SpaceportSystemId); if(customerId != null){ return "Customer"; } else{ var companyId= await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Company", SpaceportSystemId); if(companyId!=null){ if(Type == "Parent Company"){ return "ParentCompany"; } return "Company"; } }`	ReadOnlyRelationshipType	Required. HubSpot must know what kind of record it is associating before it can create the association, and this mapping determines that.
Dynamic Formula	`var customerId = await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Customer", SpaceportSystemId); if(customerId != null){ return customerId; } else{ return await GetExternalIdAsync(RelatedToId.Split("\|")[0], "Company", SpaceportSystemId); }`	ReadOnlyRelationshipId	Required. HubSpot must be given the id of the record being associated, and this mapping supplies it.

ReadOnlyRelationshipType

This mapping is identical to its counterpart on Add HubSpot Company Association FROM iPaaS.com, so an association behaves the same whether the company is being created in HubSpot or updated there. It works together with ReadOnlyRelationshipId in this table, which resolves the same related-to-id to the HubSpot id of that record. It is not advised to alter this mapping, as it is required to support the HubSpot associations.

ReadOnlyRelationshipId

Reading only the first segment of the related-to-id is deliberate. Relationships that originated in HubSpot have the HubSpot association tag appended to their related-to-id by the Add/Update HubSpot Company Association TO iPaaS.com collection, so that multiple association tags on the same pair of records stay unique in iPaaS.com. Taking the portion before the appended tag is what allows those relationships to resolve correctly on the way back to HubSpot. Because this collection runs on every transfer of an established company, it is the one that returns such round-tripped associations, and the one that carries associations added in iPaaS.com after the company was created.

Error Handling

The errors these collections can raise are catalogued, with their causes and resolutions, in HubSpot Error Messages. Rather than repeat them here, the entries most relevant to company transfers are:

HubSpot API Communication: covers the messages raised when HubSpot rejects or cannot receive a company write, including the rate limit case. At the time this documentation was written, the integration does not wait and retry when HubSpot throttles it, so a throttled transfer fails and must be re-run.
Company category property errors: raised when the property named in Company Category Field Name does not exist in HubSpot, or is not a Dropdown select property with at least one option. Correct the property in HubSpot, or clear the setting to disable category processing, then re-sync the company.

Testing & Validation

Test Scenarios

Create a new iPaaS.com Company that has never been transferred, then manually sync it by its iPaaS.com Company id. Confirm a new HubSpot company is created and that the iPaaS.com Company now carries the HubSpot company id as its external-id link.
Change the name or website address on that same iPaaS.com Company and re-sync. Confirm the existing HubSpot company is updated in place and no second company appears.
Populate the HubSpot Owner Email custom field with the email address of a real HubSpot owner and re-sync. Confirm the HubSpot company owner is set. Repeat with HubSpot LifeCycleStage Name and confirm the lifecycle stage.
Flag an address on the iPaaS.com Company as primary billing and re-sync. Confirm the address, city, state, postal code, and country reach the HubSpot company. Remove the primary billing flag and confirm no address is sent.
Add a relationship between the iPaaS.com Company and a record whose counterpart has not been transferred to HubSpot, then sync. Confirm the association is skipped without an error. Transfer the related record, re-sync, and confirm the association is created.
Populate the Company Category Field Name setting with a valid HubSpot Dropdown select property, assign a category to the iPaaS.com Company, and re-sync. Confirm the category value appears on the HubSpot company property. Clear the setting and confirm category processing stops with no error raised.

Validation Checklist

A first transfer creates a HubSpot company and records the external-id link.
A second transfer of the same company updates it rather than creating a duplicate.
Fields left unmapped on the HubSpot company are not blanked by a transfer.
Owner and lifecycle stage are set only when their custom fields carry values.
Only the primary billing address reaches HubSpot.
Associations appear only once both ends of the relationship exist in HubSpot.
Errors appear under Dashboard, Integration Monitoring, Error Logs.

Additional Notes

At the time this documentation was written, iPaaS.com Company custom fields are not written to HubSpot company properties in this direction. A custom field mapping added to either company collection does not populate a property on the HubSpot company, and no error is raised. Subscribers or their MiSP should not rely on custom-field mappings to carry company data into HubSpot. The two shipped mappings that read a company custom field — Lifecycle Stage and Owner — resolve a standard HubSpot property rather than a custom one; confirm both produce the expected result on a test company before relying on them.
Updates to existing companies are handled by the Update collection; the Add collection only creates.
Custom association types from iPaaS.com are covered by the association child collections.
At the time this documentation was written, this direction does not search HubSpot for an existing company before creating one. An iPaaS.com Company with no link produces a new HubSpot company even when a company with the same name or domain already exists there. Record matching by name is available only on the inbound direction. Subscribers or their MiSP should link pre-existing HubSpot companies before the first outbound transfer, or expect to merge duplicates in HubSpot afterward.
At the time this documentation was written, only one of the iPaaS.com category assignments is applied when several are provided, because HubSpot holds a single property for the category designation. The last assignment processed becomes the final property value.
At the time this documentation was written, only the primary billing address transfers, because standard HubSpot company fields hold a single address entry.

iPaaS.com to HubSpot Company Mapping Documentation

Summary

ID Format

Manual Sync ID Format

External ID Format

Deleted Record Support

Custom Field Support

Mapping Collection Status

Duplicate or Conflicting Mappings

Supported Child Collections

System Caveats

HubSpot Caveats

iPaaS.com Caveats

Setup Requirements

iPaaS.com Configuration

HubSpot Configuration

Integration Flow

Mappings

Add HubSpot Company FROM iPaaS.com (Parent)

HubSpotOwnerId

Update HubSpot Company FROM iPaaS.com (Parent)

HubSpotOwnerId

Add HubSpot Company Association FROM iPaaS.com (Child)

ReadOnlyRelationshipType

ReadOnlyRelationshipId

Update HubSpot Company Association FROM iPaaS.com (Child)

ReadOnlyRelationshipType

ReadOnlyRelationshipId

Error Handling

Testing & Validation

Test Scenarios

Validation Checklist

Additional Notes

Related Documents