> For the complete documentation index, see [llms.txt](https://docs.migration-center.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.migration-center.com/3.14/veeva-export-types-tool.md).

# Veeva Export Types Tool

## Introduction

The tool will display all the available types and after selecting one of them, all its editable fields will be shown and exported in a formatted CSV file. Moreover, the tool allows you to select multiple types and in this case, multiple formatted CSV files will be created containing all editable fields.

## Prerequisites

* Java SE 8

## Usage

By using this tool, you can export object or document type definitions from Veeva Vault into CSV files. Having the files already properly formatted, you can easily import them into the migration-center client to create the corresponding object types.  

### Steps for Exporting Type Definitions from Veeva Vault

Firstly, you have to authenticate into the Veeva Vault using your credentials.

* username
* password
* server
* API version 

{% hint style="warning" %}
The tool doesn't support proxy configuration!
{% endhint %}

![](https://2889039308-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LXwpM5nhZwVq8kDixeu%2F-MDEtcx4BsDO506zJLoz%2F-MDEv3FCZpN5GCzv776k%2FwrongApi.PNG?alt=media\&token=2a061137-b590-4208-93d1-d1a553db097e)

After successful authentication, all the object & document types will be displayed in the middle grid view. Subtypes and classifications will be loaded on request when you'll select a type from the list. By using the *Filter Table* text box, you can search for a specific type, subtype or classification and by using radio buttons *Object types* & *Document types,* you can pick which type have to be displayed.

In the next step, you can choose which type definitions to export as CSV, but as a constraint, you can select just leaves node from the hierarchy. When hovering a row in the grid, a tooltip with type *name\_\_v* value will be displayed.

![](https://2889039308-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LXwpM5nhZwVq8kDixeu%2F-MDF8Ofc16T11ByxALnw%2F-MDF9F-9guHOfAPCyaNj%2FselectionAndToolTip.png?alt=media\&token=c1be824d-07e5-43d2-a600-fd323bead7a1)

You have two options to export the selected types:

* one type at a time - it allows you to select specific fields for a type to export
* more types at a time - all the editable fields of the selected types will be automatically exported  

After the selection, the types will be exported as CSV files in the export location which has to be set in advance by you in the |Settings| tab. If the target folder wasn't previously selected, the tool location will be used as the default folder.

![](https://2889039308-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LXwpM5nhZwVq8kDixeu%2F-MDFB6QoHSyc6mEjLelQ%2F-MDFBVrtFkTzZMYDOD9S%2FexportFOlderPNG.PNG?alt=media\&token=3fa7c8e4-af8e-4497-85ec-cbe6611d7709)

The CSV files will have a similar format:

![](https://2889039308-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LXwpM5nhZwVq8kDixeu%2F-MDFCaYUVEdMa6K4T2p_%2F-MDFDehnYezFJdvH1tuZ%2FCSVFormat.PNG?alt=media\&token=13528edd-b212-4806-a221-e2ca18ef56f6)

### Import CSV Files into Migration-Center Client

You can import the created CSV files in migration-center client following the instructions of the chapter **Object Types Definitions** from the below guide.

{% content-ref url="/pages/-M7JN\_nlWl5ICX76HA86" %}
[Client User Guide](/3.14/client-user-guide.md)
{% endcontent-ref %}


---

# 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://docs.migration-center.com/3.14/veeva-export-types-tool.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.