# Importing & Exporting Design Data

If configured by a Vault admin, Design Data Admins can use the Design Data Portability feature to import and export Veeva LIMS Design Data. This allows you to easily move *Spec Data* records between Vaults for testing or other business needs.

## Exporting Design Data

To export a Design Data record, navigate to its *Record Details* page and select **All Actions > Export [Object Name]**. Veeva LIMS performs the export asynchronously and notifies you when it is ready. Click the file name in the notification to download the export.

### Limitations

The following limitations apply to exporting Design Data:

* You cannot export the following fields and field types:
    * Custom object references
    * Lookup fields
    * Formula fields
    * `locked__v`
    * `prior_version__v`
    * Effective Start Date
    * Effective End Date
    * System_sys fields
* You cannot export cancelled Design Data records.
* You cannot export draft Design Data records.
* You cannot export Design Data records currently in an approval workflow.

## Importing Design Data

To import Design Data in your target Vault, navigate to the *Design Data Loader* tab and do the following:

1. Click **Choose** to select a file. Only ZIP files may be imported.
2. Click **Start Load**.

Veeva LIMS performs the import asynchronously and notifies you when it is complete. You can download a CSV file containing a log of all operations performed.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: You cannot import Design Data files that were not generated by Vault or that exceed 1GB in size.</p>
    </div>
  </div>
</div>



## Creating a New Version on Import

When importing Design Data, the system automatically assesses whether a new version should be created or a new standalone record is required.

A new version will be created in the *Draft* state if:

* A Design Data record exists in the target Vault with the same *Trace ID.*
* The existing record is in an approved state and not in a pending approval workflow.