# Import & export

Note: The features below are intended to primarily function with the [Violet Requirements module](https://docs.violetlabs.com/features/requirements). If you intend to continue utilizing your existing requirements tool (e.g., DOORs, Jama, Valispace, etc.), you should establish an [Integration](https://docs.violetlabs.com/integrations#requirements--mbse) between your tool and Violet to enable synchronization of changes.

### Importing requirements

First, you'll need create a [Program](https://docs.violetlabs.com/features/programs) for your requirements. Navigate to that program's requirements page, then import data by uploading a .csv file.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FEnLtYoKPVvaJRtkYRI1Y%2FRequirementsCSV.png?alt=media&#x26;token=e5df64c4-8369-4782-8659-289b9daa828b" alt="" width="563"><figcaption></figcaption></figure>

#### Mapping CSV Columns to Requirement Attributes

When importing requirements from a .csv file, you will be able to map attributes of your existing requirements to the fields used in Violet Requirements. The most common ones are:

* Requirement ID
* Name
* External URL (to aid in navigating back to an external requirements tool, e.g.)
* Requirement Statement
* Requirement Approval Status
* Verification Method(s) (comma separated)
* [systems](https://docs.violetlabs.com/features/requirements/systems "mention") (comma separated)
  * Note: Systems will be created for you automatically as part of the import process. You can then manage, edit and nest them within the corresponding Program page.
* Owner(s)
* Approver(s)

If you wish to include additional attributes, you can optionally configure them prior to performing the import process (see [custom-fields](https://docs.violetlabs.com/features/requirements/custom-fields "mention")). Or, Violet will automatically create new custom attributes for any unmapped columns for you.

#### Configuring Parent/Child Hierarchy for Import

Violet supports two approaches for capturing parent/child relationships between requirements during import: via **Parent ID** or **Hierarchy Levels**.

Your CSV file can be configured to support one of these options:

1. **Parent ID:** Include a **Parent** column in your sheet that indicates either:
   1. the `Requirement ID` of the parent requirement (exactly as it is listed elsewhere on the same CSV), or
   2. a delimited list of the `Row IDs` of the parent requirements (e.g., ROW-1, ROW-2)
2. **Level:** Include a `Level` column with a delimiter indicating hierarchical levels (e.g. 1.2.1).

We recommend consolidating all requirements into one CSV for import.

### Exporting requirements

Violet Requirements can be exported to Excel or CSV as tables, or to a Word document. The export process is conducted from Violet's Tabular View.

1. **Configure Requirements Attributes to Include in Export**
   * In the tabular view, show the columns you wish to include in the exported view and hide the columns you do not want to export.
2. **Select Requirements to Export**
   * Use the checkboxes to select one or more requirements from the current view to include in the export (or select the top-most checkbox to select everything).
3. **Initiate Export**&#x20;
   * Select the **Export Requirements** button located on the main toolbar to export to .csv, Excel or Word.
   * Alternatively, to export to CSV or Excel,  you can right click on the requirements and choose "Export" or "Export Selected Rows." You will not have the ability to able to customize the filename or add a timestamp before downloading using this method.
4. **Edit Exported File Name and Choose Format** In the **Export Requirements** window:
   * Set a filename for your export. Use the check box to add a timestamp to the filename.&#x20;
   * Use the dropdown arrow to choose a file format from the dropdown: `.csv`, `.xlsx`, or `.docx`.
5. **Customize .docx Export (Optional)**&#x20;

   1. If exporting to `.docx`, you can choose to include Cover Page, Table of Contents, Header and Footer, Link to the Violet Requirement&#x20;

   *Note: Only individual requirement attributes will be included in the document. Parent folders are excluded.*&#x20;
6. Click **Export** to begin downloading the file.

<p align="center"> <img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FC9qtl4jayjz0G6Fnnbkv%2Fimage.png?alt=media&#x26;token=b548b908-f245-4e3e-9ef1-a0366abc0863" alt="" data-size="original"></p>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.violetlabs.com/features/requirements/import-and-export.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.