Instem Case Study

Three CRMs Consolidated Into One Salesforce Instance in Eight Weeks

SectorLife Sciences Software and Services

Services Used

3 to 1
CRM systems consolidated
8 Weeks
Kickoff to full delivery
0%
Downtime or data loss
100%
On time and under budget
Project summary

A Global Life Sciences Solutions Provider Needed to Unify the Commercial Operations of Its Two Largest Acquisitions

Instem is a software solution provider for the life sciences industry, supporting clinical and preclinical customers with analysis software and services that drive discovery, accelerate studies, and advance research. Following the 2025 acquisitions of Xybion Digital and Autoscribe Informatics, Instem needed to consolidate all three CRM environments into a single Salesforce Enterprise instance, with a completion deadline of January 1, 2026.

Marzipan was brought in to lead the complete integration: auditing data across all three systems, harmonizing field structures, migrating all records, and training the acquired commercial teams to operate within Instem's platform from day one of the new year.

Instem case study

Two Acquisitions. Three CRMs. One Commercial Team That Needed to Function as One.

Instem's 2025 acquisitions of Xybion Digital and Autoscribe Informatics represented its most complex commercial integrations to date. Each company brought its own CRM environment, account structures, processes, and commercial team, requiring Instem to manage the simultaneous migration of three distinct systems.

The acquisitions of Xybion Digital and Autoscribe Informatics were far larger than previous acquisitions. With that came full integration requirements across the whole company, finance, product, operations, sales, and the CRM and customer data side of things. This was a much bigger piece of work across multiple CRM platforms that we needed expertise and resources from external providers to get done.

Leanne Coles

Business Operations Manager, Instem

The complexity wasn't just technical. Each acquired business had different data hygiene standards, field naming conventions, and compliance requirements for what was captured and how it was captured.

  • Three distinct CRM systems, each with different field structures, object types, and data standards, needed to be mapped into a single Salesforce instance.
  • Each acquired business used different naming conventions, account hierarchies, and contact ownership models, with no existing Instem standard for alignment.
  • Migrating inaccurate or duplicated data into Instem's Salesforce posed a significant risk, as compromised data would immediately impact forecasting and pipeline reporting.

The complexities of the mapping, and getting the data aligned into a way that's useful for our sales team and our business, that was the difficulty. We didn't want to flood our instance of Salesforce with data that was going to compromise any of the outputs or measures that we needed to make as a business afterwards.

Leanne Coles

Business Operations Manager, Instem
Why Marzipan

Capability Was Expected. What Made the Difference Was Something Else.

Instem considered several options, including internal resources, before selecting Marzipan to lead the integration. With a firm December deadline and a highly complex project, the decision was based on technical expertise, timeline alignment, and a less tangible sense of confidence.

When having conversations with different suppliers, there's a feeling you get, a feeling of care and a feeling of getting a job done. It's a combination of both of those things that came across with Marzipan. You were evidently capable, but you also cared and were invested in the business and the outcome. I didn't see that failure was going to be an option.

Leanne Coles

Business Operations Manager, Instem

Leanne identified trust as the key factor that set Marzipan apart from other options. This trust was evident in the project's approach from the outset, rather than being based on price or methodology.

The overarching element for the decision-making is definitely trust. Definitely trust.

Leanne Coles

Business Operations Manager, Instem
The approach

Before migrating any data, it was essential to understand the specific needs of each business.

With only eight weeks to complete the project, precision was critical. Marzipan began with a discovery phase, collaborating with key stakeholders in each acquired organization to identify business-critical elements, legacy data, and requirements for the new Salesforce environment.

01. Audit first. Migrate nothing without purpose.

All records across the three CRM systems were evaluated using a clear framework: migrate, archive, or discard. Proprietary custom fields were catalogued. Where possible, fields and processes were transitioned to Instem's standard tools; otherwise, new fields and objects were created in Salesforce to maintain operational continuity.

Accounts, contacts, opportunities, quotes, historical emails, contracts, and file attachments were all included to ensure that sales representatives could access all relevant information in Salesforce from the start of the new year.

02. Bring the people along, not just the data.

The primary risk in such projects is not technical failure, but lack of user adoption. Acquired teams often resist new systems. Marzipan addressed this by involving legacy sales teams and their managers from the outset, rather than introducing a completed migration at the end.

We involved the legacy sales teams and their managers within the integration project, because we needed their help and support to identify what their data points were, why they kept them, what they were measuring, and to be able to fully translate that not only into Salesforce, but to create the training materials and training sessions to help the team through that change process.

