> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/ropa/export-import.md).

# Export / import the record

Learn how to export and import a complete existing record into Dastra.

## Record export

To export the entire record, open the record of processing activities, click the arrow on the right of the **Create data processing** button, then select **Export**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f397b90318380f83db65017a7574bc0a0f7c3fb2%2Fropa-export-import-1.png?alt=media" alt="Create data processing menu with the Export entry"><figcaption><p>Record drop-down menu with the export feature</p></figcaption></figure>

In the window that opens, **Choose an export format**: PDF, Word, HTML, CSV, Excel, JSON or Markdown. For PDF, Word and HTML, also **Choose an export type** (**Complete**, **Article 30 GDPR**, **Standard information notice** or **Data retention policy**). Then click **Download file**. Your record is exported.

Depending on the format, additional options are available, for example:

* **Group by areas** (PDF, Word, HTML), to group the processing activities by organizational unit
* **Export Progress, quality and sensitivity indicators** and **Export associated tasks** (PDF and HTML, Complete type)
* **Complex table (Multi-sheets)** (Excel)
* **Use native column names or reports (recommended for importing data)** and **Export custom fields**, which lets you choose the columns to export (CSV and Excel)
* **Export for customer/data controller**, to produce an export for one of your clients only, without the other clients' data

PDF, Word and HTML exports include up to 500 processing activities, and CSV, Excel, JSON and Markdown exports up to 10,000. A warning appears in the window if your selection is larger.

For a large record, the JSON export is prepared in the background: you can keep working, a notification keeps you informed of its progress and the file downloads as soon as it is ready.

### Article 30 GDPR format

The Article 30 GDPR format corresponds to what the GDPR requires: the export only contains the fields that Article 30 makes mandatory in the record of processing activities. The information contained is:

* Name of the processing activity, and the identity of the controller (or processor), its representative and its DPO
* Purposes (without legal basis)
* Categories of data subjects and of personal data, and retention periods
* Recipients and possible transfers outside the EU
* Security measures

### Complete format

The complete format is the native Dastra format: you export all the fields that make up the processing activity. In the PDF, Word and HTML exports, the data subject rights section lists only the rights that are filled in the processing activity. When none is filled in, the section is left out.

{% hint style="info" %}
You can also export only one or several processing activities of the record, instead of the whole record. To do this, tick the boxes on the left of the processing activities concerned, then click **Select a batch action** and **Export**. To export a single processing activity, you can also use **Export** in the menu at the end of its row.
{% endhint %}

## Record import

Click the arrow on the right of the **Create data processing** button, then select **Import**. The **Import data processings** window offers three formats:

* **Complex excel workbook**: import your processing activities from an Excel workbook made up of several sheets (Beta)
* **CSV**: import your processing activities from a CSV file
* **JSON**: import processing activities previously exported from Dastra in JSON format, for example from another workspace

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e86fcbe9b5ef3a490ebb2711d657bb49ac1fdca7%2Fropa-export-import-2.png?alt=media" alt="Import data processings window with the Complex excel workbook, CSV and JSON options"><figcaption><p>Choosing the import format</p></figcaption></figure>

### Import with the complex Excel workbook

Importing an existing record can be tedious if you have many processing activities. The complex Excel workbook lets you import your processing activities in bulk, in one go. Dastra recognizes the data in the workbook to create the processing activities and the associated repositories.

1. Choose **Complex excel workbook**.
2. Click **Download the file template** and fill it in with your data.
3. Select the **Organizational unit** in which the processing activities will be created.
4. Drop your completed file to start the import.

{% hint style="info" %}
No organizational unit is created during the import. Data from fields that are not part of the template is placed in the HTML description fields.
{% endhint %}

When the recipient category of a row is empty, Dastra imports the recipient with the **Other** category.

The data fields sheet of the workbook has a **Remarks** column: it carries the remarks entered for each data field of a dataset, as in the **Remarks** field of the dataset. The export fills it and the import reads it, up to 1,000 characters per remark. A workbook exported before this column existed can still be imported.

### Import a JSON file

The JSON format is the one of the **JSON** export of the record. It carries complete processing activities, which makes it the format to copy activities from one workspace to another. Choose **JSON**, select the **Organizational unit** in which the processing activities will be created, then drop the file. The window then lists the processing activities created and the items that already existed.

The file has the structure of the export: `$schema`, `version`, `date`, `label`, `source` and a `records` array, with one processing activity per entry.

What the import accepts:

* a file exported from Dastra with the version `1.4`. Another version is refused with the message "Incorrect version of your JSON import file (required version : 1.4)";
* all the content of an entry: the general information, the purposes, the datasets and their retention rules, the assets, the recipients and stakeholders, the categories of data subjects, the security measures, the tags and the custom fields;
* an entry with the same label as an existing processing activity: it creates a new one, it never overwrites;
* the stakeholders, assets, datasets, categories of data subjects, security measures and tags of an entry: when an item with the same name already exists in the workspace, Dastra reuses it, otherwise it creates it;
* the owners of an entry, when they are users of the organization. The others are skipped.

What the import ignores or resets:

