Skip to main content

Map Import Fields

After uploading a CSV or Excel file, Map import fields decides where each column will be saved. Check every automatic match before you queue the import.

Entry pointAdmin → Settings → Import/Export → Import → Map and import

Who Can Do This​

Users with import access can map fields for the record types they are importing. If Import is missing from Settings, ask an admin to check your permissions.

Map Each Column​

The mapping table shows a column from your file, sample values, Import as, and CRM field.

  1. For each file column, choose the record type under Import as. A contact-only or deal-only import uses one record type; a combined import may have both.
  2. Under CRM field, choose the Brixi field that should receive the column. For example, map a spreadsheet's email column to the contact Email field.
  3. If you do not want a column imported, choose Ignore field. Resolve columns highlighted as unmapped before continuing.
  4. Map every required field shown on the page. If a required value is the same for every row, use Add constant under Constant mappings and enter the record type, CRM field, and value.
  5. If you are importing related records, use Connect records across files to link them by an external ID. See Import Related Records.

For a contact update, also map the column that identifies each existing contact and choose it under Match contacts by → Matching field. See Update Existing Contacts.

Preview and Correct Values​

Select Preview 5 rows. The preview checks the first five rows against field types and allowed values. If a column shows an issue, choose Review and fix to select or enter a valid value. You can also correct the source spreadsheet and upload it again.

After changing a mapping or value, preview again. The final Import records or Update contacts button becomes available when the required mappings are complete and preview issues are resolved. Because the preview shows five rows, check the whole source file before queuing a large import.

Common Issues​

IssueWhat to check
A column could not be mapped automaticallyChoose its record type and CRM field, or Ignore field.
A required field is missingMap a file column or provide a constant value.
A value has the wrong type or is not an allowed optionUse Review and fix, or correct the file.
Preview 5 rows is disabled for an updateMap and select a matching ID, email, or phone number, plus at least one field to change.

Contact Brixi support if a field visible in your workspace does not appear in the mapping picker or valid values continue to fail preview. Include the field name and the error shown.

Was this article helpful?If something is unclear or out of date, email support@brixi.ai with the article title — or see Getting Help for what to check first.