Reveal Help Center

Reveal Migration Services

Overview

Move data from your current database systems to the Reveal™ platform seamlessly using our Migration Services. We offer a software-driven process that makes migration of your data both efficient and affordable. Reveal™ can transfer ongoing or legacy matters from Relativity using either an ARM or load-files, and from any other e-discovery platform with a load-file export. We will consult with you from start to finish to choose the best method and ensure all work product your team has created will be maintained and is available in your new environment.

Relativity ARM Migrations

When transferring from Relativity, we recommend exporting an ARM archive. This will capture the most comprehensive set of data to be re-created in a Reveal™ database.

Load-File Exports

Virtually every item transferred via a Relativity ARM is also transferrable through load-file imports. Thus, load-file exports can be used to migrate from Relativity or any other e-discovery software application with the capability to export data via standard Concordance .DAT and .OPT files. Here is a sample list of technologies that migrate to Reveal™:

  • Concordance

  • CaseLogistix

  • Casepoint

  • Catalyst

  • CS Disco

  • Everlaw

  • IPRO

  • Lexbe

  • Logikcull

  • NextPoint

  • Relativity

  • Ringtail / Nuix

  • Summation

  • Xerra

What are .DAT and .OPT files?

A Concordance .DAT file is an industry standard text file with unique delimiters for typical punctuation used when populating a database. E-Discovery applications will generally export record information such as email senders, recipients, dates, subjects, file names of documents, in addition to various record IDs, work-product, and analytics performed on the original data such as near duplication and concept grouping.

A .OPT file is an image cross-reference text file that will link the series of images representing a document record. Since Reveal™ can manage multiple image sets, an .OPT can be provided for the “clean” set and any production sets created within the original database.

Our team will work with you to produce exports that will provide maximum data from the original database to transfer and be made visible and usable within the Reveal™ platform.

The chart below represents what can be automatically transferred to the Reveal™ platform with each type of migration format.

Database Item

Relativity ARM

Load File Exports

Metadata Fields

Automatic Field Mapping

Extracted & OCR Text

Native Files

Original Images

Production Images

Tags & Tag-like metadata1

Document & STR Folders

Wordlists (STR & Highlighting)

Image Highlights & Redactions

Not Currently

List of Users2

Not Currently

Assignment Batch Information3

Not Currently

Relativity Lists & Views

Not Currently

Relativity Saved Searches4

Not Currently

Relativity plugin analytics

Not Currently

Not Currently

Relativity Layouts

Not Currently

Not Currently

Relativity inverse redactions

Not Currently

Not Currently

Audit History

Not Currently

Not Currently

1 All metadata in Relativity that are set up with ’choices’ we import as tags. We also provide these tags as metadata in Reveal™, as often custodial metadata are in Relativity as ’choices’.

2 Transfer does not retain user information beyond first and last name.

3 User association to batch is not maintained.

4 Created as a folder without search criteria.

Maintaining Existing Work-Product

Through automated processes, data that is or can be added to a field can be imported to Reveal™ and used as a field, folder or tag. In many ways, these function similarly, with the decision to place information in one over the other based on purpose.

image1.png
image2.png

Fields, folders and tags all provide details and organizational structure to the document database, but folders and tags separate themselves from fields with the ability to provide a more functional structure allowing users to share and store sub-sets of records in a meaningful way. Only a folder can be used to isolate a group of documents for production. In addition, tags further differentiate themselves by providing additional ease to a document review for any type of legal proceeding. Tags can be set as Required or On By Default depending on review workflow; they can also be flagged as Privileged to prevent documents with this tag from being produced accidentally. Reveal™ has established workflow and reporting utilizing the tagging mechanism, making it a clear choice for certain information being migrated.

The automated import of tags and folders works similarly for other data uploaded to Reveal™. A unique ID and a field with the associated tag or folder is all that is necessary to rebuild current work-product for optimal function in the platform, all while maintaining the same structure and hierarchy utilized in the original database.

Finally, Reveal can develop methods to use combinations of technology and manual effort to re-create “must-have” work-product within the database. For example, use Reveal™ folders to capture saved searches from existing databases, original image production with redactions ‘burned in’ to transfer as an additional image set to represent all redaction and not just those produced, are just a couple of typical workflows. With access to your migrating databases, we can further assist in emulating current look, feel and functionality by manually transferring saved searches, tag profiles, users/user profiles and other items not susceptible to automated transfer. We can capture redaction coordinates with systems that export these to .XML.

In conclusion, Reveal™ will apply both automated and custom methods to migrate your projects completely and will recommend the best course of action to limit the interruption of your ordinary course of business.

Migration Process & Timelines

The timelines, success, and accuracy of a migration is dependent on database size, the kind and number of work product items being transferred, and the diligence applied to the overall process.

Tracking logs are created and maintained to provide visibility and assurance that every item is accounted for throughout the project.

image3.png

Record tracking chart for documents, text, image, and native counts.

image4.png

Tag tracking chart for tag names, new tag type and document counts for each tag.

The following chart outlines a typical schedule to move a database to Reveal™ showing the stages depending on the artifacts requiring transfer.

image5.png

A smaller project with few artifacts to transfer will take less time and larger projects with millions of records will take longer. It is also possible to migrate several databases on a parallel track to save additional time.