Import contacts
Map CSV and Excel files to contact types and properties, detect existing contacts, and review results
With the Manage CRM permission, import contacts from CSV, XLSX, or XLS. Files may be up to 10 MB. Import creates new CRM contacts and can optionally detect and update contacts that already exist. Only the first worksheet of the file is read. You can import into all directly maintained contact types; the mirrored types Users, Freelancers, and Service Providers are not offered. Start the import with Import in the header of the contact list.
Handle duplicates deliberately
Without the Detect existing contacts option, every row becomes a new contact, even if a contact with the same name already exists. Enable detection when the file contains known contacts and, if needed, use Find duplicates after the import.
Prepare the file
- Use the first row for clear column headers.
- Put one contact on each data row.
- Provide a display name or separate first/last-name columns that can map to correspondingly named properties.
- For selection properties, use exactly the configured Artwork values, including upper and lower case.
- For a multiple choice property, separate several options in one cell with
a semicolon, for example
Light;Sound. - In CSV files and text cells, write numbers with a decimal point rather than a comma and without thousands separators. Real number cells of an Excel file are read regardless of how they are displayed.
- Write dates in one of the supported formats, see Supported values.
- Upload properties cannot receive files through this table import.
Completely empty rows are ignored.
One contact type for the file
Disable Determine different contact types by column in Excel, choose a type, and upload the file. Then map every relevant source column to the display name, a property, or Skip. The selectable fields are the properties of the groups assigned to the contact type in the CRM settings.
Artwork attempts to match similar headers automatically. Always check the preview. Each CRM property and the display name can only be mapped once.
If the right contact type is missing, create it with New contact type directly in the upload step, including the property groups it should have. You do not need to leave the import.
Several contact types in one file
Enable the type column when one source column contains values such as “Artist”, “Agency”, and “Accommodation”.
The type column itself is not imported as an extra property. Rows with unknown or deliberately unmapped type values are skipped. If a contact type is missing, create it in the CRM settings and restart the import so it appears in the mapping.
Detect existing contacts
In the mapping step you can enable Detect existing contacts. Artwork then checks every row against the existing contacts of the same type:
| Setting | Meaning |
|---|---|
| Match by | The name or one of the mapped properties used to match a row to an existing contact, such as the email address. The value must match completely; upper and lower case and surrounding spaces do not matter. |
| Skip row | On a match, the existing contact stays unchanged and the row is skipped as a duplicate. |
| Update existing contact with the values from the file | On a match, the mapped values from the file are written to the existing contact. Empty cells overwrite nothing: an existing value stays. |
When importing several contact types from one file, matching is done via the contact name within the respective contact type.
Detection also works within the file: if the same match value occurs again in a later row, that row is treated like a match, so it is skipped or written to the contact that was just created.
Required fields and display name
Every imported type needs a display name. This can come from a directly mapped name column or be built from first and last name when matching properties are mapped.
Required fields are marked during mapping. Map them where possible and verify that the source cells actually contain values. Unmapped properties remain empty on newly created contacts. Missing required fields do not stop the import: the mapping lists them under The following required fields are not mapped, and the contacts are created without these values. Artwork asks for them only when someone edits the contact later.
Supported values
| CRM field | Expected import content |
|---|---|
| Text, textarea, link | Cell text |
| Number | A valid numeric value with a decimal point, such as 1250.5 |
| Date Coming with the next update | DD.MM.YYYY, DD.MM.YY, YYYY-MM-DD, DD/MM/YYYY (day before month) or an Excel cell formatted as a date, each with or without a time; the time is discarded |
| Checkbox | 1, true, yes, ja, or x means yes; other values mean no |
| Selection | Exact match with a configured option |
| Multiple choice | One or more options separated by a semicolon; each must match a selection value exactly |
| Upload | Not importable; upload the file later on the contact |
Empty cells are always allowed. If a cell contains an invalid value, however, the whole row is skipped, not just that one field.
How the import reads dates
- Two-digit years:
00to69count as 2000 to 2069,70to99as 1970 to 1999;15.03.26therefore becomes 15 March 2026. - Slashes: the day comes before the month;
05/06/2026is 5 June.12/31/2026is invalid. - Excel date cells are recognised as dates, also with a time. Only a
value without a leading zero that results in a date from 1 January 1930
counts as such a number. Small numbers such as
12.05,5,010124or a bare year such as2026are invalid. - Any other format is invalid and skips the row with a message, like other invalid values. The import never stores a guessed date.
Review the result
After import, Artwork shows in the contact list:
- the number of contacts created,
- the number of existing contacts updated,
- the number of rows skipped as duplicates,
- the number of other skipped rows with row number and reason.
Common reasons include an empty name, unmapped type, invalid date, non-numeric number, or selection value absent from the configuration. Put only failed rows into a corrected file before importing again, or enable detection of existing contacts on the second run so that successfully imported rows are not duplicated.
Cancel an import
Cancel ends the mapping process and discards the temporary upload. If the import session expires, start again from the upload step.
Last updated on