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 Clinical Basics.
Clinical Basics Overview
Watch this video to learn more about Veeva Clinical Basics: eTMF before you begin your Clinical migration.
We highly recommend taking our role-based Clinical training and using our Clinical 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 Clinical Basics involves:
Uploading your files (source documents, renditions, etc.) to the File Staging Server
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.
Understanding Which Template to Use
Veeva Clinical Basics offers two versions of the Document Template:
With TSC Map — Use this template if your legacy system has a formal document classification structure, such as a TMF filing structure. You will provide a mapping of your distinct legacy classifications to Veeva Basics classifications, and Veeva will use that mapping to classify your documents during migration.
Without TSC Map — Use this template if your legacy system does not have a formal document classification structure, such as documents stored in SharePoint or Box. You will classify documents directly into Veeva Basics classifications when filling out the template.
If you are unsure which template applies to your organization, refer to the Templates page or contact the Veeva Basics Migration Team using the Migration Communication Form and select Submit a Migration Question.
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 templates for you to easily migrate these core items:
| Documents | Clinical Data | Core Associations |
|---|---|---|
| Source | Organizations | Study to Country Association |
| Versions | Personnel | Study to Product Association |
| Renditions | Product | |
| Document Audit Trails | Site | |
| Study |
General Recommendations
Due to their complexity or less common use, Veeva does not recommend migrating the following:
| Item | Rationale |
|---|---|
| Document Links, Document Relationships & Binders | Due to their complexity, we do not recommend that you migrate Document Links, Document Relationships, or Binders. |
| Individual Document Attachments | Supplementary documents can be loaded as documents and then later related or attached manually after migration completion. |