Table of contents
- Obtaining work product from a ZIP Export
- Obtaining work product from a CSV Export
- Importing work product
You can use the import feature in the Codes tab within Project Settings to import review data. This could be useful if you need to migrate review data into Everlaw, potentially from other review platforms. This feature can also be used to quickly add new codes to a coding sheet. You might also want to transfer review work from an original document on one project, to a produced document on another project.
By default, projects do not share review product when you create multiple projects in a database. 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.
You can use the import feature to migrate data from one project to another, or to migrate data from another review platform.
For more information on how to save a copy of your project’s documents and work product, see this help article on exporting your project's documents and review work. Depending on your chosen method of export, you will proceed in one of the following two ways.
Obtaining work product from a ZIP Export
Create a ZIP Export that includes the documents you want to transfer data from, and select Review work product. This will include a CSV with all review work product on the selected documents. This includes notes, ratings, binders, codes, user-editable metadata, and Storybuilder data.
Obtaining work product from a CSV Export
Alternatively, you can 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’, ‘Annotation Data’, ‘Binder’, or ‘Rating’ fields, depending on your needs.
- For notes or redactions, select “Annotation Data” under the “Grid Column”
- For Binders, select “Binders” under the “Grid Column”
- For Rating, select “Rating” under the “Grid Column”
- For codes, select specific codes or categories you plan to transfer. If you want to transfer all codes, simply select "All Codes" or "All Categories". Make sure to also select “Exported Codes” under “Special Columns”, which allows you to export codes in the correct format for import.
- For Storybuilder data, you must export your documents in a ZIP export.
If codes are exported, you need to take two extra steps to prepare the CSV file for import. Open the file in a program like Microsoft Excel. Change the column header "Exported Codes" to "Codes." Then, delete the remaining columns of specific codes or categories, including "All Codes" and/or "All Categories" if included. Be sure to save this file as a CSV.
Importing work product
Now that you are equipped with your work product CSV, navigate to the project that you want to import the data into. Go to the ‘Codes’ section of the Project Settings page and scroll to the bottom. Open the file selector and choose the CSV you just created (please note there is a 70 MB cap on the CSV size). 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 project, 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.
Click ‘Import’ to launch the batch update. The progress of the update can be monitored on the homepage, under the Batches and Exports column.
Review work can be migrated from original documents to produced documents during production. However, you can also use the review work import function to transfer review work from original documents to the produced versions. The steps are very similar to transferring data between projects.
Create an export that includes the original documents you want to transfer data from and any review data you want to transfer.
Create an export that includes the produced documents you want to transfer data to and the field “Produced From". This will serve as a mapping file in Step 3.
Prepare a CSV file for import by replacing Begin Bates in the first CSV file with the Begin Bates from the second CSV file.
Import the data using the CSV file created in Step 3.
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. There is an example Everlaw CSV template that you can download that is linked at the bottom of this article.
You should use this Everlaw CSV template 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.
You can also request Everlaw to import your review data as codes for you. This would incur data manipulation charge at $140 per hour. The amount of time required will depend on the size of your dataset and the complexity of your coding sheet.