Migration Workflow Guide and Best Practices

To read more about uploading documents on Everlaw, feel free to refer to the articles in our Uploads section.

While uploading data into Everlaw is easy, there are some special considerations when migrating your case documents and review data from another platform. This article will walk you through elements to consider and information you should provide your account representative or the Customer Experience team (reachable at support@everlaw.com) before sending Everlaw migrated data.

Note: If you are interested in ARM database migration, please reach out to support@everlaw.com to learn more.

What is migrated data?

For the purposes of this article, migrated data refers to data currently or previously hosted on a different platform, including both the documents, their intrinsic metadata, and the review work done so far. This could be either pre-produced data that you are reviewing for responsiveness or produced data that you have received and are reviewing for case preparation. This does not include produced data that you have received from another party and have not reviewed.

Information Everlaw needs

Before we are ready to ingest migrated data, we need some information:

  1. Will the documents be produced?

If so, Everlaw needs either the raw natives, or a complete set of processed formats (i.e., image, text, and native formats). This will ensure we can either send the raw native documents through on our platform processing system, or upload the already processed documents as we would a normal production. We cannot work with processed documents where a particular format (text, image, or native) is missing. See the native uploads article and the processed uploads article for more information on how uploads work in Everlaw. 

  1. How would you like review data ingested?

If you would like your review data from other platforms added to Everlaw, you have two options. The first is to upload your codes as metadata fields. This would still allow you to search for all documents that have that value in their metadata but the data would not display as a code in Everlaw.  You can also easily batch code the search results for a given metadata search and transfer metadata to codes that way.

The second option is to import your review data as codes after the documents have been uploaded to the platform. You can either perform the import by yourself with a CSV file that conforms with the required structure (a template is attached at the end of this article). For instructions on how to import codes and ratings into Everlaw, see Section 1 Step 2 of this article. You can also request Everlaw to import your review data as codes for you. The amount of time required will depend on the size of your dataset and the complexity of your coding sheet. More information about codes and coding categories can be found here.

Uploading your data

Once you have determined whether your documents will be produced and how you would like your review data ingested, your data can be uploaded to the platform. While we need to receive any opposing party productions in their original format, our preferred format for migrated data is a load file with natives, text, and images. Even if your data does not meet those criteria, we can still upload it. We can upload standard data at no charge but non-standard data will incur a charge of $140/hour. More information about non-standard data can be found here.


Have more questions? Submit a request


Article is closed for comments.