Associating or Linking Records During Import

On the Associate (or Link) tab in the Magical Import module's Data Operations section, configure an association rule to define how CSV rows are linked to related records already in your CRM.

1. Click the Data Operations heading to expand the section, then select the Associate (or Link) tab.
2. Select the Action to take. You can Add or Remove associations for any CRM. For HubSpot, you can also use the Replace action to remove existing associations and create new ones in one step.
3. Set Associate/Link to the object type you want to create the relationship with. You can associate objects of different types, such as contacts with companies, or objects of the same type, such as companies with companies. In the example below, contacts are associated with companies — available options vary depending on your CRM, object type, and configuration.
4. HubSpot users will also see a Labels field. Labels are not free text — they must already exist in HubSpot, where they're used to name or categorize the relationship. This field does not appear for other CRMs.
5. Set the CSV Column to the field in your CSV you want to match against CRM records. For example, if you were associating contacts to companies, you could choose the “Company” or “Domain” field from your CSV.
6. Set the Match Field to the CRM field the CSV Column should match. The CSV Column and Match Field often have similar names on both sides. For example, a "Company" CSV column could be matched to a "Company Name" CRM field, or a "Domain" CSV column could be matched to a "Company Domain" CRM field.

The image above shows the Data Operations section of the Magical Import module, with the Associate tab selected. One rule is configured: Action set to "Add," Associate set to "Contact to Company," Labels set to "Primary," CSV Column set to "Company Name," and Match Field set to "Company name." The "Create when no matching is found" checkbox is unchecked.

You can also create parent-child relationships between companies or accounts, though the various CRMs handle this differently:

• In Salesforce, parent-child relationships use a dedicated Link type, such as "Child Account to Parent Account," unlike HubSpot's Labels field. 

  

  The image above shows the Data Operations section of the Magical Import module, with the Link tab selected. One rule is configured: Action set to "Add," Link set to "Child Account to Parent Account," CSV Column set to "Company name," and Match Field set to "Account Name." Unlike the HubSpot Associate tab, no Labels field appears—in Salesforce, the Link type specifies the relationship direction. The "Create when no matching is found" checkbox is unchecked.

• In HubSpot, the same relationship uses the standard "Company to Company" Associate type, with the direction specified through a pre-existing Label — for example, "Parent to Child." Unlike Salesforce's dedicated Link type, HubSpot specifies the parent-child direction through the Labels field rather than a distinct Associate option. The "Create when no matching is found" checkbox is unchecked. 

  

  The image above shows the Data Operations section of the Magical Import module, with the Associate tab selected. One rule is configured: Action set to "Add," Associate set to "Company to Company," Labels set to "Parent to Child," CSV Column set to "Company name," and Match Field set to "Company name" (partially visible).

You can also associate custom objects.

The image above shows the Data Operations section of the Magical Import module, with the Associate tab selected. One rule is configured: Action set to "Add," Associate set to "Cars to Deals," Labels set to "Unlabeled," CSV Column set to "Make," and Match Field set to "Maker," illustrating an association between two custom object types. The "Create when no matching is found" checkbox is unchecked.

On the Associate (or Link) tab in the Magical Import module's Data Operations section, creating a new related record when no match is found lets Insycle automatically create a related record instead of skipping the association entirely.

If no matching record is found in the CRM for an association rule, Insycle doesn't create an association by default. Check Create when no matching is found to enable this behavior — Insycle will automatically create a new record based on the CSV data.

This only works when associating contacts to companies. When enabled, Insycle populates the new company's name and domain name using the contact's email domain.

The image above shows the Data Operations section of the Magical Import module, with the Associate tab selected. One rule is configured: Action set to "Add," Associate set to "Contact to Company," Labels set to "Primary," CSV Column set to "Company Name," and Match Field set to "Company name." The "Create when no matching is found" checkbox is checked.