To access Field Mapping, go to Integrations → Attio → Configure → Step 2: Field Mapping.
Important: Attio uses a structured value format — each field type has its own expected format. Enginy handles these conversions automatically when the correct field type is selected. Mapping to the wrong field type will cause the export to fail.
Understanding the Status Icons
Icon | Status | What it means |
✓ Blue | Compatible | The field types match. No action needed. |
! Yellow | Warning | The field types may be incompatible. Review this mapping carefully before saving. |
✕ Red | Error | The mapping cannot be applied. The export will fail for any record using this mapping. |
Warning: Do not save a configuration with red icons. Exports will fail for all records using that field mapping.
Which Attio Field Type Should I Use?
Use this table as a reference when selecting the destination Attio field for each Enginy field.
Enginy field | Recommended Attio field type | Notes |
First name, Last name | text | Enginy splits the full name into first and last name automatically. |
Job title, Description | text | Standard text fields. Fully compatible. |
Professional email | Map to an Attio email field. Enginy sends it in the correct structured format automatically. | |
Mobile phone | phone_number | Map to an Attio phone_number field. Enginy sends it in the correct structured format automatically. |
Number of employees, Years in role, Growth % | number | Map to an Attio number field. |
Created at, Last activity at CRM | date_time | Enginy sends dates in ISO 8601 format. Map to a date_time field, never to a text field. |
Outreach Stage, Sequence Status | select (single) | Value must match an existing option exactly. |
Languages, Sub-industries | multi-select | Values must match existing options exactly. |
Domain, Website | domain | Map to an Attio domain field. Enginy sends it in the correct structured format automatically. |
LinkedIn URL | url | Map to an Attio url field. |
Personal emails, Other phones | text | Use Professional email and Mobile phone instead where possible to avoid sending arrays. |
Boolean fields (e.g. verified) | checkbox | Map to an Attio checkbox field. |
Yellow Warning: What to Do
1. Text mapped to a Select field
If you map an Enginy text field to an Attio select field, the export will fail if the value does not match one of the configured options exactly.
How to fix it:
Create an AI Variable with output type One off and define the tag options to exactly match the Attio select field options.
For Fixed Value or Engagement fields: enter the exact option value directly in the field mapping configuration.
For Manual Export fields: enter the exact option value at the time of export.
2. Date field mapped to a Text field
Enginy sends date fields (such as Created at or Last activity at CRM) in ISO 8601 format. If the destination field is a plain text field, the value will not be processed correctly.
How to fix it: Map Enginy date fields to an Attio date_time field.
Red Error: What to Do
A red icon means the mapping will always fail. There are two reasons this happens:
1. Incompatible field types
The field types on both sides are incompatible and Attio cannot process the value.
How to fix it: Remove the mapping and select an Attio field with a compatible type. Use the reference table above to choose the correct type.
2. Read-only Attio field
The destination field in Attio is read-only and cannot be updated by Enginy. This typically affects system-generated fields.
How to fix it: Remove the mapping and choose a writable Attio field, or contact your Attio administrator to confirm field permissions.
Common Attio Mapping Mistakes
Mistake | What happens | How to fix it |
Mapping a Company field in the Contacts tab (or vice versa) | Export fails with a field mapping error | Verify that only Contact fields appear under Contacts, and only Company fields under Companies |
Mapping an Enginy date field to an Attio text field | Value not processed correctly | Map to an Attio date_time field instead |
Mapping an Enginy text field to an Attio select field without matching option values | Export fails | Use an AI Variable (One off) with the exact Attio option values |
Mapping emails, phones or domains to a text field | Value may not be stored in the correct format | Map to the dedicated Attio field type: email, phone_number, or domain |
Mapping to a read-only or system field | Export fails | Choose a writable field instead |
Saving mappings with red icons | All records using that mapping fail to export | Fix or remove any red-icon mappings before saving |
Need More Help?
If you have reviewed your mapping configuration and the export still fails, contact our support team with:
The name of the Enginy field and the Attio field you are trying to map
The error message or icon you are seeing
A screenshot of the Field Mapping configuration if possible