Migrate External Cases

You can migrate external cases from an E2B file to the Imported Case object type, where case processing features are disabled.

About Imported Cases

When you import a Case using E2B Case Migration, the resulting Case is an Imported Case.

An Imported Case is a special type of Case, which is 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.

The following table summarizes which reports you can generate with an Imported Case:

Report Format Support for Imported Case?
E2B Yes
FDA 3500A Yes
Aggregate Reports (DSUR, PADER, PBRER, PSUR) Yes

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. Define 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.

Note We recommend that you contact Veeva Managed Services for assistance with migrating Cases from E2B files.

  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 (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.


The system 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

As an alternative to migrating cases from E2B, you can use Vault Loader to bulk migrate Imported Cases. Vault Online Help provides instructions on using Vault Loader to migrate records. Contact Veeva Managed Services for assistance with importing Cases using Vault Loader.

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 select the Index Migrated Cases checkbox. Once the migrated Cases are successfully indexed for duplicate detection, the system clears the Index Migrated Cases checkbox. If more Cases are migrated into the system, your Admin can select the checkbox again to index them.

If any migrated Cases were unable to be indexed (for example, due to errors), the system leaves the checkbox enabled. Contact Veeva Support for assistance.

Manage Safety Inbox Loader Multi-Case CSV Data Import
Configure Company Product Match Verification