Skip to main content

Export Contacts and Organizations to TribeCRM

Enginy can create and update TribeCRM Contacts and Organizations. A new Contact needs an associated Organization.

Enginy can create and update TribeCRM Contacts and Organizations.

Important: A new Contact needs an associated Organization. If it does not exist in TribeCRM and the Contact has no Company in Enginy, the export will fail.

What Enginy can export

  • New or existing Organizations.

  • Contacts linked to an Organization.

  • Standard and custom fields configured in Field Mapping.

  • Values from Fixed value fields and Manual export fields.

  • Owners configured through User Mapping.

  • The relationship between a Contact and an Organization.

The integration does not export Lead, List or Note objects. It does not delete Contacts or Organizations from TribeCRM either.

Before exporting

Check that:

  1. The OAuth connection is still active.

  2. The OAuth user can read, create and modify the objects and fields.

  3. You have saved Contact Type and Organization Type.

  4. You have reviewed Contact identifier and Company identifier.

  5. The fields appear in Field Mapping.

  6. Owners are configured if you want to assign them.

  7. Default Task Status and Completed Task Status have a value, even if you are not exporting Tasks.

Export records

  1. Select Contacts, Companies or an Enginy list.

  2. Open Export to CRM.

  3. Choose TribeCRM.

  4. Select CRM Owner if you want to assign one.

  5. Turn on Override only if the new owner should replace the current one.

  6. Fill in the Manual export fields, if there are any.

  7. Decide whether to include the associated records.

  8. Review the fields that can be overwritten.

  9. Click Review mapping.

  10. Check the summary and click Export.

When it finishes, open the report to see which records were created, updated or could not be processed.

An export can end with partial results. Do not repeat the whole batch without reviewing the affected records first.

How it decides whether to create or update

For Organizations, Enginy can search by Website, Website or company name, or Custom Mapping Conditions.

Website or company name evaluates both values in the same search. Website does not take priority over Name.

For Contacts, standard matching compares first and last name. If Enginy already knows the Organization's CRM ID, it also narrows the search to that relationship.

The LinkedIn option uses an exact URL match or, failing that, first and last name.

If Enginy does not know the Organization, two Contacts with the same name can be ambiguous.

Creating an Organization

Enginy applies the selected Organization Type and the configured mappings.

The initial setup includes Name, Website, CoCDescription and PhoneNumber.

The value has to exist in Enginy, be compatible, and be available to the OAuth user.

Creating a Contact

Enginy creates the Person and the Relationship matching the Contact Type.

The initial setup includes FirstName, LastName, EmailAddress, PhoneNumber, MobilePhoneNumber and Title.

The associated Company is prepared first. If it does not exist, Enginy tries to create it.

A specific field can be skipped if it is empty, read-only or does not accept the value. The Contact can still be created even if that custom field is missing.

Updating existing values

Sync with TribeCRM

Enginy keeps the value that already exists and can fill the field in if it is empty.

Enginy overwrites TribeCRM

Enginy can replace the value during the export.

Empty Enginy values do not clear content in TribeCRM. Neither option switches on continuous bi-sync.

Associations

TribeCRM represents the relationship between Person and Organisation through Relationships.

Enginy updates the Relation property on the Relationship it manages. If you export the Contact with a different Company, the previous Organisation may change.

Do not assume the integration will add an extra Relationship. Run a test if a Person works with several Organisations.

Owners

When there is a match in User Mapping, Enginy can assign the user as AccountManager.

During an update, the owner changes if the field is empty or if you have turned on Override.

User Mapping does not grant permissions and does not start a session as the mapped user. Every call uses the original OAuth connection.

Partial results

One record can fail while the rest are processed correctly.

Check:

  • A Contact with no Organization.

  • A read-only field.

  • An Enumeration with an option that does not exist.

  • The OAuth user's permissions.

  • The API limit.

  • Ambiguous matching.

  • A custom field that was changed or deleted.

Fix the cause and retry only the affected records.

Did this answer your question?