* the identifiers: every processing activity gets a new one;
* the organizational unit of the file: all the activities go to the unit you selected;
* the status and the workflow step: the activities are created as drafts, on the first step of the workflow;
* the creator, the creation date and the review dates: the creator is the person who imports, and the dates start again;
* the risk level and the scores: Dastra calculates them again;
* the relationships between processing activities (parent, child, related).

Each entry is checked before anything is created. If one entry is invalid, for example a required field is empty, the import stops with the message "Error on data processing" followed by its label and its line number, and nothing is created.

The import requires the permission to import processing activities.

### Standard import, step by step

To avoid filling in each processing activity by hand and to handle every possible record format, Dastra has designed a methodology based on the principle of **splitting the record into data domains**. Thus, 7 steps are recommended to import an entire existing record into Dastra.

{% hint style="info" %}
These steps, which are not mandatory, are nevertheless strongly recommended, especially when the record contains many processing activities.
{% endhint %}

See our library of data processing templates: <https://www.dastra.eu/en/data-processing/referentials>

The import page works the same way for every step. It is described in detail in [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md).

### Step 1: Import of processing activity labels

To import your existing processing activity labels, click the arrow on the right of **Create data processing**, select **Import**, then choose **CSV**. The **Data import** page opens.

Click **Download the file template** to get a sample file, and **View columns format** to see the list of expected columns, their rules and their possible values.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-9b213968bf64c384710e1dd2a789c97c614102a5%2Fropa-export-import-3.png?alt=media" alt="Data import page with the Download the file template and View columns format buttons"><figcaption><p>Downloading the file template</p></figcaption></figure>

Fill in the file with your processing activities. The main columns are:

| Column           | Description                                  | Possible values                                     |
| ---------------- | -------------------------------------------- | --------------------------------------------------- |
| Label            | Name of the processing activity (required)   |                                                     |
| Ref              | Internal reference                           |                                                     |
| Processing state | State of the processing activity             | "Study", "BeingDeployed", "InProduction", "Stopped" |
| Description      | Short description of the processing activity |                                                     |

Select the **Organizational unit**, then drop your file:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-40716740bec650e4a9fda98cee7c1cfee99f2a79%2Fropa-export-import-4.png?alt=media" alt="Organizational unit selection and file upload area on the Data import page"><figcaption><p>Choosing the organizational unit before uploading the file</p></figcaption></figure>

Match the columns of your file with the Dastra fields in the **Columns mapping** step, then click **Continue** to run the import.

Your processing activity labels are imported.

### Step 2: Import of the asset repository

To import your existing applications and assets, go to the **Repositories** module, **Assets** tab, click the arrow on the right of **Add an asset**, then select **Import**:

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-38628ce75e8c1fcc1ee5990e50847b2e3341b3d1%2Fropa-export-import-5.png?alt=media" alt="Add an asset menu with the Import entry in the Assets repository"><figcaption><p>Importing assets</p></figcaption></figure>

Then download the file template, fill it in with your assets (use **View columns format** for the list of columns) and import it as in step 1.

Your assets are imported.

### Step 3: Import of the stakeholders repository

Repeat the same procedure from the **Repositories** module, **Stakeholders** tab.

Your stakeholders repository lists all the parties involved in a processing activity: legal entities such as processors, clients or joint controllers, or natural persons such as the contact persons for a processing activity.

This repository serves as an internal directory for the workspace. For each stakeholder, you can define a type that characterizes it. For example, if you want to add your processors, you add them all as stakeholders and then associate each processor with the processing activities concerned.

### Step 4: Import of the security measures repository

Repeat the same procedure from the **Repositories** module, **Measures** tab.

### Step 5: Import of the data glossary

Repeat the same procedure from the **Repositories** module, **Data glossary** tab.

### Step 6: Import of the datasets repository

Repeat the same procedure from the **Repositories** module, **Datasets** tab.

#### Export / import datasets with their data fields

You can export and import your datasets **including their associated data fields**. This makes it easier to migrate an existing data map or to update your data glossary in bulk.

**Exporting datasets with their fields**

From the **Repositories** module, **Datasets** tab:

1. Select the datasets to export, or export the full list
2. Click **Export**
3. Choose the CSV or Excel format and click **Download file**

The exported file includes, for each dataset, its name, description, retention rule and the list of its data fields. In this column, each data field is written as `name#sensitivity#category`, and the data fields are separated by `|`. Turn on **Use native column names or reports (recommended for importing data)** if you plan to re-import the file.

**Importing datasets with their fields**

The import file follows the same format as the export. For each dataset, fill in its data fields in the dedicated column, for example `Last name#Current#CivilStatus|Salary#HighlyPersonalNature#EconomicFinancialData`. During import:

* Data fields that do not yet exist in the data glossary are **created automatically**
* Data fields already present (same name) are **associated** with the dataset without duplication

{% hint style="info" %}
This feature is particularly useful for harmonizing the data map between multiple workspaces, or for initialising a new workspace from an existing data map.
{% endhint %}

### Step 7: Construction of links

Now that all the repositories have been imported, edit each processing activity and fill in its information based on the imported data, following the guide below:

{% content-ref url="/pages/-LvMDW-VMCrzSDNt2PC8" %}
[Complete a data processing activity](https://doc.dastra.eu/en/features/ropa/activity.md)
{% endcontent-ref %}

The links are built.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.dastra.eu/en/features/ropa/export-import.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
