KEMBAR78
RelativityOne - Import Export Guide | PDF | File Format | Zip (File Format)
0% found this document useful (0 votes)
17 views217 pages

RelativityOne - Import Export Guide

Uploaded by

vojen72775
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views217 pages

RelativityOne - Import Export Guide

Uploaded by

vojen72775
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 217

Import/Export Guide

October 6, 2025

For the most recent version of this document, visit our documentation website.
Table of Contents
1 Import/Export overview 6
1.1 Getting started with Import/Export checklist 6
1.2 Available import and export workflows 7
1.3 Import/Export transfer modes 8
1.4 Considerations when to use and not use Express Transfer with Import/Export 8
1.5 Supported file types 9
1.6 Data upload size limitation 9
1.7 Concurrent and consecutive jobs 9
2 Installing Import/Export 10
2.1 Requirements 10
2.1.1 Workspace requirements 10
2.1.2 Port Access 10
2.2 Installing Import/Export 10
3 Permissions 12
4 Import/Export load file specifications 14
4.1 Supported file types 14
4.2 Metadata, extracted text, and native files 14
4.2.1 Encoding 15
4.2.2 Header row 16
4.2.3 Fields 16
4.2.4 Accepted date formats 18
4.2.5 Delimiters 19
4.2.6 Default delimiters 20
4.2.7 ZIP archive with extracted text and natives 20
4.3 Image and extracted text files 21
4.3.1 Supported image file formats 21
4.3.2 Load file format 21
4.3.3 ZIP archive with images 22
4.3.4 Importing extracted text during an image load 22
4.4 Processed data 22
4.5 Transcript file types supported 23
4.6 Access DB (MDB) load file specifications 23

Import/Export Guide 2
4.6.1 Export table 23
4.6.2 Parties Table 24
4.6.3 Pages table 25
4.6.4 Export_Extras table 25
4.6.5 Example of values in Export_Extras table 25
4.6.6 Export recommendations 26
5 General recommendations for structured data import and export jobs 27
5.1 Load file import recommendations 27
5.2 Load file export recommendations 27
6 Express Transfer overview 29
6.1 Prerequisites 29
6.2 Considerations when to use and not use Express Transfer with Import/Export 29
6.3 Express Transfer overview 30
6.3.1 Prerequisites 30
6.3.2 Considerations when to use and not use Express Transfer with Import/Export 30
6.4 Installing and updating Express Transfer desktop application 31
6.4.1 Requirements 31
6.4.2 Prerequisites 31
6.4.3 Installing Express Transfer 32
6.4.4 Silent installation of Express Transfer 34
6.4.5 Locating the Express Transfer version number 35
6.4.6 Automatically checking for software updates 37
6.4.7 Manually checking for software updates 39
6.5 Activating and deactivating Express Transfer 40
6.5.1 Prerequisites 40
6.5.2 Considerations when to use and not use Express Transfer with Import/Export 41
6.5.3 Activating Express Transfer 41
6.5.4 Deactivating Express Transfer 43
6.5.5 Data transfer performance considerations 43
6.6 Express Transfer system tray menu 45
6.7 Express Transfer Preferences 45
6.7.1 Automatically checking for software updates 46
6.7.2 Limit bandwidth 48
6.7.3 Exclude temporary Microsoft Office files from data import 51

Import/Export Guide 3
6.7.4 Configuring proxy settings 54
6.8 Express Transfer Connectivity check 56
6.8.1 Network Throughput Check 59
6.9 Express Transfer Job tracking and history 59
6.10 Express Transfer reporting jobs failed or completed with errors 64
7 Importing data using Import/Export 67
7.1 Structured data import from Staging 67
7.2 Pre-check Load File 69
7.2.1 Document and RDO load file import 70
7.2.2 Image and Production load file import 71
7.2.3 Working with Pre-check Load File results 72
7.3 Importing data using Import/Export 72
7.3.1 Structured data import from Staging 73
7.3.2 Pre-check Load File 74
7.4 Importing a document load file 77
7.5 Importing an image load file 89
7.5.1 Considerations 89
7.5.2 References 89
7.5.3 Before you begin 89
7.5.4 Importing image load file workflow 89
7.6 Importing a production load file 98
7.7 Importing an RDO load file 106
7.8 Importing an Access DB load file (MDB) 117
7.9 Importing transcript MDB data for Processing via Import/Export Limited General Availability 126
7.9.1 Before you begin 126
7.9.2 Importing transcript MDB data 127
7.10 Importing raw unprocessed data for Processing via Import/Export 132
8 Exporting data using Import/Export 141
8.1 Exporting data using Import/Export 141
8.2 Exporting a folder load file 141
8.3 Exporting a production set load file 155
8.4 Exporting an RDO load file 167
8.5 Exporting a saved search load file 178
8.6 Exporting a saved search or a folder with Access DB load file (MDB) 191

Import/Export Guide 4
8.7 Exporting a production set with Access DB load file (MDB) 202
9 Import/Export Job tracking and history 213
9.1 Reviewing the Import/Export Job page 213
9.2 Support for Mass Operations 214
10 Import/Export queue 215

Import/Export Guide 5
1 Import/Export overview
Import/Export provides an efficient and streamlined ability to import raw data files, document load files, image load
files, production files, RDO files, as well as to export folders and subfolders, production sets, saved searches, and
RDO files. It is the recommended method for importing and exporting data for RelativityOne.

You can use Import/Export with or without activating Express Transfer, however, we recommend activating Express
Transfer. For more information on Express Transfer, see Express Transfer overview on page 30 and review the
section below on considerations when to use and not use Express Transfer.

Notes:
l For customers whose file shares haven’t been fully migrated to ADLS yet, Import/Export offers a solution
where the import process utilizes the primary file share to store the uploaded data. See the Community article
Import/Export uses ADLS if one is present on the tenant for details.
l After documents are imported using Import/Export, you can automate creating a dtSearch index or run a
search terms report with those documents using Automated Workflows

1.1 Getting started with Import/Export checklist


Ready to get up-to-speed with Import/Export? Learn more about the functionality, how to get it installed in your
instance of RelativityOne, and workflow specifics with the resources listed below.
Overview Sessions:

Import/Export Guide 6
Take a deeper dive by watching our recorded Import/Export Foundations: Comprehensive Overview webinar, in
addition to other Import/Export self-paced webinars on the Relativity Learning site under Data Ingestion
& Management.
Before you can start working with Import/Export, you will have to set things up in your RelativityOne instance:

1. Reach out to your IT Department and ensure TCP port 443 is open to transfer data in RelativityOne with
Express Transfer.
2. Install Import/Export from the Relativity Application Library.
3. Open Import/Export and install Express Transfer for larger data transfers and to streamline structured data
loads. Only complete this step if your organization intends to use Express Transfer with Import/Export.
4. Ensure that users have the proper permissions.

Note: Feature Permissions provide an alternative to Relativity's security management by shifting the focus
from Object Types and Tab Visibility to feature-based permissions. This method is simply another option; any
feature-specific permissions information already in this and other topics is still applicable. The Feature Per-
missions interface enables administrators to manage permissions at the feature level, offering a more intu-
itive experience. By viewing granular permissions associated with each feature, administrators can ensure
comprehensive control, ultimately reducing complexity and minimizing errors. For details see Instance-level
permissions and Workspace-level permissions.

Now that Import/Export is set up, you are ready to perform these workflows and benchmark your speeds:

l Import data, both structured and unstructured


l Export folders, RDO data, productions and saved searches
l Import and export data using Express Transfer with Import/Export
l View the Job History
Have questions?

l Submit a ticket to Customer Support for workflow assistance.


l Visit our What’s New page, Relativity Documentation or our Community Site.
l Contact Relativity Customer Support.

1.2 Available import and export workflows


The following workflows can be performed using Import/Export.

l Import workflows:
l Unstructured Data —Unprocessed/unstructured files and transcript MDB data that require processing
l Raw (Unprocessed) data workflow with Processing
l Transcript data for Processing

l Structured (Processed) Data—Structured data includes natives, text, image, and PDF files, and load files
containing metadata.

l Document load file import


l Image load file import
l Production load file import

Import/Export Guide 7
l Relativity Dynamic Object load file import
l Access DB load file import (MDB) (for Asia-Pacific region only)
l Export workflows:
l Folder export
l Production set export
l Saved Search export
l RDO export
l Saved Search or Folder with Access DB export (MDB)Saved Search or Folder with Access DB export
(MDB) (for Asia-Pacific region only)
l Production set with Access DB export (MDB) (for Asia-Pacific region only)

1.3 Import/Export transfer modes


There are two methods available to transfer data using Import/Export. Refer to the next section for considerations
when to use each one.

l Import/Export with Express Transfer


This refers to activating Express Transfer within Import/Export to transfer data into and out of RelativityOne.
This mode is the recommended method for data transfer. Express Transfer is a separately installed desktop
application that sits outside of the RelativityOne browser software and handles the data transfer process. See
Express Transfer overview and Installing Express Transfer for more information.
l Import/Export only
This refers to only using the Import/Export browser application within the RelativityOne software to import and
export data without Express Transfer activated. This mode is sometimes referred to as web mode or web only
mode. See Installing Import/Export. Even if the Express Transfer application is installed on the desktop, it must
not be activated when using web mode.

1.4 Considerations when to use and not use Express Transfer with
Import/Export
We recommend using Import/Export with Express Transfer activated whenever possible for all importing and
exporting workflows, and particularly when:

l data file size is greater than 20 GB, although Express Transfer can be used for any size data transfer.
l processing multiple import jobs. The jobs will be queued and executed when the previous job is complete.
l slow or unstable network connection. Express Transfers enables you to retry the upload.
Use Import/Export without activating Express Transfer when:

l your company policy prohibits installing desktop applications.


l your network configuration does not allow third party applications to send or receive data, such as proxy set-
tings.
l data file size is less than 20 GB.
l data is in ZIP files.

Import/Export Guide 8
Note: You need to use Express Transfer to upload and process encrypted materials, such as password-protected
zip files or Case files (L01/N01) that require Password Bank functionality. If you cannot use Express Transfer for
such imports, zip your encrypted materials in a single unencrypted ZIP container. The 20 GB limit for the zip file size
applies. Import/Export will transfer and extract the top-level zip file, preparing your encrypted materials for Pro-
cessing. Then, Processing will utilize Password Bank to decrypt materials.

1.5 Supported file types


Import/Export supports the following file types. Refer to Import/Export load file specifications for more information
regarding load files. Also see General recommendations for structured data import and export jobs on page 27.

l ZIP and PST files—for transferring data to the server-side.


l Native files for processing—see the list of supported file types for processing within the Processing guide.
l Document Load File import—.dat, .csv and .txt load files.
l Image Load File import—Opticon-formatted page-level files. Formats supported: single page TIFF (Group IV)
files, single page JPG files, and single and multiple PDF files.
l Access DB load file import—.mdb or .accdb. For more information, see Access DB (MDB) load file spe-
cifications.

Note: RelativityOne allows users to restrict given file types from being imported into their instances with the Restric-
tedFileTypes instance setting. Import/Export reads and applies this instance setting when importing materials into
RelativityOne, therefore, all file types listed as restricted file types will be skipped.

1.6 Data upload size limitation


When Express Transfer is activated for use with Import/Export, there is no data upload limit. See Express Transfer
overview and Activating Express Transfer for more information.
When Express Transfer is not activated for use with Import/Export, the application accepts single .zip or .pst
containers or a single structured import data set load file up to 20 GB for a single import.

1.7 Concurrent and consecutive jobs


The concurrent or consecutive nature of a job depends on what stage the job is at, which data transfer mode you're
using: web only or Express Transfer, and what type of job you're running: Processing, Import, or Export. For more
information, see the Community article Import/Export Concurrent and Consecutive Jobs.

Import/Export Guide 9
2 Installing Import/Export
The Import/Export application will not be installed automatically in all your workspaces so you must do so manually in
each one from the Relativity Application Library.

2.1 Requirements
Refer to the sections below for the necessary requirements for Import/Export.

2.1.1 Workspace requirements


When using Import/Export, you need the following RelativityOne applications installed in your workspace from the
Relativity Application Library:

Note: Import/Export requires the Relativity.Transfer.Service to be installed in your RelativityOne instance. This is a
global RelativityOne application that is installed and updated automatically.

l Import/Export; see installation steps below


l Export
l Import
l Processing; only required if you intend to process unstructured raw data for processing with Import/Export
l Relativity Lists (version 1.2.305 or newer)

Note: Import/Export requires Relativity Lists version 1.2.305 or newer to be installed and enabled in the work-
space for running import and export jobs. If the Relativity Lists application is not available, all Import/Export
workflows will be disabled.

2.1.2 Port Access


Import/Export requires TCP port 443 to be open to transfer data. For further assistance, please contact your
IT Department. Also refer to the Import Export Application - Required Ports article in Community for additional
information.

2.2 Installing Import/Export


To manually install Import/Export in the workspace:

1. Log into RelativityOne as an Admin user.


2. Navigate to the Application Library.
3. Type Import/Export in the Name field's filter and press Enter.
4. Click the Import/Export application name to go to the Application Information tab.
5. Click Select in the Workspaces Installed pane.
6. Find and select your workspace(s) and click the right arrow button to move it to the right-hand pane.
7. Click Apply.

Import/Export Guide 10
If you want to use Import/Export with Express Transfer, which is recommended in most cases, you must activate
Express Transfer within the Import/Export application. Refer to Express Transfer overview on page 30 and Activating
Express Transfer on page 41 for more information.

Import/Export Guide 11
3 Permissions
Note: Feature Permissions provide an alternative to Relativity's security management by shifting the focus from
Object Types and Tab Visibility to feature-based permissions. This method is simply another option; any feature-
specific permissions information already in this and other topics is still applicable. The Feature Permissions inter-
face enables administrators to manage permissions at the feature level, offering a more intuitive experience. By
viewing granular permissions associated with each feature, administrators can ensure comprehensive control, ulti-
mately reducing complexity and minimizing errors. For details see Instance-level permissions and Workspace-level
permissions.

Import/Export validates the user's permissions and checks if all required applications are installed in their workspace.
If the user does not have permission to run a given workflow or if any application needed for that workflow is not
installed, Import/Export grays out the workflow button and displays a warning message below it explaining why it's
inactive. This validation process works separately for each workflow. For example, if a user does not have permission
to run a Processing job, they may still be able to import load file data but will not be able to process it.
All permissions are set in Workspace security.
The following permissions are designated for all import and export workflows:

Other Set-
Object security Tab visibility
tings

l Document—Add, Edit, View l Documents


l Folder—Add, Edit l Import/Export
Job
l Import/Export Extraction Job—Add, Edit
l Import/Export Job—Add, Edit
l Relativity Time Zone—View
Additional permissions designated for Raw (Unprocessed) Data import and Transcript MDB Data import workflows
only:

Object security Tab visibility Other Settings

l Entity—Add, Edit Mass operations

l OCR Language—View l Allow Import


l Processing Data Source—Add, Edit, View l Allow Staging
Import
l Processing Error—Add, Edit
l Processing Set—Add, Edit, View
l Quick Create Set—Add, Edit

Additional permissions designated for Structured Data import workflows only:

Object security Tab visibility Other Settings

l Production—View Admin operations

l Relativity Import Data Source—Add, Edit, l Allow Import


View l Allow Staging

Import/Export Guide 12
Object security Tab visibility Other Settings

l Relativity Import Job—Add, Edit, View Import

Note: Import/Export now allows importing data directly from the Staging locations, such as StructuredData (load
file) and ProcessingSource (raw data). The Allow Staging Import permission is required to activate these import
options in the application UI.

Additional permissions designated for Export workflows only:

Object security Tab visibility Other Settings

l Import/Export Job—Add, Edit Admin operations

l Production—View l Allow
Export
l Relativity Export Service Job—Add,
Edit, View

Import/Export Guide 13
4 Import/Export load file specifications
A load file is used to transfer data and its associated metadata into a database. During import, the application reads
the load file to determine what metadata should be written into each field and to copy it to the workspace. If your
organization uses a processing vendor, you’ll need to upload case data with a load file. You'll also use load files when
you receive a subset of data from another party, such as a production from opposing counsel.
Below are the load file specifications for Import/Export.

4.1 Supported file types


Import/Export supports the following file types.

l ZIP and PST files—for transferring data to the server-side.


l Native files for processing—see the list of supported file types for processing within the Processing guide.
l Document Load File import—.dat, .csv and .txt load files.
l Image Load File import—Opticon-formatted page-level files. Formats supported: single page TIFF (Group IV)
files, single page JPG files, and single and multiple PDF files.
l Access DB load file import—.mdb or .accdb. For more information, see Access DB (MDB) load file spe-
cifications.

Note: RelativityOne allows users to restrict given file types from being imported into their instances with the Restric-
tedFileTypes instance setting. Import/Export reads and applies this instance setting when importing materials into
RelativityOne, therefore, all file types listed as restricted file types will be skipped.

Import/Export web only accepted file types:


For Unstructured Processing Jobs

l PST—Individual Entity and Custodian files


l ZIP containers:
l All loose files must be in a ZIP container
l Entity and Custodian identifier at the folder level
For Load Files and Structured Data Sets

l Load file—Keep the Load File (.dat, .opt, etc.) separate from zipped documents
l Files—Native or Image/Production files must be in a ZIP container

4.2 Metadata, extracted text, and native files


Import/Export uses a flat, document-level load file to load metadata, document level extracted text, and natives files.
Each line should represent one document.

Note: Import/Export requires consistent line breaks, that is, end-of-line (EOL) characters, throughout the load file.
Mixing line endings, such as UNIX (LF), Mac (LF), and Windows (CRLF), can cause errors or unexpected behavior
during import. To ensure smooth processing, use only one type of line break in the entire file.

Import/Export Guide 14
4.2.1 Encoding
You must choose the proper encoding of a file when a load file is first selected. Import/Export supports the following
encodings:
l Arabic (ASMO 708)
l Arabic (ISO)
l Arabic (Windows)
l Baltic (ISO)
l Baltic (Windows)
l Central European (ISO)
l Central European (Windows)
l Chinese Simplified (GB18030)
l Chinese Simplified (GB2312)
l Chinese Traditional (Big5)
l Cyrillic (DOS)
l Cyrillic (ISO)
l Cyrillic (KOI8-R)
l Cyrillic (KOI8-U)
l Cyrillic (Mac)
l Cyrillic (Windows)
l Estonian (ISO)
l Greek (ISO)
l Greek (Windows)
l Hebrew (ISO-Logical)
l Hebrew (ISO-Visual)
l Hebrew (Windows)
l Japanese (EUC)
l Japanese (JIS 0208-1990 and 0212-1990)
l Japanese (JIS)
l Japanese (JIS-Allow 1 byte Kana - SO/SI)
l Japanese (JIS-Allow 1 byte Kana)
l Japanese (Shift-JIS)
l Korean
l Korean (EUC)
l Latin 3 (ISO)
l Latin 9 (ISO)

Import/Export Guide 15
l Thai (Windows)
l Turkish (ISO)
l Turkish (Windows)
l Ukrainian (Mac)
l Unicode (UTF-16)
l Unicode (Big-Endian)
l Unicode (UTF-8)
l US-ASCII
l Vietnamese (Windows)
l Western European (ISO)
l Western European (Mac)
l Western European (Windows)

4.2.2 Header row


Import/Export does not require load file header rows. However, they are strongly recommended to ensure accuracy.
The field names in your header do not need to match the field names in your workspace.

4.2.3 Fields
RelativityOne doesn’t require any specific load file field order. You can create any number of workspace fields to store
metadata or coding.
During the load process, you can match your load file fields to the fields in your workspace. The identifier field is
required for each load. When loading new records, this is your workspace identifier.
When performing an overlay, you can use the workspace identifier or select another field as the identifier. This is
useful when overlaying production data. For example, you could use the Bates number field rather than the document
identifier in the workspace.
All fields except Identifier are optional.
However, you may find some of the following system fields beneficial:
l Identifier—the unique identifier of the record.
l Group Identifier—the identifier of a document’s family group.
l The group identifier repeats for all records in the group.
l Usually, this is the document identifier of the group’s parent document. For example: If an email with the
document identifier of AS00001 has several attachments, the email and its attachments have a group
identifier of AS00001.
l If a group identifier for a record is not set, the document identifier populates the group identifier field in the
case. This effectively creates a “group” of one document.
l MD5 Hash—the duplicate hash value of the record.
l You can enter any type of hash value, and rename the field in your case.
l If documents share the same hash value, the software identifies the documents as a duplicate group.

Import/Export Guide 16
l If a hash field for a record is not set, the document identifier populates the hash field in the case. This
effectively creates a “group” of one document.
l Extracted Text—the text of the document. Either the OCR or Full Text. The extracted text appears in the
viewer and is added to search indexes. This field can contain either:
l The actual OCR or Full Text.
l The path to a document level text file containing the OCR or Full Text. Both relative and absolute (full)
paths are supported; however, to import load file data that contains absolute paths, Express Transfer
must be activated. Relative paths can start with Blank or .\, as in: MainFolder\SubFolder\File.extension or
.\MainFolder\SubFolder\File.extension. Absolute paths can start with a backslash (\), as in: \MainFolder-
\SubFolder\File.extension.
l Native File Path—the path to any native files you would like to load. Both relative and absolute (full) paths are
supported; however, to import load file data that contains absolute paths, Express Transfer must be activated.
Relative paths can start with Blank or .\, as in: MainFolder\SubFolder\File.extension or .\MainFolder-
\SubFolder\File.extension. Absolute paths can start with a backslash (\), as in: \MainFolder-
\SubFolder\File.extension.

Notes:
l To avoid import errors, run a load file precheck via the Precheck Load File button to validate whether
the native file paths are correct and that linked native files exist and are accessible.
l Currently, the application does not check if duplicate native file paths are in the load file. Therefore, you
may want to manually review your load file data to ensure there are no duplicated file paths before start-
ing an import job. Duplicated native file paths do not cause import errors, but they may lead to billing
consequences.

l Folder Info—builds the folder browser structure for the documents.


l This field is backslash “\” delimited.
l If not set, the documents load to the root of the case.
l Each entry between backslashes is a folder in the system's folder browser.
l Each backslash indicates a new subfolder in the browser. For example, if the load file contained the fol-
lowing entry in the folder information field, “Slinger, Ryan\Email\deleted_items”, then the software would
build the following folder structure:

Each document with the above entry would be stored in the “deleted_items” folder.
l Relativity Native Time Zone Offset—numeric field in decimal format that applies a time zone offset to date/-
time values displayed in the Native Viewer, such as the Sent Date/Time in email headers.
l If the field value is blank or 0, no offset is applied, and the date/time is displayed in Coordinated Universal
Time (UTC).
l The field accepts whole or fractional numbers, positive or negative, to represent the desired offset from
UTC. For example, “-5”, “5.5”, “-6.0”. To display time in India Standard Time (IST), enter “5.5” because
IST is UTC+5:30. If you want to display time in Central Time for Chicago, use “-6.0” for standard time or “-
5.0” if Daylight Saving Time (CDT) is in effect.

Import/Export Guide 17
l The value should account for any Daylight Saving Time (DST) adjustments based on the document’s
date and the intended time zone. The Native Viewer does not automatically adjust for DST.
l This offset only affects how date/time values appear in the Native Viewer. Metadata fields and extracted
text are displayed exactly as imported.

4.2.4 Accepted date formats


RelativityOne accepts date and time as one field. For example, Date Sent and Time Sent should be one field. If date
sent and time sent ship separately, you must create a new field for time. You can format date fields to accept the date
without the time, but not the time without the date. Dates cannot have a zero value. Format dates in a standard date
format such as “6/30/2023 1:23 PM” or “6/30/2023 13:23”.

Note: To import or export data with a date/time format that differs from the US format, be sure to select the correct
Regional Settings option when creating a new Import/Export job.

The table below lists the date formats recognized by Import/Export and Import Service (IAPI). It contains both valid
and invalid date formats:

Entry in Load File Object Type Definition

Monday January 4 1/4/2318 0:00


2023
05/28/2023 7:11 AM 05/28/2023
7:11 AM
5.08:40 PM 6/30/2023 The current date will be entered if the date is missing. For this example,
17:08 assume the import was done on 6/30/2023.
17:08:33 6/30/2023 The current date will be entered if the date is missing. For this example,
17:08 assume the import was done on 6/30/2023.
17:08 6/30/2023 The current date will be entered if the date is missing. For this example,
17:08 assume the import was done on 6/30/2023.
5:08 PM 6/30/2023 The current date will be entered if the date is missing. For this example,
17:08 assume the import was done on 6/30/2023.
14-Apr 4/14/2023 The current year will be entered if the year is missing.
0:00
9-Apr 4/9/2023 0:00 The current year will be entered if the year is missing.
14-Mar 3/14/2023 The current year will be entered if the year is missing.
0:00
1-Mar 3/1/2023 0:00 The current year will be entered if the year is missing.
22-Feb 2/22/2023 The current year will be entered if the year is missing.
0:00
20230420 4/20/2023
0:00
20230420 2:22:00 4/20/2023
AM 0:00
4/9/2023 16:13 4/9/2023
16:13

Import/Export Guide 18
Entry in Load File Object Type Definition
4/9/2023 8:49 4/9/2023 8:49
9-Apr-23 4/9/2023 0:00
Apr. 9, 23 4/9/2023 0:00
4.9.2023 4/9/2023 0:00
4.9.23 4/9/2023 0:00
4/9/2023 4/9/2023 0:00
4;9;2023 4/9/2023 0:00
Wednesday, 09 April 4/9/2023 0:00
2023
12-31-2023 12/31/2023
12:00 AM
2023-11- 11/28/2023
28T17:45:39.744- 0:00
08:00
4/9/23 13:30 PM Results in an error
2023-044-09 Results in an error
4/9/2023 10:22:00 Results in an error
a.m.
00/00/0000 Results in an error unless the CreateErrorForInvalidDate value is set to false.

4.2.5 Delimiters
During import, you can choose which delimiters are used in your load file. You can select each delimiter from the
ASCII characters, 001 – 255.
The delimiter characters have the following functions:

l Column—separates load file columns.


l Quote—marks the beginning and end of each load file field. It is also known as a text qualifier.
l Newline—marks the end of a line in any extracted or long text field.
l Multi-value—separates distinct values in a column. This delimiter is only used when importing into a Relativ-
ityOne multi-choice field.
l Nested-values—denotes the hierarchy of a choice. This delimiter is only used when importing into a Relativ-
ityOne multi-choice field.
For example, say a load file contained the following entry, and was being imported into a multi-choice field:
“Hot\Really Hot\Super Hot; Look at Later”
With the multi-value delimiter set as “;” and the nested value delimiter set as “\"”, the choices would appear in

Import/Export Guide 19
RelativityOne as:

All checkboxes are automatically selected under each nested value. The full path to each multi-choice element is
required. For example:

DocID New Privilege

04. Redact;01. Yes\b.


NZ997.001.00000048 Solicitor/Client;
appears as:

To select "01. Yes/a. Litigation," add it to the record after ";".

4.2.6 Default delimiters


If you generate your own load files, you may choose to use the system defaults:

l Column—Unicode 020 (ASCII 020 in the application)


l Quote—Unicode 254 (ASCII 254 in the application)
l Newline—Unicode 174 (ASCII 174 in the application)
l Multi-Value—Unicode 059 (ASCII 059 in the application)
l Nested Values—Unicode 092 (ASCII 092 in the application)

4.2.7 ZIP archive with extracted text and natives


To import any text or native file when not using Express Transfer, you need to zip the files and upload the zip file in the
Choose Load File And Location dialog in Import/Export.
The zip file structure can be either flat or hierarchical with multiple levels of sub-folders. You must ensure that file
paths in the related load file match the zip file's structure.
See below for a sample of a hierarchical zip file structure and a matching load file:

Import/Export Guide 20
^Control Number^|^Extracted Text^|^Native File^
^DOCUMENT_
12345^|^MainFolder\SubFolderTextA\SubFolderTextB\TextFile12345.txt^|^MainFolder\SubFolderNatives\NativeFile
12345.xls^

4.3 Image and extracted text files


For image imports, Import/Export requires Opticon load files with ANSI/Western European encoding. This .opt text file
references the Control ID on a page level. The first page should match up to any data you intend to load. You can use
this same process for importing page-level extracted text.
Import/Export does not support Unicode .opt files for image imports. When you have a Unicode .opt file, you must
save it in ANSI/Western European encoding.
You must convert images in unsupported formats using a third-party conversion tool before Import/Export can
successfully upload them.

4.3.1 Supported image file formats


Import/Export accepts only the following file types for image loads:

l Single page, Group IV TIF (1 bit, B&W)


l Single page JPG
l Single page PDF
l Multi page PDF
l Multi page TIF can be imported into the system, but you must load them as native files.
l Only one PDF per document is supported.

4.3.2 Load file format


The Opticon load file is a page-level load file in which each line represents one image.
A sample of Opticon load file is the following:
REL00001,REL01,D:\IMAGES\001\REL00001.TIF,Y,,,3
REL00002,REL01,D:\IMAGES\001\REL00002.TIF,,,,
REL00003,REL01,D:\IMAGES\001\REL00003.TIF,,,,
REL00004,REL01,D:\IMAGES\001\REL00004.TIF,Y,,,2
REL00005,REL01,D:\IMAGES\001\REL00005.TIF,,,,
The fields are, from left to right:

l Field One (REL00001)—page identifier.


l Field Two (REL01)—volume identifier; not required and not used in Import/Export.
l Field Three (D:\IMAGES\001\REL00001.TIF)—path to the image to be loaded.
l Field Four (Y)—document marker: “Y” indicates the start of a unique document.

Import/Export Guide 21
l Field Five (blank)—used to indicate a folder; not required and not used in Import/Export.
l Field Six (blank)—used to indicate a box; not required and not used in Import/Export.
l Field Seven (3)—used to store page count; not required and not used in Import/Export.

4.3.3 ZIP archive with images


To import images when not using Express Transfer, you need to zip the image files and upload the zip file in the
Choose Load File And Location dialog in Import/Export.
The zip file structure can be either flat or hierarchical with multiple levels of sub-folders. You must ensure that image
file paths in the related load file match the zip file's structure.

4.3.4 Importing extracted text during an image load


You can also import extracted text during the image import process by setting an option in Import/Export. For more
information about importing extracted text during an image load, see Importing an image file via Import/Export.
No changes are needed in the Opticon load file. If the aforementioned setting is active, Import/Export looks for page
level .txt files that are named identically to their corresponding TIF files. For example:

4.4 Processed data


Some data originates from client files and needs processing to extract the metadata. The following table shows the
delimiters that your internal processing software must use to present data as fields.

Value Character ASCII Number


Column ¶ 020
Quote þ 254
Newline ® 174
Multi-Value ; 059
Nested Value \ 092
You can provide this list to your vendor to help communicate the required delivery format for load files. The fielded
data should be delivered as delimited files with column or field names located in the first line.

Import/Export Guide 22
4.5 Transcript file types supported
Import/Export only supports these transcript file types: .ptf, .xmptf, .rtf, .txt, .trn, and .lef. See Uploading transcripts in
the User Guide for more information on transcripts.

4.6 Access DB (MDB) load file specifications


Note: The import and export workflows with Access DB (MDB) are designed for and are currently available for the
Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your
Account Representative.

In certain markets, the Import/Export supports data transfer of structured data defined in Access DB load files. The
structure of the Access DB contains the following four tables.

Table Name Table Description


Export Main document information.
Parties People and organization information for each document.
Pages Listing of electronic image filenames for each document.
Export_Extras Additional data fields for each document.

l Import workflow: Import/Export supports import from Access DB load file with .mdb or .accdb extension.
l Export workflow: Import/Export generates a single Access DB load file with .mdb extension.

4.6.1 Export table


This table holds the primary information about a document.

Explanation—Document Types and Coding


Field Data Type If Mandatory
Method and Possible Values
Document_ID Text, 255 Uniquely identifies the document and is the link to the Yes
other four tables.
Host_Reference Text, 255 If the document is an Attachment, this field contains No, can be left blank
the Document ID of its host document.
Document_Date Text, 11 Dates in the format "DD-MMM-YYYY," where: Yes, if information is

Import/Export Guide 23
Explanation—Document Types and Coding
Field Data Type If Mandatory
Method and Possible Values

l "DD" equals the day date; available

l "MMM" equals the month;


l "YYYY" equals the year.
For example, 26 March 2017 would be represented
as "26-Mar-2017".
Estimated Text, 3 The estimated date for a document (for example: No
YES, NO, Y, N).
Document_Type Text, 255 The document type (for example: letter, minutes, No
maintenance reports, etc.).
Title Text, 255 The title for a document. No
level_1 Text, 20 The Party level of the Document ID. Yes
level_2 Text, 20 The Box level of the Document ID. No
level_3 Text, 20 The Folder level of the document ID. No
Description Long Text The description for a document. No

4.6.2 Parties Table


This table holds the names of people associated with a particular document and their relationship to the document. It
may also hold organization information for these people.
There is a one-to-many relationship between the Export table containing the primary document information and the
Parties table, because many people could be associated with a single document.

Field Data Type Explanation If Mandatory


Document_ID Text, 255 Identifies the document (related to the Export table Yes
via the Document_ID field).
Correspondence_Type Text, 100 Correspondence Type (for example: To, From, CC, Yes
BCC).
Persons Text, 255 Hard copy—information from the face of the No
document in the format "Last Name, First Name" or
"Last Name, Initial".
Emails and other electronic files—information
should be in the format as extracted from the
document metadata.
Organisations Text, 255 The organization information from the face of the No
document or extracted from the document
metadata.

Note: Persons and Organisations fields are treated as a single value on import with the correspondence type as
<Corresondence_Type>_Persons_and_Organisations. This way it can be imported into a single workspace field on
the import. That allows you to select it on export as a single value as well.
Example value: Last Name, First Name [Organisation].

Import/Export Guide 24
4.6.3 Pages table
There will be an entry in the Pages table for every TIFF page, text, or PDF document that relates to a single document
in the Export table.
There is a one-to-many relationship between the Export table and the Pages table. Where Native Electronic
Documents only are exchanged, no TIFF, text, PDF files or placeholder pages, there will only be one entry in the
Pages table corresponding to each Native Electronic Document.

Field Data Type Explanation If Mandatory


Document_ID Text, 255 Identifies the document (related to the Export table Yes
via the Document_ID field).
Image_File_Name Text, 128 Filename, including extension of each indexed doc- Yes
ument.
page_label Text, 32 Label for each document (for example: Native, Text, Yes
PDF, or Document ID).
page_num Number, An integer indicating the order in which the files Yes
Double related to the Document ID should be sequenced
when viewing the full document.
num_pages Number, Long The number of pages in the file. For rendered PDF No
Integer files, this will be the number of pages in the PDF. For
native electronic files (including native PDF files),
this will be set to "1".

4.6.4 Export_Extras table


This table holds any additional metadata the parties wish to exchange that is not held in the other three tables.

Field Data Type Explanation If Mandatory


Document_ID Text, 255 Identifies the document (related to the Export table Yes
via the Document_ID field).
theCategory Text, 50 Identifies the data type (supported types currently Yes
are: TEXT, NUMB, BOOL, DATE, PICK, MEMI).
theLabel Text, 255 The name of the field. Yes
theValue Text, 255 If not Memo, Custom Field Data. No if MEMO category
memoValue Long Text or If Memo, Custom Field Data. No if not MEMO cat-
Text fixed- egory
length setup
as length >
255

4.6.5 Example of values in Export_Extras table


This table presents exemplary values in Export_Extras table.

theLabel theCategory theValue or memoValue Explanation


File Name TEXT Monthly Reports.docx For all electronic files, the ori-

Import/Export Guide 25
theLabel theCategory theValue or memoValue Explanation
ginal filename (including exten-
sion).
MD5 TEXT 08a008a01d498c404b0c30852b39d3b8 The MD5 (a message-digest
algorithm) hash value of the file.
Sent Date/Time DATE 26/05/1999 8:33 PM The date and time the email
was sent.

4.6.6 Export recommendations


If you need to export a date with the time zone and have the date formatted "Day name, DD Month YYYY hh:mm:ss
TZ," for example, "Thursday, 28 June 2012 6:29:00 PM (UTC+10:00) Canberra, Melbourne, Sydney," include the
Time Zone Field in the Export_Extras at the time of export.
If you need to add the num_pages to the Pages table for PDF documents, include the Relativity PDF Page Count field
to the Export_Extras at the time of export.
As the Import/Export generates a single Access DB load file, consider splitting the large volumes of export data into
smaller jobs. Also, select the option to extract long text field, for example Extracted Text, to a separate file. The MDB
file limit is 2 GB for the load file, excluding: external file exported as native, images, PDF, extracted text.

Import/Export Guide 26
5 General recommendations for structured data import and
export jobs
The following are recommendations for importing and exporting load files.

5.1 Load file import recommendations


l Use Pre-check Load File feature to validate load file data before executing the import job. We strongly recom-
mend using this feature to make sure that the import job doesn’t come across metadata errors. If your workflow
uses Staging, the Pre-check Load File step won't be available. In such case, validate your load file manually
before proceeding.
l When using Import/Export in web only mode, make sure that the full path listed in the load file is captured in the
ZIP file.
l Try to limit the number of fields in a single import job to 100 to minimize risk of job failure due to SQL exception
related issues.
l When importing new choice fields, you may experience the unexpected behaviors, such as errors occurring
when importing choice fields or slow import jobs for choice fields. To help prevent these issues, try to limit the
number of choice values in a single import job to 100. This number indicates the maximum of new values in all
choice type fields across the entire set of records.
l Extracted Text import:
l There is no limitation or performance impact related to size of extracted text when the import is per-
formed to Data Grid.
l Performance and stability are affected for extracted texts import to SQL. If there is no other option and
you must use SQL, please import extracted text distinctly from other data fields.
l Depending on the job configuration, the extracted text import to Data Grid is 60-80% faster than similar
import to SQL.
l Performance improves when extracted text files use UTF-16 encoding.

5.2 Load file export recommendations


l For some combinations of job configuration and data, Windows system on your local machine may not be able
to open ZIP archives due to too long file paths. You may receive an error message: “The compressed (zipped)
folder is invalid.” In such case, you can do the following:
l Use Express Transfer to export the dataset to your local disk without creating an archive.
l Use other tools to extract the archive or move the archive file to a different location on your local
machine.
l Group files by “File Type” and not “Workspace Structure”. This may shorten the folder structure inside the
archive file.
l Depending on the exported data structure, a Workspace folder structure can degrade performance significantly,
up to 30 times slower in edge cases. We recommend using the File Type folder structure.
l Exporting many fields with complex data structures may affect performance or cause job errors. We recom-
mend exporting only necessary fields.

Import/Export Guide 27
l Increasing the Max Files to over 10,000 per folder may lead to significant export performance degradation. We
recommend using the default setting of the Max Files per folder=2,000.
l The default Max (Volume) Size is set to 6,000 MB. You can adjust this setting to any value that works best for
you. Setting it higher than the default value does not impact the export performance.
l Exporting images as PDFs or multi-page TIFFs is slower than exporting them as single page images.
l Exporting to a ZIP archive using Import/Export in web only mode is significantly slower than exporting data with
Express Transfer or exporting data to the Staging only.
l Exporting text files in Unicode (UTF-16) encoding is faster than in other encodings.

Import/Export Guide 28
6 Express Transfer overview
Express Transfer is an integral part of Import/Export workflows when activated for use with Import/Export. Using
Import/Export with Express Transfer active is the recommended method of transferring data in Relativity. It can be
used to transfer any data size, but it's designed especially for transferring large structured and unstructured data files
greater than 20 GB.
Using Import/Export with Express Transfer active helps reduce the time and effort it takes to transfer data in Relativity.
For additional information on performance considerations when transferring data using desktop applications, see Data
transfer performance considerations on page 43.
Express Transfer is a separately installed desktop application that operates outside of RelativityOne. Although you are
accessing and using Import/Export within RelativityOne to process transfer jobs, it is the activated Express Transfer
application that is handling the actual data transfer (upload and download) process in the background to and from
RelativityOne and the staging area or local disk. It uploads (imports) a single job at a time and downloads (exports) up
to five concurrent jobs at a time on a single client machine. You can have multiple users running jobs on multiple
machines without conflict.
Monitoring import and export job transfers is done through the Express Transfer application as well as from the
Import/Export Jobs page.
To ensure that you always have the most recent version and features of Express Transfer, the default update setting is
configured to automatically prompt you when a new version is available. We recommend keeping this setting enabled.
See Installing and updating Express Transfer desktop application on page 31 for more information. You can manually
check for updates anytime by right-clicking the Express Transfer icon in your system tray. See Express Transfer
system tray menu on page 45 for more information.

6.1 Prerequisites
To use Import/Export with Express Transfer, complete the following in this order:

1. Install Import/Export application from the Application Library in the workspace. Refer to Installing Import/Export
for more information.
2. Install Express Transfer desktop application on your computer. Refer to Installing Express Transfer for more
information.
3. Activate Express Transfer within Import/Export. Refer to Activating Express Transfer for more information.

6.2 Considerations when to use and not use Express Transfer with
Import/Export
We recommend using Import/Export with Express Transfer activated whenever possible for all importing and
exporting workflows, and particularly when:

l data file size is greater than 20 GB, although Express Transfer can be used for any size data transfer.
l processing multiple import jobs. The jobs will be queued and executed when the previous job is complete.
l slow or unstable network connection. Express Transfers enables you to retry the upload.
Use Import/Export without activating Express Transfer when:

l your company policy prohibits installing desktop applications.


l your network configuration does not allow third party applications to send or receive data, such as proxy set-
tings.

Import/Export Guide 29
l data file size is less than 20 GB.
l data is in ZIP files.

Note: You need to use Express Transfer to upload and process encrypted materials, such as password-protected
zip files or Case files (L01/N01) that require Password Bank functionality. If you cannot use Express Transfer for
such imports, zip your encrypted materials in a single unencrypted ZIP container. The 20 GB limit for the zip file size
applies. Import/Export will transfer and extract the top-level zip file, preparing your encrypted materials for Pro-
cessing. Then, Processing will utilize Password Bank to decrypt materials.

6.3 Express Transfer overview


Express Transfer is an integral part of Import/Export workflows when activated for use with Import/Export. Using
Import/Export with Express Transfer active is the recommended method of transferring data in Relativity. It can be
used to transfer any data size, but it's designed especially for transferring large structured and unstructured data files
greater than 20 GB.
Using Import/Export with Express Transfer active helps reduce the time and effort it takes to transfer data in Relativity.
For additional information on performance considerations when transferring data using desktop applications, see Data
transfer performance considerations on page 43.
Express Transfer is a separately installed desktop application that operates outside of RelativityOne. Although you are
accessing and using Import/Export within RelativityOne to process transfer jobs, it is the activated Express Transfer
application that is handling the actual data transfer (upload and download) process in the background to and from
RelativityOne and the staging area or local disk. It uploads (imports) a single job at a time and downloads (exports) up
to five concurrent jobs at a time on a single client machine. You can have multiple users running jobs on multiple
machines without conflict.
Monitoring import and export job transfers is done through the Express Transfer application as well as from the
Import/Export Jobs page.
To ensure that you always have the most recent version and features of Express Transfer, the default update setting is
configured to automatically prompt you when a new version is available. We recommend keeping this setting enabled.
See Installing and updating Express Transfer desktop application on the next page for more information. You can
manually check for updates anytime by right-clicking the Express Transfer icon in your system tray. See Express
Transfer system tray menu on page 45 for more information.

6.3.1 Prerequisites
To use Import/Export with Express Transfer, complete the following in this order:

1. Install Import/Export application from the Application Library in the workspace. Refer to Installing Import/Export
for more information.
2. Install Express Transfer desktop application on your computer. Refer to Installing Express Transfer for more
information.
3. Activate Express Transfer within Import/Export. Refer to Activating Express Transfer for more information.

6.3.2 Considerations when to use and not use Express Transfer with Import/Export
We recommend using Import/Export with Express Transfer activated whenever possible for all importing and
exporting workflows, and particularly when:

l data file size is greater than 20 GB, although Express Transfer can be used for any size data transfer.
l processing multiple import jobs. The jobs will be queued and executed when the previous job is complete.
l slow or unstable network connection. Express Transfers enables you to retry the upload.

Import/Export Guide 30
Use Import/Export without activating Express Transfer when:

l your company policy prohibits installing desktop applications.


l your network configuration does not allow third party applications to send or receive data, such as proxy set-
tings.
l data file size is less than 20 GB.
l data is in ZIP files.

Note: You need to use Express Transfer to upload and process encrypted materials, such as password-protected
zip files or Case files (L01/N01) that require Password Bank functionality. If you cannot use Express Transfer for
such imports, zip your encrypted materials in a single unencrypted ZIP container. The 20 GB limit for the zip file size
applies. Import/Export will transfer and extract the top-level zip file, preparing your encrypted materials for Pro-
cessing. Then, Processing will utilize Password Bank to decrypt materials.

6.4 Installing and updating Express Transfer desktop application


The Express Transfer application must be installed on your computer in order to use it with Import/Export workflows.
The instructions below can be used for both Microsoft Windows and Apple macOS installations. You can configure
preferences to automatically check for new software versions or you can check for them manually. We recommend
keeping the default setting to enable the system to automatically check for new software versions to ensure you're
using the latest software features available.
For additional information on performance considerations when transferring data using desktop applications, see Data
transfer performance considerations.

6.4.1 Requirements
Refer to the sections below for the necessary requirements for Express Transfer.

6.4.1.1 System requirements


To use Express Transfer, your computer must meet the following minimum system requirements:

System Configuration Requirement


Operating system MS Windows 10, MS Windows 11, or Apple macOS
Windows Server operating system Windows Server 2019 or Windows Server 2022
System memory 4 GB RAM, recommended 8 GB RAM

6.4.1.2 Port access


Express Transfer requires TCP port 443 to be open in order for it to operate. For more specific information about port
considerations relating to Express Transfer, please see our Data Transfer Tools: Required Port Considerations for
RelativityOne (Import/Export, Express Transfer, ROSE and Migrate) article in the Relativity Community.

6.4.2 Prerequisites
To use Express Transfer, complete the following in this order:
1. Install Import/Export application from the Application Library in the workspace. Refer to Installing Import/Export
for more information.
2. Install Express Transfer desktop application on your computer. Refer to Installing Express Transfer for more
information.
3. Activate Express Transfer within Import/Export. Refer to Activating Express Transfer for more information.

Import/Export Guide 31
6.4.3 Installing Express Transfer
To install the Express Transfer application on your computer for use with Import/Export:

1. Navigate to the Import/Export Job page.


2. Click the New Import/Export Job button.
3. Depending on the operating system used, click the Windows or MacOS button to download the installer file.

4. For macOS systems, you need to have administrative privileges to use and install the software, as well as to
receive automatic software updates. On the Installer dialog, enter your user name and password, then click
Install Software.

5. Navigate to the folder on your computer where the installer file was downloaded. Depending on the operation
system, double-click one of the following files to begin the installation process:
l For Windows OS: Express Transfer Setup.exe
l For macOS: Express Transfer Setup.pkg

Import/Export Guide 32
6. Click one of the options on the Select Setup Install Mode dialog:
l Install for me only (recommended)—enables Express Transfer to be used by your account only.
l Install for all users—enables Express Transfer to be used by anyone who logs on to this computer. You
will need Admin credentials to select this option.
7. Click Next.
8. Use the default destination folder already displayed or click Browse to select a different location for the Express
Transfer application.
9. Click Next.
10. (Optional) On the Select Additional Tasks dialog, do any of the following:
l Autostart Express Transfer on system startup—select this check box to automatically launch the
Express Transfer application each time your computer starts. Leave it blank if you want to manually
launch Express Transfer when you want to use it.
l Create a desktop shortcut—select this checkbox to create a shortcut icon on your desktop for Express
Transfer. Otherwise, leave it blank.
11. Click Next.
12. Click Install on the Ready to Install dialog to begin the installation process.
13. When the installation is complete, click Finish to close the installation wizard. Express Transfer is now installed.
To use Express Transfer for import and export workflows, you must activate it within Import/Export. See Activ-
ating Express Transfer for more information.

If you selected the Run Express Transfer checkbox on the finish setup dialog of the wizard, the Express Transfer

application will open and its icon will be available in the system tray. Right-click on the icon to display an
application menu with these options:

Import/Export Guide 33
l Connectivity check—choose this option to check if Express Transfer is successfully accessing the Internet
and the Import/Export application. See Express Transfer Connectivity check for more information.
l Show logs—choose this option if instructed to do so by Relativity Support to investigate or troubleshoot an
issue with Express Transfer transaction logs and text files. File explorer will open the logs folder on your local
drive. For example, C:\Users\<username>\AppData\Local\Express Transfer\logs. With Express Transfer open,
you can also press F8 to display the logs folder.
l Check for Updates—choose this option if you want to manually check to see if your version is up-to-date or if a
new version of Express Transfer is available. See Manually checking for software updates on page 39 for more
information.
l Preferences—choose this option to modify the application settings. You can also view the software version
number from this dialog.
l Quit—choose this option to completely exit the Express Transfer application. The Express Transfer icon will no
longer be displayed in the system tray. To reopen Express Transfer, double-click on its desktop shortcut, if you
saved one for it, or select it from your computer's list of programs.

6.4.4 Silent installation of Express Transfer


In some organizations, the IT department or System Administrator may be the one to install the Express Transfer
desktop application installer file behind the scenes over a network instead of having each end user do it themselves on
their individual desktop. This method is often referred to as a silent, or unattended, installation because it requires no
end user interaction with the installation wizard. The Express Transfer end user is not aware that the installation
process is occurring. Typically, this type of installation is used in large enterprise organizations to help control the
software installation process to ensure that it’s done consistently so that all users have the same installation
configuration.
When installing Express Transfer from command line tools, we support silent and verysilent mode:

l /silent—this option displays the installation wizard as it goes through the installation process. All the default
options are automatically selected.
l /verysilent—this option does not display the installation wizard as it goes through the installation process. All
default options are selected automatically.
Prerequisites

Import/Export Guide 34
l Administrator rights to run the command prompt.
l Knowledge of how to use command line interface (CLI) tools.
l Obtain the downloaded Express Transfer installer file for Windows OS, which is Express Transfer Setup.exe.
See Installing Express Transfer for more information on how to download the file using the Import/Export applic-
ation.

6.4.5 Locating the Express Transfer version number


The Express Transfer version number is displayed at the bottom of the In Progress and History tabs within the
application.

You can also find it in the bottom left corner of the Preferences dialog by right-clicking on the Express Transfer
icon in the system tray and selecting Preferences.

Import/Export Guide 35
Import/Export Guide 36
The Express Transfer software version number is contained in the first few numbers after the "v", for example
"v2.49.0." The numbers after the hyphen are session identifiers that change each time you launch Express Transfer
after quitting the application. These numbers may be used by Customer Support if you encounter a problem with the
software. You can disregard them otherwise.

6.4.6 Automatically checking for software updates


You can configure whether or not you want the system to automatically check for new software versions of Express
Transfer each time it opens and notify you with a message box. By default, this feature is enabled in Express Transfer
Preferences. We recommend that you keep it enabled to ensure your system is running the latest software version
containing the most recent software features available. If you choose to change this default setting, you will need to
use the Check for Updates option in the Express Transfer system tray. See Manually checking for software updates
on page 39 for more information.
To automatically check for software updates:

1. Right-click on the Express Transfer icon in your system tray.

Import/Export Guide 37
2. Click Preferences.

3. By default, the Check for Updates is toggled on. If you do not want the system to automatically check for
updates and notify you, toggle it off.

Note: We do not recommend turning this option off. If it is off, your Express Transfer version may not contain
the latest features. If it is off, you will need to regularly use the Check for Updates option in the Express Trans-
fer system tray to determine if your software version is current. See Manually checking for software updates
on the next page for more information.

4. Click Save after updating the setting.


5. To apply any changes made to Preferences, quit the Express Transfer application by right-clicking on the
Express Transfer

Import/Export Guide 38
icon in your system tray and clicking Quit.

6. Reopen the application by double-clicking on its desktop shortcut, if you saved one for it, or select it from your
computer's list of programs.
Whenever a new version is available, you'll be notified with an Application update dialog displaying the new version
number available and release notes for it. Click Update now to download the new version's executable file, and then
follow the Installing Express Transfer on page 32 steps to finish installing the update on your system.

6.4.7 Manually checking for software updates

You can check for software updates anytime by right-clicking on the Express Transfer icon in your system tray
and clicking Check for Updates. If your software version is current, a message is displayed letting you know it's up-
to-date.

Import/Export Guide 39
If a new version is available, the Application update window displays the new version number available and release
notes for it. Click Update now to download the new version's executable file, and then follow the Installing Express
Transfer on page 32 steps to finish installing the update.

6.5 Activating and deactivating Express Transfer


You have the ability to activate and deactivate Express Transfer for use with Import/Export. However, the
recommended method for transferring data is with Express Transfer activated.

6.5.1 Prerequisites
To use Express Transfer, install the following in this order:

1. Install Import/Export application from the Application Library in the workspace. Refer to Installing Import/Export
for more information..

Import/Export Guide 40
2. Install Express Transfer desktop application on your computer. Refer to Installing Express Transfer for more
information..

6.5.2 Considerations when to use and not use Express Transfer with Import/Export
We recommend using Import/Export with Express Transfer activated whenever possible for all importing and
exporting workflows, and particularly when:

l data file size is greater than 20 GB, although Express Transfer can be used for any size data transfer.
l processing multiple import jobs. The jobs will be queued and executed when the previous job is complete.
l slow or unstable network connection. Express Transfers enables you to retry the upload.
Use Import/Export without activating Express Transfer when:

l your company policy prohibits installing desktop applications.


l your network configuration does not allow third party applications to send or receive data, such as proxy set-
tings.
l data file size is less than 20 GB.
l data is in ZIP files.

Note: You need to use Express Transfer to upload and process encrypted materials, such as password-protected
zip files or Case files (L01/N01) that require Password Bank functionality. If you cannot use Express Transfer for
such imports, zip your encrypted materials in a single unencrypted ZIP container. The 20 GB limit for the zip file size
applies. Import/Export will transfer and extract the top-level zip file, preparing your encrypted materials for Pro-
cessing. Then, Processing will utilize Password Bank to decrypt materials.

6.5.3 Activating Express Transfer


To use Import/Export with Express Transfer, you need to activate Express Transfer. Once activated, it will remain
active until your Relativity session ends or until you deactivate it.
To activate Express Transfer for use with Import/Export:

1. Navigate to the Import/Export Job page.


2. Click the New Import/Export Job button to start a new job.

Import/Export Guide 41
3. Click Activate on the Choose workflow dialog to activate Express Transfer.

4. If a browser message box appears asking to allow the site to open Express Transfer, click Open Link to pro-
ceed with activating Express Transfer. If you do not, then Express Transfer will not be activated.

Note: To always allow your system to open the link to Express Transfer, select the "Always allow" checkbox,
and the message box will not appear anymore.

Note: If the activation process fails, click the Complete activation button on the message that appears to ini-
tiate the activation process. Refer to Express Transfer Connectivity check on page 56 for more information on
connection status information.

Import/Export Guide 42
5. When the activation process successfully completes, the Express Transfer application opens.

6. Return to the Import/Export application. The Express Transfer status will change to Active on the Choose Work-
flow dialog.

Note: The Express Transfer application will remain active until you click the Deactivate button or log out of
RelativityOne. You do not need to keep reactivating it to use it. However, if you deactivate it or log out of
RelativityOne, you will need to reactivate Express Transfer to use it again with Import/Export.

6.5.4 Deactivating Express Transfer


If you do not want to use an active session of Express Transfer with Import/Export, you can click the Deactivate button
on the Choose Workflow dialog.

In order to use Express Transfer again with Import/Export, you will need to reactivate it.

6.5.5 Data transfer performance considerations


There are many variables that can degrade or improve the performance of data transfers for desktop applications,
such as Express Transfer. Transfer rates when using desktop applications are influenced by several variables and
results may vary based on factors such as RAM, CPU, local drive specifications, network drive specifications, and
available bandwidth at the time of the transfer.
Review the list of performance considerations below before beginning to use Express Transfer.
If you experience issues despite following the information below, please contact Support for assistance. For additional
information, refer to the Community article Performance considerations for data transfers.

Import/Export Guide 43
l Run on local machine: Express Transfer has been designed and tested as a desktop application being run on
a user’s local machine.
l Read access: Ensure that Express Transfer has read access to all files/folders. Remove system / hidden attrib-
utes.
l Port 443: Ensure that port 443 is open and is not blocked or traffic is restricted to it. See the Community article
Performance considerations for data transfers for more information.
l Internet connection: Use a strong and stable internet connection for data transmission. Wi-Fi is not recom-
mended.
l Internet speed: Transfer speeds are dependent on your internet speeds. Check your internet connection using
Speedtest or any other bandwidth testing website. Make note of the upload speed in megabits per second. Also
refer to Express Transfer Limit bandwidth setting if needed.
l Local storage speed: Transfers from network drives or external disks, such as thumb drives/USB drives, will
degrade performance and/or cause issues maintaining a connection. It is most effective to copy data to and
from a fast local storage.
l Local machine specs: Ensure your local machine and browser adheres to the Express Transfer minimum sys-
tem requirements and is operating the latest version of the software.
l Level of data fragmentation: Due to bandwidth sharing, avoid performing large and fragmented transfers in
parallel. The more fragmented the dataset, the lower the transfer performance.
l Concurrent transfers: Number of concurrent transfers that are happening at the same time within the network
by various tools, services, and users.
l Concurrent utilization: Level of concurrent utilization of the user's computer resources, that is CPU, RAM,
I/Os, by other processes on that computer.
l Compressed datasets: Avoid compressing datasets with ZIP, 7z, etc. The faster transfer time due to fewer
multi-part files is negated by the time and effort to compress and decompress data. However, compressing data-
sets without decompressing in the destination folder (staging directory) can be considered when all the fol-
lowing are true:
l Dataset consist of fragmented data
l Destination folder is a Processing source location
l The dataset uploaded is going to be processed by Relativity Processing
l VPN usage: Using a VPN can potentially slow down internet traffic. When workstations use a VPN session, it
can interfere with transfers from that workstation. RelativityOne is hosted in a public cloud and does not require
VPN to use. See the Community article Performance considerations for data transfers for more information.
l Traffic monitoring and data protection software: These types of software tools influence data transfer. See
the Community article Performance considerations for data transfers for more information on each of these:
l Firewall: Firewall configuration may require special tuning to use the Express Transfer.
l Antivirus software: Antivirus software may disrupt the transfer protocol in Express Transfer.
l Anti-malware software: An exception should be created for Express Transfer in Windows Defender or
in other anti-malware software installed on the user's machine.

Import/Export Guide 44
6.6 Express Transfer system tray menu

Once the Express Transfer application is installed, its icon will be available in the system tray. Right-click on
the icon to display an application menu with these options:

l Connectivity check—click this option to check if Express Transfer is successfully accessing the Internet and
the Import/Export application. See Express Transfer Connectivity check for more information.
l Show logs—click this option if instructed to do so by Relativity Support to investigate or troubleshoot an issue
with Express Transfer transaction logs and text files. File explorer will open the logs folder on your local drive.
For example, C:\Users\<username>\AppData\Local\Express Transfer\logs. With Express Transfer open, you
can also press the F8 key on your keyboard to display the logs folder.
l Check for Updates—click this option if you want to manually check to see if your version is up-to-date or if a
new version of Express Transfer is available. See Manually checking for software updates on page 39 for more
information. If you do not have Express Transfer Preferences set to automatically check for updates, you will
need to use this option frequently to ensure your version of Express Transfer is the most current one available.
We recommend keeping the Check for updates option in Express Transfer Preferences toggled on. See
Installing and updating Express Transfer desktop application on page 31 for more information.
l Preferences—click this option to modify the application settings. You can also view the software version num-
ber from this dialog. See Express Transfer Preferences below for more information.
l Quit—choose this option to completely exit the Express Transfer application. The Express Transfer icon will no
longer appear in the system tray. To reopen Express Transfer, double-click on its desktop shortcut, if you saved
one for it, or select it from your computer's list of programs.

6.7 Express Transfer Preferences


Use Express Transfer Preferences to modify the Check for Updates setting, to limit bandwidth, to exclude temporary
Microsoft Office files from data import, and to configure proxy settings.

Import/Export Guide 45
6.7.1 Automatically checking for software updates
You can configure whether or not you want the system to automatically check for new software versions of Express
Transfer each time it opens and notify you with a message box. By default, this feature is enabled in Express Transfer
Preferences. We recommend that you keep it enabled to ensure your system is running the latest software version
containing the most recent software features available. If you choose to change this default setting, you will need to
use the Check for Updates option in the Express Transfer system tray. See Manually checking for software updates
on page 39 for more information.
To automatically check for software updates:

1. Right-click on the Express Transfer icon in your system tray.

Import/Export Guide 46
2. Click Preferences.

3. By default, the Check for Updates is toggled on. If you do not want the system to automatically check for
updates and notify you, toggle it off.

Note: We do not recommend turning this option off. If it is off, your Express Transfer version may not contain
the latest features. If it is off, you will need to regularly use the Check for Updates option in the Express Trans-
fer system tray to determine if your software version is current. See Manually checking for software updates
on page 39 for more information.

4. Click Save after updating the setting.


5. To apply any changes made to Preferences, quit the Express Transfer application by right-clicking on the
Express Transfer

Import/Export Guide 47
icon in your system tray and clicking Quit.

6. Reopen the application by double-clicking on its desktop shortcut, if you saved one for it, or select it from your
computer's list of programs.
Whenever a new version is available, you'll be notified with an Application update dialog displaying the new version
number available and release notes for it. Click Update now to download the new version's executable file, and then
follow the Express Transfer Preferences on page 45 steps to finish installing the update on your system.

6.7.2 Limit bandwidth


Some organizations may have slow internet speeds and experience issues with transfer job stability causing jobs to
fail due to connection timeouts. In this situation, the organization may want to limit bandwidth so that it's shared with
Import/Export transfers and other business activities. This may help improve the efficiency and stability of job
transfers. Limiting bandwidth can be configured in Express Transfer by turning on the Limit bandwidth option in
Preferences. When this option is on, Express Transfer job transfers will be slower, but more stable.

Import/Export Guide 48
To configure Limit bandwidth:

1. Right-click on the Express Transfer icon in your system tray.

Import/Export Guide 49
2. Click Preferences.

3. The Limit bandwidth option is off by default. If you wish to turn the option on, click the toggle.
4. Click Save after updating the settings.

Import/Export Guide 50
5. To apply any changes made to Preferences, quit the Express Transfer application by right-clicking on the

Express Transfer icon in your system tray and clicking Quit.

6. Reopen the application by double-clicking on its desktop shortcut, if you saved one for it, or select it from your
computer's list of programs.

6.7.3 Exclude temporary Microsoft Office files from data import


Whenever you open a Microsoft Office file, a temporary file is created which contains a ~ (tilde) sign at the beginning of
the file name. When you’re importing unprocessed data for Processing and selecting the data source on the Create
Processing Job dialog, these temporary files will be displayed in the file list and will also be included in the data import
process.

To prevent these temporary files from being included in the import process, the Exclude temporary file(s) option
defaults to the On position in Express Transfer Preferences. If you wish to change that setting and include those
temporary files, refer to the steps below.
To include temporary Microsoft Office files in import jobs:

Import/Export Guide 51
1. Right-click on the Express Transfer icon in your system tray.

Import/Export Guide 52
2. Click Preferences.

3. The Exclude temporary file(s) option is on by default. If you wish to turn the option off, click the toggle.
4. Click Save after updating the setting.

Import/Export Guide 53
5. To apply any changes made to Preferences, quit the Express Transfer application by right-clicking on the

Express Transfer icon in your system tray and clicking Quit.

6. Reopen the application by double-clicking on its desktop shortcut, if you saved one for it, or select it from your
computer's list of programs.

6.7.4 Configuring proxy settings


If your organization or IT department requires using Express Transfer with a proxy server, follow the steps below to set
up the necessary credentials. Contact your IT Department for the required information

Note: The port number used in the steps below will be different from Port 443, which is still required to be open
regardless of this proxy configuration. See Port access on page 31 for more information.

To configure proxy settings:

1. Right-click on the Express Transfer icon in your system tray.

Import/Export Guide 54
2. Click Preferences.

3. The Proxy settings option is off by default. If you wish to turn the option on, click the toggle, and then enter the
necessary information for the following fields. Contact your IT Department for the correct information:
l Proxy address (required)
l Port (required)
l Username
l Password
4. Click Save after updating the setting.

Import/Export Guide 55
5. To apply any changes made to Preferences, quit the Express Transfer application by right-clicking on the

Express Transfer icon in your system tray and clicking Quit.

6. Reopen the application by double-clicking on its desktop shortcut, if you saved one for it, or select it from your
computer's list of programs.
7. Perform a Connectivity Check to make sure Express Transfer is connected to the Internet. If not, then the proxy
settings are incorrect and will need changed.

6.8 Express Transfer Connectivity check


Connectivity check ensures that the Express Transfer desktop application authenticates and successfully accesses
the Internet, the necessary ports, and the Import/Export application to transfer data. This check executes
automatically when you activate Express Transfer from the Import/Export application within RelativityOne. You can
also manually perform a connectivity check anytime, even when there are active transfers.
The following checks occur during the connectivity check process:

Connectivity
Description
Check

Internet con- This step confirms your system is connected to the internet. If this step fails, there is either no inter-
nection net connection available or the proxy or firewall is blocking the connection for Express Transfer.
Please contact your IT department for help.
Access to This step confirms Express Transfer successfully set up all ports needed to connect to your spe-
Express Trans- cific region. If this step fails, please contact your IT department for help.
fer gateway
Connection with This step confirms Express Transfer successfully connected to the infrastructure specific to your
Express Trans- RelativityOne region. If this step fails, please contact your IT department so they can verify the cor-
fer infra- rect port configuration. For more information, refer to Data Transfer Tools: Required Port Con-
structure siderations for RelativityOne (Import/Export, Express Transfer, ROSE and Migrate) article in
Community.
Activation This step confirms Express Transfer is active. If it fails, see Activating and deactivating Express
status Transfer for more information on reactivating it.

Import/Export Guide 56
Connectivity
Description
Check
Connection with This step confirms Express Transfer is communicating with Import/Export in RelativityOne.
Import/Export

Note: If you perform a connectivity check before activating Express Transfer in Import/Export, only the Internet

connection is checked and the others display the no connectivity icon. Express Transfer must be active to
perform the full connectivity check.

To manually run a connectivity check, use any of these methods:

l From the System tray: Right-click on the icon in the desktop system tray and choose Connectivity check
from the pop-up menu.

Import/Export Guide 57
l From within Express Transfer: Click the circled check mark icon at the bottom of the Express Transfer applic-
ation.

The test results are displayed after each process completes. The word "Successful" appears when all connections are
working properly. If any of the system checks fail, Express Transfer will not work.
Click the Check again button to refresh the connection in the event you lose connectivity.

Note: If the "Activation status" test fails, the Activate button will appear next to an inactive Check again button.
Click the Activate button to try to activate Express Transfer again.

Icon legend:

icon indicates the connectivity test was successful.

Import/Export Guide 58
icon indicates the connectivity test failed.

icon indicates the connectivity test is in progress.

icon indicates the connectivity test was not performed on this item. Tip: If this is displayed, double check to be
sure Express Transfer is active in Import/Export.

6.8.1 Network Throughput Check


If there are issues with your network speeds and connectivity, a notice is displayed next to the Connectivity check icon
to notify you that the network connection is poor and this may cause slow transfer speeds. Check your internet
connection or consult your IT department for further assistance.

6.9 Express Transfer Job tracking and history


You can track the progress and history of jobs that were started with Express Transfer without logging into
RelativityOne.
To do so, open Express Transfer by double-clicking the shortcut on your desktop.

Note: Once the job is running using Express Transfer, you can close the Import/Export application, if desired, and
the transfer job will continue and not be affected. You can monitor the job using the steps below. You do not have to
be logged into RelativityOne to view information within the Express Transfer application.

6.9.0.1 Prerequisites
To use Express Transfer, the following must be completed in this order:
1. Import/Export application must be installed in the workspace from the Application Library. Refer to Installing
Import/Export for more information.
2. Express Transfer desktop application must be installed on your computer. Refer to Installing Express Transfer
for more information.
3. Express Transfer must be activated within Import/Export. Refer to Activating Express Transfer for more inform-
ation.

6.9.0.2 In Progress Tab


The In Progress tab displays ongoing transfer information. With Express Transfer, on a single client machine you can
have one import (upload) job at a time and up to five concurrent export (download) jobs at a time. For uploads, the jobs
will be queued on the client machine.

Import/Export Guide 59
l Job Name—displays the name of the job. Click the job name to view more information about the job on the Job
Details window. Or, click the Actions button next to the transfer line, then click View details. See Viewing and
copying details of Express Transfer jobs.
l Transfer progress bar—displays the percentage of transfer completion.
l Starting—this status indicates the job is beginning to transfer data.
l In Queue—this status indicates the job is waiting until the first job is complete.
l Cancel a job—to cancel a job that's in progress, click the Actions button next to the transfer line and then click
Cancel.
If no transfers were triggered, the tab displays a message that there are no jobs at the moment and directs you to
RelativityOne to start a new job.
To check more details about the job, visit the Import/Export Job page in RelativityOne. Refer to "Import/Export Job
tracking and history" for more information.

6.9.0.3 History tab


The History tab displays information about the status of previous transfer jobs that were executed.

Import/Export Guide 60
l Finished—a full green bar and 100% indicates that the transfer successfully finished. To view details about the
job, click the job name link or click the Actions button next to the transfer line and then click View details. See
Viewing and copying details of Express Transfer jobs.
l Job Failed (with red exclamation mark icon)—is displayed in red and indicates that the transfer has failed
and the number of items that failed. The reason for the failure is displayed next to the icon. You can perform a
manual retry for a failed transfer by clicking the Actions button next to the transfer line and then clicking Retry
failed files. Jobs older than seven days cannot be restarted. See Express Transfer reporting jobs failed or com-
pleted with errors for more information. To view job details, click the Actions button next to the transfer line and
then click View details.
l Completed with Errors (with warning symbol icon)—indicates that the transfer has completed but
encountered errors. The number of skipped files is displayed. You can skip failed files by clicking the Actions
button next to the transfer line and then clicking Skip failed files. See Express Transfer reporting jobs failed or
completed with errors for more information. To view job details, click the Actions button next to the transfer line
and then click View details.
l Cancelled—indicates that the transfer has been cancelled from within RelativityOne Import/Export or from
within the Express Transfer desktop application. To view more information about the job, click the Actions but-
ton next to the transfer line and then click View details.

Import/Export Guide 61
To check the full history, visit the Import/Export Job page in RelativityOne. Refer to"Import/Export Job tracking and
history" for more information.

6.9.0.4 Filtering Express Transfer jobs


To filter your jobs based on the type of transfer (Import or Export) on the In Progress or History tabs, click the drop-
down arrow and select Import or Export. By default, all transfer types are displayed.

6.9.0.5 Viewing and copying details of Express Transfer jobs


To obtain information about a particular Express Transfer job, click the Actions button next to the transfer line and
then click View details.

Import/Export Guide 62
The Job details window displays the transfer information. Click the copy button if you need to copy and paste
the information to the clipboard to use it elsewhere.

Import/Export Guide 63
6.10 Express Transfer reporting jobs failed or completed with errors
When using Express Transfer with Import/Export, if a job fails to finish or completes with errors, you can generate a
report from Express Transfer Job Details. The report includes information such as the time stamp, file status, file
name, error message, and file path. You also have a few options on how to handle the failed or errored jobs, such as
retrying or skipping failed files. For more information about job tracking and history, see Express Transfer Job tracking
and history.

Note: Available for Express Transfer version 2.21.1 and above. See Locating the Express Transfer version number
on page 35 if needed.

1. From the Express Transfer application, click the History tab.


2. Click the Actions button corresponding with the job that failed or completed with warnings and do any of the fol-
lowing:

Import/Export Guide 64
l View details—click to view job information in another window.
l Show report—click to view the saved Excel file (.csv) with the failed jobs or those completed with errors.
This link will open File Explorer on your local drive to the Reports folder, such as C:\User-
s\<username>\AppData\Local\Express Transfer\Reports. You cannot generate a report for jobs that
were run prior to upgrading to version 2.21.1.
l Retry failed files—click to rerun the failed files. Jobs older than seven days cannot be rerun.
l Skip failed files—click to continue running the job excluding the failed files. The job status will be “Com-
pleted with errors.” The successful documents will be uploaded and available. You can view information
about the failed files by clicking Show report to decide how you want to proceed with them. This option is
recommended if you attempted to retry the failed files and the job still fails. Once Skip failed files is

Import/Export Guide 65
executed, the Retry failed files option is no longer available.

Import/Export Guide 66
7 Importing data using Import/Export
You can use Import/Export to import unprocessed raw native files, document load files, image load files, production
load files, and Relativity Dynamic Objects. Refer to Import/Export load file specifications and Data upload size
limitation on page 9 for more information regarding load files. Also see General recommendations for structured data
import and export jobs on page 27.

Note: After documents are imported using Import/Export, you can automate creating a dtSearch index or run a
search terms report with those documents using Automated Workflows. To learn more, visit Automated Workflows.

l Document load file import—use this workflow to import load files containing document metadata, native files, or
extracted text into Relativity.
l Image load file import—use this workflow to import load files containing images and PDFs into Relativity.
l Production load file import—use this workflow to import load files containing productions into Relativity.
l Relativity Dynamic Object load file import—use this workflow to import dynamic object (RDO) data into Relativ-
ity.
l Access DB load file import (MDB)—use this workflow to import an Access DB load file (MDB) into Relativity.
l Unstructured data workflow with Processing—use this workflow to import raw (unprocessed) native files that
require processing in Relativity.
l Transcript data import for Processing—use this workflow to import transcript MDB data with the linked audi-
o/video files into RelativityOne.

7.1 Structured data import from Staging


You can now import structured data directly from the Staging area using the Structured (Processed) Data workflow.
This option works just like other Structured Import workflows, with the only difference being the source location.
To use this option, you must have Allow Staging Import permission enabled. With this permission:

Import/Export Guide 67
l When Express Transfer is active, Staging Load File button is available on the Select data to Import dialog.

Import/Export Guide 68
l When Express Transfer is not active, Choose From Staging button is available on the Choose Load File and
Location dialog.

Note: This feature is only available when appropriate set of permissions is granted. For details, see Workspace-
level permissions and the Community article Changes to Import/Export Choose From Staging Option FAQ.

7.2 Pre-check Load File


The Pre-check Load File is an optional process when configuring an import job. It ensures consistency of date before
the import job starts.
This feature helps to identify data inconsistencies early, allowing you to correct the source load file for a successful
import job. That way, you don't need to run the entire import job, including transferring native files and images, to
detect potential load file errors. The Pre-check Load File process reduces time needed for complete load file imports
using Import/Export, particularly for large load files.
The Pre-check load file process validates different data depending on the import workflow.

Import/Export Guide 69
Note: The Pre-check Load File feature is not available in workflows that utilize Staging. If your import job is
configured to use Staging, the Pre-check step will be skipped, and validation will occur during the actual import
process.

7.2.1 Document and RDO load file import


For these workflows, the Pre-check Load File validations are based on the configured Fields Mapping. The load file
metadata is compared with the mapped workspace fields. It is also checked if the metadata can be successfully
imported to the selected fields.
The Pre-check load file process validates the following:

l Date/Time format— checks if the metadata mapped to Data/Time fields is within acceptable format, expected
by the Relativity field.
l Field type—checks if the metadata type matches the expected type of the selected field, for example
Date/Time, Number, Text, Boolean.
l Field length—checks if the text metadata is not longer than maximum number of characters defined for the
selected Relativity field.
l Number of the load file cells—checks if each row of the load file contains the same number of columns and if it
matches the number of the mapped fields.
l Number of folders and choice fields—checks total number of folders and choice fields that will be created during
the import job. Large total number may significantly extend the job processing time.
l File paths for native and extracted text files—checks if the file paths lead to actual files to be uploaded during
the import job.
The Pre-check Load file process validates all load file rows against the metadata consistency. It also validates random
1,000 rows across the entire load file against the file paths errors. The file paths validation is run when using either
Express Transfer or Web Upload for importing files.
After the validation, the summary dialog displays identified errors, which are divided into error categories. You can
click the down arrow next to any error category to view its details.
The summary dialog displays a maximum of 1,000 errors for each error category, so your web browser
responsiveness is not affected. For example, if an error category has 2,000 errors, only the first 1,000 will be displayed
in the drop-down list.

Import/Export Guide 70
7.2.2 Image and Production load file import
For these workflows, the Pre-check Load File validates if image or PDF file paths lead to actual files which will be
uploaded during the import job.
During that process, random 1,000 rows across the entire load file are checked against the file paths errors. The file
paths validation is run when using either Express Transfer or Web Upload mode for importing files.
After the validation, the summary dialog displays identified errors, which are divided into error categories. You can
click the down arrow next to any error category to view its details.

Import/Export Guide 71
7.2.3 Working with Pre-check Load File results
When the Load File Pre-check process is complete, you may choose to correct the errors in the source files and
upload the files again. To do so, keep clicking back to the Choose Load File And Location dialog. Then, upload the
corrected files and perform the import steps again.
If you don’t want to correct the source files, click the Import button and proceed with importing the data.

7.3 Importing data using Import/Export


You can use Import/Export to import unprocessed raw native files, document load files, image load files, production
load files, and Relativity Dynamic Objects. Refer to Import/Export load file specifications and Data upload size
limitation on page 9 for more information regarding load files. Also see General recommendations for structured data
import and export jobs on page 27.

Note: After documents are imported using Import/Export, you can automate creating a dtSearch index or run a
search terms report with those documents using Automated Workflows. To learn more, visit Automated Workflows.

l Document load file import—use this workflow to import load files containing document metadata, native files, or
extracted text into Relativity.
l Image load file import—use this workflow to import load files containing images and PDFs into Relativity.
l Production load file import—use this workflow to import load files containing productions into Relativity.
l Relativity Dynamic Object load file import—use this workflow to import dynamic object (RDO) data into Relativ-
ity.

Import/Export Guide 72
l Access DB load file import (MDB)—use this workflow to import an Access DB load file (MDB) into Relativity.
l Unstructured data workflow with Processing—use this workflow to import raw (unprocessed) native files that
require processing in Relativity.
l Transcript data import for Processing—use this workflow to import transcript MDB data with the linked audi-
o/video files into RelativityOne.

7.3.1 Structured data import from Staging


You can now import structured data directly from the Staging area using the Structured (Processed) Data workflow.
This option works just like other Structured Import workflows, with the only difference being the source location.
To use this option, you must have Allow Staging Import permission enabled. With this permission:

l When Express Transfer is active, Staging Load File button is available on the Select data to Import dialog.

Import/Export Guide 73
l When Express Transfer is not active, Choose From Staging button is available on the Choose Load File and
Location dialog.

Note: This feature is only available when appropriate set of permissions is granted. For details, see Workspace-
level permissions and the Community article Changes to Import/Export Choose From Staging Option FAQ.

7.3.2 Pre-check Load File


The Pre-check Load File is an optional process when configuring an import job. It ensures consistency of date before
the import job starts.
This feature helps to identify data inconsistencies early, allowing you to correct the source load file for a successful
import job. That way, you don't need to run the entire import job, including transferring native files and images, to
detect potential load file errors. The Pre-check Load File process reduces time needed for complete load file imports
using Import/Export, particularly for large load files.
The Pre-check load file process validates different data depending on the import workflow.

Import/Export Guide 74
Note: The Pre-check Load File feature is not available in workflows that utilize Staging. If your import job is
configured to use Staging, the Pre-check step will be skipped, and validation will occur during the actual import
process.

7.3.2.1 Document and RDO load file import


For these workflows, the Pre-check Load File validations are based on the configured Fields Mapping. The load file
metadata is compared with the mapped workspace fields. It is also checked if the metadata can be successfully
imported to the selected fields.
The Pre-check load file process validates the following:

l Date/Time format— checks if the metadata mapped to Data/Time fields is within acceptable format, expected
by the Relativity field.
l Field type—checks if the metadata type matches the expected type of the selected field, for example
Date/Time, Number, Text, Boolean.
l Field length—checks if the text metadata is not longer than maximum number of characters defined for the
selected Relativity field.
l Number of the load file cells—checks if each row of the load file contains the same number of columns and if it
matches the number of the mapped fields.
l Number of folders and choice fields—checks total number of folders and choice fields that will be created during
the import job. Large total number may significantly extend the job processing time.
l File paths for native and extracted text files—checks if the file paths lead to actual files to be uploaded during
the import job.
The Pre-check Load file process validates all load file rows against the metadata consistency. It also validates random
1,000 rows across the entire load file against the file paths errors. The file paths validation is run when using either
Express Transfer or Web Upload for importing files.
After the validation, the summary dialog displays identified errors, which are divided into error categories. You can
click the down arrow next to any error category to view its details.
The summary dialog displays a maximum of 1,000 errors for each error category, so your web browser
responsiveness is not affected. For example, if an error category has 2,000 errors, only the first 1,000 will be displayed
in the drop-down list.

Import/Export Guide 75
7.3.2.2 Image and Production load file import
For these workflows, the Pre-check Load File validates if image or PDF file paths lead to actual files which will be
uploaded during the import job.
During that process, random 1,000 rows across the entire load file are checked against the file paths errors. The file
paths validation is run when using either Express Transfer or Web Upload mode for importing files.
After the validation, the summary dialog displays identified errors, which are divided into error categories. You can
click the down arrow next to any error category to view its details.

Import/Export Guide 76
7.3.2.3 Working with Pre-check Load File results
When the Load File Pre-check process is complete, you may choose to correct the errors in the source files and
upload the files again. To do so, keep clicking back to the Choose Load File And Location dialog. Then, upload the
corrected files and perform the import steps again.
If you don’t want to correct the source files, click the Import button and proceed with importing the data.

7.4 Importing a document load file


You can use Import/Export to import document load files, .dat, .csv, and .txt, into RelativityOne that contain document
metadata, native files, or extracted text. You're also able to use saved job profiles to expedite the configuration
process.
If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer,
refer to Express Transfer overview on page 30 for more information.
Refer to Import/Export load file specifications and Data upload size limitation on page 9 for more information regarding
load files. Also see General recommendations for structured data import and export jobs on page 27.
To import a document load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Pro-
cessed) Data workflow box to import a document load file to your workspace.

Import/Export Guide 77
Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 78
4. On the Choose the Load File Type dialog, click the Document box to import a document load file to your work-
space.

5. If Express Transfer is not Active, skip this step. If it is Active:


l Click Select Folder on the Select data to Import dialog to browse to your local drive and select the folder
with the files that you want to upload. In the case of universal naming convention (UNC) paths, you can
copy and paste the path into the Select Folder address bar in the dialog box to access the desired folder.
For example, \\ServerName\SharedResourceName\FilePath.
l Click Staging Load File to select a load file from the StructuredData folder in Staging.

Notes:
l Accessing Choose from Staging requires Allow Staging Import permissions. Refer to the Per-
missions on page 12 page for more information.
l If you choose to import load file data from Staging, the load file and all linked files will be copied
to the destination located outside of your Staging Area. After the import is completed, you can
clean up the source data in Staging.

Import/Export Guide 79
Notes:
l You can choose only one folder with a load file to transfer.
l File names must be 200 characters or less, including the extension.
l We recommend using a local drive instead of a mapped or external drive to avoid potential slowness
and connection issues with the file import process. Also see Data transfer performance considerations
on page 43.
l When Express Transfer is active, you should not zip data for importing.
l When Express Transfer is active, it uploads only files linked in the selected load file, regardless of their
location.
l When Express Transfer is active, it ignores mismatches in upper and lower case between file paths in
the load file and the actual file names.
l When Express Transfer is active, it supports load files with relative paths, absolute paths, and UNC
paths. It is possible to mix different path types in a single load file.

6. On the Choose Load File and Location dialog, complete the following fields, then click Continue. Refer to
Import/Export load file specifications for more information regarding load files.

Import/Export Guide 80
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on the
Import/Export Job Page. The Job name field accepts up to 50 characters.
l Destination folder—click the Select button, and do one of the following:
l Choose an existing folder.
l Create a new workspace folder by right-clicking on an existing folder, click Create, enter a new
folder name, click out of the new folder to save it, then click Select.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They can
be reused when creating future jobs with the same or similar settings in RelativityOne. This saves time
and effort as well as helps prevent data entry errors when you're mapping fields, for example. Profiles
with the ".ie" extension can only be used in Import/Export.
l None—select this option if you do not desire to use a profile for this import or if you intend to create
a new profile based on the settings entered in the upcoming steps. You will be able to save the pro-
file settings later to an .ie file via the Download Profile (.ie) button.

Import/Export Guide 81
l From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie
file) or an existing .kw* profile, created via the former Relativity Desktop Client application, to reuse
the job settings for this workflow. Use the drag and drop feature or browse for a file to choose it. All
job settings provided within the selected profile file will be automatically entered where applicable
in the succeeding workflow dialogs.
l Regional Settings (Date and Time)—select the desired format for imported date and time data. A pre-
view of the chosen format will appear below the selection. The setting selected will remain for all future
jobs until you choose another one from the list or until you clear your browser cache. When browser
cache is cleared, the setting will revert to the US date and time by default.
l Load File—use the drag and drop feature or click browse for a file to select the document load file from
your local drive.
l Choose From Staging—select a load file from the StructuredData in Staging. Your load file data must
not be zipped. Otherwise, you will not be able to choose it from Staging.
l Include Native & Text—select this option to include native and text files.

Note: The Include Native & Text option is not available for image or production import workflows as
there are no native files included in OPT files.

l Native & Text—if Include Native & Text was selected, use the drag and drop feature or click browse for
a file to select the zipped native and text file from your local drive. See ZIP archive with extracted text
and natives on page 20.
l (Optional) Notification Addresses—enable email notifications by providing the email addresses of
those who should get notified once the job completed, failed, or canceled.
7. On the Load File Settings dialog, select the delimiters and encoding values of the document load file for the
import, then click Continue. The File Column Headers Preview pane will help you to choose the proper set-
tings.

l File Encoding—select an encoding format for the document load file. Consult your processing vendor or
department to determine the correct encoding option, if necessary. The File Column Headers Preview
pane automatically updates when you select the File Encoding type. Since the load file is parsed based
on the delimiter set, you may need to check delimiters used in the load file if the column headers are not
lined up correctly. Determine the delimiters used in the file, and then select them in the delimiters section
of this dialog.
l First Line Contains Column Names toggle—select this option if the first line contains column names.
Select the delimiters and encoding values used by your load file as needed:
l Column—select the character used to separate columns.
l Quote—select the character used as the text qualifier.
l Newline (Long Text Fields)—select the character used to indicate the end of a line in any extrac-
ted text or long text field.

Import/Export Guide 82
l Multi-Value—select the character used to separate choices within a field.
l Nested Value—select the character used to separate the different levels of a multi-choice hier-
archy.
8. On the Load File Fields Mapping dialog, select the load file fields to import and map them to the workspace
fields, then click Continue.

l Click Auto Map Fields to automatically map fields. The fields from the load file will be mapped to any
existing fields of the exact same name in the workspace. Any fields without a match will display
"Choose..." in the Workspace Fields column. You will need to select one from the drop-down list. To
search for a field in the list, begin typing the desired field name and matching search results are dis-
played for selection.
l Consider the following when auto-mapping fields:
l Case is not taken into account for the mapping. For example, a field named "email" in the load file
would map to a field named "Email" in the workspace.
l Spacing is taken into account. For example, in a two-word field name, if there is one space
between words in the workspace field, and two spaces between words in the load file field, the
fields will not be mapped.
l Characters are mapped only to themselves. For example, an underscore is only mapped to
another underscore, not to a space.
l Only fields matched or those with additional settings selected are loaded into the workspace. Other fields
in the Load File Fields and Workspace Fields are ignored. You must always match the identifier field for
the load file.
l When field names in the load file don't match precisely field names in the workspace, you can click Map
with AI to map similarly named fields.
l Consider the following when mapping fields with AI:
l Your data is neither used for training nor sent outside of the RelativityOne infrastructure. It remains
fully protected within our secure environment.

Import/Export Guide 83
l Fields are mapped based on the similarities in the meaning of fields’ names.
l Fields are mapped automatically when the name meaning similarities are strong.
l The Review label appears for the mappings that may require your attention.
l Fields remain unmapped if the AI model cannot understand the meaning of the field name, or the
name similarities are below the threshold. If you want to map these fields, choose a corresponding
field from the Workspace Fields list or create a new workspace field.
9. Depending on your workflow, complete the following additional fields on this dialog:
l Sort by button—click to choose your preferred sorting option:
l Default (A-Z)—sorts all rows in alphabetical order, based on the load file field names.
l Mapped on top—brings the mapped fields to the top and sorts them in alphabetical order.
l Unmapped on top—brings the unmapped fields to the top and sorts them in alphabetical order.
l Review on top—brings the mapped fields which require review to the top and sorts them in alpha-
betical order.
l Create Field button—click if you want to create a new workspace field.
l Export to CSV button—click to save the field mapping configuration to a .csv file on your local
drive. This option cannot be accessed after the job has run and can only be selected prior to
executing the job.
l Load File Sample column—presents read-only example data from the load file fields.
l Load File Fields column—displays the field names from the load file. Use the Filter box to search
for field names.
l Workspace Fields column—allows you to manually map the load file fields to the existing work-
space fields. Use the Filter box to search for field names.
l Additional Field Settings column—to enable additional field settings, click the Choose down arrow in
this column to select the additional field as follows:
l Text File—select this option if the mapped Long Text field contains a relative path, absolute path,
or UNC path to a text file, and then select the File Encoding type for the file. If using absolute or
UNC paths, Express Transfer must be activated prior to starting the import job. This field was
renamed from Extracted Text since it now applies to any Long Text field.
l Folder Information Column—select this option if you want to use a metadata field to build the
folder structure for the workspace.
l Native File—select this option if the field from your load file contains a relative path, absolute path,
or UNC path to the native files. If using absolute or UNC paths, Express Transfer must be activ-
ated prior to starting the import job.
10. On the Import Settings dialog, configure your import job by selecting from which line number you want the load
file to begin importing and how you want the records to be imported.

Import/Export Guide 84
l Start Line—select the line number in the load file where you want the import process to begin. The
default value is set to 0, which results in loading the entire load file.
l Import mode—choose an import mode:
l Append Only—loads only new records.
l Overlay Only—updates existing records only. If selected, then you must include an Overlay Iden-
tifier in an overlay load. This field acts as a link indicating to RelativityOne where to import the
data.
l Append/Overlay—adds new records and overlays data on existing records.

Note: For Append/Overlay and Overlay Only, if a blank metadata field exists in the load file, .dat or.csv, the
blank value will overlay (remove) any existing value that may reside in the corresponding mapped field.

l Multi-Select Field Overly Behavior—this field appears if you selected Overlay Only or Append/Overlay
as the Import Mode and have mapped at least one Multiple Choice or Multiple Object field. Choose one
of the following options:
l Use Field Settings—merges or replaces all values for multi-choice and multi-object fields in the
load file with corresponding multi-choice and multi-option fields in the workspace. The fields are
merged according to the overlay behavior settings in the environment.
l Merge Values—merges all values for multi-choice and multi-object fields in the load file with cor-
responding multi-choice and multi-option fields in the workspace. The fields are merged regard-
less of the overlay behavior settings in the environment.
l Replace Values—replaces all values for multi-choice and multi-object fields in the load file with
corresponding multi-choice and multi-option fields in the workspace.
11. (Optional) Click Download Profile (.ie) on the Import Settings dialog to download the job configuration settings
entered thus far to an .ie file on your computer. This way they can be reused for other jobs.
12. (Optional) Click Precheck Load File to check for errors prior to importing the load file. For details, see Pre-
check Load File optional step on page 87.
13. Click the Import button to start the importing process.
14. Review the importing progress on the Overview tab on the Importing dialog. Real-time details regarding the
number of transferred files and data size being processed are displayed during the Uploading and Extracting
steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the import-
ing process is complete.

Caution: If you used Import/Export in web only mode, meaning Express Transfer was not active, do not
close the Importing dialog until after the Uploading step has successfully completed. Closing the dialog prior
to the Uploading step completing will terminate the data transfer (upload) process.

Import/Export Guide 85
15. Go to the Job Settings tab on the Importing dialog to review the job configuration settings. If desired, click
Download Profile (.ie) to download the job configuration settings entered thus far to an .ie file on your com-
puter. This way they can be reused for other jobs.

16. If no errors were found in the load file, go to the next step. If errors were found, click the Errors tab on the Import-
ing dialog to view them, then do either of the following:

Note: Only records that imported without errors will appear in the workspace.

l To proceed without correcting the errors, click Close.


l To manually correct them now, click the Download Error Load File button. Review the errors and cor-
rect them as needed. When you have finished, upload the file with the corrected data by clicking the
Select button on the Importing screen next to New Load File. Then, navigate to the load file on your local
drive to select it. Once selected, click Import to import the job with corrected data.

Import/Export Guide 86
Note: You can only correct documents included in the original load file. If you need to add missing doc-
uments, create a new import job.

17. Click Finish to close the dialog.


You can review the Import/Export Job page to see more information about the job. Refer to Import/Export Job tracking
and history for details.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and
history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You
do not have to be logged into RelativityOne to view information within the Express Transfer application.

7.4.0.1 Pre-check Load File optional step


You can click Precheck Load File option on the Import Settings dialog to run a validation process on the load file to
check for errors prior to importing it. For more details, refer to Pre-check Load File.

Note: If the workflow is configured to use Staging, the Pre-check Load File step will be unavailable. Ensure your
load file is validated manually before proceeding.

All detected errors are displayed in the Pre-check window. Click the down arrow next to any error message to view its
details. If you want to correct the errors in the source file(s) and repeat the importing steps, click Cancel to discontinue
importing the file at this time. Otherwise, go to the next step to import the load file with errors and correct them later.
The following validations are performed during precheck:

l Date format
l Field type
l Field length
l Number of load file cells
l Number of folders and choice fields
l File paths for natives and extracted text. The precheck checks 1,000 random lines across the whole load file.

Import/Export Guide 87
Note: The Pre-check Load File summary dialog displays a maximum of 1,000 errors for each error category. For
example, if an error category has 2,000 errors, only the first 1,000 will be displayed in the drop-down list.

Import/Export Guide 88
7.5 Importing an image load file
You can use Import/Export to import image and PDF load files that are Opticon-formatted (.opt) page-level files. For
more information on Opticon load file, see Load file format.

7.5.1 Considerations
Before you begin, consider the following:

l When you import images, they are added to a workspace as documents.


l RelativityOne only accepts the following types of image files:
l Single page TIFF (Group IV)
l Single page JPG
l Single page and multi page PDF. The files must have a .pdf extension. See the Community articles How
to import multipage PDF files with Express Transfer Active and How to import multipage PDF files using
Import/Export for more information.
l When you import PDFs, they are visible in the PDF Viewer and Extracted Text view, if you included text files.
l To import PDFs as images, they must be converted to an image file type, .tiff or .jpg, before you run the import
job.
l Import/Export expects all the files in the .opt load files to be of the same type. This means you cannot mix image
and PDF files in the same load file.

7.5.2 References
We recommend referring to the following information when importing image load files:

l Refer to Image and extracted text files for more details on importing image files using Import/Export.
l If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data
transfer, refer to Express Transfer overview on page 30 for more information.
l Refer to Import/Export load file specifications and Data upload size limitation on page 9 for more information
regarding import of load files. Also see Load file import recommendations on page 27.

7.5.3 Before you begin


Before you begin importing images load files in Import/Export:

l Find out about Opticon load file structure in Load file format.
l Review information in Image and extracted text files.
l Read Considerations above.
l Read References above.

7.5.4 Importing image load file workflow


To import an image load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job.

Import/Export Guide 89
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Pro-
cessed) Data box.

Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 90
4. On the Choose the Load File Type dialog, click the Image box.

5. If Express Transfer is not Active, skip this step. If it is Active, go to Select data to Import dialog on page 94.

Import/Export Guide 91
6. Complete fields on the Choose Load File and Location dialog, then click Continue. For more information, see
Choose Load File and Location options on page 95.

7. On the Import Settings dialog, configure your import job by selecting the numbering and choosing the import
mode. For more information, see Import Settings options on page 96.

8. (Optional) Click Download Profile (.ie) on the Import Settings dialog to download the job configuration settings
entered thus far to an .ie file on your computer. This way they can be reused for other jobs.
9. (Optional) Click Precheck Load File on the Import Settings dialog to check for errors prior to importing the load
file. For more information, see Pre-check Load File optional step on page 97.

Import/Export Guide 92
10. Click the Import button to start the importing process.
11. Review the importing progress on the Overview tab on the Importing dialog. Real-time details regarding the
number of transferred files and data size being processed are displayed during the Uploading and Extracting
steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the import-
ing process is complete.

Caution: If you used Import/Export in web only mode, meaning Express Transfer was not active, do not
close the Importing dialog until after the Uploading step has successfully completed. Closing the dialog prior
to the Uploading step completing will terminate the data transfer (upload) process.

12. Click the Job Settings tab on the Importing dialog to review the job configuration settings. If desired, click
Download Profile (.ie) to download the job configuration settings entered thus far to an .ie file on your com-
puter. This way they can be reused for other jobs.

13. If no errors were found in the load file, go to the next step. If errors were found, click the Errors tab on the Import-
ing dialog to view them, then do either of the following:

Import/Export Guide 93
Note: Only records that imported without errors will appear in the workspace.

l To proceed without correcting the errors, click Close.


l To manually correct them now, click the Download Error Load File button. Review the errors and cor-
rect them as needed. When you have finished, upload the file with the corrected data by clicking the
Select button on the Importing screen next to New Load File. Then, navigate to the load file on your local
drive to select it. Once selected, click Import to import the job with corrected data.

Note: You can only correct documents included in the original load file. If you need to add missing doc-
uments, create a new import job.

14. Click Finish to close the dialog.


You can review the Import/Export Job page to see more information about the job. Refer to Import/Export Job tracking
and history for details.
For more information on where Import/Export saves files, see the Community article Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and
history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You
do not have to be logged into RelativityOne to view information within the Express Transfer application.

7.5.4.1 Select data to Import dialog


If you are importing images with Express Transfer active, you can do the following in the Select data to Import dialog:

l Click Select Folder to browse to your local drive and select the folder with the files that you want to upload. In
the case of universal naming convention (UNC) paths, you can copy and paste the path into the Select Folder
address bar in the dialog box to access the desired folder. For example, \\Server-
Name\SharedResourceName\FilePath.

Import/Export Guide 94
l Click Staging Load File to select a load file from the StructuredData folder in Staging.

Notes:
l Accessing Choose from Staging requires Allow Staging Import permissions. Refer to the Permissions
for more information.
l If you choose to import load file data from Staging, the load file and all linked files will be copied to the
destination located outside of your Staging Area. After the import is completed, you can clean up the
source data in Staging.

Notes:
l You can choose only one folder with a load file to transfer.
l File names must be 200 characters or less, including the extension.
l We recommend using a local drive instead of a mapped or external drive to avoid potential slowness and con-
nection issues with the file import process. Also see Data transfer performance considerations on page 43.
l When Express Transfer is active, you should not zip data for importing.
l When Express Transfer is active, it uploads only files linked in the selected load file, regardless of their loc-
ation.
l When Express Transfer is active, it ignores mismatches in upper and lower case between file paths in the
load file and the actual file names.
l When Express Transfer is active, it supports load files with relative paths, absolute paths, and UNC paths. It
is possible to mix different path types in a single load file.

7.5.4.2 Choose Load File and Location options


See options available in the Load file and Location dialog.
Complete the options in the Load File and Location dialog:

Import/Export Guide 95
l Job name—provide a descriptive job name so that you can quickly identify and track that job on the Import/Ex-
port Job page. The Job name field accepts up to 50 characters.
l Destination folder—click the Select button, and do one of the following:
l Choose an existing folder.
l Create a new workspace folder by right-clicking on an existing folder, click Create, enter a new folder
name, click out of the new folder to save it, then click Select.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They can be
reused when creating future jobs with the same or similar settings in RelativityOne. This saves time and effort
as well as helps prevent data entry errors when you're mapping fields, for example. Profiles with the ".ie" exten-
sion can only be used in Import/Export.
l None—select this option if you do not desire to use a profile for this import or if you intend to create a new
profile based on the settings entered in the upcoming steps. You will be able to save the profile settings
later to an .ie file via the Download Profile (.ie) button.
l From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie file) or
an existing .kw* profile, created via the former Relativity Desktop Client application, to reuse the job set-
tings for this workflow. Use the drag and drop feature or browse for a file to choose it. All job settings
provided within the selected profile file will be automatically entered where applicable in the succeeding
workflow dialogs.
l Load File—drag and drop or use browse for a file to select the load file from your local drive.
l Choose From Staging—select a load file from the StructuredData in Staging. Your load file data must not be
zipped. Otherwise, you will not be able to choose it from Staging.
l Images—drag and drop or use browse for a file to select a zipped image file from your local drive. See Image
and extracted text files on page 21.
l (Optional) Notification Addresses—enable email notifications by providing the email addresses of those who
should get notified once the job completed, failed, or canceled.

7.5.4.3 Import Settings options


See options available in the Import Settings dialog.
Complete the options in the Import Settings dialog:

l Start Line—select the line number in the load file where you want the import process to begin. The default
value is set to 0, which results in loading the entire load file.
l Numbering—select one of the following options:
l Use load file page IDs—default setting.
l Auto-number pages—select this option if page IDs in the production are not unique. For example, you
might import a set of .tiff files that share a page identifier for each record. The page identifiers are shared
per document and are not unique. The Auto-number pages option appends the 01, 02, and so on to the
page-level identifier, creating a unique number per page.
l Import Mode—choose how you want the records to be imported:
l Append Only—load only new records.
l Overlay Only—update existing records only. If selected, then you must assign a unique identifier in the
Overlay Identifier field that will be used to overlay data in the workspace. This field acts as a link indic-
ating to RelativityOne where to import the data.
l Append/Overlay—adds new records and overlays data on existing records.

Import/Export Guide 96
l (Optional) Load Extracted Text toggle—select this option to load new text for Production documents that may
be revised based on redactions. The Files encoding field will be displayed once this toggle is selected. The text
files must be meet these requirements:
l Have .txt extensions
l Stored in the same directory as image files
l Named in the same way as the image files
l Files encoding—this field displays if the Load Extracted Text option is selected. Choose the encoding format
for the text file:
l Western European (Windows)—indicates the Windows standard encoding for English.
l Unicode—utilizes more than 107,000 characters covering 90 scripts.
l Unicode (Big-Endian)—is the same as Unicode, except that the byte order is reversed.
l Unicode (UTF-7)—represents Unicode text using a stream of ASCII characters to guarantee that the
high bit will always be zero.
l Unicode (UTF-8)—represents all characters in the Unicode character set using 8-bit bytes.

7.5.4.4 Pre-check Load File optional step


You can click Precheck Load File option on the Import Settings dialog to run a validation process on the load file to
check for errors prior to importing it. For more details, refer to Pre-check Load File.

Note: If the workflow is configured to use Staging, the Pre-check Load File step will be unavailable. Ensure your
load file is validated manually before proceeding.

The following validation is performed during precheck: Image file paths. The precheck checks 1,000 random lines
across the whole load file. All detected errors are displayed in the Pre-check window. Click the down arrow next to any
error message to view its details. If you want to correct the errors in the source file(s) and repeat the importing steps,
click Cancel to discontinue importing the file at this time. Otherwise, go to the next step to import the load file with
errors and correct them later.

Note: The Pre-check Load File summary dialog displays a maximum of 1,000 errors for each error category. For
example, if an error category has 2,000 errors, only the first 1,000 will be displayed in the drop-down list.

Import/Export Guide 97
7.6 Importing a production load file
You can use Import/Export to import external productions, including single and multiple PDF files, into RelativityOne
with Import/Export. This is useful after a production goes out the door in the event a case team needs access to
documents as they were in the production and needs them available for searching.
If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer,
refer to Express Transfer overview on page 30 for more information.
Refer to Import/Export load file specifications and Data upload size limitation on page 9 for more information regarding
load files. Also see General recommendations for structured data import and export jobs on page 27.
To import a production load file:

Note: You can import data from a production load file into an existing production. If no production sets exist in the
workspace, you must create one before starting an import job. For more details, refer to the Production
documentation. If you want to import a production consisting of produced images, natives, and extracted text, see
the Community article Import Export | Importing a Production with Natives and Extracted Text.

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Pro-
cessed) Data workflow box to import a production load file into your workspace.

Import/Export Guide 98
Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 99
4. On the Choose the Load File Type dialog, click the Production box to import a production load file to your work-
station.

5. If Express Transfer is not Active, skip this step. If it is Active:


l Click Select Folder on the Select data to Import dialog to browse to your local drive and select the folder
with the files that you want to upload. In the case of universal naming convention (UNC) paths, you can
copy and paste the path into the Select Folder address bar in the dialog box to access the desired folder.
For example, \\ServerName\SharedResourceName\FilePath.
l Click Staging Load File to select a load file from the StructuredData folder in Staging.

Notes:
l Accessing Choose from Staging requires Allow Staging Import permissions. Refer to the Per-
missions for more information.
l If you choose to import load file data from Staging, the load file and all linked files will be copied
to the destination located outside of your Staging Area. After the import is completed, you can
clean up the source data in Staging.

Import/Export Guide 100


Notes:
l You can choose only one folder with a load file to transfer.
l File names must be 200 characters or less, including the extension.
l We recommend using a local drive instead of a mapped or external drive to avoid potential slowness
and connection issues with the file import process. Also see Data transfer performance considerations
on page 43.
l When Express Transfer is active, you should not zip data for importing.
l When Express Transfer is active, it uploads only files linked in the selected load file, regardless of their
location.
l When Express Transfer is active, it ignores mismatches in upper and lower case between file paths in
the load file and the actual file names.
l When Express Transfer is active, it supports load files with relative paths, absolute paths, and UNC
paths. It is possible to mix different path types in a single load file.

6. On the Choose Load File and Location dialog, complete the following fields, then click Continue. Refer to
Import/Export load file specifications for more information regarding load files.

Import/Export Guide 101


l Job name—provide a descriptive job name so that you can quickly identify and track that job on the
Import/Export Job page. The Job name field accepts up to 50 characters.
l Destination folder—click the Select button, and do one of the following:
l Choose an existing folder.
l Create a new workspace folder by right-clicking on an existing folder, click Create, enter a new
folder name, click out of the new folder to save it, then click Select.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They can
be reused when creating future jobs with the same or similar settings in RelativityOne. This saves time
and effort as well as helps prevent data entry errors when you're mapping fields, for example. Profiles
with the ".ie" extension can only be used in Import/Export.
l None—select this option if you do not desire to use a profile for this import or if you intend to create
a new profile based on the settings entered in the upcoming steps. You will be able to save the pro-
file settings later to an .ie file via the Download Profile (.ie) button.
l From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie
file) or an existing .kw* profile, created via the former Relativity Desktop Client application, to reuse
the job settings for this workflow. Use the drag and drop feature or browse for a file to choose it. All

Import/Export Guide 102


job settings provided within the selected profile file will be automatically entered where applicable
in the succeeding workflow dialogs.
l Load file—drag and drop or use browse for a file to select the load file from your local drive.
l Choose From Staging—select a load file from the StructuredData in Staging. Your load file data must
not be zipped. Otherwise, you will not be able to choose it from Staging.
l Images—drag and drop or use browse for a file to select a zipped image file from your local drive. See
Image and extracted text files on page 21.
l (Optional) Notification Addresses—enable email notifications by providing the email addresses of
those who should get notified once the job completed, failed, or canceled.
7. On the Import Settings dialog, you can select the production to import and choose the numbering and import
mode settings.

l Production—select the Production set to import.

Note: You can import data from a production load file into an existing empty production. If no empty
production sets exist in the workspace, you must create one before starting an import job. For more
details, refer to the Production documentation.

l Start Line—select the line number in the load file where you want the import process to begin. The
default value is set to 0, which results in loading the entire load file.
l Numbering—choose the numbering option:
l Use load file page IDs—default setting.
l Auto-number pages—select this option if page IDs in the production are not unique.
l Import mode—choose how you want the records to be imported:
l Append Only—loads only new records.
l Overlay Only—updates existing records only. If selected, then you must assign a unique identifier
in the Overlay Identifier field that will be used to overlay data in the workspace. This field acts as
a link indicating to RelativityOne where to import the data.
l Append/Overlay—adds new records and overlays data on existing records. If selected, then you
must assign a unique identifier in the Overlay Identifier that will be used to overlay data in the
workspace. This field acts as a link indicating to RelativityOne where to import the data.
8. If you selected Overlay Only or Append/Overlay in the previous step, select an Overlay Identifier to specify the
field that links your overlay load file to the workspace.
l Merge Values—merges all values for multi-choice and multi-object fields in the load file with cor-
responding multi-choice and multi-option fields in the workspace. The fields are merged regardless of the
overlay behavior settings in the environment.

Import/Export Guide 103


l Replace Values—replaces all values for multi-choice and multi-object fields in the load file with cor-
responding multi-choice and multi-option fields in the workspace.
l Use Field Settings—merges or replaces all values for multi-choice and multi-object fields in the load file
with corresponding multi-choice and multi-option fields in the workspace. The fields are merged accord-
ing to the overlay behavior settings in the environment.
9. (Optional) Click Download Profile (.ie) on the Import Settings dialog to download the job configuration settings
entered thus far to an .ie file on your computer. This way they can be reused for other jobs.
10. (Optional) Click Precheck Load File on the Import Settings dialog to run a validation process on the load file to
check for errors prior to importing it.

Note: If the workflow is configured to use Staging, the Pre-check Load File step will be unavailable. Ensure
your load file is validated manually before proceeding.
The following validation is performed during precheck: Image file paths. The precheck checks 1,000 random
lines across the whole load file. All detected errors are displayed in the Pre-check window. Click the down arrow
next to any error message to view its details. If you want to correct the errors in the source file(s) and repeat the
importing steps, click Cancel to discontinue importing the file at this time. Otherwise, go to the next step to
import the load file with errors and correct them later.

Note: The Pre-check Load File summary dialog displays a maximum of 1,000 errors for each error category.
For example, if an error category has 2,000 errors, only the first 1,000 will be displayed in the drop-down list.

11. Click the Import button to start the importing process.

Import/Export Guide 104


12. Review the importing progress on the Overview tab on the Importing dialog. Real-time details regarding the
number of transferred files and data size being processed are displayed during the Uploading and Extracting
steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the import-
ing process is complete.

Caution: If you used Import/Export in web only mode, meaning Express Transfer was not active, do not
close the Importing dialog until after the Uploading step has successfully completed. Closing the dialog prior
to the Uploading step completing will terminate the data transfer (upload) process.

13. Go to the Job Settings tab on the Importing dialog to review the job configuration settings. If desired, click
Download Profile (.ie) to download the job configuration settings entered thus far to an .ie file on your com-
puter. This way they can be reused for other jobs.

14. If no errors were found in the load file, go to the next step. If errors were found, click the Errors tab on the Import-
ing dialog to view them, then do either of the following:

Note: Only records that imported without errors will appear in the workspace.

Import/Export Guide 105


l To proceed without correcting the errors, click Close.
l To manually correct them now, click the Download Error Load File button. Review the errors and cor-
rect them as needed. When you have finished, upload the file with the corrected data by clicking the
Select button on the Importing screen next to New Load File. Then, navigate to the load file on your local
drive to select it. Once selected, click Import to import the job with corrected data.

Note: You can only correct documents included in the original load file. If you need to add missing doc-
uments, create a new import job.

15. Click Finish to close the dialog.


You can review the Import/Export Job page to see more information about the job. Refer to Import/Export Job tracking
and history for details.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and
history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You
do not have to be logged into RelativityOne to view information within the Express Transfer application.

7.7 Importing an RDO load file


You can import Relativity's dynamic objects (RDO) for use in Relativity applications. The workflow for RDO data import
follows the same general guidelines as those for document load file imports.
If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer,
refer to Express Transfer overview on page 30 for more information.
Refer to Import/Export load file specifications and Data upload size limitation on page 9 for more information regarding
load files. Also see General recommendations for structured data import and export jobs on page 27.
To import RDO data:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Pro-
cessed) Data workflow box to import an RDO load file to your workspace.

Import/Export Guide 106


Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 107


4. On the Choose the Load File Type dialog, click the RDO box to import a load file to your workspace.

5. If Express Transfer is not Active, skip this step. If it is Active:


l Click Select Folder on the Select data to Import dialog to browse to your local drive and select the folder
with the files that you want to upload. In the case of universal naming convention (UNC) paths, you can
copy and paste the path into the Select Folder address bar in the dialog box to access the desired folder.
For example, \\ServerName\SharedResourceName\FilePath.
l Click Staging Load File to select a load file from the StructuredData folder in Staging.

Notes:
l Accessing Choose from Staging requires Allow Staging Import permissions. Refer to the Per-
missions on page 12 page for more information.
l If you choose to import load file data from Staging, the load file and all linked files will be copied
to the destination located outside of your Staging Area. After the import is completed, you can
clean up the source data in Staging.

Import/Export Guide 108


Notes:
l You can choose only one folder with a load file to transfer.
l File names must be 200 characters or less, including the extension.
l We recommend using a local drive instead of a mapped or external drive to avoid potential slowness
and connection issues with the file import process. Also see Data transfer performance considerations
on page 43.
l When Express Transfer is active, you should not zip data for importing.
l When Express Transfer is active, it uploads only files linked in the selected load file, regardless of their
location.
l When Express Transfer is active, it ignores mismatches in upper and lower case between file paths in
the load file and the actual file names.
l When Express Transfer is active, it supports load files with relative paths, absolute paths, and UNC
paths. It is possible to mix different path types in a single load file.

6. On the Choose Load File and Location dialog, complete the following fields, then click Continue. Refer to
Import/Export load file specifications for more information regarding load files.

Import/Export Guide 109


l Job Name—provide a descriptive job name so that you can quickly identify and track that job on the
Import/Export Job Page. The Job name field accepts up to 50 characters.
l Relativity Object Type—select the Relativity object type from the drop-down list that you want to import
data.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They can
be reused when creating future jobs with the same or similar settings in RelativityOne. This saves time
and effort as well as helps prevent data entry errors when you're mapping fields, for example. Profiles
with the ".ie" extension can only be used in Import/Export.
l None—select this option if you do not desire to use a profile for this import or if you intend to create
a new profile based on the settings entered in the upcoming steps. You will be able to save the pro-
file settings later to an .ie file via the Download Profile (.ie) button.
l From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie
file) or an existing .kw* profile, created via the former Relativity Desktop Client application, to reuse

Import/Export Guide 110


the job settings for this workflow. Use the drag and drop feature or browse for a file to choose it. All
job settings provided within the selected profile file will be automatically entered where applicable
in the succeeding workflow dialogs.
l Regional Settings (Date and Time)—select the desired format for imported date and time data. A pre-
view of the chosen format will appear below the selection. The setting selected will remain for all future
jobs until you choose another one from the list or until you clear your browser cache. When browser
cache is cleared, the setting will revert to the US date and time by default.
l Load File—use the drag and drop feature or click browse for a file to select load file with RDO data
from your local drive.
l Choose From Staging—select a load file from the StructuredData in Staging. Your load file data must
not be zipped. Otherwise, you will not be able to choose it from Staging.
l Include Native & Text—select this option to include native and text files.

Note: The Include Native & Text option is not available for image or production import workflows as
there are no native files included in OPT files.

l Native & Text—if Include Native & Text was selected, use the drag and drop feature or click browse for
a file to select the zipped native and text file from your local drive. See ZIP archive with extracted text
and natives on page 20
l (Optional) Notification Addresses—enable email notifications by providing the email addresses of
those who should get notified once the job completed, failed, or canceled.
7. On the Load File Settings dialog, select the delimiters and encoding values of the load file for the import, then
click Continue. The File Column Headers Preview pane will help you to choose the proper settings.

l File Encoding—select an encoding format for the load file. Consult your processing vendor or depart-
ment to determine the correct encoding option, if necessary.
The File Column Headers Preview pane automatically updates when you select the File Encoding type.
Since the load file is parsed based on the delimiter set, you may need to check delimiters used in the load
file if the column headers are not lined up correctly. Determine the delimiters used in the file, and then
select them in the delimiters section of this tab.
l First Line Contains Column Names toggle—select this option if the first line contains column names.
l Select the delimiters and encoding values used by your load file:
l Column—select the character used to separate columns.
l Quote—select the character used as the text qualifier.
l Newline (Long Text Fields)—select the character used to indicate the end of a line in any extrac-
ted text or long text field.
l Multi-Value—select the character used to separate choices within a field.

Import/Export Guide 111


l Nested Value—select the character used to separate the different levels of a multi-choice hier-
archy.
8. On the Load File Fields Mapping dialog, select the load file fields to import and map them to the workspace
fields, then click Continue.

l Click Auto Map Fields to automatically map fields. The fields from the load file will be mapped to any
existing fields of the exact same name in the workspace. Any fields without a match will display
"Choose..." in the Workspace Fields column. You will need to select one from the drop-down list. To
search for a field in the list, begin typing the desired field name and matching search results are dis-
played for selection.
l Consider the following when auto-mapping fields:
l Case is not taken into account for the mapping. For example, a field named "email" in the load file
would map to a field named "Email" in the workspace.
l Spacing is taken into account. For example, in a two-word field name, if there is one space
between words in the workspace field, and two spaces between words in the load file field, the
fields will not be mapped.
l Characters are mapped only to themselves. For example, an underscore is only mapped to
another underscore, not to a space.
l Only fields matched or those with additional settings selected are loaded into the workspace. Other fields
in the Load File Fields and Workspace Fields are ignored. You must always match the identifier field for
the load file.
l To import RDO data into a workspace, you must map the RDO identifier, whether it be Name, Control
Number, or another field. If you do not, the import mode options will be limited and you will be unable to
proceed with the import.
l When field names in the load file don't match precisely field names in the workspace, you can click Map
with AI to map similarly named fields.

Import/Export Guide 112


l Consider the following when mapping fields with AI:
l Your data is neither used for training nor sent outside of the RelativityOne infrastructure. It remains
fully protected within our secure environment.
l Fields are mapped based on the similarities in the meaning of fields’ names.
l Fields are mapped automatically when the name meaning similarities are strong.
l The Review label appears for the mappings that may require your attention.
l Fields remain unmapped if the AI model cannot understand the meaning of the field name, or the
name similarities are below the threshold. If you want to map these fields, choose a corresponding
field from the Workspace Fields list or create a new workspace field.
9. Depending on your workflow, complete the following additional fields on this dialog:
l Sort by button—click to choose your preferred sorting option:
l Default (A-Z)—sorts all rows in alphabetical order, based on the load file field names.
l Mapped on top—brings the mapped fields to the top and sorts them in alphabetical order.
l Unmapped on top—brings the unmapped fields to the top and sorts them in alphabetical order.
l Review on top—brings the mapped fields which require review to the top and sorts them in alpha-
betical order.
l Create Field button—click if you want to create a new workspace field.
l Export to CSV button—click to save the field mapping configuration to a .csv file on your local
drive. Be aware that this option cannot be accessed after the job has run and can only be selected
prior to executing the job.
l Load File Sample column—presents read-only example data from the load file fields.
l Load File Fields column—displays the field names from the load file. Use the Filter box to search
for field names.
l Workspace Fields column—allows you to manually map the load file fields to the existing work-
space fields. Use the Filter box to search for field names.
l Additional Field Settings column—to enable additional field settings, click the Choose down arrow in
this column to select the additional field as follows:
l Native File—select this option if the field from your load file contains a relative path, absolute path,
or UNC path to the native files. If using absolute or UNC paths, Express Transfer must be activ-
ated prior to starting the import job.
l Parent Object—select this option if the RDO has a parent that is not of Workspace type.
10. On the Import Settings dialog, configure your import job by selecting from which line number you want the load
file to begin importing and how you want the records to be imported.

l Start Line—select the line number in the load file where you want the import process to begin. The
default value is set to 0, which results in loading the entire load file.

Import/Export Guide 113


l Import mode—choose how you want the records to be imported.
l Append Only—loads only new records.
l Append/Overlay—adds new records and overlays data on existing records. If selected, then you
must assign a unique identifier in the Overlay Identifier field that will be used to overlay data in
the workspace. This field acts as a link indicating to RelativityOne where to import the data. For
Append/Overlay and Overlay Only, if a blank metadata field exists in the load file, .dat or .csv, the
blank value will overlay (remove) any existing value that may reside in the corresponding mapped
field.
l Overlay Only—updates existing records only. If selected, then you must include an Overlay Iden-
tifier next.
l Overlay Identifier—if either Overlay Only or Append/Overlay mode is selected, then assign the
unique identifier that will be used to overlay data in the workspace. This field acts as a link indic-
ating to RelativityOne where to import the data.
11. (Optional) Click Download Profile (.ie) on the Import Settings dialog to download the job configuration settings
entered thus far to an .ie file on your computer. This way they can be reused for other jobs.
12. (Optional) Click Precheck Load File on the Import Settings dialog to run a validation process on the load file to
check for errors prior to importing it.

Note: If the workflow is configured to use Staging, the Pre-check Load File step will be unavailable. Ensure
your load file is validated manually before proceeding.
All detected errors are displayed in the Pre-check window. Click the down arrow next to any error message to
view its details. If you want to correct the errors in the source file(s) and repeat the importing steps, click Cancel
to discontinue importing the file at this time. Otherwise, go to the next step to import the load file with errors and
correct them later. The following validations occur during pre-check:
l Date format
l Field type
l Field length
l Number of load file cells
l Number of folders and choice fields
l File paths for natives and extracted text (checks 1,000 random lines across the whole load file)

Note: The Pre-check Load File summary dialog displays a maximum of 1,000 errors for each error category.
It will also display a message indicating the total number of errors found. For example, if an error category
has 2,000 errors, only the first 1,000 will be displayed in the drop-down.

Import/Export Guide 114


13. Click the Import button to start the importing process.
14. Review the importing progress on the Overview tab on the Importing dialog. Real-time details regarding the
number of transferred files and data size being processed are displayed during the Uploading and Extracting
steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the import-
ing process is complete.

Note: If you used Import/Export in web only mode, meaning Express Transfer was not active, do not close
the Importing dialog until after the Uploading step has successfully completed. Closing the dialog prior to the
Uploading step completing will terminate the data transfer (upload) process.

Import/Export Guide 115


15. Go to the Job Settings tab on the Importing dialog to review the job configuration settings. If desired, click
Download Profile (.ie) to download the job configuration settings entered thus far to an .ie file on your com-
puter. This way they can be reused for other jobs.

16. If no errors were found in the load file, go to the next step. If errors were found, click the Errors tab on the Import-
ing dialog to view them, then do either of the following:

Note: Only records that imported without errors will appear in the workspace.

l To proceed without correcting the errors, click Close.


l To manually correct them now, click the Download Error Load File button. Review the errors and cor-
rect them as needed. When you have finished, upload the file with the corrected data by clicking the
Select button on the Importing screen next to New Load File. Then, navigate to the load file on your local
drive to select it. Once selected, click Import to import the job with corrected data.

Import/Export Guide 116


Note: You can only correct documents included in the original load file. If you need to add missing doc-
uments, create a new import job.

17. Click Finish to close the dialog.


You can review the Import/Export Job page to see more information about the job. Refer to Import/Export Job tracking
and history for details.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and
history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You
do not have to be logged into RelativityOne to view information within the Express Transfer application.

7.8 Importing an Access DB load file (MDB)


Note: The import and export workflows with Access DB (MDB) are designed for and are currently available for the
Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your
Account Representative.

You can use Import/Export to import document load files, .mdb .and mdbacc, into RelativityOne that contain document
metadata, native files, or extracted text. You're also able to use saved job profiles to expedite the configuration
process.
If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer,
refer to Express Transfer overview on page 30 for more information.
Refer to Access DB (MDB) load file specifications and Data upload size limitation on page 9 for more information
regarding load files. Also see General recommendations for structured data import and export jobs on page 27.
To import an Access DB load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Structured (Pro-
cessed) Data workflow box to import a document load file to your workspace.

Import/Export Guide 117


Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 118


4. On the Choose the Load File Type dialog, click the Access DB box to import an MDB load file to your work-
space.

5. If Express Transfer is not Active, skip this step. If it is Active, click Select on the Select data to Import dialog to
browse to your local drive and select the folder with the files that you want to upload. In the case of universal
naming convention (UNC) paths, you can copy and paste the path into the Select Folder address bar in the dia-
log box to access the desired folder. For example, \\ServerName\SharedResourceName\FilePath.

Import/Export Guide 119


Notes:
l You can choose only one folder with a load file to transfer.
l File names must be 200 characters or less, including the extension.
l We recommend using a local drive instead of a mapped or external drive to avoid potential slowness
and connection issues with the file import process. Also see Data transfer performance considerations
on page 43.
l When Express Transfer is active, you should not zip data for importing.
l When Express Transfer is active, it ignores mismatches in upper and lower case between file paths in
the load file and the actual file names.
l When Express Transfer is active, it supports load files with relative paths, absolute paths, and UNC
paths. It is possible to mix different path types in a single load file.

6. On the Choose Load File and Location dialog, complete the following fields. Then click Continue. Refer to
Access DB (MDB) load file specifications for more information regarding load files.

l Job Name—provide a descriptive job name so that you can quickly identify and track that job on the
Import/Export Job page. The Job Name field accepts up to 50 characters.

Import/Export Guide 120


l Destination folder—click the Select button, and do one of the following:
l Choose an existing folder.
l Create a new workspace folder by right-clicking on an existing folder, click Create, enter a new
folder name, click out of the new folder to save it, then click Select.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They can
be reused when creating future jobs with the same or similar settings in RelativityOne. This saves time
and effort as well as helps prevent data entry errors when you're mapping fields. For example, profiles
with the ".ie" extension can only be used in Import/Export.
l None—select this option if you do not desire to use a profile for this import or if you intend to create
a new profile based on the settings entered in the upcoming steps. You will be able to save the pro-
file settings later to an .ie file via the Download Profile (.ie) button.
l From Local Disk Profiles—use this option to select a previously saved Import/Export profile (.ie
file) or an existing .kw* profile, created via the former Relativity Desktop Client application, to reuse
the job settings for this workflow. Use the drag and drop feature or browse for a file to choose it. All
job settings provided within the selected profile file will be automatically entered where applicable
in the succeeding workflow dialogs.
l Regional Settings (Date and Time)—select the desired format for imported date and time data. A pre-
view of the chosen format will appear below the selection. The setting selected will remain for all future
jobs until you choose another one from the list or until you clear your browser cache. When browser
cache is cleared, the setting will revert to the US date and time by default.
l Load File—use the drag and drop feature or click browse for a file to select the .mdb or .accdb load file
from your local drive.
l (Optional) Notification Addresses—enable email notifications by providing the email addresses of
those who should get notified once the job completed, failed, or canceled.
7. On the Import Data Settings dialog, select options referring to file types you want to import. The following
options are available:

l Import PDF Files toggle—select this option to import PDF files.


l Import Native Files toggle—select this option to import Native files.

Import/Export Guide 121


l Import Text Files toggle—select this option to import Text files.
l Workspace Long Text Field—select a field from your Relativity workspace that you want to
import to.
l Text File Encoding—select an encoding format for Text files.
8. On the Load File Fields Mapping dialog, select the load file fields to import and map them to the workspace
fields, then click Continue.

l Click Auto Map Fields to automatically map fields. The fields from the load file will be mapped to any
existing fields of the exact same name in the workspace. Any fields without a match will display
"Choose..." in the Workspace Fields column. You will need to select one from the drop-down list. To
search for a field in the list, begin typing the desired field name and matching search results are dis-
played for selection.
l Consider the following when auto-mapping fields:
l Case is not taken into account for the mapping. For example, a field named "email" in the load file
would map to a field named "Email" in the workspace.
l Spacing is taken into account. For example, in a two-word field name, if there is one space
between words in the workspace field, and two spaces between words in the load file field, the
fields will not be mapped.
l Characters are mapped only to themselves. For example, an underscore is only mapped to
another underscore, not to a space.
l Only fields matched or those with additional settings selected are loaded into the workspace. Other fields
in the Load File Fields and Workspace Fields are ignored. You must always match the identifier field for
the load file.
l When field names in the load file don't match precisely field names in the workspace, you can click Map
with AI to map similarly named fields.

Import/Export Guide 122


l Consider the following when mapping fields with AI:
l Your data is neither used for training nor sent outside of the RelativityOne infrastructure. It remains
fully protected within our secure environment.
l Fields are mapped based on the similarities in the meaning of fields’ names.
l Fields are mapped automatically when the name meaning similarities are strong.
l The Review label appears for the mappings that may require your attention.
l Fields remain unmapped if the AI model cannot understand the meaning of the field name, or the
name similarities are below the threshold. If you want to map these fields, choose a corresponding
field from the Workspace Fields list or create a new workspace field.
9. On the Import Settings dialog, configure your import job by selecting from which line number you want the load
file to begin importing and how you want the records to be imported.

l Production—select the Production set to import.


l Start Line—select the line number in the load file where you want the import process to begin. The
default value is set to 0, which results in loading the entire load file.
l Workspace Folder Structure—choose the workspace structure:
l MDB Folder Sturcture—uses the information from the levels data from the Export table.
l Flat Structure—includes all documents in a single folder without the folder structure.
l Import mode—choose an import mode:
l Append Only—loads only new records.
l Overlay Only—updates existing records only. If selected, then you must include an Overlay Iden-
tifier in an overlay load. This field acts as a link indicating to RelativityOne where to import the

Import/Export Guide 123


data.
l Append/Overlay—adds new records and overlays data on existing records.

Note: For Append/Overlay and Overlay Only, if a blank metadata field exists in the load file, the blank value
will overlay (remove) any existing value that may reside in the corresponding mapped field.

10. (Optional) Click Download Profile (.ie) on the Import Settings dialog to download the job configuration settings
entered thus far to an .ie file on your computer. That way they can be reused for other jobs.
11. Click the Import button to start the importing process.
12. Review the importing progress on the Overview tab on the Importing dialog. Real-time details regarding the
number of transferred files and data size being processed are displayed during the Uploading and Extracting
steps. If needed, click Cancel to stop the import job before it completes. Otherwise, click Close when the import-
ing process is complete.

Caution: If you used Import/Export in web only mode, meaning Express Transfer was not active, do not
close the Importing dialog until after the Uploading step has successfully completed. Closing the dialog prior
to the Uploading step completing will terminate the data transfer (upload) process.

13. Go to the Job Settings tab on the Importing dialog to review the job configuration settings. If desired, click
Download Profile (.ie) to download the job configuration settings entered thus far to an .ie file on your com-

Import/Export Guide 124


puter. That way they can be reused for other jobs.

14. If no errors were found in the .mdb file, click Close. If errors were found, you can click the Errors tab on the
Importing dialog to view them. Then, click Close to close the dialog.

l To proceed without correcting the errors, click Close.


l To manually correct them now, click the Download Error Load File button. Depending on error types,
you can download:

Import/Export Guide 125


l Document Error Load File (.dat)—for errors related to documents and native files import.
l Image/PDF Error Load File (.opt)—for errors related to Images/PDFs import.

Note: If you want to correct the documents or add missing documents, create a new import job.

You can review the Import/Export Job page to see more information about the job. Refer to Import/Export Job tracking
and history for details.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and
history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You
do not have to be logged into RelativityOne to view information within the Express Transfer application.

7.9 Importing transcript MDB data for Processing via Import/Export Lim-
ited General Availability
Note: This content refers to Preview, Advance Access or limited-availability functionality that may not be available
in all Relativity environments.

Note: Effective August 20, 2024, Import/Export uploads raw (unprocessed) data to the ProcessingSource folder
and triggers the Processing application. The ProcessingSource folder is included in your Staging threshold. To
avoid additional storage costs, you may want to delete the uploaded raw (unprocessed) data from this folder once it
is no longer needed.

You can use Import/Export to import transcript MDB data with the linked audio/video files into RelativityOne. This will
automatically trigger a Processing job to extract metadata from the selected transcript MDB file, create documents
and link them with audio/video content included in the dataset, in one operation. Once the transcript data is
successfully imported into your workspace, you can use the Relativity Transcript application to review the content.

7.9.1 Before you begin


The following applications should be installed in a workspace before you begin using Relativity Transcripts:

l Import/Export
l Processing
l Transcripts
If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer,
refer to Express Transfer overview on page 30 for more information.
To import transcript MDB data with linked audio/video files for Processing:

Import/Export Guide 126


Notes:
l Prepare the transcript dataset for import with Import/Export by creating a single ZIP file that contains the tran-
script MDB file and all linked audio and video files. No ZIP size limits apply.
l All files, including the MDB file, should be located on the top level of the ZIP file structure. The audio and
video files cannot be included in a nested container.

l Do not edit the MDB file, and do not change the video file names. Changing the file names can cause errors.

l Do not add any other container or loose files to the ZIP file. Otherwise, the import job may fail.
l If you need to process additional data, do it in a separate set.

7.9.2 Importing transcript MDB data


1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Raw (Unprocessed)
and Transcript MDB data workflow box.

Import/Export Guide 127


Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

4. On the Choose Unstructured Data Type dialog, click the Transcript MDB data workflow box.

Import/Export Guide 128


5. Select the transcript data files to import as follows depending on the activation status of Express Transfer:
l With Express Transfer Active: Click Select on the Select data to Import dialog to browse to your local
drive and select the folder that includes only the zipped transcript data you want to upload. In the case of
universal naming convention (UNC) paths, you can copy and paste the path into the Select Folder
address bar in the dialog box to access the desired folder. For example, \\Server-
Name\SharedResourceName\FilePath. You also have the option on the dialog to choose from file share
by clicking Choose from File Share, selecting the import source folder that includes only the zipped tran-
script data, and clicking Select Folder. Once the folder has been selected, click Continue.

Note: When you select a folder to upload, ensure that it contains only the zipped Transcript data.
Express Transfer will transfer all the data from the selected folder, including sub-folders, to the staging
area, regardless of the specific job configuration. If the selected folder contains any other files than the
zipped transcript data, the import job may fail.

l With Express Transfer not Active: On the Select file dialog, do one of the following below to upload a
file. Transcript MDB file along with the linked audio/video files must be zipped when using the first two
options mentioned below.

Import/Export Guide 129


l Drag and drop the zipped transcript data file into the upload area.
l Click browse for a file to select a zipped transcript data from your local drive.
l Click Choose From Staging to upload files directly from the Staging Area, select the folder that
contains the zipped transcript file and click Select.
6. On the Transcript Import and Processing dialog, complete the following fields:

l Job name—provide a descriptive job name so that you can quickly identify and track that job on the
Import/Export Job page. The Job name field accepts up to 50 characters.
l Processing Profile—select the desired Processing profile. The Processing profile must already exist in
Relativity.

Note: Select the Processing profile with the Auto-Publish setting enabled to automatically publish the
discovered documents.

l Destination folder—click the Select button, and do one of the following:


l Choose an existing folder.
l Create a new workspace folder by right-clicking on an existing folder, click Create, enter a new
folder name, click out of the new folder to save it, and then click Select.
l Deponent—assign the deponent manually or by adding a new deponent now, as described below:

Note: The Deponent drop-down list shows custodians available in the workspace. When you create a
new deponent with the Add Deponent feature, it is stored in the Entity Object as a custodian.

l (Optional) Notification Addresses—enable email notifications by providing the email addresses of


those who should get notified once the job completed, failed, or canceled.

Import/Export Guide 130


7. Click Run Job to start importing data.

Note: Import/Export will upload all the zipped transcript data to the staging area and create a new Processing
job based on the provided job configuration. The Processing application will extract the uploaded zip file and
process the attached MDB file with the audio/video files.

8. Review the importing progress on the Importing & Processing dialog. Real-time details regarding the number of
transferred files and data size being processed are displayed during the Uploading and Extracting steps. Do
any of the following:

Note: Only records that imported without errors will appear in the workspace.

l Click Cancel to stop the importing process before it completes.


l Click Close when the importing process is complete.

Note: If you imported data without activating Express Transfer, you can close the dialog before the
import process finishes without causing an interruption in data flow as long as it's closed after the
Uploading step is completed. Closing the dialog earlier will terminate the data transfer (upload) pro-
cess.

l Click Go to Processing when the Discovery step begins to go to the Processing Sets page of the Pro-
cessing application.
Import/Export utilizes the Processing application to process extract transcript metadata from the MDB file, create
documents, and link the attached audio/video files. Depending on the processing profile configuration, the following
processing phases will be triggered:

l Discovery
l Discovery and publish, if the auto-publish option is enabled in your processing profile

Notes:
l We recommend using the Processing application directly to determine global dedupe order creating pro-
cessing sets.
l The Inventory phase of processing is always skipped when you import unstructured data. If Inventory is
needed, use Staging Explorer to import data into RelativityOne, and then run Processing directly.

Import/Export Guide 131


Please refer to Processing in Relativity documentation for more information about using the Processing application to
ingest raw data directly into your workspace.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running, if desired, and the transfer job will continue and not be affected. You can monitor the progress and
history of jobs within Express Transfer. For more information, see Express Transfer Job tracking and history. You
do not have to be logged into RelativityOne to view information within the Express Transfer application.

7.10 Importing raw unprocessed data for Processing via Import/Export


Note: Effective August 20, 2024, Import/Export uploads raw (unprocessed) data to the ProcessingSource folder
and triggers the Processing application. The ProcessingSource folder is included in your Staging threshold. To
avoid additional storage costs, you may want to delete the uploaded raw (unprocessed) data from this folder once it
is no longer needed.

You can use Import/Export to import native, unprocessed/unstructured files, including Slack data, into RelativityOne
that require processing and it will automatically trigger a Processing job in one operation.

Notes:
l Import/Export is not a replacement for the Processing application; however it is a simplified workflow when
setting up a processing set. Using the Processing application is recommended when setting up large, com-
plex processing jobs. Also, within the Processing application, you can use Quick Create Sets, Inventory,
check and update Processing Profiles, and customize data source options.
l Processing profiles must already exist in RelativityOne before using them in the steps below.
l For optimal performance, we recommend using Import/Export with Express Transfer and organizing data in
such a way that there are as few Data Sources as possible in a single job.

If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer,
refer to Express Transfer overview on page 30 for more information.
To import raw unprocessed/unstructured files for Processing:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, the Import button is selected by default. Next, click the Raw (Unprocessed)
and Transcript MDB data workflow box to import native (raw) files into your workspace.

Import/Export Guide 132


Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

4. On the Choose Unstructured Data Type, click the Raw Data workflow box.

Import/Export Guide 133


5. Select the data files to import as follows depending on the activation status of Express Transfer:
l With Express Transfer Active: Click Select on the Select data to Import dialog to browse to your local
drive and select the folder with the files that you want to upload. In the case of universal naming con-
vention (UNC) paths, you can copy and paste the path into the Select Folder address bar at the top of the
dialog box in order to access the desired folder. For example, \\Server-
Name\SharedResourceName\FilePath.
You also have the option on the dialog to choose from file share by clicking Choose from File Share,
selecting the import source folder, and clicking Select Folder. Once the folder has been selected, click
Continue.

Note: When you select a folder to upload, Express Transfer will transfer all the data from the selected
folder, including sub-folders, to the staging area, regardless of the specific job configuration, like the
custodian mapping settings.

l With Express Transfer not Active: On the Select File dialog, do one of the following below to upload a
file. Data files must be zipped when using the first two options mentioned below. Single PST files do not
require zipping.

Import/Export Guide 134


l Drag and drop the zipped data file or single PST file into the upload area.
l Click browse for a file to select a zipped data or single PST file from your local drive.
l Click Choose From Staging to upload files directly from the Staging Area. Then, select the cor-
rect ProcessingSource folder and click Select. You do not need to zip files when importing with
this option.

Note: Effective July 5, 2025, accessing Choose from Staging requires Allow Staging Import per-
missions. Refer to the Community article Changes to Import/Export Choose From Staging
Option FAQ and the Permissions on page 12 page for more information.

6. On the Create Processing Job dialog, complete the following fields:

l Job name—provide a descriptive job name so that you can quickly identify and track that job on the
Import/Export Job page. The Job name field accepts up to 50 characters.
l Profile—select the desired Processing profile. The Processing profile must already exist in Relativity.

Note: If you are importing Slack data, please refer to Importing Slack short message data for Pro-
cessing via Import/Export on page 140 below.

l Destination folder—click the Select button, and do one of the following:


l Choose an existing folder.
l Create a new workspace folder by right-clicking on an existing folder, click Create, enter a new
folder name, click out of the new folder to save it, and then click Select.
l (Optional) Notification Addresses—enable email notifications by providing the email addresses of
those who should get notified once the job completed, failed, or canceled.

Import/Export Guide 135


7. Next, use the Select Data Sources section to select the Data Sources and assign Custodians. A maximum of
70 data sources, for example folders with data or loose files, can be selected and assigned to custodians. See
recommendations below for preparing data sources.

Import/Export Guide 136


Notes:
Recommendations for preparing data sources:
l Each selected file is treated as a separate data source. Consider organizing loose files into folders per
custodian.
l If you import data for a single custodian, you may want to create a top-level folder and place all the
data into that folder to speed up the configuration and execution of the Processing job.
l To exclude Microsoft Office temporary files, which are those file names starting with a ~ (tilde) sign,
see Exclude temporary Microsoft Office files from data import on page 51 for more information.
l Be sure your data sources have unique names. Data sources are not case sensitive. If you have data
sources with duplicate names, you may see processing errors. For example, \\[file.share]\Processing
Source[SOURCE.NAME] and \\[file.share]\Processing Source[Source.Name] would be considered
duplicate names since the system does not differentiate between capital and lower-case letters. To
make them unique, you could rename the folders [SOURCE.NAME1] and [Source.Name2].
l To import multi-part containers, place all parts inside a sub-folder within a top-level folder.
l If you use Express Transfer, select the top-level folder as the data source.
l If you prefer the web flow, compress the subfolder and choose the zip file as the data source.
Following these steps ensures all parts are treated as a single data source, allowing the multi-
part container to process correctly.
l To import Google Vault data, place all files per custodian in separate subdirectories. For example, to
import Google Vault data for two custodians, create two subdirectories. See the example and follow
the instructions:

Import/Export Guide 137


l If you use the web mode, compress all subdirectories. Do not include the root folder when com-
pressing data. Select the zip file as a data source.
l In case you prefer to go with Express Transfer, select the root folder as a data location. That way
you can assign custodians to the subdirectories.
l Avoid assigning loose files to custodians when importing Google Vault data.
Choose the Data Source by selecting the checkbox next to the folder name. Then, assign the Custodian manu-
ally or automatically, or by adding a new custodian now, as described below:
l Manually assign custodians: Select the proper custodian from the Custodian drop-down list and click
the Assign button.
l Automatically assign custodians: Click the Auto Map Custodians button to automatically assign cus-
todians to data source folders and files based on the naming pattern. Only the Last name, First name
naming pattern is supported at this time. If you want to modify the automatic assignment, click Clear next
to the custodian’s name. The application reads data source names and checks if matching custodians
have already been added to the Entity object. Depending on the result, one of the following occurs:
l Custodian(s) already exists in the Entity: If the custodian(s) already exists in the Entity, the
application automatically assigns corresponding custodians to folders and files.
l New custodian automatically created: If the application cannot find the corresponding cus-
todian in the Entity object, it creates a new one based on the data source name. Newly created cus-
todians are marked with a blue dot in the Select Data Sources pane. New custodians will be added
to the Entity object after you click Run Job in the next step. However, if you click Cancel instead of
running the job, the new custodians will not be created.
l Add a new custodian now: If you want to add a new custodian to the drop-down list from here instead
of through the Entity object, click the Add Custodian link, and do the following on the Add Custodian dia-
log:

a. Select the custodian Type:


l Person—select this option to enter a First Name and Last Name of the individual acting as
custodian of the data to be processed.
l Other—select this option if the custodian of the data to be processed is not an individual but
is, for example, an entity or company name. Then, enter the name in the Full Name field.
You can also select this option if you wish to enter an individual's full name without having
that name include a comma once you export the data associated with it.
b. Click the Add Custodian button. The newly created custodian will be added to the Custodian
drop-down list. Then, you can select and assign the custodian to the data source.

Import/Export Guide 138


8. Click Run Job to start importing data.

Note: Import/Export will upload all the zipped data to the Staging area, extract it, and create a new Pro-
cessing job based on the data source selection. Only data sources assigned to custodians will be processed
and imported to your workspace.

Note: Effective August 20, 2024, Import/Export uploads raw (unprocessed) data to the ProcessingSource
folder and triggers the Processing application. The ProcessingSource folder is included in your Staging
threshold. To avoid additional storage costs, you may want to delete the uploaded raw (unprocessed) data
from this folder once it is no longer needed.

9. Review the importing progress on the Importing & Processing dialog. Real-time details regarding the number of
transferred files and data size being processed are displayed during the Uploading and Extracting steps. Do
any of the following:

Note: Only records that imported without errors will appear in the workspace.

l Click Cancel to stop the importing process before it completes.


l Click Close when the importing process is complete.

Caution: If you imported data without activating Express Transfer, you can close the dialog before the
import process finishes without causing an interruption in data flow as long as it's closed after the
Uploading step is completed. Closing the dialog earlier will terminate the data transfer (upload) pro-
cess.

l Click Go to Processing when the Discovery step begins to go to the Processing Sets page of the Pro-
cessing application.
Import/Export utilizes the Processing application to process native files, extract metadata, and create documents.
Depending on the processing profile configuration, the following processing phases will be triggered:

l Discovery
l Discovery and publish. If the autopublish option is enabled in your processing profile

Import/Export Guide 139


Notes:
l We recommend using the Processing application directly to determine global dedupe order creating pro-
cessing sets.
l The Inventory phase of processing is always skipped when you import unstructured data. If Inventory is
needed, use Staging Explorer to import data into RelativityOne, and then run Processing directly.

Please refer to Processing in Relativity documentation for more information about using the Processing application to
ingest raw data directly into your workspace.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Note: If you ran the job with Express Transfer active, you are able to close the Import/Export application while the
job is running. The transfer job will continue and not be affected. You can monitor the progress and history of jobs
within Express Transfer. For more information, see Express Transfer Job tracking and history. You do not have to
be logged into RelativityOne to view information within the Express Transfer application.

7.10.0.1 Importing Slack short message data for Processing via Import/Export
All commercial customers can now leverage Import/Export to upload Slack data for Processing.
To import Slack short messages for Processing via Import/Export:

1. Copy the zip file containing the Slack data into a folder on your drive.
2. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
3. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
4. Activate Express Transfer. See Activating and deactivating Express Transfer on page 40 for more information.

Note: If your organization is not permitted to use Express Transfer and you need to leverage the web mode
of Import/Export to import Slack data, you must zip the folder in which the zip file is located from Step 1. Be
aware that this will create an additional zip level, the zip file from Step 1 within a zipped folder file, for trans-
port purposes only. For this reason, we recommend using Express Transfer for all your imports and exports.

5. On the Choose workflow dialog, the Import button is selected by default.


6. Click the Raw (Unprocessed) Data workflow box.
7. Provide the Job Name, select a Destination Folder, and select the Processing Profile.

Note: The following settings must already be enabled in the Processing Profile: Convert Slack to RSMF
and Download Attachments. See Processing profiles documentation for more information.

8. For Data Source, select the folder that contains the zipped Slack data, then assign a Custodian.
9. Click Run Job. Import/Export uploads the data and passes the job configuration to the Processing application.
Please refer to Processing in Relativity documentation for more information about using Processing to ingest
raw data directly into your workspace.

Note: All the RSMF conversion is done in Processing automatically. See Processing documentation on RSMF files
for more information.

Import/Export Guide 140


8 Exporting data using Import/Export
You can use Import/Export to export the following:

l Exporting a folder—use this workflow to export a folder.


l Exporting a production set—use this workflow to export a production set.
l Exporting a saved search—use this workflow to export a saved search load file.
l Exporting RDO data—use this workflow to export Relativity's dynamic objects (RDO) load file.
l Exporting a saved search or a folder with Access DB load file (MDB)—use this workflow to export a saved
search or a folder with Access DB load file (MDB).
l Exporting a production set with Access DB load file (MDB)—use this workflow to export a production set with
Access DB load file (MDB).
Also see General recommendations for structured data import and export jobs on page 27.

8.1 Exporting data using Import/Export


You can use Import/Export to export the following:

l Exporting a folder—use this workflow to export a folder.


l Exporting a production set—use this workflow to export a production set.
l Exporting a saved search—use this workflow to export a saved search load file.
l Exporting RDO data—use this workflow to export Relativity's dynamic objects (RDO) load file.
l Exporting a saved search or a folder with Access DB load file (MDB)—use this workflow to export a saved
search or a folder with Access DB load file (MDB).
l Exporting a production set with Access DB load file (MDB)—use this workflow to export a production set with
Access DB load file (MDB).
Also see General recommendations for structured data import and export jobs on page 27.

8.2 Exporting a folder load file


You can use Import/Export to export folders and sub-folders out of RelativityOne.
If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to
Express Transfer overview on page 30 for more information. With Express Transfer activated, you can run up to five
concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs on
page 9.
Refer to Import/Export load file specifications for more information regarding load files. Also see General
recommendations for structured data import and export jobs on page 27.
To export folders:

Import/Export Guide 141


1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.

Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

3. On the Choose workflow dialog, click the Export button, then click Folder.

Import/Export Guide 142


4. On the Export Settings, complete the following fields and click Continue:

l Data Source:
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on
the Import/Export Job page. The Job name field accepts up to 50 characters.
l Folders—choose which workspace folder to export.
l Export Sub-folders toggle—select this option to export sub-folders of the previously selected
folder.
l Views—select the workspace view that you would like to use to export metadata.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They
can be reused when creating future jobs with the same or similar settings in RelativityOne. This
saves time and effort as well as helps prevent data entry errors when you're mapping fields, for

Import/Export Guide 143


example.
l None—select this option if you do not desire to use a profile for this export or if you intend to
create a new profile based on the settings entered in the upcoming steps. You will be able to
save the profile settings later on the Export Job Configuration Summary dialog. The file
extension for the new profile created will be “.ie.”
l From Local Disk Profiles—use this option to select a previously saved Import/Export pro-
file (.ie file) or an existing .kw* profile to reuse the job settings for this workflow. Use the drag
and drop feature or browse for a file to choose it. All job settings provided within the selected
profile file will be automatically entered where applicable in the succeeding workflow dia-
logs.
l Location and Files:
l Export Location Type—select one or both of these options:
l Local Disk—select this option to export the selected production set data to the Staging
Area and compress it to a single zip file. Once complete, you can download the zip file with
your web browser directly to a local disk by clicking the Download button. This is the recom-
mended option when Express Transfer is activated.

Note: This temporary non-Staging Area location is automatically deleted once the down-
load is completed when using Express Transfer or is deleted after 5 days when using web
mode for downloads. This data is not included in your Staging Area threshold.

l Staging Area—select this option to create a copy of the data in the StructuredData folder in
the Staging Area. You will need to use Staging Explorer later to download data. The expor-
ted data will not be compressed.
l Local Disk and Staging Area—select both options to create a copy of the selected data in
the StructuredData folder in the Staging Area, as well as download it to your local disk with
Express Transfer or web browser.

Notes:
l The StructuredData folder is included in your Staging Area threshold. To avoid
additional storage costs, you may want to delete the exported data from that folder
once it is no longer needed.
l For some combinations of job configuration and data, Windows system on your
local machine may not be able to open ZIP archives due to too long file paths. You
may receive an error message: “The compressed (zipped) folder is invalid.” For
details, go to General recommendations for structured data import and export jobs.

l Notifications:
l (Optional) Notification Addresses—enable email notifications by providing the email addresses
of those who should get notified once the job completed, failed, or canceled.

Import/Export Guide 144


5. On the Load File Settings dialog, select the data file format and data file encoding, then click Continue.

l Data File Format—select one of the formats below for the load file you are exporting:
l .dat (Concordance)—load file exports with the standard Concordance delimiters.
l .csv (Comma separated)—load file exports with comma separated delimiters.
l .html (HTML)—load file is in HTML format and contains hyperlinks to launch any exported files.
l .txt (Custom)—load file exports with the custom delimiters that you select in the Load File Char-
acters section that is displayed when this option is selected.

l Start Line—select a line (record number) that identifies the initial document for export. The application
begins by exporting the document with this number and continues by exporting documents with sub-
sequent record numbers.
l Data File Encoding—select the encoding type for the document-level load file from the drop-down.
l Regional Settings (Date and Time)—select the desired format for the exported date and time data. A
preview of the chosen format will appear below the next field. Your selection for this field will remain for
future export jobs until you change it or clear the browser cache. Clearing the browser cache will default
the format to "English (United States)."

Import/Export Guide 145


l Long Time (with seconds)—by default, this option is toggled off. Toggle it on if you want to include
seconds with the exported date and time information. For example, the time will export as 12:10 AM
(HH:MM AM/PM) when the toggle is off. It will export as 12:10:25 AM (HH:MM:SS AM/PM) when the
toggle is on.
l Export Multiple Choice Fields as Nested—select this option to maintain the hierarchy of RelativityOne
multiple-choice lists, when applicable. The Nested Value delimiter, a backslash, separates child choices.
6. On the Select Fields dialog, choose the Workspace Fields that you want to export by moving them to the Selec-
ted Fields box, then click Continue. Optionally, you can enter field name aliases to replace the original work-
space field names in the exported load file. The Workspace Fields box displays all available fields, but only the
fields in the Selected Fields box will be exported.

Note: All fields from the chosen View are automatically added in the Selected Fields column.
You can do the following to move fields:
l Highlight a field and click one of the directional arrow buttons in the center to move it between boxes.
l Double-click on a field to move it between boxes.
l Use CTRL+ left mouse click to select multiple fields, then choose the desired directional arrow to move
between boxes.
l In Selected Fields column, set the load file column order by dragging the fields to their proper ordering
position.

Note: Field aliases should not include delimiters that define the load file structure. The job will not start if a
field alias includes such delimiter.

Import/Export Guide 146


7. On the Image Source dialog, select what images you want to export.

l Production Images Type:


l Original Images—select to export only the original, non-produced images.
l Produced Images—select to export a produced version of the images.
l Select Productions:
l Include original images toggle—select to export original images for the documents that are not
in a specified production.
8. Move the productions that you want to export from the Available Productions box to the Selected Pro-
ductions box.

Note: Any produced native files will be exported as a native instead of an image. Only one produced image is
exported based on precedence in the list. If the document is in the topmost production, that version is expor-
ted. If not, Relativity checks for the document in the second production and so on. If the document is not a
part of any of the selected productions, and "Include original images" toggle is enabled, then the original doc-
ument is produced.

9. On the File Settings dialog, select the options to include native files, images, and/or PDFs in the exported data,
then click Continue.

Import/Export Guide 147


l Export Native Files toggle—select this option to export native files.
l Export Images toggle—select this option to include images in the export. If toggled on, then you must
set the Data File Format for image-level load file, that is Opticon, IPRO, or IPRO (FullText), and the File
Type for export images, that is Single-page TIFF/JPG, Multi-page TIFF/JPG, or Rendered PDF.
l Export PDF toggle—select this option to include existing stored PDFs in the export. No document-to-
PDF conversion functionality is performed in this step. The PDFs must already exist as PDF files. If this
option is toggled on, then you must set the Data File Format for PDF-level load file, that is Opticon,
IPRO, or IPRO (FullText).
10. On the File And Folders dialog, choose the desired naming convention and folder structure for the exported
files, then click Continue.

Import/Export Guide 148


l Text and Native File Names:
l Named after—select one of the following naming conventions for exported files:
l Control Number—select this option to name the files using the document identifier/control
number.
l Custom name—select this option to customize the file names. If selected, enter data in the
following fields that appear:
l Prefix—choose whether to have the prefix be the Control Number or Production
Begin Bates.
l Select spacing—select the desired spacing option from the drop-down list.
l Select field—choose a field from your workspace or choose Custom Text and enter
your text.
l Preview—you will be able to view a Preview of the custom file name to see if it's what
you want and make changes in the fields as needed.
l Append original filename toggle—select this option to append the original file name, which is
defined as the file name as it was on disk, to the end of the exported file name.
l Folder Structure:
l Group files by—select one of the options below for how to group the exported files:

Note: Depending on the structure of your exported data, export job performance degradation
may result and be several times longer when using Workspace Structure compared with using
File Type. Unless it is necessary to use Workspace Structure, we recommend using the File
Type option for the export job.

l Workspace Structure—select this option to preserve the workspace folder structure. This
option may reduce the time of preparing production data since the files will not need to be
manually realigned later to replicate the folder structure in the workspace.

Import/Export Guide 149


l File Type—select this option to group files by their type and place them in separate folders
based on type, such as in Natives, Images, Text, and PDFs folders.
11. On the Text File Settings dialog, you can select to export text field as files and then choose the text file encoding
as follows.

l Export Text Field as Files toggle—determines the export method of the extracted text or OCR. Select
this option if you want to export files as individual document-level text files, with one file per document.
Deselect it to include text as part of the load file.
l Text File Encoding—if Export Text Field as Files is toggled on, then select the encoding format for the
document-level text files.
l Text Fields Precedence—select and assign an order to long text fields that Relativity checks for text
when performing an export. Relativity adds the Text Fields Precedence column as the last column in the
load file. You must select at least one long text field to use this functionality. Choose the fields from the
Add Fields drop-down, then click Add. To delete a selected field, click its trashcan icon.

To order the precedence of the fields, click the six-dot handle next to the field name and drag it to the
proper ordering position.
During an export, the system checks the first field in the list for text. If the field is null, it checks the next

Import/Export Guide 150


field in order of precedence for text, and so on. When Relativity finds a field that contains text, it adds the
contents of that field to the Text Fields Precedence column in the document load file. Then continues
checking the fields for the next document and so on. For example, if you listed the Extracted Text field
first and the Production OCR field second, the system would first check the Extracted Text field for con-
tent, and if it was null, it would move on to the Production OCR field, and so on.
The Text Fields Precedence column displays the file path to the exported files if you select the Export
Text Field as Files checkbox above.
12. Click Continue.
13. (Optional) In the Advanced Settings dialog, toggle on Set Custom Information if you want to customize the
volume and folder information. Otherwise, leave the toggle off.

Import/Export Guide 151


For more information, see Load file export recommendations.
l Volume Information —this section controls the naming and size of the volume identifier. Set the fol-
lowing options in this section:

Import/Export Guide 152


l Prefix—enter the alpha prefix for the volume identifier.
l Start—enter the first number used for the numeric section of the volume identifier. Multiple
volumes increment numbers during export creating unique volume identifiers.
l # of digits—enter the number of digits attached to the prefix. For example, if you enter 3, the out-
put is VOL001, VOL002, and so on.
l Max Size (MB)—enter the maximum size allowed for each volume.
l Subdirectory Information—this section controls the naming and size of volume sub-folders. Set the fol-
lowing options in this section:
l Image Prefix—enter the alpha prefix for the sub-directory that stores exported images.
l Native Prefix—enter the alpha prefix for the sub-directory that stores exported native files.
l Text Prefix—enter the alpha prefix for the sub-directory that stores exported extracted text files.
l PDF Prefix—enter the alpha prefix for the sub-directory that stores exported extracted PDF files.
l Start—enter the starting number for the sub-directories.
l # of digits—select the number of digits of the sub-directory prefix. For example, if you enter 3, the
output is IMG001, IMG002, and so on.
l Max Files—select the number of files to store in each sub-directory.
14. Click Continue.
15. On the Export Job Configuration Summary dialog, review the export job settings and go back to make any cor-
rections as needed.

16. (Optional) Click Save Settings on the Export Job Configuration Summary dialog to export the job configuration
settings entered thus far to its own profile file (.ie file extension) and save it on your computer. This way you can
reuse these settings when creating a new export job with Import/Export.

Import/Export Guide 153


Note: Import/Export saves job configuration settings to its own profile file format, .ie file extension. Com-
paring to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across
various workspaces. The .ie profile file format is not supported in other RelativityOne data transfer tools.

17. Click the Export button to start the exporting process.


18. When it's complete, the job summary lists the records exported successfully, including Load files containing
.dat, opt, etc., errors found, and path to your exported files.
l If using Import/Export with Express Transfer active, the exported files automatically start to download.
You can track the download's progress in the Exporting dialog or in Express Transfer. For more inform-
ation, see Express Transfer Job tracking and history.

Note: If you ran the job with Express Transfer active, you can close the Import/Export application while
the job is running. The transfer job will continue uninterrupted. You can monitor the progress and his-
tory of the job within Express Transfer. You do not have to be logged into RelativityOne to view inform-
ation within the Express Transfer application.

l If using Import/Export in web only mode, the application generates a zip file containing the exported data
that can be download. Click the Download button to save the exported data zip file to your computer, or
click the Close button to close the dialog without downloading the file.

Note: When downloading zip files to your computer, you can configure your browser to allow you save
the zip file to a custom file name of your choosing as well as to a specific folder destination instead of
using the default file name and destination. In the Settings menu of your browser, select Downloads.
Toggle on the option to ask where to save or what to do with each file before downloading. Now, when
you click the Download button in the Exporting dialog, your browser will display a dialog that allows
you to change the default zip file name and select a destination other than the default one. If needed,
you can also create a new folder in the chosen destination for the exported data.

l If you chose to Export to Staging Area when setting up your export job on the Export Settings dialog,
the application automatically exports data to your RelativityOne file share and skips the downloading pro-
cess. Go to the path listed on the dialog to access the exported data files.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Import/Export Guide 154


You can always view the job's Exporting dialog information after it's closed by going to the Import/Export Job page and
clicking the job name link. The Job page also contains more details about all jobs.

8.3 Exporting a production set load file


You can use Import/Export to export a production set load file out of RelativityOne.
If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to
Express Transfer overview on page 30 for more information. With Express Transfer activated, you can run up to five
concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs on
page 9.
Refer to Import/Export load file specifications for more information regarding load files. Also see General
recommendations for structured data import and export jobs on page 27.
To export a production load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, click the Export button, then click Production Set.

Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 155


4. On the Export Settings dialog, complete the following fields and click Continue.

l Data Source:
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on
the Import/Export Job page. The Job name field accepts up to 50 characters.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They
can be reused when creating future jobs with the same or similar settings in RelativityOne. This
saves time and effort as well as helps prevent data entry errors when you're mapping fields, for
example.
l None—select this option if you do not desire to use a profile for this export or if you intend to
create a new profile based on the settings entered in the upcoming steps. You will be able to
save the profile settings later on the Export Job Configuration Summary dialog. The file
extension for the new profile created will be “.ie”.
l From Local Disk Profiles—use this option to select a previously saved Import/Export pro-
file (.ie file) or an existing .kw* profile to reuse the job settings for this workflow. Use the drag
and drop feature or browse for a file to choose it. All job settings provided within the selected

Import/Export Guide 156


profile file will be automatically entered where applicable in the succeeding workflow dia-
logs.
l Production—choose the desired production set to export.
l Location and Files:
l Export Location Type—select one or both of these options:
l Local Disk—select this option to export the selected production set data to the Staging
Area and compress it to a single zip file. Once complete, you can download the zip file with
your web browser directly to a local disk by clicking the Download button. This is the recom-
mended option when Express Transfer is activated.

Note: This temporary non-Staging Area location is automatically deleted once the down-
load is completed when using Express Transfer or is deleted after 5 days when using web
mode for downloads. This data is not included in your Staging Area threshold.

l Staging Area—select this option to create a copy of the data in the StructuredData folder in
the Staging Area. You will need to use Staging Explorer later to download data. The expor-
ted data will not be compressed.
l Local Disk and Staging Area—select both options to create a copy of the selected data in
the StructuredData folder in the Staging Area, as well as download it to your local disk with
Express Transfer or web browser.

Notes:
l The StructuredData folder is included in your Staging Area threshold. To avoid
additional storage costs, you may want to delete the exported data from that folder
once it is no longer needed.
l For some combinations of job configuration and data, Windows system on your
local machine may not be able to open ZIP archives due to too long file paths. You
may receive an error message: “The compressed (zipped) folder is invalid.” For
details, go to General recommendations for structured data import and export jobs.

l Notifications:
l (Optional) Notification Addresses—enable email notifications by providing the email addresses
of those who should get notified once the job completed, failed, or canceled.

Import/Export Guide 157


5. On the Load File Settings dialog, select the data file format and data file encoding, then click Continue.

l Data File Format—select one of the formats below for the load file you are exporting:
l .dat (Concordance)—load file exports with the standard Concordance delimiters.
l .csv (Comma separated)—load file exports with comma separated delimiters
l .html (HTML)—load file is in HTML format and contains hyperlinks to launch any exported files.
l .txt (Custom)—load file exports with the custom delimiters that you select in the Load File Char-
acters section that is displayed.

l Start Line—select a line (record number) that identifies the initial document for export. The application
begins by exporting the document with this number and continues by exporting documents with sub-
sequent record numbers.
l Data File Encoding—select the encoding type for the document-level load file from the drop-down.
l Regional Settings (Date and Time)—select the desired format for the exported date and time data. A
preview of the chosen format will appear below the next field. Your selection for this field will remain for
future export jobs until you change it or clear the browser cache. Clearing the browser cache will default
the format to "English (United States)."

Import/Export Guide 158


l Long Time (with seconds)—by default, this option is toggled off. Toggle it on if you want to include
seconds with the exported date and time information. For example, the time will export as 12:10 AM
(HH:MM AM/PM) when the toggle is off. It will export as 12:10:25 AM (HH:MM:SS AM/PM) when the
toggle is on.
l Export Multiple Choice Fields as Nested—select this option to maintain the hierarchy of RelativityOne
multiple-choice lists, when applicable. The nested value delimiter, a backslash, separates child choices.
6. On the Select Fields dialog, choose the Workspace Fields that you want to export by moving them to the Selec-
ted Fields box, then click Continue. Optionally, you can enter field name aliases to replace the original work-
space field names in the exported load file. The Workspace Fields box displays all available fields, but only the
fields in the Selected Fields box will be exported.

Note: The Production::Begin Bates and Production::End Bates fields automatically populate in the Selected
Fields column.
You can do the following to move fields:
l Highlight a field and click one of the directional arrow buttons in the center to move it between boxes.
l Double-click on a field to move it between boxes.
l Use CTRL+ left mouse click to select multiple fields, then choose the desired directional arrow to move
between boxes.
l In Selected Fields column, set the load file column order by dragging the fields to their proper ordering
position.

Note: Field aliases should not include delimiters that define the load file structure. The job will not start
if a field alias includes such delimiter.

7. In order to include native files and/or images in the exported data, select the corresponding options on the File
Settings dialog, then click Continue.

Import/Export Guide 159


l Natives:
l Export Native Files toggle—select this option to export native files
l Production:
l Export Images toggle—select this option to include images in the export. If this option is toggled
on, then you must set the Data File Format and the File Type for export images.
l Data File Format—select one of the formats for image-level load file: Opticon, IPRO, or IPRO
(FullText).
l File Type—select one of the file types: Single-page TIFF/JPG, Multi-page TIFF/JPG, or Rendered
PDF.
8. On the File And Folders dialog, choose the desired naming convention and folder structure for the exported
files, then click Continue.

Import/Export Guide 160


l Text and Native File Names:
l Named after—select one of the following naming conventions for exported files:
l Control Number—select this option to name the files after the control number.
l Production Begin Bates—select this option to name the files after the production number.
l Custom name—select this option to customize native and text file names. If this option is
selected, enter data in the following fields that are displayed:
l Prefix—choose whether to have the prefix be the Control Number or Production
Begin Bates.
l Select spacing—select the desired spacing option from the drop-down list.
l Select field—choose a field from your workspace or choose Custom Text and
provide your text.
l Preview—you will be able to view a Preview of the custom file name to see if it's what
you want and make changes in the fields as needed.
l Append original filename toggle—select this option to append the original file name,
which is defined as the file name as it was on disk, to the end of the exported file name.

Import/Export Guide 161


l Folder Structure:
l Group files by—select one of the options below for how to group the exported file:

Note: Depending on the structure of your exported data, export job performance degrad-
ation may result and be several times longer when using Workspace Structure com-
pared with using File Type. Unless it is necessary to use Workspace Structure, we
recommend using the File Type option for the export job.

l File Type—select this option to group files by their type and place them in separate
folders based on type, such as in Natives, Images, Text, and PDFs folders.
l Workspace Structure—select this option to preserve the workspace folder struc-
ture. This option may reduce the time of preparing production data since the files will
not need to be manually realigned later to replicate the folder structure in the work-
space.
9. On the Text File Settings dialog, you can select to export text field as files and then choose the text file encoding
as follows.

l Export Text Field as Files toggle—determines the export method of the extracted text or OCR. Select
this option if you want to export files as individual document-level text files, with one file per document.
Deselect it to include text as part of your load file.
l Text File Encoding—if Export Text Field as Files is toggled on, then select the encoding format for the
document-level text files.
l Text Fields Precedence—select and assign an order to long text fields that Relativity checks for text
when performing an export. Relativity adds the Text Fields Precedence column as the last column in the
load file. You must select at least one long text field to use this functionality. Choose the fields from the
Add Fields drop-down, then click Add. To delete a selected field, click its trashcan icon.

Import/Export Guide 162


To order the precedence of the fields, click the six-dot handle next to the field name and drag it to the
proper ordering position.
During an export, the system checks the first field in the list for text. If the field is null, it checks the next
field in order of precedence for text, and so on. When Relativity finds a field that contains text, it adds the
contents of that field to the Text Fields Precedence column in the document load file. Then continues
checking the fields for the next document and so on. For example, if you listed the Extracted Text field
first and the Production OCR field second, the system would first check the Extracted Text field for con-
tent, and if it was null, it would move on to the Production OCR field, and so on.

Note: If you have workflows that rely on clearing a text field for multiple production versions, you will
need to ensure that you clear this field using either Mass Replace or a load file that sets the values to
NULL. Operations such as Mass Edit will clear the field but set it to blank instead of null. This may res-
ult in exporting blank text files.
The Text Fields Precedence column displays the file path to the exported files if you select the Export
Text Field as Files checkbox above.
10. Click Continue.
11. (Optional) In the Advanced Settings dialog, toggle on Set Custom Information if you want to customize the
volume and folder information using the fields below. Otherwise, leave the toggle off.

Import/Export Guide 163


For more information,see Load file export recommendations.
l Volume Information —this section controls the naming and size of the volume identifier. Set the fol-
lowing options in this section:

Import/Export Guide 164


l Prefix—enter the alpha prefix for the volume identifier.
l Start—enter the first number used for the numeric section of the volume identifier. Multiple
volumes increment numbers during export creating unique volume identifiers.
l # of digits—enter the number of digits attached to the prefix. For example, if you enter 3, the out-
put is VOL001, VOL002, and so on.
l Max Size (MB)—enter the maximum size allowed for each volume.
l Subdirectory Information —this section controls the naming and size of volume sub-folders. Set the fol-
lowing options in this section:
l Image Prefix—enter the alpha prefix for the sub-directory that stores exported images.
l Native Prefix—enter the alpha prefix for the sub-directory that stores exported native files.
l Text Prefix—enter the alpha prefix for the sub-directory that stores exported extracted text files.
l PDF Prefix—enter the alpha prefix for the sub-directory that stores exported extracted PDF files.
l Start—enter the starting number for the sub-directories.
l # of digits—select the number of digits of the sub-directory prefix. For example, if you enter 3, the
output is IMG001, IMG002, and so on.
l Max Files—select the number of files to store in each sub-directory.
12. Click Continue.
13. On the Export Job Configuration Summary dialog, review the export job settings and go back to make any cor-
rections as needed.

14. (Optional) Click Save Settings on the Export Job Configuration Summary dialog to export the job configuration
settings entered thus far to its own profile file, .ie file extension. Save it on your computer so you can reuse
these settings when creating a new export job with Import/Export.

Import/Export Guide 165


Note: Import/Export saves job configuration settings to its own profile file format, .ie file extension. Com-
paring to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across
various workspaces. The .ie profile file format is not supported in other RelativityOne data transfer tools.

15. Click the Export button to start the exporting process.


16. When it's complete, the job summary lists the records exported successfully, including Load files containing
.dat, opt, etc., errors found, and path to your exported files.
l If using Import/Export with Express Transfer active, the exported files automatically start to download.
You can track the download's progress in the Exporting dialog or in Express Transfer. For more inform-
ation, see Express Transfer Job tracking and history.

Note: If you ran the job with Express Transfer active, you can close the Import/Export application while
the job is running. The transfer job will continue uninterrupted. You can monitor the progress and his-
tory of the job within Express Transfer. You do not have to be logged into RelativityOne to view inform-
ation within the Express Transfer application.

l If using Import/Export in web only mode, the application generates a zip file containing the exported data
that can be download. Click the Download button to save the exported data zip file to your computer, or
click the Close button to close the dialog without downloading the file.

Note: When downloading zip files to your computer, you can configure your browser to allow you save
the zip file to a custom file name of your choosing as well as to a specific folder destination instead of
using the default file name and destination. In the Settings menu of your browser, select Downloads.
Toggle on the option to ask where to save or what to do with each file before downloading. Now, when
you click the Download button in the Exporting dialog, your browser will display a dialog that allows
you to change the default zip file name and select a destination other than the default one. If needed,
you can also create a new folder in the chosen destination for the exported data.

l If you chose to Export to Staging Area when setting up your export job on the Export Settings dialog,
the application automatically exports data to your RelativityOne file share and skips the downloading pro-
cess. Go the path listed on the dialog to access the exported data files.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Import/Export Guide 166


You can always view the job's Exporting dialog information after it's closed by going to the Import/Export Job page and
clicking the job name link. The Job page also contains more details about all jobs.

8.4 Exporting an RDO load file


You can use Import/Export to export Relativity's dynamic objects (RDO) load file out of RelativityOne.
If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to
Express Transfer overview on page 30 for more information. With Express Transfer activated, you can run up to five
concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs on
page 9.
Refer to Import/Export load file specifications for more information regarding load files. Also see General
recommendations for structured data import and export jobs on page 27.
To export an RDO load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, click the Export button, then click RDO.

Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 167


4. On the Export Settings dialog, complete the following fields, then click Continue:

l Data Source:
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on
the Import/Export Job page. The Job name field accepts up to 50 characters.
l Relativity Object Type—select the Object Type you want to export.

Note: If you need to perform a mass export of native translated files, select Translated Docu-
ments as the object type. See Mass exporting translated documents and the Community article
Mass Export Native Translated files via Import/Export.

Import/Export Guide 168


l View—select the View for the selected Object Type.

Note: If exporting translated files, you can use Views if you do not want to export all the trans-
lated documents in the workspace. Create a new View on the "Translated Documents Object"
and use Conditions to limit it to specific documents. See Mass exporting translated documents
and the Community article Mass Export Native Translated files via Import/Export.

l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They
can be reused when creating future jobs with the same or similar settings in RelativityOne. This
saves time and effort as well as helps prevent data entry errors when you're mapping fields, for
example.
l None—select this option if you do not desire to use a profile for this export or if you intend to
create a new profile based on the settings entered in the upcoming steps. You will be able to
save the profile settings later on the Export Job Configuration Summary dialog. The file
extension for the new profile created will be “.ie”.
l From Local Disk Profiles—use this option to select a previously saved Import/Export pro-
file (.ie file) or an existing .kw* profile to reuse the job settings for this workflow. Use the drag
and drop feature or browse for a file to choose it. All job settings provided within the selected
profile file will be automatically entered where applicable in the succeeding workflow dia-
logs.
l Location and Files:
l Export Location Type—select one or both of these options:
l Local Disk—select this option to export the selected production set data to the Staging
Area and compress it to a single zip file. Once complete, you can download the zip file with
your web browser directly to a local disk by clicking the Download button. This is the recom-
mended option when Express Transfer is activated.

Note: This temporary non-Staging Area location is automatically deleted once the down-
load is completed when using Express Transfer or is deleted after 5 days when using web
mode for downloads. This data is not included in your Staging Area threshold.

l Staging Area—select this option to create a copy of the data in the StructuredData folder in
the Staging Area. You will need to use Staging Explorer later to download data. The expor-
ted data will not be compressed.
l Local Disk and Staging Area—select both options to create a copy of the selected data in
the StructuredData folder in the Staging Area, as well as download it to your local disk with
Express Transfer or web browser.

Notes:
l The StructuredData folder is included in your Staging Area threshold. To avoid
additional storage costs, you may want to delete the exported data from that folder
once it is no longer needed.
l For some combinations of job configuration and data, Windows system on your
local machine may not be able to open ZIP archives due to too long file paths. You
may receive an error message: “The compressed (zipped) folder is invalid.” For
details, go to General recommendations for structured data import and export jobs.

Import/Export Guide 169


l Notifications:
l (Optional) Notification Addresses—enable email notifications by providing the email addresses
of those who should get notified once the job completed, failed, or canceled.
5. On the Load File Settings dialog, select the data file format and data file encoding, then click Continue.

l Data File Format—select one of the formats below for the load file you are exporting:
l .dat (Concordance)—load file exports with the standard Concordance delimiters.
l .csv (Comma separated)—load file exports with comma separated delimiters
l .html (HTML)—load file is in HTML format and contains hyperlinks to launch any exported files.
l .txt (Custom)—load file exports with the custom delimiters that you select in the Load File Char-
acters section that is displayed when this option is selected.

l Start Line—select a line (record number) that identifies the initial document for export. The application
begins by exporting the document with this number and continues by exporting documents with sub-
sequent record numbers.
l Data File Encoding—select the encoding type for the document-level load file from the drop-down.

Import/Export Guide 170


l Regional Settings (Date and Time)—select the desired format for the exported date and time data. A
preview of the chosen format will appear below the next field. Your selection for this field will remain for
future export jobs until you change it or clear the browser cache. Clearing the browser cache will default
the format to "English (United States)."
l Long Time (with seconds)—by default, this option is toggled off. Toggle it on if you want to include
seconds with the exported date and time information. For example, the time will export as 12:10 AM
(HH:MM AM/PM) when the toggle is off. It will export as 12:10:25 AM (HH:MM:SS AM/PM) when the
toggle is on.
l Export Multiple Choice Fields as Nested—select this option to maintain the hierarchy of RelativityOne
multiple-choice lists, when applicable. The Nested Value delimiter, a backslash, separates child choices.
6. On the Select Fields dialog, choose the Workspace Fields that you want to export by moving them to the Selec-
ted Fields box, then click Continue. Optionally, you can enter field name aliases to replace the original work-
space field names in the exported load file. The Selected Fields column is automatically populated with fields
that are included in the selected view. The Workspace Fields box displays all available fields. Only the fields lis-
ted in the Selected Fields box will be exported.
You can do the following to move fields:
l Highlight a field and click one of the directional arrow buttons in the center to move it between boxes.
l Double-click on a field to move it between boxes.
l Use CTRL+ left mouse click to select multiple fields, then choose the desired directional arrow to move
between boxes.
l In Selected Fields column, drag fields up and down to set the load file column order.

Note: Field aliases should not include delimiters that define the load file structure. The job will not start
if a field alias includes such delimiter.

7. To include native files in the exported data, toggle on Export Native Files on the File Settings dialog, and click
Continue.

Import/Export Guide 171


8. On the File And Folders dialog, choose the desired naming convention and folder structure for the exported
files, then click Continue.

l Text and Native File Names:


l Named after—select one of the following naming conventions for exported files:
l Identifier—select this option to name the files using the document identifier/control number.

l Custom name—select this option to customize the file names. If this option is selected,
enter data in the following fields that are displayed:
l Prefix—choose whether to have the prefix be the Control Number or Production
Begin Bates.
l Select spacing—select the desired spacing option from the drop-down list.
l Select field—choose a field from your workspace or choose Custom Text and
provide your text.
l Preview—you will be able to view a Preview of the custom file name to see if it's what
you want and make changes in the fields as needed.
l Append original filename toggle—select this option to append the original file name, which is
defined as the file name as it was on disk, to the end of the exported file name.

Import/Export Guide 172


9. On the Text File Settings dialog, you can select to export text field as files and then choose the text file encoding
as follows.

l Export Text Field as Files toggle—determines the export method of the extracted text or OCR. Select
this option if you want to export files as individual document-level text files, with one file per document.
Deselect it to include text as part of the load file.
l Text File Encoding—if Export Text Field as Files is toggled on, then select the encoding format for the
document-level text files.
l Text Fields Precedence—select and assign an order to long text fields that Relativity checks for text
when performing an export. Relativity adds the Text Fields Precedence column as the last column in the
load file. You must select at least one long text field to use this functionality. Choose the fields from the
Add Fields drop-down, then click Add. To delete a selected field, click its trashcan icon.

To order the precedence of the fields, click the six-dot handle next to the field name and drag it to the
proper ordering position.
During an export, the system checks the first field in the list for text. If the field is null, it checks the next
field in order of precedence for text, and so on. When Relativity finds a field that contains text, it adds the
contents of that field to the Text Fields Precedence column in the document load file. Then continues

Import/Export Guide 173


checking the fields for the next document and so on. For example, if you listed the Extracted Text field
first and the Production OCR field second, the system would first check the Extracted Text field for con-
tent, and if it was null, it would move on to the Production OCR field, and so on.
The Text Fields Precedence column displays the file path to the exported files if you select the Export
Text Field as Files checkbox above.
10. Click Continue.
11. (Optional) In the Advanced Settings dialog, toggle on Set Custom Information if you want to customize the
volume and folder information. Otherwise, leave the toggle off.

Import/Export Guide 174


For more information, see Load file export recommendations.
l Volume Information —this section controls the naming and size of the volume identifier. Set the fol-
lowing options in this section:

Import/Export Guide 175


l Prefix—enter the alpha prefix for the volume identifier.
l Start—enter the first number used for the numeric section of the volume identifier. Multiple
volumes increment numbers during export creating unique volume identifiers.
l # of digits—enter the number of digits attached to the prefix. For example, if you enter 3, the out-
put is VOL001, VOL002, and so on.
l Max Size (MB)—enter the maximum size allowed for each volume.
l Subdirectory Information —this section controls the naming and size of volume sub-folders. Set the fol-
lowing options in this section:
l Image Prefix—enter the alpha prefix for the sub-directory that stores exported images.
l Native Prefix—enter the alpha prefix for the sub-directory that stores exported native files.
l Text Prefix—enter the alpha prefix for the sub-directory that stores exported extracted text files.
l PDF Prefix—enter the alpha prefix for the sub-directory that stores exported extracted PDF files.
l Start—enter the starting number for the sub-directories.
l # of digits—select the number of digits of the sub-directory prefix. For example, if you enter 3, the
output is IMG001, IMG002, and so on.
l Max Files—select the number of files to store in each sub-directory.
12. Click Continue.
13. On the Export Job Configuration Summary dialog, review the export job settings and go back to make any cor-
rections as needed.

14. (Optional) Click Save Settings on the Export Job Configuration Summary dialog to export the job configuration
settings entered thus far to its own profile file, .ie file extension. Save it on your computer so you can reuse
these settings when creating a new export job with Import/Export.

Import/Export Guide 176


Note: Import/Export saves job configuration settings to its own profile file format, .ie file extension. Com-
paring to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across
various workspaces. The .ie profile file format is not supported in other data transfer tools.

15. Click the Export button to start the exporting process.


16. When it's complete, the job summary lists the records exported successfully, including Load files containing
.dat, opt, etc., errors found, and path to your exported files.
l If using Import/Export with Express Transfer active, the exported files automatically start to download.
You can monitor the download's progress in the Exporting dialog or in Express Transfer. For more inform-
ation, see Express Transfer Job tracking and history.

Note: If you ran the job with Express Transfer active, you can close the Import/Export application while
the job is running, if desired, and the transfer job will continue uninterrupted. You can monitor the pro-
gress and history of the job within Express Transfer. You do not have to be logged into RelativityOne to
view information within the Express Transfer application.

l If using Import/Export in web only mode, the application generates a zip file containing the exported data
that can be download. Click the Download button to save the exported data zip file to your computer, or
click the Close button to close the dialog without downloading the file.

Note: When downloading zip files to your computer, you can configure your browser to allow you save
the zip file to a custom file name of your choosing as well as to a specific folder destination instead of
using the default file name and destination. In the Settings menu of your browser, select Downloads.
Toggle on the option to ask where to save or what to do with each file before downloading. Now, when
you click the Download button in the Exporting dialog, your browser will display a dialog that allows
you to change the default zip file name and select a destination other than the default one. If needed,
you can also create a new folder in the chosen destination for the exported data.

l If you chose to Export to Staging Area when setting up your export job on the Export Settings dialog,
the application automatically exports data to your RelativityOne file share and skips the downloading pro-
cess. Go the path listed on the dialog to access the exported data files.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Import/Export Guide 177


You can always view the job's Exporting dialog information after it's closed by going to the Import/Export Job page and
clicking the job name link. The Job page also contains more details about all jobs.

8.5 Exporting a saved search load file


You can use Import/Export to export a saved search load file out of RelativityOne.
If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to
Express Transfer overview on page 30 for more information. With Express Transfer activated, you can run up to five
concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs on
page 9.
Refer to Import/Export load file specifications for more information regarding load files. Also see General
recommendations for structured data import and export jobs on page 27.
To export a saved search load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, click the Export button, then click Saved Search.

Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 178


4. On the Export Settings, complete the following fields, then click Continue:

l Data Source:
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on
the Import/Export Job page. The Job name field accepts up to 50 characters.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They
can be reused when creating future jobs with the same or similar settings in RelativityOne. This
saves time and effort as well as helps prevent data entry errors when you're mapping fields, for
example.
l None—select this option if you do not desire to use a profile for this export or if you intend to
create a new profile based on the settings entered in the upcoming steps. You will be able to
save the profile settings later on the Export Job Configuration Summary dialog. The file
extension for the new profile created will be “.ie”.
l From Local Disk Profiles—use this option to select a previously saved Import/Export pro-
file (.ie file) or an existing .kw* profile to reuse the job settings for this workflow. Use the drag
and drop feature or browse for a file to choose it. All job settings provided within the selected

Import/Export Guide 179


profile file will be automatically entered where applicable in the succeeding workflow dia-
logs.
l Saved Search—choose the desired saved search to export.
l Location and Files:
l Export Location Type—select one or both of these options:
l Local Disk—select this option to export the selected production set data to the Staging
Area and compress it to a single zip file. Once complete, you can download the zip file with
your web browser directly to a local disk by clicking the Download button. This is the recom-
mended option when Express Transfer is activated.

Note: This temporary non-Staging Area location is automatically deleted once the down-
load is completed when using Express Transfer or is deleted after 5 days when using web
mode for downloads. This data is not included in your Staging Area threshold.

l Staging Area—select this option to create a copy of the data in the StructuredData folder in
the Staging Area. You will need to use Staging Explorer later to download data. The expor-
ted data will not be compressed.
l Local Disk and Staging Area—select both options to create a copy of the selected data in
the StructuredData folder in the Staging Area, as well as download it to your local disk with
Express Transfer or web browser.

Notes:
l The StructuredData folder is included in your Staging Area threshold. To avoid
additional storage costs, you may want to delete the exported data from that folder
once it is no longer needed.
l For some combinations of job configuration and data, Windows system on your
local machine may not be able to open ZIP archives due to too long file paths. You
may receive an error message: “The compressed (zipped) folder is invalid.” For
details, go to General recommendations for structured data import and export jobs.

l Notifications:
l (Optional) Notification Addresses—enable email notifications by providing the email addresses
of those who should get notified once the job completed, failed, or canceled.

Import/Export Guide 180


5. On the Load File Settings dialog, select the data file format and data file encoding, then click Continue.

l Data File Format—select one of the formats below for the load file you are exporting:
l .dat (Concordance)—load file exports with the standard Concordance delimiters.
l .csv (Comma separated)—load file exports with comma separated delimiters.
l .html (HTML)—load file is in HTML format and contains hyperlinks to launch any exported files.
l .txt (Custom)—load file exports with the custom delimiters that you select in the Load File Char-
acters section that is displayed when this option is selected.

l Start Line—select a line (record number) that identifies the initial document for export. The application
begins by exporting the document with this number and continues by exporting documents with sub-
sequent record numbers.
l Data File Encoding—select the encoding type for the document-level load file from the drop-down.
l Regional Settings (Date and Time)—select the desired format for the exported date and time data. A
preview of the chosen format will appear below the next field. Your selection for this field will remain for
future export jobs until you change it or clear the browser cache. Clearing the browser cache will default
the format to "English (United States)."

Import/Export Guide 181


l Long Time (with seconds)—by default, this option is toggled off. Toggle it on if you want to include
seconds with the exported date and time information. For example, the time will export as 12:10 AM
(HH:MM AM/PM) when the toggle is off. It will export as 12:10:25 AM (HH:MM:SS AM/PM) when the
toggle is on.
l Export Multiple Choice Fields as Nested—select this option to maintain the hierarchy of RelativityOne
multiple-choice lists, when applicable. The Nested Value delimiter, a backslash, separates child choices.
6. On the Select Fields dialog, choose the Workspace Fields that you want to export by moving them to the Selec-
ted Fields box, then click Continue. Optionally, you can enter field name aliases to replace the original work-
space field names in the exported load file. The Workspace Fields box displays all available fields, but only the
fields in the Selected Fields box will be exported.

Note: The Production::Begin Bates and Production::End Bates fields automatically populate in the Selected
Fields column.
You can do the following to move fields:
l Highlight a field and click one of the directional arrow buttons in the center to move it between boxes.
l Double-click on a field to move it between boxes.
l Use CTRL+ left mouse click to select multiple fields, then choose the desired directional arrow to move
between boxes.
l In Selected Fields column, set the load file column order by dragging the fields to their proper ordering
position.

Note: Field aliases should not include delimiters that define the load file structure. The job will not start if a
field alias includes such delimiter.

Import/Export Guide 182


7. On the Image Source dialog, select what images you want to export.

l Production Images Type:


l Original Images—select to export only the original, non-produced images.
l Produced Images—select to export a produced version of the images.
l Select Productions:
l Include original images toggle—select to export original images for the documents that are not
in a specified production.
8. Move the productions that you want to export from the Available Productions box to the Selected Pro-
ductions box.

Note: Any produced native files will be exported as a native instead of an image. Only one produced image is
exported based on precedence in the list. If the document is in the topmost production, that version is expor-
ted. If not, Relativity checks for the document in the second production and so on. If the document is not a
part of any of the selected productions, and "Include original images" toggle is enabled, then the original doc-
ument is produced.

9. On the File Settings dialog, select the options to include native files, images, and/or PDFs in the exported data,
then click Continue.

Import/Export Guide 183


l Export Native Files toggle—select this option to export native files.
l Export Images toggle—select this option to include images in the export. If toggled on, then you must
set the Data File Format for image-level load file, that is Opticon, IPRO, or IPRO (FullText), and the File
Type for export images, that is Single-page TIFF/JPG, Multi-page TIFF/JPG, or Rendered PDF.
l Export PDF toggle—select this option to include existing stored PDFs in the export. No document-to-
PDF conversion functionality is performed in this step. The PDFs must already exist as PDF files. If this
option is toggled on, then you must set the Data File Format for PDF-level load file, that is Opticon,
IPRO, or IPRO (FullText).
10. On the File And Folders dialog, choose the desired naming convention and folder structure for the exported
files, then click Continue.

Import/Export Guide 184


l Text and Native File Names:
l Named after—select one of the following naming conventions for exported files:
l Control Number—select this option to name the files using the document identifier/control
number.
l Custom name—select this option to customize the file names. If selected, enter data in the
following fields that are displayed:
l Prefix—choose whether to have the prefix be the Control Number or Production
Begin Bates.
l Select spacing—select the desired spacing option from the drop-down list.
l Select field—choose a field from your workspace or choose Custom Text and enter
your text.
l Preview—you will be able to view a Preview of the custom file name to see if it's what
you want and make changes in the fields as needed.
l Append original filename toggle—select this option to append the original file name, which is
defined as the file name as it was on disk, to the end of the exported file name.
l Folder Structure:
l Group files by—select one of the options below for how to group the exported files:

Note: Depending on the structure of your exported data, export job performance degradation
may result and be several times longer when using Workspace Structure compared with using
File Type. Unless it is necessary to use Workspace Structure, we recommend using the File
Type option for the export job.

l File Type—select this option to group files by their type and place them in separate folders
based on type, such as in Natives, Images, Text, and PDFs folders.

Import/Export Guide 185


l Workspace Structure—select this option to preserve the workspace folder structure. This
option may reduce the time of preparing production data since the files will not need to be
manually realigned later to replicate the folder structure in the workspace.
11. On the Text File Settings dialog, you can select to export text field as files and then choose the text file encoding
as follows.

l Export Text Field as Files toggle—determines the export method of the extracted text or OCR. Select
this option if you want to export files as individual document-level text files, with one file per document.
Deselect it to include text as part of the load file.
l Text File Encoding—if Export Text Field as Files is toggled on, then select the encoding format for the
document-level text files.
l Text Fields Precedence—select and assign an order to long text fields that Relativity checks for text
when performing an export. Relativity adds the Text Fields Precedence column as the last column in the
load file. You must select at least one long text field to use this functionality. Choose the fields from the
Add Fields drop-down, then click Add. To delete a selected field, click its trashcan icon.

To order the precedence of the fields, click the six-dot handle next to the field name and drag it to the

Import/Export Guide 186


proper ordering position.
During an export, the system checks the first field in the list for text. If the field is null, it checks the next
field in order of precedence for text, and so on. When Relativity finds a field that contains text, it adds the
contents of that field to the Text Fields Precedence column in the document load file. Then continues
checking the fields for the next document and so on. For example, if you listed the Extracted Text field
first and the Production OCR field second, the system would first check the Extracted Text field for con-
tent, and if it was null, it would move on to the Production OCR field, and so on.
The Text Fields Precedence column displays the file path to the exported files if you select the Export
Text Field as Files checkbox above.
12. Click Continue.
13. (Optional) In the Advanced Settings dialog, toggle on Set Custom Information if you want to customize the
volume and folder information. Otherwise, leave the toggle off.

Import/Export Guide 187


For more information, see Load file export recommendations.
l Volume Information —this section controls the naming and size of the volume identifier. Set the fol-
lowing options in this section:

Import/Export Guide 188


l Prefix—enter the alpha prefix for the volume identifier.
l Start—enter the first number used for the numeric section of the volume identifier. Multiple
volumes increment numbers during export creating unique volume identifiers.
l # of digits—enter the number of digits attached to the prefix. For example, if you enter 3, the out-
put is VOL001, VOL002, and so on.
l Max Size (MB)—enter the maximum size allowed for each volume.
l Subdirectory Information —this section controls the naming and size of volume sub-folders. Set the fol-
lowing options in this section:
l Image Prefix—enter the alpha prefix for the sub-directory that stores exported images.
l Native Prefix—enter the alpha prefix for the sub-directory that stores exported native files.
l Text Prefix—enter the alpha prefix for the sub-directory that stores exported extracted text files.
l PDF Prefix—enter the alpha prefix for the sub-directory that stores exported extracted PDF files.
l Start—enter the starting number for the sub-directories.
l # of digits—select the number of digits of the sub-directory prefix. For example, if you enter 3, the
output is IMG001, IMG002, and so on.
l Max Files—select the number of files to store in each sub-directory.
14. Click Continue.
15. On the Export Job Configuration Summary dialog, review the export job settings and go back to make any cor-
rections as needed.

16. (Optional) Click Save Settings on the Export Job Configuration Summary dialog to export the job configuration
settings entered thus far to its own profile file (.ie file extension) and save it on your computer. This way you can
reuse these settings when creating a new export job with Import/Export.

Import/Export Guide 189


Note: Import/Export saves job configuration settings to its own profile file format, .ie file extension. Com-
paring to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across
various workspaces. The .ie profile file format is not supported in other RelativityOne data transfer tools.

17. Click the Export button to start the exporting process.


18. When it's complete, the job summary lists the records exported successfully, including Load files containing
.dat, opt, etc., errors found, and path to your exported files.
l If using Import/Export with Express Transfer active, the exported files automatically start to download.
You can track the download's progress in the Exporting dialog or in Express Transfer. For more inform-
ation, see Express Transfer Job tracking and history.

Note: If you ran the job with Express Transfer active, you can close the Import/Export application while
the job is running. The transfer job will continue uninterrupted. You can monitor the progress and his-
tory of the job within Express Transfer. You do not have to be logged into RelativityOne to view inform-
ation within the Express Transfer application.

l If using Import/Export in web only mode, the application generates a zip file containing the exported data
that can be download. Click the Download button to save the exported data zip file to your computer, or
click the Close button to close the dialog without downloading the file.

Note: When downloading zip files to your computer, you can configure your browser to allow you save
the zip file to a custom file name of your choosing as well as to a specific folder destination instead of
using the default file name and destination. In the Settings menu of your browser, select Downloads.
Toggle on the option to ask where to save or what to do with each file before downloading. Now, when
you click the Download button in the Exporting dialog, your browser will display a dialog that allows
you to change the default zip file name and select a destination other than the default one. If needed,
you can also create a new folder in the chosen destination for the exported data.

l If you chose to Export to Staging Area when setting up your export job on the Export Settings dialog,
the application automatically exports data to your RelativityOne file share and skips the downloading pro-
cess. Go to the path listed on the dialog to access the exported data files.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.

Import/Export Guide 190


You can always view the job's Exporting dialog information after it's closed by going to the Import/Export Job page and
clicking the job name link. The Job page also contains more details about all jobs.

8.6 Exporting a saved search or a folder with Access DB load file (MDB)
Note: The import and export workflows with Access DB (MDB) are designed for and are currently available for the
Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your
Account Representative.

You can use Import/Export to export a saved search or a folder with MDB load file out of RelativityOne.
If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to
Express Transfer overview on page 30 for more information. With Express Transfer activated, you can run up to five
concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs on
page 9.
Refer to Access DB (MDB) load file specifications for more information regarding load files. Also see General
recommendations for structured data import and export jobs on page 27.
To export a saved search or a folder load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, click the Export button, then click Saved Search or Folder.

Import/Export Guide 191


Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

4. On the Export Settings dialog, complete the following fields, then click Continue:

Import/Export Guide 192


l Data Source:
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on
the Import/Export Job page. The Job name field accepts up to 50 characters.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They
can be reused when creating future jobs with the same or similar settings in RelativityOne. This
saves time and effort as well as helps prevent data entry errors when you're mapping fields, for
example.
l None—select this option if you do not desire to use a profile for this export or if you intend to
create a new profile based on the settings entered in the upcoming steps. You will be able to
save the profile settings later on the Export Job Configuration Summary dialog. The file
extension for the new profile created will be “.ie”.
l From Local Disk Profiles—use this option to select a previously saved Import/Export pro-
file (.ie file) or an existing .kw* profile to reuse the job settings for this workflow. Use the drag
and drop feature or browse for a file to choose it. All job settings provided within the selected
profile file will be automatically entered where applicable in the succeeding workflow dia-
logs.
l Saved Search—choose the desired saved search to export. This option is available for a saved
search export.
l Folders—choose which workspace folder to export. This option is available for a folder export.
l Export Sub-folders toggle—select this option to export sub-folders of the previously selected
folder. This option is available for a folder export.
l Views—select the workspace view that you would like to use to export metadata. This option is
available for a folder export.
l Location and Files:
l Export Location Type—select one or both of these options:
l Local Disk—select this option to export the selected production set data to the Staging
Area and compress it to a single zip file. Once complete, you can download the zip file with
your web browser directly to a local disk by clicking the Download button. This is the recom-
mended option when Express Transfer is activated.

Note: This temporary non-Staging Area location is automatically deleted once the down-
load is completed when using Express Transfer or is deleted after 5 days when using web
mode for downloads. This data is not included in your Staging Area threshold.

l Staging Area—select this option to create a copy of the data in the StructuredData folder in
the Staging Area. You will need to use Staging Explorer later to download data. The expor-
ted data will not be compressed.
l Local Disk and Staging Area—select both options to create a copy of the selected data in
the StructuredData folder in the Staging Area, as well as download it to your local disk with
Express Transfer or web browser.

Import/Export Guide 193


Notes:
l The StructuredData folder is included in your Staging Area threshold. To avoid
additional storage costs, you may want to delete the exported data from that folder
once it is no longer needed.
l For some combinations of job configuration and data, Windows system on your
local machine may not be able to open ZIP archives due to too long file paths. You
may receive an error message: “The compressed (zipped) folder is invalid.” For
details, go to General recommendations for structured data import and export jobs.

l Notifications:
l (Optional) Notification Addresses—enable email notifications by providing the email addresses
of those who should get notified once the job completed, failed, or canceled.
5. On the Load File Settings dialog, select the data file format and data file encoding, then click Continue.

Import/Export Guide 194


l Data File Format—select one of the formats below for the load file you are exporting:
l .dat (Concordance)—load file exports with the standard Concordance delimiters.
l .csv (Comma separated)—load file exports with comma separated delimiters.
l .html (HTML)—load file is in HTML format and contains hyperlinks to launch any exported files.
l .txt (Custom)—load file exports with the custom delimiters that you select in the Load File Char-
acters section that is displayed when this option is selected.

l Start Line—select a line (record number) that identifies the initial document for export. The application
begins by exporting the document with this number and continues by exporting documents with sub-
sequent record numbers.
l Generate MDB File—toggle on if you want to generate Access DB load file (MDB). This option is toggled
off by default.
l Data File Encoding—select the encoding type for the document-level load file from the drop-down.
l Regional Settings (Date and Time)—select the desired format for the exported date and time data. A
preview of the chosen format will appear below the next field. Your selection for this field will remain for
future export jobs until you change it or clear the browser cache. Clearing the browser cache will default
the format to "English (United States)."
l Long Time (with seconds)—by default, this option is toggled off. Toggle it on if you want to export full-
name date format with the exported date and time information. For example, when using Regional Set-
ting set to "English (Australia) | en-AU", the date and time will export as 08/04/2025, 9:01 AM
(DD/MM/YYYY HH:MM AM/PM) when the toggle is off. It will export as Tuesday, 8 April 2025 09:01:00
AM (Day name, DD Month YYYY hh:mm:ss AM/PM) when the toggle is on.
l Export Multiple Choice Fields as Nested—select this option to maintain the hierarchy of RelativityOne
multiple-choice lists, when applicable. The Nested Value delimiter, a backslash, separates child choices.
6. On the Select Fields dialog, configure how to populate individual columns and tables in the exported MDB file.
Select options in the three tabs:
l Export—on this tab, map the Relativity workspace fields to the corresponding columns in the Export
table.

Import/Export Guide 195


l Export Extras—on this tab, select which Relativity workspace fields to export into the Export_extras
table. There is also an option to rename a workspace field to a custom name. Label value in MDB file.

Import/Export Guide 196


l Parties—on this tab, select which Relativity workspace fields to export into the Parties table. There is
also an option to rename a workspace field to a custom name. Correspondence_Type value in MDB file.

Note: For multichoice fields or multiple values separated with a semicolon within a text field, there will be sep-
arate row entries created for each such value in the generated record in the Parties table.

Import/Export Guide 197


7. On the Image Source dialog, select what images you want to export.

l Production Images Type:


l Original Images—select to export only the original, non-produced images.
l Produced Images—select to export a produced version of the images.
l Select Productions:
l Include original images toggle—select to export original images for the documents that are not
in a specified production.
8. Move the productions that you want to export from the Available Productions box to the Selected Pro-
ductions box.

Import/Export Guide 198


Note: Any produced native files will be exported as a native instead of an image. Only one produced image is
exported based on precedence in the list. If the document is in the topmost production, that version is expor-
ted. If not, Relativity checks for the document in the second production and so on. If the document is not a
part of any of the selected productions, and "Include original images" toggle is enabled, then the original doc-
ument is produced.

9. On the File Settings dialog, select the options to include native files, images, and/or PDFs in the exported data,
then click Continue.

l Export Native Files toggle—select this option to export native files.


l Export Images toggle—select this option to include images in the export. If toggled on, then you must
set the Data File Format for image-level load file, that is Opticon, IPRO, or IPRO (FullText), and the File
Type for export images, that is Single-page TIFF/JPG, Multi-page TIFF/JPG, or Rendered PDF.

Import/Export Guide 199


l Export PDF toggle—select this option to include existing stored PDFs in the export. No document-to-
PDF conversion functionality is performed in this step. The PDFs must already exist as PDF files. If this
option is toggled on, then you must set the Data File Format for PDF-level load file, that is Opticon,
IPRO, or IPRO (FullText).
10. On the Text File Settings dialog, you can select to export text field as files and then choose the text file encoding
as follows.

l Export Text Field as Files toggle—determines the export method of the extracted text or OCR. Select
this option if you want to export files as individual document-level text files, with one file per document.
Deselect it to include text as part of the load file.
l Text File Encoding—if Export Text Field as Files is toggled on, then select the encoding format for the
document-level text files.
l Text Fields Precedence—select and assign an order to long text fields that Relativity checks for text
when performing an export. Relativity adds the Text Fields Precedence column as the last column in the
load file. You must select at least one long text field to use this functionality. Choose the fields from the
Add Fields drop-down, then click Add. To delete a selected field, click its trashcan icon.

To order the precedence of the fields, click the six-dot handle next to the field name and drag it to the

Import/Export Guide 200


proper ordering position.
During an export, the system checks the first field in the list for text. If the field is null, it checks the next
field in order of precedence for text, and so on. When Relativity finds a field that contains text, it adds the
contents of that field to the Text Fields Precedence column in the document load file. Then continues
checking the fields for the next document and so on. For example, if you listed the Extracted Text field
first and the Production OCR field second, the system would first check the Extracted Text field for con-
tent, and if it was null, it would move on to the Production OCR field, and so on.
The Text Fields Precedence column displays the file path to the exported files if you select the Export
Text Field as Files checkbox above.
11. Click Continue.
12. On the Export Job Configuration Summary dialog, review the export job settings and go back to make any cor-
rections as needed.

13. (Optional) Click Save Settings on the Export Job Configuration Summary dialog to export the job configuration
settings entered thus far to its own profile file (.ie file extension). Save it on your computer so you can reuse
these settings when creating a new export job with Import/Export.

Note: Import/Export saves job configuration settings to its own profile file format, .ie file extension. Com-
paring to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across
various workspaces. The .ie profile file format is not supported in other RelativityOne data transfer tools.

14. Click the Export button to start the exporting process.


15. When it's complete, the job summary lists the records exported successfully, including Load files containing
.mdb, .dat, opt, etc., errors found, and path to your exported files.
l If using Import/Export with Express Transfer active, the exported files automatically start to download.
You can track the download's progress in the Exporting dialog or in Express Transfer. For more inform-
ation, see Express Transfer Job tracking and history.

Import/Export Guide 201


Note: If you ran the job with Express Transfer active, you can close the Import/Export application while
the job is running. The transfer job will continue uninterrupted. You can monitor the progress and his-
tory of the job within Express Transfer. You do not have to be logged into RelativityOne to view inform-
ation within the Express Transfer application.

l If using Import/Export in web only mode, the application generates a zip file containing the exported data
that can be download. Click the Download button to save the exported data zip file to your computer, or
click the Close button to close the dialog without downloading the file.

Note: When downloading zip files to your computer, you can configure your browser to allow you save
the zip file to a custom file name of your choosing as well as to a specific folder destination instead of
using the default file name and destination. In the Settings menu of your browser, select Downloads.
Toggle on the option to ask where to save or what to do with each file before downloading. Now, when
you click the Download button in the Exporting dialog, your browser will display a dialog that allows
you to change the default zip file name and select a destination other than the default one. If needed,
you can also create a new folder in the chosen destination for the exported data.

l If you chose to Export to Staging Area when setting up your export job on the Export Settings dialog,
the application automatically exports data to your RelativityOne file share and skips the downloading pro-
cess. Go to the path listed on the dialog to access the exported data files.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.
You can always view the job's Exporting dialog information after it's closed by going to the Import/Export Job page and
clicking the job name link. The Job page also contains more details about all jobs.

8.7 Exporting a production set with Access DB load file (MDB)


Note: The import and export workflows with Access DB (MDB) are designed for and are currently available for the
Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your
Account Representative.

You can use Import/Export to export a production set with MDB load file out of RelativityOne.
If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to
Express Transfer overview on page 30 for more information. With Express Transfer activated, you can run up to five

Import/Export Guide 202


concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs on
page 9.
Refer to Access DB (MDB) load file specifications for more information regarding load files. Also see General
recommendations for structured data import and export jobs on page 27.
To export a production load file:

1. Use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.
2. On the Import/Export Job page, click the New Import/Export Job button to start a new job.
3. On the Choose Workflow dialog, click the Export button, then click Production Set.

Note: If Express Transfer has been activated, the Express Transfer section will display a status of Active.
See Activating and deactivating Express Transfer on page 40 for more information.

Import/Export Guide 203


4. On the Export Settings, complete the following fields and click Continue:

l Data Source:
l Job Name—provide a descriptive job name so that you can quickly identify and track that job on
the Import/Export Job page. The Job name field accepts up to 50 characters.
l Folders—choose which workspace folder to export.
l Export Sub-folders toggle—select this option to export sub-folders of the previously selected
folder.
l Views—select the workspace view that you would like to use to export metadata.
l Profile—the job configuration settings that were previously saved to a profile file (.ie or .kw*). They
can be reused when creating future jobs with the same or similar settings in RelativityOne. This
saves time and effort as well as helps prevent data entry errors when you're mapping fields, for

Import/Export Guide 204


example.
l None—select this option if you do not desire to use a profile for this export or if you intend to
create a new profile based on the settings entered in the upcoming steps. You will be able to
save the profile settings later on the Export Job Configuration Summary dialog. The file
extension for the new profile created will be “.ie”.
l From Local Disk Profiles—use this option to select a previously saved Import/Export pro-
file (.ie file) or an existing .kw* profile to reuse the job settings for this workflow. Use the drag
and drop feature or browse for a file to choose it. All job settings provided within the selected
profile file will be automatically entered where applicable in the succeeding workflow dia-
logs.
l Location and Files:
l Export Location Type—select one or both of these options:
l Local Disk—select this option to export the selected production set data to the Staging
Area and compress it to a single zip file. Once complete, you can download the zip file with
your web browser directly to a local disk by clicking the Download button. This is the recom-
mended option when Express Transfer is activated.

Note: This temporary non-Staging Area location is automatically deleted once the down-
load is completed when using Express Transfer or is deleted after 5 days when using web
mode for downloads. This data is not included in your Staging Area threshold.

l Staging Area—select this option to create a copy of the data in the StructuredData folder in
the Staging Area. You will need to use Staging Explorer later to download data. The expor-
ted data will not be compressed.
l Local Disk and Staging Area—select both options to create a copy of the selected data in
the StructuredData folder in the Staging Area, as well as download it to your local disk with
Express Transfer or web browser.

Notes:
l The StructuredData folder is included in your Staging Area threshold. To avoid
additional storage costs, you may want to delete the exported data from that folder
once it is no longer needed.
l For some combinations of job configuration and data, Windows system on your
local machine may not be able to open ZIP archives due to too long file paths. You
may receive an error message: “The compressed (zipped) folder is invalid.” For
details, go to General recommendations for structured data import and export jobs.

l Notifications:
l (Optional) Notification Addresses—enable email notifications by providing the email addresses
of those who should get notified once the job completed, failed, or canceled.

Import/Export Guide 205


5. On the Load File Settings dialog, select the data file format and data file encoding, then click Continue.

l Data File Format—select one of the formats below for the load file you are exporting:
l .dat (Concordance)—load file exports with the standard Concordance delimiters.
l .csv (Comma separated)—load file exports with comma separated delimiters
l .html (HTML)—load file is in HTML format and contains hyperlinks to launch any exported files.
l .txt (Custom)—load file exports with the custom delimiters that you select in the Load File Char-
acters section that is displayed.

Import/Export Guide 206


l Start Line—select a line (record number) that identifies the initial document for export. The application
begins by exporting the document with this number and continues by exporting documents with sub-
sequent record numbers.
l Generate MDB File—toggle on if you want to generate Access DB load file (MDB). This option is toggled
off by default.
l Data File Encoding—select the encoding type for the document-level load file from the drop-down.
l Regional Settings (Date and Time)—select the desired format for the exported date and time data. A
preview of the chosen format will appear below the next field. Your selection for this field will remain for
future export jobs until you change it or clear the browser cache. Clearing the browser cache will default
the format to "English (United States)."
l Long Time (with seconds)—by default, this option is toggled off. Toggle it on if you want to export full-
name date format with the exported date and time information. For example, when using Regional Set-
ting set to "English (Australia) | en-AU", the date and time will export as 08/04/2025, 9:01 AM
(DD/MM/YYYY HH:MM AM/PM) when the toggle is off. It will export as Tuesday, 8 April 2025 09:01:00
AM (Day name, DD Month YYYY hh:mm:ss AM/PM) when the toggle is on.
l Export Multiple Choice Fields as Nested—select this option to maintain the hierarchy of RelativityOne
multiple-choice lists, when applicable. The Nested Value delimiter, a backslash, separates child choices.
6. On the Select Fields dialog, configure how to populate individual columns and tables in the exported MDB file.
Select options in the three tabs:
l Export—on this tab, map Relativity workspace fields to columns in the Export table. You can map the
Document ID field to values beyond the default Control Number, including PDF Begin Number and Pro-
duction: Begin Bates.

Import/Export Guide 207


l Export Extras—on this tab, select which Relativity workspace fields to export into the Export_extras
table. There is also an option to rename a workspace field to a custom name. Label value in MDB file.

l Parties—on this tab, select which Relativity workspace fields to export into the Parties table. There is
also an option to rename a workspace field to a custom name. Correspondence_Type value in MDB file.

7. In order to include native files and/or images and/or PDFs in the exported data, select the corresponding
options on the File Settings dialog, then click Continue.

Import/Export Guide 208


l Natives:
l Export Native Files toggle—select this option to export native files. Native files will be exported if
they exist in the production set.
l Production:
l Export Images / Export PDFs /Export Images and PDFs toggle—select this option to include
additional files in the export. If this option is toggled on, you must set the following options:
l Data File Format—select one of the formats for image/PDF-level load file: Opticon, IPRO,
or IPRO (FullText).
l File Type—select one of the file types for images: Single-page TIFF/JPG, Multi-page
TIFF/JPG, or Rendered PDF.
8. On the Text File Settings dialog, you can select to export text field as files and then choose the text file encoding
as follows.

Import/Export Guide 209


l Export Text Field as Files toggle—determines the export method of the extracted text or OCR. Select
this option if you want to export files as individual document-level text files, with one file per document.
Deselect it to include text as part of your load file.
l Text File Encoding—if Export Text Field as Files is toggled on, then select the encoding format for the
document-level text files.
l Text Fields Precedence—select and assign an order to long text fields that Relativity checks for text
when performing an export. Relativity adds the Text Fields Precedence column as the last column in the
load file. You must select at least one long text field to use this functionality. Choose the fields from the
Add Fields drop-down, then click Add. To delete a selected field, click its trashcan icon.

To order the precedence of the fields, click the six-dot handle next to the field name and drag it to the
proper ordering position.
During an export, the system checks the first field in the list for text. If the field is null, it checks the next
field in order of precedence for text, and so on. When Relativity finds a field that contains text, it adds the
contents of that field to the Text Fields Precedence column in the document load file. Then continues
checking the fields for the next document and so on. For example, if you listed the Extracted Text field
first and the Production OCR field second, the system would first check the Extracted Text field for

Import/Export Guide 210


content, and if it was null, it would move on to the Production OCR field, and so on.

Note: If you have workflows that rely on clearing a text field for multiple production versions, you will
need to ensure that you clear this field using either Mass Replace or a load file that sets the values to
NULL. Operations such as Mass Edit will clear the field but set it to blank instead of null. This may res-
ult in exporting blank text files.
The Text Fields Precedence column displays the file path to the exported files if you select the Export
Text Field as Files checkbox above.
9. Click Continue.
10. On the Export Job Configuration Summary dialog, review the export job settings and go back to make any cor-
rections as needed.

11. (Optional) Click Save Settings on the Export Job Configuration Summary dialog to export the job configuration
settings entered thus far to its own profile file (.ie file extension). Save it on your computer so you can reuse
these settings when creating a new export job with Import/Export.

Note: Import/Export saves job configuration settings to its own profile file format, .ie file extension. Com-
paring to the legacy .kw* standard, it brings more flexibility as you now can apply saved job settings across
various workspaces. The .ie profile file format is not supported in other RelativityOne data transfer tools.

12. Click the Export button to start the exporting process.


13. When it's complete, the job summary lists the records exported successfully, including Load files containing
.mdb, .dat, opt, etc., errors found, and path to your exported files.
l If using Import/Export with Express Transfer active, the exported files automatically start to download.
You can track the download's progress in the Exporting dialog or in Express Transfer. For more inform-
ation, see Express Transfer Job tracking and history.

Import/Export Guide 211


Note: If you ran the job with Express Transfer active, you can close the Import/Export application while
the job is running. The transfer job will continue uninterrupted. You can monitor the progress and his-
tory of the job within Express Transfer. You do not have to be logged into RelativityOne to view inform-
ation within the Express Transfer application.

l If using Import/Export in web only mode, the application generates a zip file containing the exported data
that can be download. Click the Download button to save the exported data zip file to your computer, or
click the Close button to close the dialog without downloading the file.

Note: When downloading zip files to your computer, you can configure your browser to allow you save
the zip file to a custom file name of your choosing as well as to a specific folder destination instead of
using the default file name and destination. In the Settings menu of your browser, select Downloads.
Toggle on the option to ask where to save or what to do with each file before downloading. Now, when
you click the Download button in the Exporting dialog, your browser will display a dialog that allows
you to change the default zip file name and select a destination other than the default one. If needed,
you can also create a new folder in the chosen destination for the exported data.

l If you chose to Export to Staging Area when setting up your export job on the Export Settings dialog,
the application automatically exports data to your RelativityOne file share and skips the downloading pro-
cess. Go the path listed on the dialog to access the exported data files.
For more information on where Import/Export saves files, see the Community article, Import/Export: Where Files Are
Saved By The Import/Export Application.
You can always view the job's Exporting dialog information after it's closed by going to the Import/Export Job page and
clicking the job name link. The Job page also contains more details about all jobs.

Import/Export Guide 212


9 Import/Export Job tracking and history
The Import/Export Job page enables you to monitor the progress of jobs currently running, review previous jobs that
were executed, and view other pertinent job details at the workspace level.

Note: To monitor jobs at the instance level, see Import/Export queue on page 215.

9.1 Reviewing the Import/Export Job page


To access the page, use tabs, search, or the quick nav bar to navigate to the Import/Export Job page.

The following columns are displayed on the Import/Export Job page:

l Name—the name of the job. You can click this link to:
l Return to the data transfer progress dialog if the job is still in progress.
l View the data transfer summary if the job has completed.

Note: You may need to refresh the Import/Export Job page to see the job's current progress.

l Job Workflow
l Unprocessed—for imports of raw native files that require file processing.
l MsAccess Import—for imports of load file data in MS Access (.mdb) format.
l Transcript Import—for imports of transcript data in MS Access (.mdb) format.
l Document Import—for imports of document load files.
l Image Import—for imports of image load files.
l RDO Import—for imports of Relativity Dynamic Object (RDO) data.
l Production Import—for imports of production load files.
l Saved Search Export—for exports of saved search results.
l Folder Export—for exports of the contents of a folder.
l Production Export—for exports of production load files.
l RDO Export—for exports of Relativity Dynamic Object (RDO) data.
l Job Status—the current job status.
l General job statuses:
l New—a new job has been configured but has not been started.
l Uploading phase—data is being uploaded to RelativityOne. Statuses include: Uploading, Upload
Completed, Upload Failed, and Upload Canceled.

Import/Export Guide 213


l Extracting phase—uploaded data is being extracted. Statuses include: Extraction Requested,
Extraction Request Failed, Extracting, Extraction Failed, and Extraction Canceled.
l Transferring phase—Statuses include: Transfer Requested, Transfer Request Failed, Trans-
ferring, Transfer Failed, and Transfer Canceled
l Processing phase (only for unprocessed data import)—Statuses include: Processing
Request Failed and Processing Requested.
l Detailed job statuses:
l Import job statuses (for structured data import)—Import Job Canceled, Import Job Com-
pleted, Import Job Completed with Errors, Import Job Failed, Import Job Inserting, Import Job
Scheduled, Import Job Started, and Import Request Failed
l Processing job statuses (for unprocessed data import)—Discovery Not Started, Discovery in
Progress, Discovery Completed, Discovery Completed with Errors, Discovery Failed, Discovery
Canceled, Publish Not Started, Publish in Progress, Publish Completed, Publish Completed with
Errors, Publish Failed, and Publish Canceled.
l Export job statuses—Export Job Started, Export Job Request Failed, Export Job Scheduled,
Export Job in Progress, Export Job Completed, Export Job Completed with Errors, Export Job
Failed, Export Job Canceled, Download Read, Download Requested, Download in Progress,
Download Completed, Download Completed with Errors, Download Failed, and Download
Canceled.
l System Created by—the name of the user who started the job.
l Date Started Local—the local date and time when the job started.
l Date End Local—the local date and time when the job was completed.
l Identifier—displays the ID of the job.
You can extend the Import/Export Job view by creating your own view. Please refer to Creating a view for more
information.

9.2 Support for Mass Operations


The Import/Export Job page only supports the following Mass Operations:

l Delete—select the check box next to the desired Import/Export jobs that you want to delete from the Job list.
Then, choose Delete from the Mass Operations drop-down list at the bottom of the list. This action only
removes the job line item from the Job list. It does not remove the job data that was already uploaded to or
exported from your system. You will need to manually delete those files from your system.
l Export to a file—select the check box next to the desired Import/Export jobs in list to export the data in the cur-
rent view to a text file. Then, choose Export to File from the Mass Operations drop-down list at the bottom of
the list. The data currently displayed in the rows and columns of the Job list for the selected jobs will be expor-
ted. As you change the columns displayed, so will the data that is exported. If no individual records are selected,
Relativity will export all records in the current view, regardless of how many records are displayed per page.

Import/Export Guide 214


10 Import/Export queue
Import/Export Queue lists the current Import/Export jobs in progress and their status throughout the RelativityOne
instance. You can find the Import/Export Queue under the Queue Management tab.

Notes:
l Users who have been granted permissions to the Queue Management tab in the Tab Visibility section of the
Admin Security console automatically have access to the Import/Export Queue tab.
l To monitor jobs at the workspace level, see Import/Export Job tracking and history on page 213.

Note: Feature Permissions provide an alternative to Relativity's security management by shifting the focus from
Object Types and Tab Visibility to feature-based permissions. This method is simply another option; any feature-
specific permissions information already in this and other topics is still applicable. The Feature Permissions inter-
face enables administrators to manage permissions at the feature level, offering a more intuitive experience. By
viewing granular permissions associated with each feature, administrators can ensure comprehensive control, ulti-
mately reducing complexity and minimizing errors. For details see Instance-level permissions and Workspace-level
permissions.

The Import/Export Queue provides job information for the following fields:

l Job Name—the name of the job, as entered during creation. Click on the link to navigate to the Import/Export
job details.
l Job Status—the current state of the job, as represented by the following status values:
l Extraction Requested
l Extraction In Progress
l Extraction Completed
l Upload Requested
l Upload In Progress
l Upload Retried
l Upload Completed
l Import Job Requested

Import/Export Guide 215


l Import Job Idle
l Import Job Scheduled
l Import Job Inserting
l Processing Requested
l Discovery Not Started
l Discovery In Progress
l Discovery Completed
l Publish Not Started
l Publish In Progress
l Transfer Requested
l Transfer In Progress
l Transfer Completed
l Export Job Requested
l Export Job Scheduled
l Export Job In Progress
l Workspace—the workspace in which the job was created and run.
l Workflow Type—the type of import/export job, as represented by the following values:
l Unprocessed—job was initiated using the Raw (Unprocessed) Data workflow option within the Import
tab.
l Document Import—job was initiated using the Structured (Processed) Data workflow>Document option
within the Import tab.
l Image Import—job was initiated using the Structured (Processed) Data workflow>Image option within the
Import tab.
l Production Import—job was initiated using the Structured (Processed) Data workflow>Production option
within the Import tab.
l RDO Import—job was initiated using the Structured (Processed) Data workflow>RDO option within the
Import tab.
l Production Export—job was initiated using the Structured (Processed) Data workflow>Production Set
option within the Export tab.
l Saved Search Export—job was initiated using the Structured (Processed) Data workflow>Saved Search
option within the Export tab.
l Folder Export—job was initiated using the Structured (Processed) Data workflow>Folder option within
the Export tab.
l RDO Export—job was initiated using the Structured (Processed) Data workflow>RDO option within the
Export tab.
l Start Date—the date on which the job was started.
l Created By—the user who started the job.

Import/Export Guide 216


Proprietary Rights
This documentation (“Documentation”) and the software to which it relates (“Software”) belongs to Relativity ODA
LLC and/or Relativity’s third party software vendors. Relativity grants written license agreements which contain
restrictions. All parties accessing the Documentation or Software must: respect proprietary rights of Relativity and
third parties; comply with your organization’s license agreement, including but not limited to license restrictions on
use, copying, modifications, reverse engineering, and derivative products; and refrain from any misuse or
misappropriation of this Documentation or Software in whole or in part. The Software and Documentation is
protected by the Copyright Act of 1976, as amended, and the Software code is protected by the Illinois Trade
Secrets Act. Violations can involve substantial civil liabilities, exemplary damages, and criminal penalties,
including fines and possible imprisonment.
©2025. Relativity ODA LLC. All rights reserved. Relativity® is a registered trademark of Relativity ODA
LLC.

Import/Export Guide 217

You might also like