Table of Contents
You can use the import feature on the ‘Codes’ page under Case Settings to update the review status and review product applied to documents. This review product can include codes, binders, or ratings. The most common reasons to use the import functionality are to migrate review data into Everlaw and to transfer review data between projects. This feature can also be used to quickly add new codes to a coding sheet.
Transferring Data Between Projects in Everlaw
By design, projects do not share review product. If the same document is in two projects, any ratings, codes, notes, etc. applied to it in one project are not reflected in the other. However, you can use the import feature to migrate data from one project to another.
Step 1: Create a CSV export that includes the documents you want to transfer data from. At minimum, the export must contain the ‘Begin Bates’ and ‘End Bates’ fields. From there, you can add the ‘Codes’, ‘Notes’, ‘Binder’, or ‘Rating’ fields, depending on your needs.
Step 2: Navigate to the database that you want to import the data into. Go to the ‘Codes’ section of the Case Settings page and scroll to the bottom. Open the file selector and choose the export you just created. Click the ‘Verify Import’ button. The following dialogue should appear:
The box displays all the detected Bates prefixes. If you don’t want to import data for documents that fall under a particular Bates prefix, delete the prefix from the list. If you are importing coding, and the codes you are attempting to import do not exist in the database, you must check the ‘Create new codes’ box. This will also add any new codes and coding categories to the coding sheet. The appropriate binders will also be created if binder information is included in the import file.
Step 3: Click ‘Import’ to launch the batch update. The progress of the update can be monitored on the homepage, under the Batches and Exports column.
Importing Outside Review Product
Review product from other platforms can be imported into Everlaw in the exact same way as transferring data between projects. The naming and structure of the import data must be the same as an Everlaw CSV export. Otherwise, the import will fail and an error message will be returned.
You should use an Everlaw CSV export as a model of how to structure outside data. Follow the instructions outlined in the previous section to import after conforming the structure of the data to match the Everlaw CSV format.