Import

Each custom object has its own import button on the list of custom items and each has its own import history. The plugin uses the core import feature from Mautic. Visit the contact import docs for more info about the import itself.

Here is an example of CSV that can be imported:

customItemId,customItemName,3,linkedContactIds
1020224,Pampers,Stuff babies **** into,
1020225,Gloves,Heat insulation for your hands,5319
,Bread, Stuff you can eat for breakfast,"5319, 2,5"

The CSV headers can be named differently and then mapped manually.

• customItemId Must be real, existing Mautic custom item ID. If provided then the import will merge the values from the CSV row with the existing custom item. If not, it will create new one.
• customItemName Name is the only default field for each custom object and therefore doesn't have a number, but this special key.
• 3 or any other custom field ID. The value will be added to the custom field for the specific custom item.
• linkedContactIds can be a list of one or more existing Mautic contacts separated by comma. Make sure you'll add the comma-separated list of contact IDs into double quotes to escape this CSV from the main CSV file.

Value limits:

• Text: 4,294,977,295 bytes
• Multiselect option: 255 bytes
• Int: -2147483648 - 2147483647

Import field mapping validation

Import field mapping form won't let you continue until you map at least one custom field with a CSV column. Also all required custom fields must be mapped before you will be able to proceed with the import. A form validation message like this will appear that will inform you what fields are required:

Some required fields are missing. You must map the field "SKU (sku), Name."

Custom Field Validation

If a custom field gets wrong value, for example invalid email address, invalid phone number or unknown select option then such CSV row will be ignored and the validation error message will be available at the import detail together with the CSV row number so you can back track it and fix it.