Earn up to $250 in gift cards this summer. Find out how.

Fields Exported From Clio Grow to Clio Manage

Information from Clio Grow is not automatically sent to Clio Manage, even if a lead becomes a client. See this article to learn how to export a Contact and/or Matter.

The two tables below list the Contact and Matter fields that are exported from Clio Grow to Clio Manage and the fields that are not exported from Clio Grow to Clio Manage. 


Contact Fields

✓ Yes, this field is exported

✕ No, this field is not exported

Contact Field Exported From Grow to Manage?
Custom fields and field sets*
Salutation
First Name
Middle Name
Last Name
Email address (multiple)
Phone number (multiple)
Address (multiple)
Company name
Notes
File attachments
Lead source
Contact type
Referred by
Tags
Tasks
Emails

*Custom fields should be created in Clio Manage and then synced to Clio Grow.


Matter Fields

✓ Yes, this field is exported

✕ No, this field is not exported

Matter Field Exported From Grow to Manage?
Custom fields and field sets*
Description
Location
Notes
Submitted Documents
Submitted Forms
Attached Files
Appointments
Responsible attorney
Originating attorney
Matter type
Matter status
Assigned to
Created on
Estimated case value
Document templates**
Form templates
Emails
Tasks

*Custom fields should be created in Clio Manage and then synced to Clio Grow.

**Document templates cannot be exported from Clio Grow to Clio Manage; however, you can download the template and save it to your desktop, then in Clio Manage add merge fields (Settings > Documents > Document Template Merge Fields), and upload your document template in Clio Manage (Documents > Categories and templates > New template).

Note: If a field cannot be exported from Clio Grow to Clio Manage, you may be able to create that field as a custom field in Clio Manage and sync it to Clio Grow. Then, export the Contact or Matter from Clio Grow to Clio Manage. You may also contact Clio Support to submit a Feature Request if you would like to export a field without using the custom field workaround.

Was this article helpful?
This information is confusing or wrong
This isn't the information that I was looking for
I don't like this functionality