Data transfer

Data transfer refers to moving your case data from one environment to another environment. This can be transferring your data between Relativity instances or from a legacy system. Relativity provides you with a suite of tools that can help you with this.

This page contains the following information:

Data transfer considerations

  • Before you can begin working in your RelativityOne environment, you may need to get your legacy data into Microsoft Azure. If you are a new RelativityOne customer or considering RelativityOne, we recommend that you review RelativityOne data migration as a first step.

  • RelativityOne also offers a variety of tools for managing your data. For more information on the methods in which data can be stored within your RelativityOne environment, refer to RelativityOne data management.

  • Changing root folder permissions during a mass import is not a supported workflow.

Data transfer network considerations

Before anyone in your organization can transfer data, you should ensure that your network and firewall settings have been configured correctly. See RelativityOne network access in the RelativityOne technical overview.

Data transfer workflows in RelativityOne

For RelativityOne, you have two major options for data transfer:

  • Loading data directly into RelativityOne using the Relativity Desktop Client in Aspera mode - you can use the RDC tool to transfer your processed data quickly and easily using Aspera.
  • Transferring data to the designated RelativityOne staging area - you can upload files to your RelativityOne staging directory using RelativityOne Staging Explorer.

    Note: The staging area is a cloud folder where you can view and edit data using the Utility Server before loading it into RelativityOne. The Utility Server is a virtual machine that can be connected to your RelativityOne instance that contains additional support tools to help you edit and view the data in your designated staging directory before loading it into RelativityOne. For example, you may want to access your uploaded files to edit in the staging directory before you add them to your RelativityOne workspaces or save them to a RelativityOne file storage location. You can also access and verify any production sets before you download them locally. Once you use the GlobalProtect VPN client to connect to the RelativityOne network, and then the Utility Server, you have access to viewing the staging area.

Refer to the following documentation topics to assist you in choosing your preferred method of data transfer.

Workflow 1: Loading processed data directly into RelativityOne (recommended)

You can use the Relativity Desktop Client locally (rather than from the Utility Server ) and import documents quickly using Aspera mode. This eliminates the need to first transfer the data to the RelativityOne storage.

For more information, see Setting up Aspera mode .

Workflow 2: Loading processed data to the staging directory and then into RelativityOne

If you need to edit or rename processed data, you can do so on your local machine prior to uploading or you can upload the processed data to the staging directory in the cloud and then ingest it into RelativityOne using the RDC in direct mode.

  1. Upload local files to your RelativityOne staging directory using the RelativityOne Staging Explorer .

    2. Note: The RelativityOne Staging Explorer uses Aspera to facilitate transfer speeds that can be 10 times faster than a traditional FTP. Combined with proprietary software, all transfers are fast, fully auditable, secure, and defensible.

  1. After you upload the files to your staging directory you can then ingest those files from your staging directory into RelativityOne using any of these three options:
    • Relativity Desktop Client (RDC) - The Relativity Desktop Client (RDC) provides the functionality for importing document load, image, and production files into your RelativityOne environment from your staging directory. The RDC is accessible from your Utility Server.
    • Integration Points - Integration Points provides you with the ability to import data directly into your workspace through the same functionality that the Relativity Desktop Client (RDC) provides for importing the document object. This includes importing a CSV file, LDAP, or load file directly into your workspace, and scheduling future or recurrent import jobs.

Workflow 3: Loading unprocessed data to your RelativityOne staging directory for processing

If you have unprocessed raw data, you can upload the raw data to the Processing folder in your staging directory in the cloud and then ingest it into RelativityOne using the Relativity Processing application.

  1. Upload local files to the Processing Source folder in your RelativityOne staging directory using the RelativityOne Staging Explorer .
  2. Using the Relativity Processing application, ingest your raw data directly into your RelativityOne workspace for eventual search, review, and production without the need for an external tool. You can use the various processing objects to create custom processing jobs that handle a wide array of information.

Workflow 4: Migrating case data to the staging directory into RelativityOne

If you have case/workspace data you need to migrate, you can upload the workspace archives to the ARM folder in your staging directory in the cloud and then ingest them into RelativityOne using the ARM application. The ARM application is used to archive, restore, and move Relativity workspaces between Relativity installations and RelativityOne. You can also use this application to convert a DBMT archive into an ARM archive.

  1. Use the ARM tool, to archive a workspace to the directory of your choosing. See Performance considerations for RelativityOne for more information on considerations for creating the archive file.
  2. Use RelativityOne Staging Explorer to upload the ARM archive to the ARM folder in your RelativityOne staging directory in the cloud.
  3. Execute an ARM Restore job to restore the ARM archive into your RelativityOne instance. ARM restore will recognize the ARM archive on the Utility Server and make it easily available for restoring.