You can bring in Contacts and Organizations through CRM Search.
The integration does not let you pick a TribeCRM List as the source. The list you select at the end is the Enginy list where the results will be stored.
Before importing
Check that:
TribeCRM is connected.
You have saved a
Contact Typeand anOrganization Type.The OAuth user can read the records and fields.
The fields you need are available for the selected type.
You know which Enginy list you will store the results in.
What each flow imports
Contacts
Enginy looks for Persons of the selected Contact Type.
The basic data includes FirstName, LastName, EmailAddress, PhoneNumber and MobilePhoneNumber.
Configured custom fields can be imported when TribeCRM returns them for that type.
If the Contact has a related Organisation, Enginy also tries to import that company and keep the association.
Companies
Enginy looks for Organisations of the selected Organization Type.
The basic data includes Name and Website, plus the supported fields configured for the flow.
Importing Companies does not automatically import their Contacts.
Build the search
Open the importer and choose
CRM Search.Select TribeCRM.
Choose
ContactsorCompanies.Select
Contact TypeorCompany Type.Add up to five filters.
Turn on
Match existing contactsorMatch existing companiesif you want to look for entities that already exist in Enginy.Set the maximum limit.
Click
Fetchto get a sample.Choose the destination list in Enginy.
Click
Import.
All filters are combined with AND. A record has to meet every one of them.
Fetch shows up to 10 examples and the total found. You can start the import without getting the sample first, but it is better to review it.
You can only query one Contact Type or Company Type per search. Repeat the process if you need to import several types.
Important: If you change Company Type and the fields do not update, go back to Configure, save the Organization Type you need with Save Changes, and open the import again.
Match existing contacts
This option tries to recognise a Contact that already exists in Enginy using data such as CRM ID, Email, LinkedIn, and Name and Company.
If it finds a match, it links the TribeCRM record to the existing entity. Imported data mainly fills in empty fields rather than replacing every value indiscriminately.
Match existing companies
For Companies, Enginy uses data such as CRM ID, Name, Domain or Website, and LinkedIn.
Review duplicates and formats before a large import.
These import rules are not exactly the same as the matching used when exporting to TribeCRM. Contact identifier and Company identifier mainly control how Enginy looks for records in the CRM before creating or updating them.
Relationships between Contacts and Organizations
When importing a Contact, Enginy reads its Relationship and tries to retrieve the linked Organisation. That is why a new Company can appear even though you started a Contacts import.
The reverse does not apply. A Companies import does not bring in all the related Persons.
A Contact without a Company can be imported into Enginy. To later create it as a new Contact in TribeCRM, you will first have to associate it with a Company.
If Fetch does not show what you expected
Check:
The
Contact TypeorCompany Type.That all the filters can be met at the same time.
The OAuth user's read permissions.
That the fields belong to the selected type.
That the Contact has a Relationship of that type.
That the Organisation is classified with the selected type.
Remove filters one at a time to find which one is excluding the records.
Avoiding duplicates
Before importing:
Review Contacts with identical names.
Normalise domains, Websites and LinkedIn URLs.
Check that emails and CRM IDs are not empty or duplicated.
Review Companies with the same Name.
Turn on matching against existing records.
Changing the rules afterwards does not automatically merge entities that have already been created.
After the import
Review the report.
Check a sample of Contacts and Companies.
Confirm the associations are correct.
Review which fields were filled in.
Fix filters or permissions before repeating the operation.
