# Creating Document Versions Using Vault Loader
When using Vault Loader, the **Document Versions** selection lets you upload additional versions (including files) and associate them with existing documents.
Note: This is only available when you select the Document Migration Mode checkbox. You can select No Triggers to bypass record triggers in Document Migration Mode.
## How to Load Document Versions {#loading-documents}
Before loading document versions:
* Upload all document source files to file staging.
* [Prepare the CSV input file][1] containing document field names and values.
To load document versions:
1. In the left panel of the **Loader** tab, click **Load**.
2. For the **CSV File**, click **Choose** and select the CSV input file.
3. In the **Entity Type** picklist, select **Document Versions**.
4. In the **Action Type** picklist, select **Create**.
5. Click **Start Load**.
Vault begins processing the request. When finished, you'll receive a Vault notification and email with request details and CSV output files.
## Past Versions as Content Placeholders
If the latest version of a document includes a source file, you cannot create a past version without a source file (as a content placeholder).
## Preparing the CSV Input File {#preparing-the-csv-input-file}
The CSV input file must include the following column headers and corresponding values:
* `id`
* `type__v`
* `subtype__v`
* `classification__v`
* `major_version_number__v`
* `minor_version_number__v`
* `lifecycle__v`
* `status__v`: Specifies the lifecycle state for the document version using the name value, for example, `in_review__c` for _In Review_.
* `external_id__v`: Optionally, you can choose to omit the id column and identify documents by external id. If both `id` and `external_id__v` are included in your CSV, the load fails.
Download example input.
You can find further explanations in Create & Update Documents.
[1]: #preparing-the-csv-input-file