# Migrating Legacy Data to QMS

With the need to preserve legacy archives from now-retired systems being a constant in Life Sciences systems, QMS has introduced a standardized way for customers and <a href="/en/gr/18300/">partners</a> to import, store and access legacy archive data.

## Supported Objects {#supported-objects}

QMS provides a set of objects to support legacy archive data:

  * _Legacy System_: Identifiers for each legacy system with content being brought to Vault.
  * _Legacy Process Record_: Houses the process data (CAPAs, findings, or others) from legacy systems.
  * _Legacy Process Artifact_: Houses artifacts associated with migrated process data (attachments, snapshots, audit trails, or others).
  * _Related Legacy Process Record_: Relates _Legacy Process Records_ to one another to provide additional context for process data.

These objects provide a standardized framework within which enables organizations to <a class="external-link " href="https://developer.veevavault.com/migration/#vault-migrations" target="_blank" rel="noopener">import migrated legacy data<i class="fa fa-external-link" aria-hidden="true"></i></a> in a uniform method. Lastly, the _Legacy Process Record_ and _Legacy Process Artifact_ objects have been optimized for high volumes of data, mitigating risks involved when considering very large volumes of legacy data from prior systems.

## Configuration Overview

We recommend configuring your Quality Vault to handle legacy data migration content in conjunction with a Veeva team or partner organization to handle tasks and issues like the identification of data to migrate, coordination of migration dry runs or production runs, or others.

The Quality model allows for a Vault to contain:

  * Data from many _Legacy Systems_.
  * Data from each _Legacy System_, expressed as zero (0) or more _Legacy Process Records_, each of which contains searchable, reportable legacy data.
  * Data from each _Legacy System's_ _Legacy Process Record_, expressed as zero (0) or more _Legacy Process Artifacts_, each of which contains any data or artifacts not represented by the data captured in _Legacy Process Record_.

This last level, the _Legacy Process Artifact_, may contain items like attachments, formatted prints of the legacy records, supporting materials for how to interpret the legacy data, or others.

### Auditing for Legacy Migration Objects

Because legacy data objects are intended to be imported and not altered, auditing is not enabled by default for record data changes. Admins can enable <a href="/en/gr/517/">Audit Trail</a> for the [supported objects][1] if any Vault users are expecting to change the data for imported records.

## Performing Legacy Data Migrations

The steps required to migrate data from a legacy system to QMS varies for each legacy system. The scope of this article does not include the execution of migration for your data, but is intended to guide you in understanding how Quality models legacy system data. You will be best served working with your <a href="/en/gr/18300/">Veeva partner or migration partner</a> to identify and guide you through all steps included in this process.

## Required Permissions

To manage legacy system data, a user requires, at a minimum, _Read_, _Create_, _Edit_, and (at the discretion of the project) _Delete_ permissions for the following objects:

  * _Legacy System_
  * _Legacy Process Record_
  * _Legacy Process Artifact_
  * _Related Legacy Process Record_

Once deployed to production, this migrated data is assumed to be at a steady-state, with no anticipated changes until the data's planned end of life. Therefore, it is common to restrict end-user, and even administrator rights to such data to _Read_ after production migration has occurred.

[1]: #supported-objects