πŸ“° BPO Industry News

Legacy CRM Is Becoming a Bigger Risk for CX Buyers β€” CX Today

Curated by Marcas BPO β€” your nearshore partner. Original source β†’

{"@context":"https://schema.org","@type":"NewsArticle","headline":"Legacy CRM Is Becoming a Bigger Risk for CX Buyers","description":"Decades of customizations, integrations and workarounds have made legacy CRM systems difficult to replace. But as AI raises expectations for faster, more connected customer service, the cost of staying put could be greater than the disruption of migration.","image":["https://media.cxtoday.com/article-images/1794834460615-50c142c4-146a-4e2c-a3c3-71d0eeada898-20261116---WilksCRM.jpg"],"articleSection":"CRM \u0026 Data","url":"https://cxtoday.com/legacy-crm-is-becoming-a-bigger-risk-for-cx-buyers","mainEntityOfPage":{"@type":"WebPage","@id":"https://cxtoday.com/legacy-crm-is-becoming-a-bigger-risk-for-cx-buyers"},"datePublished":"2026-11-16T15:01:00.758Z","dateModified":"2026-11-16T15:01:00.758Z","wordCount":1230,"author":{"@type":"Person","name":"Nicole Willing","jobTitle":"Tech Journalist","url":"https://cxtoday.com/author/nicole-willingcxtoday-com"},"publisher":{"@id":"https://cxtoday.com/#organization"},"articleBody":"Enterprises that have spent decades building their customer relationship management (CRM) environments might view replacing an established platform as a particularly risky undertaking. Customer records, business processes, integrations and custom applications have often become so deeply intertwined that even assessing what needs to move can be a major project. But as AI changes what businesses expect from their customer technology, the risks of retaining those systems are becoming harder to ignore. Many legacy CRM platforms were originally designed to record customer activity and provide a single view of the customer. Over time, organizations added layers of custom code, integrations and workarounds to make them serve increasingly complex operational requirements. The result is an environment that can be expensive to maintain, difficult to change and poorly suited to the demands of modern customer service. As Daniel Wilks, VP of CRM EMEA at ServiceNow , noted in an interview with CX Today , the problem has developed over decades of organizations building around the limitations of their original systems. \"Organizations have typically spent 20 years or more building CRM systems that were really designed to build a single view of customer and became these vast applications with huge amounts of customer data.\" Over time, the original intention of CRM has also become distorted, Wilks said. \"They were intended to serve the customer, but actually we ended up with a scenario where the organizations were serving the system.\" When customer-facing teams have to spend significant time maintaining records, navigating applications and working around disconnected processes, the technology can become an obstacle to delivering the experience it was introduced to support. The architecture of traditional CRM also presents challenges for AI adoption. Many platforms were built around human data entry and structured databases, whereas AI-driven customer operations require systems that can interpret conversations, understand customer signals and trigger actions across business processes. As Aurasell Chief Executive Officer (CEO) Jason Eubanks previously told CX Today : \"You can't expect the same level of execution and outcomes for a system that was built around a different paradigm of how software was architected.\" This raises the question for CX buyers as to whether existing CRM platforms can evolve sufficiently to support these requirements, or will their underlying architecture constrain what organizations can achieve? The Cost and Complexity of Staying Put CRM platforms rarely operate in isolation. Over the years, businesses have connected them to billing, order management, service operations, marketing platforms and other enterprise applications, and they may also have accumulated poorly-documented custom objects, workflows and business rules. Wilks describes the resulting environments as a \"Frankenstein's monster of different applications integrated together with huge customization and cost of ownership.\" Each additional layer makes migration more complicated. Buyers must establish which processes remain necessary, which integrations are redundant and which customizations support important business requirements. There is also a financial consideration. Rafael Flores, Chief Product and Growth Officer at Treasure AI has highlighted how traditional CRM platforms can leave enterprises paying for extensive functionality they rarely use. \"You only use about 10 percent of it typically, but you pay for 100 percent of it,\" Flores observed in a previous CX Today discussion . As Flores argued, the end of support for a legacy product can provide an opportunity to reassess the wider customer technology stack, including whether CRM should remain its central component. How Legacy Systems Affect Customer Resolution The limitations of legacy CRM are also visible in the everyday work of customer-facing teams. Traditional platforms can provide a record of customer activity and show what has happened during an interaction. However, they may struggle to coordinate the work required to resolve a request across the wider business. Adding AI to an existing CRM does not automatically resolve its architectural limitations. Wilks cautions against building AI capabilities on top of disconnected systems. \"What you can't do is just apply AI on top of broken foundations.\" An AI solution might understand a customer's request and recommend what an employee should do next. But if it cannot access the relevant information or trigger the necessary processes across the enterprise, the work still has to be completed manually. Wilks identifies four connected capabilities needed to support more autonomous customer service: AI intelligence, workflow orchestration, unified data and governance. AI provides the ability to interpret customer requests and context. Workflow capabilities enable actions across the business, while connected data supplies the information needed to make decisions. Governance determines what AI agents can access, which actions they can take and when human intervention is required. This also means buyers need to look beyond vendor claims about AI. They should establish whether capabilities are available in working products and can demonstrate measurable results in real business processes, rather than relying on roadmaps or demonstrations. Six Questions for CRM Buyers Replacing legacy CRM is a significant investment, but the decision should begin with the business outcomes an organization wants to achieve. Wilks recommends identifying specific use cases, whether improving customer experience, increasing efficiency or accelerating sales and service processes. Drawing on the architectural and commercial challenges facing CRM buyers, six questions deserve particular attention: Can the platform keep pace with the business? Will it support changing customer expectations and new processes without extensive development or vendor intervention? Is its AI genuinely usable? Can vendors demonstrate working AI capabilities in production environments, rather than relying on product roadmaps and prototypes? Can it connect data with action? Can the platform bring together customer information across the enterprise and trigger workflows, rather than simply recording interactions? Is the data ready for AI? Are customer records accessible, accurate and governed, with appropriate permissions and controls for agent activity? Are sunk costs delaying change? How does the ongoing cost of maintaining the current environment compare with the financial and operational benefits of migration? Is CRM still the right center of gravity? Does the organization need a replacement CRM, a more connected data and engagement architecture, or a different platform model? The last question is particularly important as businesses reassess the traditional boundaries between CRM, customer data platforms and engagement technology. The right architecture will depend on the organization's requirements. Consolidation may make sense in some environments, while others may benefit from connecting specialist platforms around a shared data and workflow foundation. ServiceNow aims to tackle the migration challenge with its Autonomous CRM Engine , designed to help enterprises map existing CRM environments, identify redundant processes and customizations, and deploy a redesigned environment on ServiceNow CRM. The company says the capability can reduce deployment timelines to weeks by automating discovery and mapping, with continuous monitoring intended to identify configuration problems before they disrupt operations. A separate customer example illustrates the potential service benefits of connecting workflows. ReSource Point of Sale has used ServiceNow CRM to automate customer support processes, increasing monthly ticket capacity from 5,000–6,000 to more than 11,000 while reducing average resolution times from eight to ten hours to three hours. For restaurants and retailers relying on functioning payment terminals, registers and drive-through systems, faster repairs can mean less operational downtime and lost revenue. The Migration Decision Legacy CRM migration will remain difficult for enterprises with years of investment and operational dependencies tied to their existing platforms. But the challenge for buyers is establishing whether their current CRM can support the next generation of customer service and whether the cost of waiting is becoming greater than the cost of migration."}{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://cxtoday.com/"},{"@type":"ListItem","position":2,"name":"CRM \u0026 Customer Data Management","item":"https://cxtoday.com/beat/crm-data"},{"@type":"ListItem","position":3,"name":"Legacy CRM Is Becoming a Bigger Risk for CX Buyers","item":"https://cxtoday.com/legacy-crm-is-becoming-a-bigger-risk-for-cx-buyers"}]}{"@context":"https://schema.org","@type":"VideoObject","name":"Legacy CRM Is Becoming a Bigger Risk for CX Buyers","description":"Legacy CRM is slowing AI-led service, and CX Today warns buyers to weigh migration against customisation, integrations and ServiceNow.","url":"https://cxtoday.com/legacy-crm-is-becoming-a-bigger-risk-for-cx-buyers","thumbnailUrl":["https://media.cxtoday.com/article-images/1794834460615-50c142c4-146a-4e2c-a3c3-71d0eeada898-20261116---WilksCRM.jpg"],"uploadDate":"2026-11-16T15:01:00.758Z","mainEntityOfPage":{"@type":"WebPage","@id":"https://cxtoday.com/legacy-crm-is-becoming-a-bigger-risk-for-cx-buyers"},"embedUrl":"https://www.youtube-nocookie.com/embed/-mXXSs814GM?rel=0"}
Front page
NewsCRM & Data16 Nov 2026 Β· 6 min read
Legacy CRM Is Becoming a Bigger Risk for CX Buyers

Decades of customizations, integrations and workarounds have made legacy CRM systems difficult to replace. But as AI raises expectations for faster, more connected customer service, the cost of staying put could be greater than the disruption of migration.

In this article

  1. The Cost and Complexity of Staying Put
  2. How Legacy Systems Affect Customer Resolution
  3. Six Questions for CRM Buyers
  4. The Migration Decision

Enterprises that have spent decades building their customer relationship management (CRM) environments might view replacing an established platform as a particularly risky undertaking. Customer records, business processes, integrations and custom applications have often become so deeply intertwined that even assessing what needs to move can be a major project.

But as AI changes what businesses expect from their customer technology, the risks of retaining those systems are becoming harder to ignore.

Many legacy CRM platforms were originally designed to record customer activity and provide a single view of the customer. Over time, organizations added layers of custom code, integrations and workarounds to make them serve increasingly complex operational requirements.

The result is an environment that can be expensive to maintain, difficult to change and poorly suited to the demands of modern customer service.

As Daniel Wilks, VP of CRM EMEA at ServiceNow, noted in an interview with CX Today, the problem has developed over decades of organizations building around the limitations of their original systems.

"Organizations have typically spent 20 years or more building CRM systems that were really designed to build a single view of customer and became these vast applications with huge amounts of customer data."

Over time, the original intention of CRM has also become distorted, Wilks said.

"They were intended to serve the customer, but actually we ended up with a scenario where the organizations were serving the system."

When customer-facing teams have to spend significant time maintaining records, navigating applications and working around disconnected processes, the technology can become an obstacle to delivering the experience it was introduced to support.

The architecture of traditional CRM also presents challenges for AI adoption. Many platforms were built around human data entry and structured databases, whereas AI-driven customer operations require systems that can interpret conversations, understand customer signals and trigger actions across business processes.

As Aurasell Chief Executive Officer (CEO) Jason Eubanks previously told CX Today:

"You can't expect the same level of execution and outcomes for a system that was built around a different paradigm of how software was architected."

This raises the question for CX buyers as to whether existing CRM platforms can evolve sufficiently to support these requirements, or will their underlying architecture constrain what organizations can achieve?

The Cost and Complexity of Staying Put

CRM platforms rarely operate in isolation. Over the years, businesses have connected them to billing, order management, service operations, marketing platforms and other enterprise applications, and they may also have accumulated poorly-documented custom objects, workflows and business rules.

Wilks describes the resulting environments as a "Frankenstein's monster of different applications integrated together with huge customization and cost of ownership."

Each additional layer makes migration more complicated. Buyers must establish which processes remain necessary, which integrations are redundant and which customizations support important business requirements.

There is also a financial consideration. Rafael Flores, Chief Product and Growth Officer at Treasure AI has highlighted how traditional CRM platforms can leave enterprises paying for extensive functionality they rarely use.

"You only use about 10 percent of it typically, but you pay for 100 percent of it," Flores observed in a previous CX Today discussion.

As Flores argued, the end of support for a legacy product can provide an opportunity to reassess the wider customer technology stack, including whether CRM should remain its central component.

How Legacy Systems Affect Customer Resolution

The limitations of legacy CRM are also visible in the everyday work of customer-facing teams.

Traditional platforms can provide a record of customer activity and show what has happened during an interaction. However, they may struggle to coordinate the work required to resolve a request across the wider business.

Adding AI to an existing CRM does not automatically resolve its architectural limitations.

Wilks cautions against building AI capabilities on top of disconnected systems.

"What you can't do is just apply AI on top of broken foundations."

An AI solution might understand a customer's request and recommend what an employee should do next. But if it cannot access the relevant information or trigger the necessary processes across the enterprise, the work still has to be completed manually.

Wilks identifies four connected capabilities needed to support more autonomous customer service: AI intelligence, workflow orchestration, unified data and governance.

AI provides the ability to interpret customer requests and context. Workflow capabilities enable actions across the business, while connected data supplies the information needed to make decisions. Governance determines what AI agents can access, which actions they can take and when human intervention is required.

This also means buyers need to look beyond vendor claims about AI. They should establish whether capabilities are available in working products and can demonstrate measurable results in real business processes, rather than relying on roadmaps or demonstrations.

Six Questions for CRM Buyers

Replacing legacy CRM is a significant investment, but the decision should begin with the business outcomes an organization wants to achieve.

Wilks recommends identifying specific use cases, whether improving customer experience, increasing efficiency or accelerating sales and service processes.

Drawing on the architectural and commercial challenges facing CRM buyers, six questions deserve particular attention:

  1. Can the platform keep pace with the business? Will it support changing customer expectations and new processes without extensive development or vendor intervention?

  2. Is its AI genuinely usable? Can vendors demonstrate working AI capabilities in production environments, rather than relying on product roadmaps and prototypes?

  3. Can it connect data with action? Can the platform bring together customer information across the enterprise and trigger workflows, rather than simply recording interactions?

  4. Is the data ready for AI? Are customer records accessible, accurate and governed, with appropriate permissions and controls for agent activity?

  5. Are sunk costs delaying change? How does the ongoing cost of maintaining the current environment compare with the financial and operational benefits of migration?

  6. Is CRM still the right center of gravity? Does the organization need a replacement CRM, a more connected data and engagement architecture, or a different platform model?

The last question is particularly important as businesses reassess the traditional boundaries between CRM, customer data platforms and engagement technology.

The right architecture will depend on the organization's requirements. Consolidation may make sense in some environments, while others may benefit from connecting specialist platforms around a shared data and workflow foundation.

ServiceNow aims to tackle the migration challenge with its Autonomous CRM Engine, designed to help enterprises map existing CRM environments, identify redundant processes and customizations, and deploy a redesigned environment on ServiceNow CRM.

The company says the capability can reduce deployment timelines to weeks by automating discovery and mapping, with continuous monitoring intended to identify configuration problems before they disrupt operations.

A separate customer example illustrates the potential service benefits of connecting workflows.

ReSource Point of Sale has used ServiceNow CRM to automate customer support processes, increasing monthly ticket capacity from 5,000–6,000 to more than 11,000 while reducing average resolution times from eight to ten hours to three hours.

For restaurants and retailers relying on functioning payment terminals, registers and drive-through systems, faster repairs can mean less operational downtime and lost revenue.

The Migration Decision

Legacy CRM migration will remain difficult for enterprises with years of investment and operational dependencies tied to their existing platforms. But the challenge for buyers is establishing whether their current CRM can support the next generation of customer service and whether the cost of waiting is becoming greater than the cost of migration.

rate this story
helps rank stories across CX Today

Join the conversation

Does this reflect your experience?

Ready to scale your BPO operations?

Stop reading. Start doing. Our nearshore teams deploy in 14 days β€” zero overhead, full English proficiency, U.S. legal entity.