Vault Domain Moves
In certain situations, your organization may need to move your vault or vaults to a different domain. Examples of when this may become necessary include rebranding, management changes, business consolidation, or moving to a different clinical research organization.
Vault Reparenting allows Veeva to move a vault from one domain to another. Once reparenting is completed, the vault is usable by customers in the new domain. This process is in three phases:
- Veeva moves the vault from the source domain to the target domain.
- Veeva Operations runs a utility to recreate users in the target domain and reassign content, data, and work to those users. See below for a more complete list of what’s moved.
- Veeva Services prepares and tests the new vault for the customer.
Aside from the organization of vaults, your domain also controls the domain portion of your user name (user.name@domain.com). You can learn more about domains in the Vault Platform documentation here.
Requesting a Domain Move
Contact your Veeva Services representative to initiate a domain move.
What is Moved
In addition to your vault’s configuration (exceptions listed below and all study data and configuration (design and execution), a domain move includes the following user references:
- Enrollment Completion
- Learning System Users
- Role Assignments
- Email Group Assignments
What Isn’t Moved
Domain reparenting doesn’t move any user references contained in the following:
- Audit trails (entries will still exist but will reference the original user values)
- Job configurations
- FTP configurations
- Data and metadata references to users
- Signaturesvault
- Reviews
- Any other non-functional user references
- Any “Modified By” or “Created By” references on object records