- Import Contact Custom Fields into Clio Manage
- Bulk upload Contact Custom Fields into Clio Manage
- Add Contact Custom Field Information to the spreadsheet template
- Populate Contact Custom Fields CSV for import into Clio
- Clio Manage
- Custom Field names must be an exact match (including spacing) to those in Clio
- Client first and last name must be an exact match to the Contact in Clio
- If importing Custom Field data to a large number of existing Contacts, export your contact list into a separate CSV and copy and paste the first and last names into their respective columns in the template
- This import only works for blank Custom Fields and will not change any information that is already entered in Custom Fields
- On the Imports page, the State will change to Complete once the import is finished. The Successes will remain at 0 as no new Notes were imported, however the data will still be added to each field
- The Custom Field must not be set as Required before importing the Custom Field data. If the Custom Field is set as Required, this must be adjusted within the Custom Field Settings before importing the CSV
- The Custom Field must not be set as Default before importing the Custom Field data. If the Custom Field is set as Default, this may cause your import to fail with the error message: "duplicate values found in row ID" Once the import has been completed you may then set your Custom Field as Default.
- Dates: dates need to be in mm/dd/yyyy format.
- Create the relevant Custom Fields in Clio (if they do not already exist)
- Open this template
- Populate the spreadsheet with your Contact Custom Fields information:
- first_name, last_name and company_name: This should match exactly to the first/last/company names listed in the Contacts section
- Update the other column headers to exactly match the name of each Custom Field which you created in Step 1, and populate each columns with their respective data
- Save the file in CSV format
- Import the file by following the steps below:
*Please note that Custom Fields that include a colon : will not import into Clio.