Software and operationsOctober 30, 20262 min · updated November 7, 2026

Gartner expects AI agents to coexist with CRM and ERP systems

Daillac research

Gartner: Why AI Isn’t Replacing Enterprise Applications

Written by

Daillac

Editorial and software engineering team

Photographic illustration of a coordinator and a warehouse manager discussing operations with a tablet

In an analysis published on October 30, 2026, Gartner argues that AI agents will continue to depend on the enterprise applications holding authoritative business records. This is an analyst perspective to examine within each business, rather than a replacement timetable that applies to every smaller organization.

Gartner reports that 22% of organizations are reconsidering major systems, including CRM and ERP, compared with 51% reassessing point solutions. Those figures concern reassessment. They do not measure completed replacements or benefits achieved after migration.

Start with a workflow crossing existing tools

For a smaller business, a useful first question is where authoritative information remains. If an agent prepares an order from an email, which system confirms prices, availability and the customer account? Choosing a conversational interface does not resolve conflicting information across databases.

A custom CRM and ERP project can begin by establishing those responsibilities, even when the current system stays in place. Documented exchange rules make it easier to assess an agent connection and compare its cost with a broader application change.

In a fictional example, a distributor could ask an agent to prepare a renewal. The representative would review the draft, while the ERP would retain the commercial decision. This illustrates one possible coexistence model; it is neither a reported customer outcome nor a universal recommendation for businesses using enterprise software.

Examine the dependence created by integration

Connecting an agent to an existing application can introduce dependencies on API access, data formats, connector versions and vendor terms. When planning CRM and ERP automation, ask how staff can suspend writes and recover pending operations if the connection fails.

A reasonable pilot keeps scope limited and human review on sensitive actions. Record the work needed to prepare and correct the output so that the team can assess the workflow’s value. Having an agent participate does not establish a productivity gain, and a successful demonstration does not show how the process handles exceptions.

Before investing in a custom web application, compare a workflow connected to the current system with a targeted redesign using equivalent rules and data. The next decision should concern a specific function and the evidence needed to authorize it, including how the team would operate if the agent were unavailable.