Regeneron and Biogen each committed on the same day to move their global commercial CRM to Veeva Vault CRM, two more marquee biopharma names landing on one side of a split that has been building since Veeva ended its long-standing platform partnership with Salesforce. The story here is not which vendor two drugmakers picked. It is that life sciences CRM, one of the most locked-in software categories in enterprise tech, is being forced to re-platform at scale, and the industry is dividing into two camps rather than consolidating around one.
A Partnership That Ran Out, Not a Feature Race
For nearly two decades, Veeva’s CRM ran on top of the Salesforce platform under a licensing agreement. That agreement was not renewed when it expired in September 2025, ending the arrangement that had made Veeva the default commercial CRM for pharma while Salesforce supplied the underlying infrastructure. Veeva has said existing customers can keep running the legacy Salesforce-based product until support ends in September 2030, but it has spent the past two years pushing its own, independently built Vault CRM as the successor.
That push is now showing up in the numbers. By its fiscal 2026 results in March, Veeva reported more than 125 customers live on Vault CRM, with 10 of the top 20 global biopharmaceutical companies already committed to the platform and management projecting that figure could reach 14 of the top 20 over time. Regeneron and Biogen becoming customer commitments 126 and 127, in effect, on the same day is less a coincidence than a sign the migration has moved from early-adopter territory into the industry’s mainstream.
Advertisement
Two Announcements, One Shared Reason
Both companies framed the move as an expansion of an existing relationship with Veeva rather than a switch away from an incumbent. “We are pleased to expand our strategic partnership with Veeva by moving to Vault CRM, which will give our commercial teams a more connected platform and help them get faster access to the information they need for efficient decision-making,” said Ryan Steinberger, EVP and Chief Digital and Technology Officer at Regeneron.
Biogen’s characterization was nearly identical in substance. “Biogen and Veeva share a deep commitment to customer experience and innovation. We are excited to expand our strategic partnership with Veeva by moving to Vault CRM,” said Guy Hadari, Senior Vice President and Global CIO at Biogen. On Veeva’s side, Tom Schwenger, President and Chief Commercial Officer, said the company was “honored to provide Vault CRM as the agentic commercial foundation for Biogen as it delivers medicines that transform patients’ lives,” adding that “bringing complex treatments to market requires a highly adaptive commercial strategy.”
Both releases point to the same underlying feature driving urgency: an Agentic Call Report capability that is meant to capture more of what happens in a field rep’s interaction with a physician, generating what Veeva calls “Commercial Evidence” for spotting where patients are losing access to a treatment. That is the actual sales pitch behind the migration. It is not just a platform swap, it is commercial teams buying into an AI layer that only exists on the new architecture.
That distinction matters because it changes what a migration decision is actually weighing. A straight platform swap is a cost and risk conversation: what breaks, what it costs to move, how long the cutover takes. An AI-capability decision is a competitive one, because the sales organization that captures richer field data first can start training and tuning models on it sooner. Regeneron and Biogen’s own language, both describing the move as “expanding” an existing partnership rather than replacing a vendor, suggests neither company saw this as a defensive rip-and-replace. They saw it as buying into whichever side of the Veeva-Salesforce split had the commercial AI capability they wanted next.
Salesforce Did Not Cede the Category
The split cuts both ways. Salesforce built its own vertical answer, Agentforce Life Sciences, and has been signing its own list of marquee logos, including AstraZeneca, Takeda, Pfizer, Boehringer Ingelheim, Chiesi Group and Fresenius Kabi. By December 2025, Salesforce said more than 70 organizations had selected Agentforce Life Sciences. That is a smaller base than Veeva’s Vault CRM numbers, but it confirms that life sciences CRM is not consolidating toward a single winner. It is splitting into two camps, each collecting its own set of household pharma names to use as leverage with the next prospect on the fence.
What It Means for the RevOps Leader
Most revenue teams outside life sciences will never touch Vault CRM or Agentforce Life Sciences directly. What is worth paying attention to is the mechanic, not the vendors: a platform relationship that looked permanent for two decades unwound in about a year, and every customer sitting on the old architecture is now working against a hard support deadline. Similar bundled arrangements exist elsewhere in the CRM and revenue stack, and the same forced-migration dynamic will not stay confined to one vertical. This publication has covered how AI depth is already reshaping how analysts rank CRM platforms, and buyers are applying the same scrutiny to how those platforms are actually built, not just what they promise on a roadmap.
The practical takeaway for a RevOps or IT leader evaluating any CRM stack: ask now what the underlying platform dependency actually is, get contractual clarity on support and end-of-life timelines before they become a forced deadline, and treat a vendor’s AI roadmap as tied to specific architecture, not a feature that will simply arrive on whatever system is already in place. Regeneron and Biogen did not wait for a crisis to make that call. Teams still running on a bundled or licensed foundation elsewhere in the stack should be asking the same question before the decision gets made for them.
There is also a procurement lesson in how little runway a five-year migration actually gives a buyer once the clock starts. Veeva’s own numbers, roughly 30 live customers in 2024 to more than 125 by early 2026, show adoption compounding once a critical mass of peers commits publicly. Waiting to see how a platform split resolves before acting is itself a decision, and it is usually the more expensive one once the vendor with fewer years left on its support clock starts raising the price of staying put.
