Unifying Salesforce Across Mergers and Legacy Systems.
How a Real CRM Consolidation Delivered ROI.
When companies consolidate Salesforce orgs, decommission legacy systems, or unify processes across business units — the instinct is often to simply “merge the CRMs.” That approach rarely solves the real problem, and often introduces more. Here is what actually works.
When companies face the need to consolidate Salesforce orgs, decommission legacy systems, or unify processes across business units — whether due to mergers, acquisitions, or internal reorganization — the instinct is often to simply “merge the CRMs” and deal with the differences later. But that approach rarely solves the real problem — and often introduces more problems and costs more.
What actually works is a Salesforce consolidation strategy grounded in system-wide visibility, stakeholder alignment, and a structured decision-making process — reinforced by tools like our Tradeoff Evaluation Matrix, a prioritization framework that compares, side-by-side, systems, workflows, and requirements against business impact, level of effort, scalability, feasibility, and alignment with Salesforce’s technical roadmap. It highlights which capabilities should be retained, merged, rebuilt, or retired — and surfaces the ripple effects across users, data models, integrations, compliance, and adoption.
This case study offers a behind-the-scenes look at how we applied these principles in practice — demonstrating what it takes to turn complexity into cohesion and create a solution that scales.
This Salesforce consolidation project showcases a real-world transformation and unification effort I led to support ~5,200 users across 25 partner sites and 9 countries — unifying Sales and Customer Support teams, eliminating over 30 external tools, simplifying workflows, and building a shared KPI model to track outcomes globally.
Want to know why most projects fail before they begin? Read:
Most Salesforce Projects Jump to Solutions. Yours Won’t.
Step 1: Lead Discoveries with End-to-End Systems Thinking
Challenge: Breaking Through the Silos and Championing a Holistic Approach
At the start of this Salesforce consolidation project, I was initially assigned to analyze just one legacy system. Other systems were assigned to different analysts or siloed across business units. But from day one, I saw how inefficient and short-sighted this approach was.
Fortunately, I was first in line — which gave me early visibility into agent workflows, data models, and pain points across the board. I took trips to call centers to shadow agents, led SME workshops, reviewed system architecture of the current state of the Salesforce org and documented the usage and process flows of the legacy systems and external tools that the customer support agents needed to swivel to while on customer calls, and began developing the KPI instrumentation for customer identity resolution to establish baseline metrics and set target KPIs.
With insight into both user behavior and system behavior, I saw clearly how everything was interconnected and fragmented.
But convincing sponsors and leadership to take a broader view wasn’t easy. It required going against the grain — pushing back on surface-level directives and advocating for a solution that aligned to real-world user needs, operational goals, and long-term CRM strategy.
Lessons Learned
Listen to Your Gut — Especially when it’s backed by 25 years of experience across both the business and technical layers. When in doubt, reflect on the wins you’ve had over the years — they’re proof that your wisdom and instincts are rooted in real insight. And if you’re newer to CRM transformations, read case studies like this one to sharpen your judgment until your own gut has earned its track record.
Get Deep During Discovery — Fragmented Salesforce orgs and external tools may look like isolated problems — but their impacts are systemic. Solving them requires zooming out and documenting end-to-end process flows: the current-state business processes and rules, terms and conditions, regulatory and privacy compliance requirements, and every system and tool that end users rely on. Don’t forget to capture reporting and dashboard requirements, along with other downstream outputs. This approach ensures you’re not just putting out fires, but getting to the root causes of pain points — the kind that quietly erode productivity, frustrate customers, and undermine user trust. Solve for these, and the end users will love you.
Ask SMEs thoughtful, targeted questions to uncover tribal knowledge — those undocumented processes and workarounds that quietly keep operations running, but vanish when key team members leave the company. Ask questions and document the answers. Leave no stones unturned.
And most importantly: when the stakes are high, make sure there’s enough time for real Discovery. Superficial intake leads to blind spots, half-informed decisions, misaligned roadmaps, and expensive rework. Discovery is where you earn the right to ask lots of questions in order to design a solution that actually works.
Advocate for the Best Interests of End Users and Customers — Be Willing to Stick Your Neck Out — These transformations demand more than technical skills. They require persistence, empathy, and heart. I still remember calls where frustrated customers yelled at overwhelmed agents — agents who didn’t have the tools or data immediately available to help them. It takes sound judgment, analytical skills, collaborative leadership, emotional intelligence, moxie, and the courage to connect the dots — bringing the right people together to move the program forward holistically, with a focus on outcomes that truly serve both users and customers.
Transformation Isn’t a Template — What works in one org won’t necessarily work in another. Success requires a framework grounded in visibility, creativity, curiosity, collaboration, and scalability — one that honors the realities of end users and business operations, guiding discovery through to consensus on smart, intentional tradeoff decisions.
Step 2: Bring Sales and Customer Support Together to Evaluate Capabilities Cross-System
Sales and Customer Support teams operated in separate Salesforce orgs with overlapping external tools. Legacy systems supported everything from ID verification to entitlements — but were siloed, redundant, and difficult to maintain.
We brought cross-functional Sales and Customer Support teams together for joint workshops. Together, we:
- Evaluated core capabilities across systems
- Mapped overlaps and dependencies
- Defined business impact statements alongside user stories and acceptance criteria
- Flagged integration risks
- Prioritized which systems to retire vs. integrate
Step 3: Map Use Cases and Workflows Before You Touch Any Systems
Before touching any systems, we started with what matters most: the business process layers.
We identified high-level use cases (e.g., customer and entitlement verification, product support, billing, RMA) and traced how those functions were executed across business units, regions, orgs, and tools. This detailed mapping allowed us to:
- Understand the real-world execution of core capabilities in each system
- Uncover hidden workarounds and pain points that weren’t visible in documentation
- Identify opportunities for harmonization into a unified Salesforce model
- Discover the root causes of friction and inefficiency — not just the symptoms
- Clarify which functions were truly MVP, and which could be deferred or redesigned
- Pinpoint integration points that were essential for delivering a complete customer experience
- Define the optimal retirement timeline for legacy systems, minimizing disruption
This revealed how teams were executing the same functions differently across business units, and where disconnected systems were causing friction, inefficiencies, inconsistent reporting, or duplicated effort.
Our two-level matrix — Level 1 (L1) Use Cases, Level 2 (L2) Workflows evaluation framework highlighted gaps, overlaps, duplication, and high-impact handoffs across the Salesforce ecosystem and legacy stack.
As an example, the diagram below summarizes the framework results for mapping L1s and supporting L2s, making it easier for stakeholders to see how activities are distributed across orgs and systems — and where there are gaps, redundancies, or misalignment.
Step 4: Define KPI Metrics Before Automating Anything
A core pain point: Agents were unable to quickly identify the customer or their associated products due to disparate systems, fragmented data, and inconsistent screen pop behavior. This often led to repeated verification steps, duplicate case creation, and average resolution times exceeding 30 minutes — sometimes across multiple calls.
Before building any automation or recommending changes to the data model, we first aligned on how success should be measured:
- Baseline Metrics included: identity resolution success, call handle time, first call resolution, screen pop accuracy, and time to locate and verify customer information across both Sales and Customer Support.
- Target KPIs focused on reducing repeat calls, improving CSAT, decreasing duplicate case creation, shortening call handle times, and improving the customer support journey continuity and user satisfaction.
To unify all stakeholders around a single, meaningful metric, we introduced:
“% of Customers We Know as They Contact Us” — defined as: “You know who I am without me having to tell you, what products/services I use, how long I’ve been using them, and what my past and current interactions with you have been.”
This metric, illustrated in the image below, reflects an agent’s ability to:
- Instantly locate and identify the correct customer, contact, related products, entitlements, and cases
- See a complete, 360-degree view of the customer
- Resolve the issue without requiring additional research or system navigation
While defining this key KPI, we discovered that executives, business unit leads, and Salesforce teams each had slightly different interpretations of what “knowing the customer” meant. Aligning on this definition was essential — it served as the foundation for establishing baseline measurements, setting realistic KPIs, and tracking measurable improvements over time.
Additional Target KPIs included:
| KPI | Description |
|---|---|
| External tools decommissioned | Number of legacy and shadow tools retired from agent workflows |
| Call Handle Time | Reduction in average handle time per support interaction |
| Tool swivel reduction | Fewer system switches required for sales reps and support agents per interaction |
| CSAT improvement | Customer satisfaction score improvement across support channels |
| First Call Resolution (FCR) | Percentage of issues resolved on the first contact without escalation or callback |
| Agent productivity & satisfaction | Agent-reported efficiency gains and satisfaction with the new unified platform |
| Increased data accuracy in Salesforce | Reduction in duplicate records, mismatched accounts, and stale contact data |
Step 5: Build a Roadmap That Respects Reality and Scales With Intention
Transformation doesn’t happen all in Sprint 1 — or even in Phase I.
To build a roadmap grounded in reality and long-term scalability, we worked closely with stakeholders to:
| Roadmap Evaluation Factors | Example |
|---|---|
|
Differentiate MVP vs. future-phase requirements. Some legacy systems had regulatory or contractual constraints, requiring phased decommissioning aligned with system dependencies. |
Immediate contact identity resolution and entitlement visibility were prioritized as MVP, while agent training dashboards and billing integration were scoped for later sprints. |
| Understand how the timing of legacy system retirements would impact the Salesforce rollout. |
The customer service team relied on a legacy knowledge base that was set to be retired two weeks before the new Salesforce Knowledge system would go live. To avoid a gap in agent support, we adjusted the Salesforce rollout plan to launch Knowledge one sprint earlier and migrated the top 100 most-used articles in advance. This ensured agents still had access to critical information during the transition, without relying on two systems at once. |
|
Ensure that the backlog captures all required features and capabilities—including those deferred for later implementation. We ensured even non-MVP requirement items were documented with business rationale, so nothing fell through the cracks. |
During discovery, sales reps requested a custom lead scoring dashboard. It wasn’t essential for MVP, so we scoped it for a later release. Still, we captured the full business rationale and added it to the backlog with clear priority and dependencies—so it wouldn’t be forgotten or delayed indefinitely. |
|
Define business impact statements for each backlog item, then apply our Tradeoff Evaluation Matrix to prioritize based on: ✓ Business impact ✓ Pain point severity (frequency and consequences) ✓ Level of effort (LOE) ✓ Scalability ✓ Feasibility ✓ Alignment with Salesforce’s current and emerging technical roadmap (this is a forward-looking strategy—it’s important to evaluate feasibility and sustainability of the solution) |
Example 1 – High Priority, Immediate Implementation: Auto-verification of customer ID across systems scored high in business impact, pain point severity, and feasibility—earning top-priority status in Sprint 1. Example 2 – High Business Need, Roadmap-Dependent: Complex quoting flows with custom discounting logic were originally supported by legacy CPQ tooling. While the need was high, the existing logic was brittle, costly to replicate, and out of alignment with Salesforce’s transition to Revenue Cloud Advanced (RCA). Instead of duplicating the legacy approach, at that time, we implemented a lightweight interim quoting process in Sprint 2 using native Salesforce flows and price books—then committed to building a longer-term scalable RCA-based quoting solution in Phase II, aligned with Salesforce’s roadmap and licensing strategy. |
This approach ensured early sprints focused on foundational readiness — the must-haves that unlock long-term value — while the entire roadmap remained structured, intentional, and traceable. We enforced backlog hygiene, RAID (Risks, Assumptions, Issues, Dependencies) tracking, and cross-functional accountability from the very beginning — ensuring decisions weren’t just made quickly, but made wisely.
The Real Payoff: One Platform. One Delightful Experience. Successful Adoption. Scalable Impact.
| Outcome | What It Delivered |
|---|---|
| ~5,200 global users unified | A single CRM ecosystem replaced siloed orgs and external tools, enabling enterprise-wide visibility and process alignment. |
| 30+ legacy tools decommissioned or integrated | Critical workflows previously scattered across shadow systems were rebuilt into Salesforce, reducing swivel-chair activity and risk-prone handoffs. |
| Key workflows transformed in Salesforce | User-friendly identity resolution, entitlement verification, billing support, and escalation paths were transformed for speed, consistency, and efficiency. |
| Standardized reporting and compliance across geographies | Teams now operate from shared definitions, data models, and dashboards — meeting regulatory, legal, and operational reporting needs at scale. |
| Identity resolution success rate drastically improved | Baseline metric of “% of Customers We Know as They Contact Us” increased significantly — cutting average time to verify a customer by more than half. |
| Call Handle times and CSAT scores improved across regions | Faster resolution, better screen-pop accuracy, and fewer repeated verification steps improved both agent efficiency and customer satisfaction. |
| Ready for automation, AI, and Agentforce at scale | The foundation now supports streamlined automation logic, trusted AI recommendations, and next-gen Salesforce service capabilities. |
| Adoption secured through embedded champions and collaborative rollout | By engaging business SMEs and stakeholders from the very beginning — representing their teams and regions — we gained alignment, surfaced hidden needs, and co-created a solution users were invested in. These early collaborators became champions of the rollout and ensured adoption success across the organization. |
| Leadership alignment built through visibility and inclusion | Program leaders, IT, and business sponsors weren’t just informed — they were engaged. Their goals, constraints, and long-term vision were reflected in backlog priorities, tradeoff decisions, and roadmap phases. |
| Champions Built Across the Globe | From Manila, Cebu, Makati, Bangalore, Singapore, Sydney, London, Brazil, France, Reno, Phoenix and Tucson — this consolidation effort unified call center agents, analysts, and managers across common global support hubs. Just as important, the needs and pain points of all impacted business units were represented — ensuring we didn’t just roll out a system, but a unified, consolidated, and transformed solution that truly works. |
One of the biggest reasons this consolidation succeeded? We didn’t jump to quick fixes. We focused on platform readiness, stakeholder alignment, and root-cause discovery. Explore the mindset: Most Salesforce Projects Jump to Solutions. Yours Won’t.
Final Thoughts: What If I Didn’t Listen to My Gut and Kept My Blinders On?
Remember the challenges and lessons learned I mentioned in Step 1?
What if I had accepted the “blinders on” mentality expected by leadership — staying narrowly focused on my assigned system, boxed in siloed directives, ignoring the interdependencies, and deferring to surface-level assumptions instead of asking deeper questions?
Here’s what likely would have happened:
| Risk | What Would Have Gone Wrong |
|---|---|
| Technical Debt | Without end-to-end visibility, we would’ve duplicated automations, hard-coded logic, and integration points — causing rework and increasing long-term maintenance costs. Examples: multiple identity resolution routines with different matching logic; inaccurate IVR (Interactive Voice Response) screen pop configuration; redundant case escalation flows embedded in each org. |
| Wasted Effort & Budget | The need for rework would have invalidated original estimates and delayed delivery across multiple tracks. |
| Loss of User Trust | Agents would have continued relying on shadow tools (like spreadsheets and external apps), reducing Salesforce adoption and confidence in the system. |
| Customer Dissatisfaction | Gaps in identity resolution and case continuity would’ve left customers repeating themselves or experiencing inconsistent service. |
| Poor Data Modeling | Point-to-point fixes would have been built on brittle data structures, making objects and relationships harder to scale, reuse, or integrate. |
| Disparate Process Flows | Redundant workflows would remain unaddressed, complicating training, QA, and performance reporting. This lack of integration can lead to fragmented data, inefficient processes, and challenges in sharing information across different departments or teams — ultimately creating friction in both employee and customer experiences. |
| Inability to Scale | Without a unified foundation, the program would have lacked the architectural integrity and operational readiness required to support growth, automation, or future AI initiatives — forcing yet another round of cleanup and redesign later. |
That’s why I founded CRM & Data Angels.AI Consulting — not just to support Salesforce initiatives, but to ensure they succeed. Because true transformation isn’t just about systems — it’s about the decisions, leadership, and frameworks that ensure those systems serve your end users, your customers, your business, and the future of your organization.