Enginy can create and update Dynamics Contacts or Leads, Accounts, and their associations. The result depends on the selected entity, matching, Field mapping, and the user's permissions.
Note: An export is a specific operation. The integration does not keep all fields continuously synchronized after exporting.
What is exported
In Enginy | In Dynamics |
Contact | Contact or Lead, depending on |
Company | Account |
Associated company | Parent Account of the person |
Selected owner | Dynamics User |
Enginy only sends fields included in Field mapping, plus any fixed, manual, or engagement values that apply to the operation.
Before exporting
Review:
Whether people are configured as Contacts or Leads.
The fields in the
ContactsandCompaniestabs.Contact identifierandCompany identifier.Associations with Parent Account.
Create, Read, Write, Append, and Append To permissions.
User mappingif you want to write as a specific user.
Run a first test with a few representative records.
Export from a table or list
Select the Contacts or Companies.
Open the
Export to CRMaction.If the option appears, choose a CRM owner.
Complete the values defined in
Manual export fields.Confirm the export.
Review the report when it finishes.
The operation runs in the background. You can continue working in Enginy while it finishes.
How Enginy decides whether to create or update
Enginy follows this order:
If the record already has a linked Dynamics ID, it uses that ID.
If it does not, it applies the configured matching.
If it finds a match, it updates that record and stores its ID.
If it does not find one, it creates a Contact, Lead, or Account.
If Dynamics returns several matches, Enginy uses the first one. Review duplicates before a large export.
What happens to existing values
Each Field mapping row uses one of these directions.
Enginy overwrites Dynamics
Enginy can replace the value that already exists in Dynamics. This is appropriate when Enginy should be the source of truth for that field.
Sync with Dynamics
During export, Enginy keeps a non-empty Dynamics value and can fill it when it is empty. For a new record, it uses the Enginy value.
Important: Sync with Dynamics does not mean real-time two-way synchronization. It describes how the Dynamics value is handled during the export operation.
Empty Enginy values are usually omitted, so you should not use them as a general method for clearing fields in Dynamics.
Associate Contacts or Leads with Accounts
If When exporting contacts, associate them with companies in Dynamics is enabled, Enginy can:
Identify or create the Company's Account.
Identify or create the Contact or Lead.
Set the Account as Parent Account.
If you export a Company and When exporting companies, associate them with contacts in Dynamics is enabled, Enginy can also export its Contacts and associate them.
Dynamics supports a single primary relationship of this type. A new association may replace the previous one.
Owners
Some exports allow selecting a Dynamics owner. That selection may take precedence over the usual mapping for that operation.
If you do not choose one, Enginy looks for the corresponding user in User mapping and, if it cannot find one, may use Default CRM owner.
Assigning an owner requires the effective user to have Assign privilege and access to the user and record.
Fields that need attention
Choice and Choices
Dynamics expects numeric codes, not labels.
Choice: send one code, for example
100000002.Multi-select Choices: use numeric codes separated by commas.
Pre-validation does not detect every case. Confirm the result in a test.
State and Status
These two fields are related. A value may be valid on its own and still be rejected because it is not compatible with the current state or the Status being sent.
DateTime
Date Only uses
YYYY-MM-DD.Other DateTime fields use ISO format.
Owner and other Lookups
Enginy handles the owner specifically. A custom Lookup represents a relationship and cannot always be filled as text or as any ID. Validate it before using it in volume.
Partial exports
Enginy splits large exports into groups of records and isolates errors. One invalid record does not necessarily stop the entire operation.
The final report helps distinguish created, updated, and failed records. If there are failures:
Open the error detail.
Correct permissions, mapping, or value.
Repeat only the affected records.
Dynamics may reject a record because of required fields, business rules, incompatible types, permissions, or an ID that no longer exists.
Recommended check
After the first export, open the records in Dynamics and verify:
Correct entity: Contact or Lead.
Correct Account and Parent Account.
Expected owner.
Choice fields by their resulting label.
Dates and time zones.
No duplicates.
Fields that were kept or overwritten.
When the result is as expected, you can increase the volume.