Import a small contact CSV to learn the mapping and validation workflow. You need the importer:execute:import permission and a workspace where creating these records is appropriate.
1. Prepare the file
Use a few contacts you intend to import, with these headers:
First Name,Last Name,Email Address,Phone
Alex,Example,alex@example.com,+442079460123
Sam,Example,sam@example.com,02079460124
The rows above are examples. Save the file as UTF-8 CSV and keep Phone as text to preserve its leading zero or plus sign. See Prepare a CSV.
2. Select the file and entity
Open Data In and Out → Upload a file. The wizard begins at Select file; click the upload area or drag in the CSV, then Next. In What to import, select Contacts and click Continue. There is no separate Single import mode switch.
3. Review mappings
In Map columns, verify each destination field uses the intended source:
| Field | Source column |
|---|---|
| First Name | First Name |
| Last Name | Last Name |
| Email Address | Email Address |
| Phone | Phone |
Leave other fields Not mapped. A mapped empty standard field can clear an existing value when a record matches, so check blank cells before continuing.
4. Run the pre-flight check
Click Next and wait for all rows to be checked. Fix missing required mappings and inspect row warnings. If you add date fields later, confirm the date format here. This stage does not create contacts.
5. Submit
Review the file, entity and mapping counts. Optionally enable Save this mapping for next time and enter a name. Click Start Import to upload the file and create the job.
There is no undo or cancellation button in the wizard. Check the previewed values and warnings before submission.
6. Verify the result
Wait for the job’s terminal status. If it completes with errors, download the available error report and correct the affected rows. Open Relationships → Contacts and check the names, email addresses and phone numbers on representative records.
Import history lets you return to a job. Keep stable external source IDs for repeat imports; do not assume every repeated row will create a new contact or that every entity is automatically deduplicated.