Does not import all fields

[ferradeira]

I'm truing to import this csv file (UTF-8) in to opportunities. But it fails with some fields related to Contact (Contact name, Contact Phone and Contact email).
I think it checks if the contact name exists in Contacts. all other fields are imported.
I think I have the right fields in step 2. But something is blocking the import of Contacts in to Opportunities.
Any idea?
Thanks

[eymen-elkum]

As Contact Name, Phone and Email are not direct Opportunity fields and belong to the linked Contact record.

The safest approach is normally a two-step import:

1. Import the Contacts first, using a unique value such as the email address or an external ID.
2. Import the Opportunities afterward and map the Contact relationship using that unique value or the Contact ID.

If the Opportunity–Contact relationship is multiple, the import wizard may not create a new Contact and populate its fields automatically from the same Opportunity row.

Could you share a screenshot showing the complete Step 2 mapping, especially the exact fields selected for Contact Name, Phone and Email? That will help determine whether this can be solved by changing the mapping or requires preprocessing the CSV.

For a large or repeatable migration, the CSV can also be transformed into separate Contact and Opportunity datasets with reliable relationship IDs before importing.

[ferradeira]

I tried using the email, which I confirmed is the same in Contacts, but import nothing.
Images attached.
In the Opportunity some contacts are multiple. But its ok if it only import one.
From the CSV I use Name for Contact (Primary) (Name), Email for Contact Email and FullMobile for Contact Phone

[eymen-elkum]

The new screenshots point to a validation problem before EspoCRM attempts to relate the Contact.

The import completed, but rows 2–4 all failed with “Validation”, and no Opportunity records were created. In the field mapping screenshot, I can see Contact (Primary), Contact Phone and Contact Email, but I do not see any column mapped to the required Opportunity “Name” field.

Please open modal detail view from an arrow beside one of the Validation errors. It should show the exact field or rule that rejected the row.

I suggest:

1. Map a CSV column to Opportunity Name. You could prepare a value such as “Event – Exhibition Code” in the CSV.
2. Check whether Stage or any custom Opportunity fields are configured as required.
3. Supply constant required values through the “Default Values” section when they are not available in the CSV.
4. Test the import with one row first.

Once the Opportunity itself imports successfully, we can verify the Contact relation separately.

Also note that Contact Phone and Contact Email are foreign/read-only values on the Opportunity; mapping them will not update those fields on the Contact. If you want EspoCRM to find the Contact by email, the corresponding foreign field must have “Relate on Import” enabled and the relationship must support this. Otherwise, continue with the two-step method: import Contacts first, then relate the Opportunity using the Contact ID or an exact matching value.