Leanne Coles

Business Operations Manager, Instem

By the time formal training began, teams had already contributed to the migration and helped shape the new system. This approach led to a sense of familiarity and smoother adoption.

Now the team are in Salesforce using the platform day-to-day. You ask them, and they're like, 'Oh, it's not as bad as I thought it was going to be.' It wasn't that much of a change. It just looks a little bit different.

Leanne Coles

Business Operations Manager, Instem

03. Deliver on the deadline, without compromise.

The December 31 deadline was firm. All acquired commercial teams needed to be operational in Salesforce before the new year. The final phase, documentation migration, was completed in early January without disrupting sales, as teams maintained access to legacy systems during the transition.

The results

Instem Entered 2026 as One Commercial Organization. Not Three.

Instem began January 2026 with a unified system. All accounts, contacts, opportunities, quotes, emails, and documents were in place. Pipeline visibility was consolidated, enabling all sales managers to work from a single platform and forecast. Success in a project of this nature can be subtle, as Leanne described:

We're done, we're on time, we're on budget, we're happy. The measure of success in this is that the users don't feel it. The users don't feel the change, and that's what makes a project like this successful.

Leanne Coles

Business Operations Manager, Instem

3 to 1
CRM systems consolidated into one Salesforce instance
8 Weeks
From kickoff to full delivery
0%
Downtime or data loss during transition
100%
On time and under budget
Why Marzipan delivered

What Made This Work, and What It Means If You're Facing Similar Challenges

  • Dedicated project resource was essential. The eight-week, three-system migration required full attention and could not be managed alongside other responsibilities. Marzipan provided focused delivery from start to finish, without competing priorities.
  • Stakeholder-first discovery was prioritized over a template-driven approach. Before migrating any records, Marzipan identified business-critical elements by working directly with data owners in each acquired organization.
  • Change management was treated as a core deliverable. Acquired teams participated in the migration process, which ensured their understanding and facilitated smooth adoption.
  • Strict data quality standards were maintained. Every record was audited using a migrate, archive, or discard framework, with the goal of a clean, efficient Salesforce environment.
  • A collaborative partnership was established, rather than a distant agency relationship. As Leanne noted: "You felt like a member of the Instem team rather than somebody we were paying to do a job. It just felt easy."
  • Firm deadlines were upheld. The December 31 cutover was a commitment, not a target. The project was planned to accommodate complexity, ensuring timely completion.
FAQs

CRM Consolidation in Life Sciences

How do you consolidate multiple CRMs after a life sciences acquisition?

A successful CRM consolidation starts with a data audit, not a migration. You need to understand what each system holds, which records are business-critical versus archivable, and how field structures need to be harmonized before anything moves. Instem's three-system consolidation began with stakeholder interviews inside each acquired business, mapping proprietary processes, custom fields, and data ownership, before a single record was imported into Salesforce.

How long does a post-acquisition Salesforce CRM migration take?

Instem's project, covering three CRMs, two acquisitions, and a full migration of accounts, contacts, opportunities, quotes, documents, and email history, was completed in eight weeks, with a hard go-live deadline of December 31, 2025. The key variable is having a dedicated resource committed to the project, not team members absorbing it alongside existing workloads.

What is the biggest risk in post-acquisition CRM integration?

People, not data. Acquired teams working in familiar systems are resistant to change, especially when that change is presented to them rather than built with them. Instem's integration involved directly involving legacy sales teams and managers in the data audit and field mapping process. By the time formal training arrived, the teams already understood the new system.

Can a CRM migration be completed with zero downtime for acquired teams?

Yes, but it requires careful planning of access windows, a phased migration, and a bridge period during which teams retain legacy system access while migration completes. Instem's acquired teams had full access to their historical systems throughout the transition. Zero downtime was a design requirement, not a hope.

Does Marzipan manage Salesforce CRM consolidations for life sciences companies?

Yes. Marzipan leads end-to-end Salesforce CRM consolidation projects for life sciences organizations, including data auditing, field mapping, record migration, custom object creation, revenue operations setup, and acquired team training. Explore Marzipan's marketing operations services or view all case studies.

For further context on the acquisitions referenced in this case study, see: Instem closes acquisition of Xybion Digital, Xybion completes acquisition of Autoscribe Informatics, Boston HQ announcement.

More case studies

Back to Case Studies