CRM

Import contacts

Map CSV and Excel files safely to contact types and properties

With CRM management permission, import contacts from CSV, XLSX, or XLS. Files may be up to 10 MB. Import creates new CRM contacts; it is not a general update of existing records.

Check duplicates first

Import does not automatically detect an existing contact with the same name. Clean the source and search samples in the CRM to avoid duplicate records.

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.
  • Format numbers and dates consistently.
  • 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.

Artwork attempts to match similar headers automatically. Always check the preview. Each CRM property and the display name can only be mapped once.

Several contact types in one file

Enable the type column when one source column contains values such as “Artist”, “Agency”, and “Accommodation”.

Upload the file.
Select the column containing the contact type.
Map every source value to a CRM type or deliberately skip its rows.
For each used type, separately map columns to its name and properties.
Review the preview and required details, then start the import.

The type column itself is not imported as an extra property. Rows with unknown or deliberately unmapped type values are skipped.

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.

Supported values

CRM fieldExpected import content
Text, textarea, linkCell text
NumberA valid numeric value
DateAn unambiguously readable date
Yes/no1, true, yes, ja, or x means yes; other values mean no
SelectionExact match with a configured option
UploadNot importable; upload the file later on the contact

Review the result

After import, Artwork shows:

  • the number of contacts created,
  • the number of skipped rows,
  • the row number and reason for each skipped row.

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; otherwise you will duplicate successful rows.

Cancel an import

Cancel ends the mapping process and discards the temporary upload. If the import session expires, start again from the upload step.

On this page