Before importing or exporting, Enginy needs to know which record types to use and how to recognise a Contact or Organization that already exists.

Getting this right reduces duplicates and prevents incorrect associations.

Open Integrations, find TribeCRM and click Configure. In Sync Configuration you will find four required fields:

Even if you are not using Tasks yet, you have to select valid values in all four fields.

Choose types your team already uses. If you change Contact Type or Organization Type, Enginy will search for and create records inside that other type. Review Field Mapping too, because the available fields can change.

Contact identifier tells Enginy how to look for an existing Contact before creating a new one.

The current behaviour compares FirstName and LastName.

If the associated Company already has a TribeCRM CRM ID, Enginy also narrows the search to that Organisation. The Company name text itself is not compared separately.

If there are several matches, Enginy picks the most recently updated Contact and keeps the other IDs as alternative references.

The option that includes LinkedIn looks for an exact match on the LinkedIn URL or, failing that, on first and last name.

If Enginy already knows the Organisation's CRM ID, it applies that relationship to the search too.

Use a consistent format for LinkedIn URLs.

Use Custom Mapping when you need other identifiers.

For example, a Condition with email and country requires both values to match. Another Condition with LinkedIn can work as a fallback.

Choose fields that are stable and unique enough. Job title, city or commercial status rarely work well as identifiers.

Company identifier controls how Enginy looks for an existing Organisation.

Looks for an exact match on Website.

Normalise your values before using this option. Avoid mixing domains with and without www, full paths or spaces.

Looks for Organisations whose Website or Name match. Both conditions are part of the same search.

Website does not take priority over Name. If each condition points to a different Organisation, Enginy uses the first result TribeCRM returns.

The option that includes any domain extension uses a broader match. It can find variants of a domain, but it also increases the risk of false positives.

You can combine TribeCRM's own fields.

The conditions follow the same logic:

A new Contact needs an associated Organisation. If the Company does not exist in TribeCRM yet, Enginy can create it first and use its CRM ID to create the Contact's Relationship.

When you change the associated Company, Enginy updates the Relation property on the Relationship it manages. This can replace the previous Organisation.

The integration does not guarantee different behaviours for append, primary or replace.

Before a large export: