Accelerate the Value of Data

Export data using Reltio export service

Learn about the essentials of exporting your data from Reltio Multidomain MDM.

Overview of exporting data

Reltio Multidomain MDM makes exporting data efficient, precise, and secure so you can:
  • Use the data in analysis and metrics reporting.
  • Make the data available in CRM (customer relationship management) or similar platforms.
  • Export the data into an ETL (export, transform, load) and move the data into other systems.

The diagram below shows how our platform handles export requests.

The flow of export requests in Reltio Multidomain MDM

Export features in Reltio Multidomain MDM and how you can use them.

What kind of data can I export?

You can export the following kinds of data:
  • Entities
  • Relations
  • Activity Log Data
  • Merge Tree Data

What permissions do I need to export data?

Reltio Multidomain MDM defines permissions by the scope of data you can access. Your access to export is the same as your Reltio Server access.

What are the ways I can export data?

You can export data from Reltio Multidomain MDM in two ways:
  • Using the Export application in Console (user interface) to create an export job.
  • Making requests directly through an API.

How do I create and execute an export job with the export UI?

Use the Export application in Console to create an execute an export job. For more information, see Create and run an export job and Export entities and relationships.

What compression file types does export support?

A file compression format determines how files are compressed. The default compression format, for exported data files, is GZIP. These compression formats are available:
FormatFile extensionDescription
GZIP.gz Compresses a single file. Has a better compression ratio for individual files.
ZIP.zipCompresses multiple files and directories into one archive, including metadata such as file paths, dates, and attributes.

What is the file-naming convention for exported data files?

By default, output export file names are built by the next template - part_<part-number>, where <part-number> indicates the number of the part of the generated output file. The numbering starts from zero.

For example, if entities/testName is the custom path parameter for the export files destination, then the output file is named as entities/testName/part_00001.csv.gz.

If five output files are generated, then they are named as
  • entities/testName/part_00000.csv.gz
  • entities/testName/part_00001.csv.gz
  • entities/testName/part_00002.csv.gz
  • entities/testName/part_00003.csv.gz
  • entities/testName/part_00004.csv.gz
Note: Every output file name is unique.