Salesforce's conversation-data migration brings a credit-usage question for administrators

Salesforce is directing administrators of older Einstein Conversation Insights deployments to check more than whether a migration has finished. A September 8, 2026 support notice says organizations that enabled the service before Spring 2026 are moving to the Salesforce Platform on a rolling schedule beginning in Summer 2026. The notice also flags potentially higher Data 360 credit consumption. The migration notice.

The first issue is functional. Salesforce says Vendor Transcript Processing is enabled as part of the move, and recorded calls need transcription to produce transcripts and insights. A call record can therefore exist without either of those outputs. The company directs administrators to verify that both appear after their organization's migration date.

The second issue is the frequency of work occurring behind the interface. A separate September 4 support article says nine batch data transforms supplied by the ECI Data Kit run hourly by default. Each performs a full-table scan. That amounts to 216 runs a day and can consume more credits when an organization has substantial historical transcript data.

Salesforce describes those transforms as supporting downstream functions such as Conversation Search and Sales Signals, as well as custom processes an organization has enabled. It recommends reviewing the schedule against the freshness those uses require. Reducing future runs does not refund credits already consumed, according to the same article.

This creates a concrete operating tradeoff. More frequent processing and more current downstream data are connected, but a team cannot judge the value of an hourly schedule from the fact that it is the default. It needs to know which functions use the transformed data and how quickly those functions need updates.

The two notices also imply different acceptance checks. A sales manager can see whether a conversation has a usable transcript. An administrator or budget owner has to examine whether the processing pattern fits the intended use. Passing one check does not answer the other: a functioning screen can coexist with an expensive background schedule.

The migration notice says an unsuccessful migration leaves existing ECI data and settings unaffected and directs affected organizations to support. It does not say every customer has migrated on the same date or that every account will experience an overage. The relevant population is the older ECI deployments identified in the notice.

For organizations in that group, the September documentation makes the next discussion specific: whether transcripts are appearing, which downstream data needs refreshing and what the chosen frequency costs. This is a change-management issue with observable outputs, rather than a general claim about CRM productivity.