# Migrate External Cases When you import external case data from a source E2B file, Vault generates an _Imported Case_ type of _Case_. _Imported Case_ types are reserved for previously processed and migrated _Cases_. Most _Case_ processing actions are permanently disabled on _Imported Cases_, including data auto-calculations. However, you can create and process a follow-up _Case_ from an _Imported Case_ and you can can generate the following reports with an _Imported Case_: * E2B * CIOMS I * FDA 3500A * Aggregate Reports (DSUR, PADER, PBRER, PSUR) ### Optional Configuration To support migrating Device and Combination Product Cases, your Admin can update the **Seriousness** picklist to include **Required Intervention to Prevent Permanent Impairment/Damage (Devices)**. See Enable Update to Seriousness Picklist for more information. ## E2B Case Migration If you have an E2B export of an external Case, you can import a Vault Safety Case directly from the E2B file. You can import a Case from both E2B(R2) and (R3) files. However, we strongly recommend that you use an E2B(R3) file when available. ### Enable E2B Case Migration Your Admin must configure a user action on the **AER** document lifecycle to allow the **Create Imported Case from E2B** action. Defining User Actions for Document States provides more information. ### Migrate a Case from an E2B File Once your Admin has enabled E2B Case migration, you can migrate E2B Cases.
1. Go to the **Library** tab. 2. From the menu bar, select **Create**. The **Create Document** window appears. If you do not see the **Create** button, you do not have permission to upload documents. 3. On the **Create Document** window, select **Upload > Continue**. 4. On the **Upload Files (Step 1)** page, drag and drop the E2B file into the blue area or select **Choose** to browse for the files on your device. 5. Select **Classify documents now**, and then under **Choose document type** select **Case › Source › Adverse Event Report**. 6. Select **Next**. 7. On the **Upload Files (Step 2)** page, select the **Organization**. 8. Select **Save**. 9. Expand the **All Actions** menu, and then select **Create Imported Case from E2B**. This option may have a different label, depending on how your Admin configured the User Action. **Result** Vault creates an Imported Case from the E2B file and maps the Study and Product to appropriate records in the Vault Safety **Business admin > Objects** library, if they are available. Inbox Item Study and Product Matching provides more information. ## (Non-E2B) Vault Loader Migration {#loader} As an alternative to migrating cases from E2B, you can use Vault Loader to bulk migrate _Imported Cases_. Contact your Veeva Representative for assistance with importing _Cases_ using Vault Loader. If you import _Cases_ from an external safety system that does not use versioning, you can utilize the _Imported Follow Up Information_ type of _Case_ to support the migration of follow-up information. This allows for tracking of follow-up dates, such as _New Info Dates_, or other relevant information without having to include placeholder _Case_ data.
## Index Migrated Cases for Search In 23R1, the **Indexing of New Migrated Cases for Duplicate Search** feature was introduced. This enables Admins to initiate indexing of newly migrated Cases to include them in duplicate detection when Case Processors are promoting Inbox Items to Cases. To begin indexing, your Admin must enable the _Index Migrated Cases_ setting. If more Cases are migrated into Vault, your Admin can select the checkbox again to index them. If any migrated Cases were unable to be indexed (for example, due to errors), Vault leaves the checkbox enabled. Contact Veeva Support for assistance.