Incident sheet · /applications

Filed
Read
3 min · 630 words
Severity
Routine

Legacy CRM's Rising Cost and AI Limits Put Buyers at Risk

Legacy CRM systems built for recordkeeping and manual data entry can cost enterprises far more than they use and may constrain AI, integrations and cross-team customer resolution.

Legacy CRM Is Becoming a Bigger Risk for CX Buyers
FeedLegacy CRM Is Becoming a Bigger Risk for CX Buyers — Innovalabs / pixabay

Event log

  1. ServiceNow's Daniel Wilks says organizations typically spend 20 years or more building CRM systems around their original limitations.
  2. Treasure AI's Rafael Flores says customers typically use about 10 percent of CRM functionality but pay for 100 percent.
  3. Legacy CRM stacks may connect billing, order management, service operations, marketing platforms and other enterprise applications.
  4. Traditional CRM architectures center on human data entry and structured databases, while AI operations must interpret conversations, signals and trigger actions.

By Amara Osei

Enterprises often pay for 100 percent of a legacy CRM platform while using only about 10 percent of its functionality, according to Treasure AI Chief Product and Growth Officer Rafael Flores.

“You only use about 10 percent of it typically, but you pay for 100 percent of it,” Flores said. Paying for dormant capability adds to a broader problem: the longer customer records, processes, integrations and custom applications remain tied to a CRM, the harder buyers may find it to change or replace.

What makes an established CRM risky to replace?

Replacing an established CRM can itself become a major project. Customer records, business processes, integrations and custom applications often become deeply intertwined, making even an assessment of what needs to move a substantial undertaking.

Daniel Wilks, ServiceNow Vice President of CRM EMEA, said organizations typically spend 20 years or more building CRM systems. The original platforms aimed to create a single view of the customer, but custom code, integrations and workarounds turned them into large applications containing extensive customer data.

Wilks captured the resulting reversal in the systems’ purpose: “They were intended to serve the customer, but actually we ended up with a scenario where the organizations were serving the system.”

Customer-facing teams can lose substantial time maintaining records, navigating applications and working around disconnected processes. That work can turn the technology intended to improve customer service into an obstacle to delivering it.

The core risk comes from age and interconnection, not from customer data alone.

Can legacy CRM architecture support AI?

Many traditional CRM platforms began as systems for recording customer activity. Their architecture centers on human data entry and structured databases, while AI-driven customer operations need software that can interpret conversations, recognize customer signals and trigger actions across business processes.

Aurasell CEO Jason Eubanks said buyers cannot expect the same execution and outcomes from a system built around a different software paradigm. Adding an AI interface to an architecture designed for manual, structured work does not automatically create the data access and process orchestration that AI operations require.

That leaves CX buyers with a consequential decision: whether existing CRM platforms can evolve far enough to meet new requirements, or whether their underlying architecture will restrict what the organization can achieve.

AI can accelerate customer operations only when the underlying system can support them.

What should buyers reassess before migration?

CRM platforms rarely operate in isolation. Enterprises have connected them to:

  • Billing systems
  • Order management
  • Service operations
  • Marketing platforms
  • Other enterprise applications

They may also have accumulated poorly documented custom objects, workflows and business rules. Wilks characterized the result as a Frankenstein-like collection of applications, with extensive customization and a high cost of ownership.

Before moving any component, buyers need to establish:

  • Which business processes remain necessary
  • Which integrations are redundant
  • Which customizations support important business requirements

The end of support for a legacy product can force a broader review of the customer technology stack. Flores said that moment creates an opportunity to decide whether CRM should remain the central component of that stack.

Migration becomes manageable only after buyers separate indispensable processes from accumulated complexity.

How do legacy systems affect customer resolution?

Traditional platforms can record customer activity and show what happened during an interaction. They often struggle to coordinate the work required to resolve a request across the wider business, particularly when teams must move among disconnected applications.

Wilks cautions against building AI capabilities on top of those disconnected systems. An AI layer can improve interaction, but it cannot remove structural constraints in the underlying records, workflows and integrations.

For CX buyers, the decisive question is not only whether they can add AI, but whether the CRM beneath it can support faster, coordinated customer resolution without preserving the old constraints.

via cxtoday.com (Source)

Filed under

  • legacy-crm
  • crm-migration
  • enterprise-ai
  • crm-modernization
  • customer-experience
Share this article:

More from Amara Osei

Amara Osei

Show full bio

Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.

188 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›