About Vault CRM Releases
Vault CRM provides regular software updates to ensure that customers have access to the latest features, enhancements, and security updates. This document outlines the release schedule, types of releases, and other important information related to Vault CRM upgrades.
Sections included:
- 2025 Release Schedule
- Release Types
- What Happens During a Release
- Release Numbering
- Release Communication
- Understanding Your Vault CRM Hosting Locations (PODs)
- Typical Regional Release Windows
2025 Release Schedule
The following release dates are subject to change. Please refer to the Veeva Trust site for the most up-to-date information.
| Release |
Upgrade Announcement |
Full Sandbox |
Production Upgrade |
|---|---|---|---|
|
24R3.4 Minor Release |
Feb. 6, 2025 |
Feb. 13, 2025 |
Feb. 20, 2025 |
|
24R3.5 Minor Release |
Mar. 6, 2025 |
Mar. 13, 2025 |
Mar. 20, 2025 |
|
25R1.0 Major Release |
Apr. 10, 2025 |
Apr. 17, 2025 |
May 1, 2025 |
|
25R1.2 Minor Release |
May 15, 2025 |
May 22, 2025 |
May 29, 2025 |
|
25R1.3 Minor Release |
June 12, 2025 |
June 19, 2025 |
June 26, 2025 |
|
25R2.0 Major Release |
July 31, 2025 |
Aug. 7, 2025 |
Aug. 21, 2025 |
|
25R2.2 Minor Release |
Sept. 4, 2025 |
Sept. 11, 2025 |
Sept. 18, 2025 |
|
25R2.3 Minor Release |
Oct. 2, 2025 |
Oct. 9, 2025 |
Oct. 16, 2025 |
|
25R3.0 Major Release |
Nov. 13, 2025 |
Nov. 20, 2025 |
Dec. 4, 2025 |
Release Types
Vault CRM releases are categorized into several types:
Major Releases
- Frequency: Three times per year (every four months)
- Content: New features, product enhancements, and fixes to existing functionality
- Validation: Fully validated, including new functionality from Minor Releases
- Sandbox Availability: Released to customer sandboxes two weeks prior to production upgrade
- Release Notes: Provided 21 days before the production upgrade, including all user visible changes, new features, and platform availability
Minor Releases
- Frequency: Up to three per Major Release (monthly)
- Content: Critical new features, product enhancements, and fixes
- Validation: Validated for current functionality; new functionality is validated with the next Major Release
- Sandbox Availability: Released to customer sandboxes one week prior to production upgrade
- Release Notes: Provided 14 days before the production upgrade, covering user visible changes, new features, and platform availability
Maintenance Releases
- Frequency: As needed (typically weekly on Thursdays)
- Content: Defect fixes for issues affecting customers
- Validation: Yes
- Sandbox and Production: Updated simultaneously
- Release Notes: Provided 2 days before the production upgrade
Hotfixes
- Frequency: As needed (unplanned)
- Content: Critical defect fixes
- Validation: Yes
- Sandbox and Production: Updated simultaneously
- Release Notes: Provided around 24 hours before the production upgrade
System Maintenance
- Frequency: As needed (scheduled downtime)
- Content: System infrastructure changes like server restarts
- Communication: Prior notice provided if service disruptions occur
- Validation: Yes
- Release Notes: Provided up to 7 days before the production upgrade
Release Details
|
Frequency |
Communication |
Communication Recipients |
Documentation | Validated | |
|---|---|---|---|---|---|
|
Major Release |
Every 4 months on a Thursday |
3 weeks prior to the production upgrade | All customers who opted in on the Trust site | Major Release Notes | Yes |
|
Major Sandbox Release |
2 weeks before the Major Release |
1 week prior to the sandbox release |
All customers who opted in on the Trust site |
Major Release Notes |
No |
|
Minor Release |
Once per month on the first Thursday of the month | 2 weeks prior to the production upgrade | All customers who opted in on the Trust site | Minor Release Notes | Validated for current functionality. New functionality added in a Minor Release is validated with the Major Release. |
|
Minor Sandbox Release |
One week before the Minor Release |
1 week prior to the sandbox release |
All customers who opted in on the Trust site |
Minor Release Notes |
No |
|
Maintenance Release |
As needed on a Thursday |
2 days in advance |
All customers who opted in on the Trust site |
Maintenance Notes |
Yes |
|
Hotfix |
Not Scheduled |
24 hours in advance |
All customers who opted in on the Trust site |
Maintenance Notes |
Yes |
|
System Maintenance |
Not scheduled |
Up to 1 week in advance |
All customers on affected PODs who opted in on the Trust site |
No |
Yes |
The frequency or day may change due to holidays. For urgent or critical releases, we may release with less than 24 hours' notice.
What Happens During a Release
- Vault CRM Browser Users: Instances are in read-only mode during upgrades.
- Offline CRM Users: Not affected during upgrades but cannot sync while an upgrade is in progress.
Release Numbering
Vault CRM uses a consistent release numbering system to identify versions. Major releases are denoted by the year and release number (e.g., 24R2.0), while minor releases increment the decimal (e.g., 24R2.2).
Release Communication
Release communications are sent via the Veeva Trust site.
How to Subscribe on Trust:
- Navigate to trust.veeva.com.
- Select the Subscribe to the Veeva Trust Site tab.
- Choose to subscribe to the PODs your Vault CRM instance is in.
- Opt-in to receive notifications.
The Trust page is updated to indicate when a release is completed.
How to Subscribe within Vault CRM:
- Navigate to your user profile in Vault CRM.
- Select the Service Availability Notifications check box.
Alternatively, if your organization maintains its own distribution list:
- Navigate to Admin > Settings > General Settings > Service Availability Notifications in Vault CRM.
- Enter the email address for the distribution list in the Service Availability Notifications field.
Understanding Your Vault CRM Hosting Locations (PODs)
Vault CRM applications are hosted on servers located in various data centers worldwide, known as Points of Delivery (PODs). They are located in data centers across Europe, Japan, and the U.S.
Knowing your POD is essential for:
- Performance Optimization: Understanding server proximity can help improve application responsiveness
- Regulatory Compliance: Ensures adherence to regional data residency laws and regulations
- Maintenance Planning: Helps anticipate maintenance windows based on your server's location
How to Find Your POD
Navigate to Admin > About > Vault Information. The POD number is listed under the Vault Information section.
POD Details
US PODs |
Europe PODs |
APAC PODs |
|||||||||||||||||||||||||||||
|
|
|
POD Locations
Vault CRM is hosted on Veeva-managed servers running on AWS. For more information on AWS server locations, see AWS Global Infrastructure.
Typical Regional Release Windows
On release dates, Vaults are typically updated to the next release during the following times:
|
Region |
Time (Pacific Time) |
|---|---|
|
Americas |
5:30 PM - 9:30 PM |
|
Asia Pacific |
10 AM - 2 PM |
|
Europe |
10 AM - 2 PM |
