Setting up a CRM Sandbox Org

These steps are required to support specialized functionality provided within the Veeva CRM application that is not automatically provided as part of the Sandbox creation process.

These steps are not required for full sandboxes.

Configuring a CRM Sandbox Org

To configure the sandbox:

  1. Request a Sandbox organization to create.
  2. Log-in as an Administrator to the Veeva CRM Application.
  3. Select Data Management from the Administration Setup.
  4. Select Sandbox
  5. Click New Sandbox and provide all appropriate information.
  6. Receive confirmation of the Sandbox creation.
  7. Export the values utilizing the DataLoader from the Message_vod object within the Production Veeva CRM org.
  8. Import the data from Step 7, into the newly created Sandbox org from Step 1 utilizing the DataLoader.

The Message_vod records (and VMOCs, Countries, and Views) are not copied over to the Sandbox org. The easiest way to identify this issue is to look at the Best Times control on the Address object layout. It displays “undefined” if the Message_vod data is not properly populated. To rectify this problem, export all the data for all columns from the Veeva Messages object using Reports. Then, using the data loader, load these records into the sandbox.

To access Engage functionality, admins must also link the sandbox org to the Engage Sandbox.

Veeva Managed Orgs

Veeva manages many Sandbox and Production orgs for customers as part of the standard upgrade and release process for Veeva CRM. Each of these orgs is automatically upgraded by Veeva for each release. This includes the Veeva CRM application, and any content and reporting data the customer is using with that org.

Any customer org, including Sandbox, QA, or Dev, can be registered to be managed by Veeva. The following table describes the differences between managed and unmanaged orgs:

Veeva Managed Orgs

Unmanaged Orgs
  • Receive automatic upgrades
  • Preserve content and reporting data
  • Receive notifications of planned upgrades
  • Must be manually upgraded by customers

    • Since upgrades are handled by customers manually and may not be up to date, Veeva reserves the right to discontinue support for old versions of CRM.

  • Can lose content and reporting data at any time due to a refresh
  • Do not receive notifications of planned upgrades

The following CRM functionality requires customer orgs to be managed by Veeva:

Requesting Unmanaged Orgs to Be Managed

To request an org to be managed, submit a support ticket and provide the VAdmin username.

If a customer requests a Sandbox org using an older version of CRM to be updated to the current version, the Sandbox must be on a CRM version within the last major CRM release. If the Sandbox's version of CRM is older than the last major release of CRM, the Sandbox must be refreshed from Production before being added to the Veeva Managed Orgs or upgraded to the latest version of CRM.

There is no additional cost to register orgs as Veeva Managed Orgs and Veeva encourages all customers to register all their orgs regardless of the environment to ensure all their data is properly maintained and up to date.