# Document Migration Mode
Document Migration Mode allows you to easily migrate large numbers of documents by relaxing some constraints that Vault typically enforces. For example, you can create documents in any lifecycle state and manually set the name, document number, and version number in your CSV input file.
You can apply Document Migration Mode to new documents that you create or existing documents that you update using the Vault API, Vault Loader, or the Vault Loader Command Line Tool. All other documents will continue to operate as usual. You must have the _Vault Owner Actions: Document Migration_ permission to apply migration mode using these options.
Note: Document Migration Mode is separate from Configuration Mode and has different functionality.
When Document Migration Mode is enabled, Vault allows you to set or edit values for fields that are normally not editable when creating and updating documents.
| Action | Fields Where Constraints are Bypassed | Notes |
| --- | --- | --- |
| Create Documents | `name__v` `major_version_number__v` `minor_version_number__v` `document_number__v status__v` | When setting major or minor version numbers with the _Create Documents_ action, the fields must have a security override. |
| Update Documents | `document_number__v` | You cannot set major or minor version numbers with the _Update Documents_ action. |
| Create Document Versions | `name__v` `major_version_number__v` `minor_version_number__v` `status__v` | When setting major or minor version numbers with the _Create Document Versions_ action, the fields must have a security override. |
| Update Document Versions | `document_number__v` | You cannot set major or minor version numbers with the _Update Document Versions_ action. |
| Add Document Renditions | `major_version_number__v` `minor_version_number__v` `rendition_type__v` | You must apply _Document Migration Mode_ when adding renditions. |
## How to Use Document Migration Mode
### Documents API
The Vault API's Create Multiple Documents, Create Multiple Document Versions, Update Multiple Documents, and Add Multiple Document Renditions endpoints allow the `X-VaultAPI-MigrationMode` header, which applies Document Migration Mode to any document created or updated in that request.
Set the `X-VaultAPI-NoTriggers` header to true to bypass triggers when Document Migration Mode is enabled. Before using this parameter, learn more about [bypassing triggers][0].
### Vault Loader API
Use the Vault API's Load Data Objects endpoint and set the `documentmigrationmode` parameter to `true`.
To also bypass record triggers, set the `notriggers` parameter to `true`. Before using this parameter, learn more about [bypassing triggers][0].
### Vault Loader UI
When creating or updating documents in bulk with Vault Loader, select the **Document Migration Mode** checkbox to apply migration mode. You can only select the checkbox if the _Entity Type_ is _Documents_, _Document Renditions_, _Document Versions_, _Document Relationships_, or _Documents, Versions, Roles_.
The _No Triggers_ option allows you to bypass record triggers. Before using this parameter, learn more about [bypassing triggers][0].
### Vault Loader CLI
Use the `-documentmigrationmode` parameter in the Vault Loader Command Line tool.
To also bypass record triggers, use the `-notriggers` parameter. Before using this parameter, learn more about [bypassing triggers][0].
## Limitations of Document Migration Mode
When you create or update documents via an API call or Vault Loader import where you apply Document Migration Mode, some Vault functions are limited and may require an additional step after the upload is complete. The following limitations apply only to the documents created or updated with Document Migration Mode applied:
|Limitation|After creating or updating documents|
|--- |--- |
|Disables automatic application of Legal Hold on documents|Re-apply Legal Hold to the intended documents|
|Disables video file rendering|Manually re-render the affected video files|
|Disables continuous EDL matching to documents|Re-apply EDL matching to the affected documents|
|Disables controlled document template creation when using the Create Multiple Document Versions API or Vault Loader: Add Document Versions.|Controlled document template creation returns to normal.|
|In Sandbox Vaults only: Disables indexing for full-text search of documents that are migrated with the `X-VaultAPI-MigrationMode` API header.|Full-text search of documents returns to normal|
|In Sandbox Vaults only: OCR indexing is disabled for documents created with the `X-VaultAPI-MigrationMode` API header.|OCR indexing of documents returns to normal|
|Vault does not execute Event Actions for documents uploaded via API or Vault Loader.|Event Action execution returns to normal.|
|Vault does not change the document lifecycle when updating documents using Vault Loader.|Reclassify the documents, which updates their lifecycle accordingly.|
|Vault may create document versions out of order when migrating documents. For example, version 0.2 may be created before version 0.1.|No additional action required.|
|Vault only sends users a notification containing the success and failure logs when a _Create_ or _Update_ document action completes with Document Migration Mode enabled. No other notification types are sent.|No additional action required.|
## About Bypassing Triggers {#about-bypassing-triggers}
When using Document Migration Mode with Vault API, Vault Loader, or Vault Loader CLI, you can optionally configure Vault to skip all trigger execution. This includes custom Vault Java SDK triggers, Action Triggers, standard triggers, and system triggers which work to deliver various Vault functionality.
Because standard and system triggers are generally expected to run, bypassing these triggers may have unexpected consequences. As a best practice, always run your document migration in a sandbox Vault and test for expected functionality before running in production.
_Document Relationships_ do not allow bypassing triggers.
[0]: #about-bypassing-triggers