Migrating Data to Veeva Submissions Publishing

The primary use case for a Veeva Publishing migration is a legacy migration. Rather than migrating directly into Veeva Publishing, Publishing data should be included in the Veeva Submissions Archive migration. This guide covers the most common aspects to consider regarding migrating data into a Publishing Vault.

The RIM product model offers some flexibility with how data is modelled or there are certain core RIM objects which are typically populated, which are used by the application and any associated document. For Veeva Publishing customers, these objects consist of the same core product hierarchy and application objects as when migrating Submissions data.

In addition, when using Veeva Publishing the following object should also be considered for Switzerland Submissions:

Submission Pharmaceutical Forms

Considerations

The same considerations as with Submissions apply to Submissions Publishing.

Enriching Existing Data

Certain metadata dictates how the submission is published, therefore it is necessary to populate the required fields. While not an exclusive list this includes elements such as:

Organization’s Type and DUNS Number
Clinical Study’s Type and Subtype (this is also applicable for Nonclinical)
Content Plan Item’s Continuous Publishing and Continuous Validation
Submission’ Continuous Publishing settings
Region, Countries and Languages
Controlled Vocabulary and Constraint publishing settings
Application and Submission relationships
Application Folder Name, XML Number, and Health Authority Division values

In-flight Submissions

If there are in-flight submissions, pay extra attention to missing or incorrect folder paths,file names, XML, and other fields on the CP and CPI templates.

We recommend completing in-flight submissions prior to publishing go-live. Consider recreating content plans once the Content Plan and Content Plans Items have been enriched.

Documents

Document types often change per release. If creating new Content Plan and Content Plans Items from the publishing templates, make sure the taxonomy in your Vault reflects the latest.

Ensure existing approved documents have Ready for Publishing set to Yes if they are ready for publishing.