Medical Documents Migration

Last updated: Apr 28, 2026

Before You Begin

The Veeva Basics Migration Center is designed to help you be self-sufficient and successful in all steps of your migration.

Carefully review the provided instructions and videos to understand your responsibilities and the activities involved in migrating from your legacy system into Veeva Medical Basics.

We recommend reviewing the Migration FAQ for commonly asked questions and answers before beginning your migration.

Medical Basics Overview

Watch this video to learn more about Veeva Medical Basics before you begin your Medical migration.

We highly recommend taking our role-based Medical training and using our Medical help to understand more about the system, fields on documents, object data, etc. These resources can help you as you fill out your migration templates.

Preparing for Your Migration

Before you begin your migration activities:

  • Review and identify the content and metadata to be migrated

  • Determine which data will be migrated and which will be created manually in Vault

    Note The maximum number of document versions/objects we will help migrate is 100,000. In cases where the volume of documents/objects is below 20, Veeva recommends creating those manually.

Migrating from your legacy system into Veeva Medical Basics involves:

  • Uploading your files (source documents) to File Staging

  • Filling out the migration template(s)

Throughout the migration process, customers are responsible for producing any required migration documentation. This may include a Migration Plan, typically drafted following Sandbox migration, and a Migration Summary Report, typically drafted following Production migration.

Veeva will provide a Migration Inventory, loader sheets, and log files upon Production completion to support your documentation.

Best Practices

Templates Provided

We have designed streamlined templates to help you migrate your core data.

Our migration templates can be filled out quickly, help ensure data entry is accurate, and get you up and running with Veeva Basics.

Veeva provides a template for you to easily migrate your source documents.

Note About Document Versions

  • Each document version requires its own row in the migration template. See the example below.

    Screenshot of filled out template

General Recommendations

Due to their complexity or less common use, Veeva does not recommend migrating the following:

ItemRationale
Document Links, Document Relationships, Revisions, Renditions, & BindersDue to their complexity, we do not recommend that you migrate Document Links, Document Relationships, or Binders.
Individual Documents AttachmentsSupplementary documents can be loaded as documents and then later related or attached manually after migration completion.