Exporting/Migrating data

Exporting data

The purpose of this article is to provide as much information as possible to the person who needs to import a large batch of data, restore a list of records, or migrate information from one collection to another.

1. Items to export 

When the user enters the Export Data page, the user is greeted by a choice of the different elements to be exported. The user will then have to select the type of export that corresponds to his need before exporting the data. The user will also need to enter an export type for a data transfer or restore. These two types of exports are described in more detail in this documentation. 

1.1 Export classification plan, retention schedule, and administrative units

The purpose of this export is to export the following: Classification plan, retention schedule, administrative units, virtual spaces, and value domains. This export also provides the option to export security related to exported administrative units by checking the Include Permissions option. 

It is possible to remove items to be imported by removing the corresponding file in the generated zip file. 

To import the zip file, the user must drop the file into the Import Records page. 

1.2 Exporting records, documents, and containers

When this option is entered, the user can target precisely which folders, documents, and containers are to be exported. 

To import the generated file, the user must drop the file into the Import Records page. 

1.3 Exporting the contents of an administrative unit

When this option is entered, the user can target which administrative units are to be exported.

To import the generated file, the user must drop the file into the Import Records page. 

1.4 Export records by their old ID

This feature allows you to target the records to be exported using their old ID /id of their old management system. 

To import the generated file, the user must drop the file into the Import Records page.

1.5 Export schemas

This option allows you to export all metadata schemas in the system. It is also possible to limit the export to custom schemas and metadata. 

Unlike other exports, to import the generated file, the user must drop the file into the Import Configurations page. 

1.6 Other 

This option, checked by default, allows users to export environment savestates or logs. These files are used by the technical support team for anomaly resolution. 

Savestate

Savestates are used for the full replication of a server's metadata records, but they do not include binary content. This file is particularly requested during an anomaly declaration since it allows the technical support team to replicate the customer's server and replicate the submitted problem. Two different options are available for exporting a savestate, exporting the data, or exporting the tools. The first export, exporting data, covers the entire system, while the second relates only to the data structure (classification plan, retention schedule, administrative units). 

Logs

The logs contain information about the execution of the various tasks of the server. They are mainly used following the detection of a bug or a return to the reception since the cause of the incident is specified. 

2. Migrate information from a collection

It is possible to demerge a collection to move some of the information to another collection. To do this, specific export and import steps must be carried out. 

1. Ensure that they are in the original collection, where the information to be exported is located;
2. Go to the Export Data and Export Schemas page;
3. Still in the Export Data page, export the classification plan, retention schedule, and administrative units;
4. Still on the Export Data page, export the desired administrative units by checking the include permissions option if you want to copy security;
5. Create a new collection OR enter the collection or import the data must be done;
6. When you are located in the targeted collection for import, go to the Import Configurations page and import the file from step 2;
7. Go to the Import Records page, drop the step 3 file, enable Allow references to non-existent users and start importing;
8. Still on the Import Records page, drop the step 4 file, enable Allow references to non-existing users, and start importing.