You'll want to properly map the data to ensure that the data from HubSpot to Katana (and vice versa) matches.

From the Data mapping tab of the configuration page, you'll find a mapping of HubSpot object properties with Katana object data fields. This mapping will be used in workflows to ensure the correct data flow between the systems.

Most fields are automatically mapped to the corresponding HubSpot property, but for those that aren't, you can manually select a HubSpot deal property.

The HubSpot properties listed in the dropdown menu are filtered by field type. For example, a date field in Katana can only be mapped with a date field in HubSpot.

In this section you can map the general data fields found on sales orders, such as dates and additional references.

While HubSpot deals can have both a Contact and a Company associated with them, Katana SOs can only have a single Customer.

By default, the Contact in a deal will be added as the Customer in Katana, but if a deal has only a Company connected, the Company is added as a Customer.

The properties containing address information for a deal's contact will be added to the Bill to address on a Katana SO. If a deal has only a Company associated, the company's address is used. The SO's Ship to address will match the Bill to.

Address fields are automatically mapped to their corresponding Contact and Company address properties.

If the address information of a contact or company changes in HubSpot and a new deal is assigned to that contact/company, a new billing address is added to the Customer data in Katana if an SO is imported.

SO row field mapping is also used when importing products from HubSpot. Katana adds the item to its inventory using the ‘Product name’, ‘SKU’ properties, and ‘default sale price’ from the HubSpot deal. The item will be skipped if an existing item already has the same SKU in Katana.

Your feedback is invaluable. Let us know your thoughts on this article or anything in Katana you'd like to see improved: [email protected]