Troubleshooting
Symptom / Error | Cause | Resolution |
Export fails with field-mapping errors | A Company field is mapped in the Contacts tab (or vice versa). | Open Step 2: Export Mapping, verify that each tab only contains fields belonging to its own object type, and remove any misplaced mappings. |
Duplicate records appear in the CRM after export | The identifier configured in Step 1 does not uniquely match existing records. | Review and tighten the Contact or Company Identifier. Consider using the LinkedIn profile URL option for contacts or enabling Include any domain extension for companies. |
Cannot enable a second CRM | Enginy allows only one active CRM at a time. | Go to the Enabled tab, disable the current CRM, then enable and configure the new one. |
CRM activity log shows the wrong user | Identities or Users Mapping is not configured correctly in Step 4. | Open Step 4: User Mapping and verify that each Enginy identity and user is linked to the correct CRM user. |
FAQs
Q1: Can I connect more than one CRM at the same time?
No. Enginy supports only one active CRM integration at a time. If you want to switch to a different CRM, disable the current one first, then enable and configure the new one.
Q2: What happens if I do not configure Export Mapping — will my data still sync?
Step 1 (Sync Configuration) controls how records are matched, but without Step 2 (Field Mapping) Enginy will not know which fields to push to your CRM. Even not which ones to pull from CRM. You must configure at least the essential field mappings before exporting or syncing.
Q3: I do not have my own AI or TheirStack account. Can I still use those features?
Yes. For AI, Enginy provides its own credits for AI variable outputs if you do not connect a personal subscription. For TheirStack, Enginy's subscription is used by default and credits are deducted from your plan when importing companies.
Q4: What does the "Overwrite existing value" checkbox do in a manual Export to CRM?
When checked, the value in Enginy replaces whatever value currently exists in the corresponding CRM field during export. When unchecked, the existing CRM value is preserved and only empty fields are populated.
Q5: Why should I avoid the "Associate as Primary and remove previous associations" option?
This option deletes all existing associations for the record before setting the new one as primary. If you have historical relationships or multiple valid associations in your CRM, using this option can result in data loss. Use it only when you are certain the new association should be the sole relationship.