Summary

  • Veeva may not sell applications using the Salesforce platform to new customers during a wind-down that runs from 1 September 2025 to 1 September 2030. For each customer already in place at the start, sales may not exceed 150% of that customer's own seat baseline.
  • Veeva says it will support the old Veeva CRM until 31 December 2029. After 1 September 2030 it cannot sell Salesforce-platform applications to any customer; specified breaches, intellectual-property claims or acquisitions can bring the wind-down forward.
  • More than 180 Vault CRM customers are live, including five top-20 biopharma customers in major markets, while 12 top-20 companies have committed. Those counts show movement but do not disclose the legacy denominator, migrated seats, revenue, cost, outages or completion by customer.

Veeva's latest Form 10-Q describes a software exit with unusually legible boundaries. The agreement under which Veeva CRM uses the Salesforce platform expired on 1 September 2025, yet it did not produce an immediate shutdown. It opened a five-year wind-down instead.

That distinction matters. An expired agreement can still contain live transition rights and obligations. For customers running a commercial system, the relevant question is not whether a contract has passed its headline expiry date. It is which actions remain permitted, who can end them, and how much operating room is left.

Four gates define the legacy corridor

The first gate concerns entry. During the wind-down, Veeva cannot sell Salesforce-platform applications to new customers. New demand therefore cannot replenish the old customer perimeter. It must go to Vault CRM or another provider.

The second gate concerns capacity. Veeva can continue selling such applications to a customer that existed on 1 September 2025, but no more than 150% of the seats that customer had in use on that date. This is a ceiling for each customer, not a disclosed aggregate allowance. A company with 1,000 baseline seats could, in principle, have room to reach 1,500; another company cannot transfer its unused headroom to it. Veeva has not published the baselines, present use or remaining headroom.

The third gate concerns support. Veeva says Veeva CRM will be supported until 31 December 2029. That date is earlier than the fourth gate: after 1 September 2030, Veeva cannot sell applications using the Salesforce platform to any customer. The filing does not explain every renewal, billing or service condition in the eight months between those dates. It would be unsafe to invent one.

The fourth gate concerns control. Salesforce can terminate the wind-down early in specified circumstances, including a material breach by Veeva or certain third-party intellectual-property claims that are not remedied under the agreement. If Veeva is acquired by specified companies, Salesforce may terminate on at least 12 months' notice. The filing neither names those companies nor says that Salesforce has exercised any of these rights.

Together the gates create a declining option. The old platform can absorb some expansion from existing customers, but it cannot recruit replacements, cannot grow any customer without limit and cannot outlive the contractual clock indefinitely.

The 180 live customers are a numerator without a denominator

Veeva's Q2 FY2027 prepared remarks provide evidence that Vault CRM is operating, not merely promised. Management said more than 180 customers were live, including five top-20 biopharma customers in major markets. It reported 12 top-20 commitments, a further top-20 go-live for all US field representatives, and migrations of different sizes.

Those are useful states only if they remain separate. A commitment is not a go-live. A market go-live is not necessarily a worldwide rollout. A live customer is not necessarily a customer migrated from old Veeva CRM, because new customers can begin directly on Vault. Nor does one customer equal another in seats, countries, integrations or workload.

The missing denominator prevents a completion rate. Veeva has not disclosed how many legacy customers or seats existed on 1 September 2025, how many have moved, how many remain, or how many of the 180 live customers are new. It also has not supplied a customer-by-customer matrix for data conversion, adjacent applications, interfaces, validation and user adoption.

The number 180 therefore answers “is the new platform being used?” It does not answer “how much of the old estate has safely left Salesforce?”

Migration can also redirect customers back to Salesforce

The dependency is becoming a competitive fork. Veeva says some customers have informed it that they intend to move to Salesforce as their CRM provider. Salesforce is both the platform beneath the legacy product and a competitor with its own life-sciences CRM offer.

The filing gives no count, seat volume, revenue or completion status for those intentions. They should not be turned into a market-share estimate. But they change the economic test. A legacy customer does not face only “old Veeva CRM versus new Vault CRM.” It can also choose Salesforce or another alternative, renegotiate scope, or reduce seats as its own field organisation changes.

That choice makes migration quality commercially material. A rushed conversion can preserve the vendor's timetable while losing the customer. A delayed conversion can protect near-term continuity while consuming the remaining contractual runway. The useful measure is cohort disposition: migrated to Vault, moved to a competitor, reduced, pending, or deliberately retired.

Revenue growth does not isolate the migration

Veeva's earnings release reports Q2 revenue of US$928.0 million, up 18%, and subscription revenue of US$766.8 million, up 16%. Prepared remarks put services revenue at US$161 million, up 24% in a record quarter.

None of those figures is a migration ledger. Veeva sells many Commercial, Development, Quality and Data products; its services include consulting and implementation beyond CRM. The filings do not separate old Veeva CRM revenue, Vault CRM revenue, Salesforce platform fees, migration services, customer credits or duplicated run costs.

Services growth could be consistent with migration work, but the public numbers do not prove the allocation. Subscription growth could coexist with a successful transition, yet it does not reveal whether migrated customers kept the same seats, modules or economics. Company-level growth is context, not a receipt for one platform change.

Continuity is the acceptance test

Veeva warns that migration is complex, can require significant time and expense, and may produce outages or performance problems in Vault CRM or other Vault applications as user volume grows. Disruptions can create liability, damage reputation and weaken renewal.

That risk is not evidence that an outage has occurred. It identifies the control surface that matters before the deadline. A credible migration record would show, for each cohort, the baseline, target scope, data reconciliation, integrations, adjacent applications, user readiness, cutover, rollback window, service incidents and formal acceptance.

The contract has already supplied the outer boundary. What remains opaque is the operating passage through it. The strongest evidence before 2029 will not be another large commitment count. It will be fewer unresolved cohorts, less legacy headroom in use, verified continuity after cutover and a clear treatment of customers that choose a different provider.

Sources