Home/HighLevel/Features/Custom Objects/How to import object records and create associations in HighLevel

CRM and Pipelines

How to import object records and create associations in HighLevel

In short

HighLevel lets you bulk import custom object records from a CSV and automatically link each new record to an existing Contact, Company or another Custom Object. The process uses the Associate Records workflow action, which matches a field from the CSV to a field on the target record and creates the defined association.

AreaCustom Objects · Getting Started with Custom Objects
Used forVeterinary clinic, Insurance agency, Event management company
Setup steps25 steps in 5 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Marketing agencies that need to migrate client data and keep relationships between contacts and custom objects without manual linking.
  • Real estate teams importing property listings and automatically tying them to owner contacts or companies.
  • Veterinary clinics moving pet records and associating each pet with its owner contact.

02Import custom object records with associations, explained

The feature combines the custom object bulk import tool with the Associate Records workflow action. When a CSV is uploaded, each row creates a new custom object record. The workflow then runs, looks for an existing record that matches a specified field, and creates the association defined by the association label.

Configuration occurs in three places. First, define the association under Settings > Objects for the custom object. Next, build a workflow for the custom object under Automation > Workflows and add the Associate Records action with the appropriate filters and label. Finally, import the CSV from the custom object’s Import button and monitor the process via Bulk Actions.

03How businesses use import custom object records with associations

  • Veterinary clinic. Create a Pet custom object and include an Owner Email column in the CSV. Build a workflow that triggers on Pet Record Created, adds an Associate Records action that matches Contact Email to Owner Email, and publish it. Import the CSV; each pet record will automatically link to its owner contact.
  • Insurance agency. Set up a Policy custom object with a Policyholder Email field. Design a workflow that, on Policy Record Created, associates the record with a Contact whose Email matches the Policyholder Email. After publishing, import policy data; policies connect to the correct policyholder contacts.
  • Event management company. Define an Event Registration custom object that contains an Attendee Email column. Create a workflow that triggers on Registration Record Created and uses the Associate Records action to find a Contact with a matching Email, applying an "Attendee" association label. Import registrations to link them automatically.

04The numbers and rules that matter

  • Recommended matching fields include email, phone, customer ID, account number, external system ID.
  • Association limits configured between objects still apply.

05Before you start

  • The custom object and all required fields must already exist.
  • An association between the custom object and the target object must be configured.
  • The CSV file must contain a column whose values can identify the matching target records.
  • A workflow that includes the Associate Records action must be created and published before the import starts.

06How to set up and use import custom object records with associations in HighLevel

Create the required association

  1. Navigate to Settings > Objects.
  2. Select the custom object you will import.
  3. Open the Associations tab and define the associated object and association label.

Prepare the CSV

  1. Add columns for all fields needed to create the custom object record.
  2. Add a column that contains the value used to locate the matching target record.
  3. Make sure a corresponding field exists on the custom object to map the matching column during import.

Create the workflow

  1. Go to Automation > Workflows and start a new workflow for the custom object.
  2. Name the workflow appropriately for the object being imported.
  3. Add a trigger of type "Record Created" for the custom object.
  4. Insert the "Associate Records" action into the workflow.
  5. Select the target object under "Create Association With".
  6. Add a filter that compares a target field to the matching field from the CSV.
  7. Choose how the workflow should handle multiple matching target records.
  8. Set the association label and publish the workflow.

Import the custom object records

  1. Open the custom object you configured.
  2. Click the Import button.
  3. Upload the prepared CSV file.
  4. Map each CSV column to the appropriate custom object field.
  5. Review the field mappings for accuracy.
  6. Start the import process.
  7. Monitor the import progress under Bulk Actions.

Verify the associations

  1. Open several of the newly imported custom object records.
  2. Check the associated records displayed on each record.
  3. Confirm that the expected association label appears.
  4. Examine the workflow execution logs for any records that did not receive an association.

07What it looks like in HighLevel

08Settings that matter

  • Associate Records. Controls the creation of an association between the imported custom object record and a target object based on matching field criteria.
  • Association Label. Specifies the name shown on the custom object record to describe the relationship to the associated target record.

09Things to know before you rely on it

  • The association limits configured between the two objects still apply; ensure the limit can accommodate the expected number of links.
  • Imports can finish successfully even if the workflow does not find a matching target record for a given custom object record.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

It removes the need to manually associate each record after an import, especially for businesses that already have contacts or companies set up.

I’d test with a handful of rows first, just to make sure the email match works, then let the bulk import handle the rest.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about import custom object records with associations.

What field should I use to match records during import?

Use a unique or stable identifier such as Email, Phone, Customer ID, Account number or an external system ID. These fields reduce the chance of multiple matches.

Can I use more than one filter to find the matching record?

Yes. When multiple filters are added, the target record must satisfy all conditions before an association is made.

Do I need to publish the workflow before starting the import?

The workflow must be created and published prior to initiating the CSV import; otherwise the Associate Records action will not run.

What happens if the workflow cannot find a matching record?

The custom object record will still be created, but no association is added. Review the workflow execution logs to identify such cases.

Are there limits on how many associations can be created?

Association limits defined between the two objects still apply, so verify that the limit supports the number of expected links.

Should I test the import with a small CSV first?

Testing with a small sample helps confirm that the workflow creates the correct associations before importing a full dataset.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.