Import companies, people, and opportunities from CSV files
The import tool lets you migrate existing data from spreadsheets or other systems into your CRM. You can import companies, people, and opportunities from CSV files with an intuitive column-mapping interface that validates your data before committing any changes.
Follow these steps to import records from a CSV file.
Open the entity list you want to import into (Companies, People, or Opportunities) and click the Import button in the toolbar. Alternatively, go to Admin → Import to access the import tool directly.
Choose which type of record you are importing: Companies, People, or Opportunities. Each entity type has its own set of required and optional fields that you will map in the next step.
Drag and drop your CSV file onto the upload area or click to browse your file system. The file must be in CSV format with UTF-8 encoding and include column headers in the first row. The importer reads the headers to prepare the column-mapping interface.
The column mapper displays each CSV header alongside a dropdown of available CRM fields. The system auto-matches columns by header name when possible — for example, a column named "Company Name" will automatically map to the Name field. Review each mapping and adjust any that were not matched correctly. Required fields are marked with an asterisk and must be mapped before proceeding.
After mapping, the importer validates every row against the field requirements and data types. Validation errors are displayed per row with a description of the issue (for example, "Invalid email format on row 15"). You can fix errors in your CSV and re-upload, or proceed with a partial import that skips invalid rows.
Click Import to begin. A progress indicator shows how many records have been processed. When the import completes, you will see a summary with the number of records created, skipped, and any errors encountered. Imported records are immediately available in the CRM.
Ensure your CSV file meets these requirements before uploading.
How the column mapper matches your CSV headers to CRM fields.
The mapper uses header-name matching to automatically pair your CSV columns with CRM fields. Common variations are recognized — for instance, "Phone Number", "Phone", and "Tel" all map to the Phone field.
If a column cannot be auto-matched, it is left unmapped. You can manually assign it using the dropdown, or leave it unmapped to skip that column during import. Unmapped columns are not imported but do not cause errors.
Custom fields defined in your organization are also available as mapping targets. If you have created custom fields under Admin → Custom Fields, they will appear in the dropdown alongside the standard fields.
How the importer identifies and handles potential duplicates.
During validation, the importer checks each record against existing data to identify potential duplicates. Matching is based on key fields depending on the entity type:
When a duplicate is detected, the row is flagged in the validation results. You can choose to skip duplicates, which is the default behavior, or review them individually before proceeding with the import.
What happens when rows fail validation.
Validation errors are displayed per row with specific error messages explaining the issue. Common errors include:
The import supports partial completion — valid rows are imported while invalid rows are skipped. After the import finishes, you can download a report of skipped rows, fix the issues in your CSV, and re-import only the corrected rows.