This article may be out of date!
Visit the New Knowledge Center

Issue: Unable To Export Custom Field Data From Grow To Manage If Field Already Exists Even Though It Is Empty

Environment:

  • Clio Manage
  • Clio Grow

Additional Information:

When a custom field already exists in Manage, Clio will not overwrite it when importing from Grow, even if that custom field has no value. Since it is possible that the field have been left blank intentionally in manage, we cannot assume that the value should be overwritten. 

Workaround:

  1. In Clio Manage, remove any custom fields that are blank and need to be populated via the export
  2. In Grow, export the matter or contact as per normal.
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