When Einstein Activity Capture isn’t enough: Why your Salesforce reports are missing sales activity (and how to fix it)

With Salesforce’s Summer ’25 release, Einstein Activity Capture (EAC) changed in meaningful ways. But for existing orgs, the story is more complicated.

Here’s the kicker: until recently, EAC didn’t store captured emails in Salesforce at all. They lived in Einstein’s separate cloud, outside your CRM database. You could see them in a record, but they didn’t exist for reports, Tableau, automation, or APIs.

Salesforce’s Summer '25 release changed that, at least for new orgs. The new Sync Email as Salesforce Activity setting can write captured emails into Task and EmailMessage records, making them reportable.

But it doesn’t fix historical data for older orgs without special setup, it only covers email activity (not calendar events), and it forces a migration before legacy EAC reports retire in Summer '26.

So yes, the update is progress. But for most RevOps, sales ops, and quota‑carrying teams, it still leaves a reporting blind spot big enough to tank forecast accuracy, hide real pipeline effort, and turn coaching into guesswork.

That’s why we wrote this article to unpack what’s going on and what you can do about it.

The real‑world scenario: "I can see the emails, but I can't report on them"

It usually starts the same way.
A RevOps leader opens Salesforce, clicks into an account, and feels reassured, there they are. All the rep’s recent emails and meetings, neatly displayed thanks to EAC.

Then they try to build a report.
Or filter a dashboard.
Or check in Tableau.

The activity data is nowhere to be found. The emails they just saw in the record don’t exist in the reporting layer. It’s as if those customer conversations never happened.

One prospect put it bluntly: ‍

I can see the emails, but I can’t report on them. My CRO keeps asking for activity‑to‑revenue correlation, and I have nothing.

Now, Salesforce’s Summer '25 release changes this for new EAC setups, at least for email activity. If you turn on EAC today, those captured emails are stored as Salesforce records and can be reported on. 

But for anyone who’s been using EAC for years, the problem still exists until you manually enable the new sync and (if needed) migrate historical data. And even then, calendar events and other activity types remain specific.

That’s why so many teams, especially long‑time Salesforce customers, still hit the same invisible wall: activity data that’s visible to humans but invisible to the systems that need it.

What Einstein Activity Capture changed — and what it didn’t

Before Summer ’25, Einstein Activity Capture stored captured emails outside the Salesforce CRM database.

You could see the emails on a record. But they weren’t actual Task or EmailMessage records. That meant they couldn’t power reports, Flows, SOQL queries, Tableau dashboards, or downstream automation.

In other words, activity was visible — but not usable.

Summer ’25 introduced Sync Email as Salesforce Activity, which allows captured emails to be written into native Salesforce records.

That’s real progress.

But it only applies when the new setting is enabled, it doesn’t automatically fix historical data for existing orgs, and it still doesn’t address non-email activity types.

So while the storage model has evolved, the impact depends entirely on how — and when — your org implements it.

Summer '25: What Changed — and What Didn’t

Salesforce’s Summer ’25 release introduced Sync Email as Salesforce Activity, allowing captured emails to be written into native Task and EmailMessage records.

That means email activity can now power reports, Flows, SOQL queries, APIs, and Tableau — without relying on Activity 360.

But the update comes with important conditions for existing orgs:

• ‍No retroactive sync by default – Historical email data remains in Einstein unless you engage Salesforce Support. Even then, migration is limited to up to six months of past email.‍
• Manual enablement required – Older orgs must request activation or wait for a broader self-service rollout. It is not automatically turned on.‍
• Email-only coverage – The update applies to email activity. Calendar events and other activity types still follow different storage behaviors.‍
• Legacy reporting retirement – By Summer ’26, Activity 360 Reporting, Activity Metrics, and the Activities Dashboard will be deprecated. Orgs relying on them must transition before that deadline.‍
• Roadmap variability – Timelines and rollout details have shifted, meaning planning assumptions should be validated against your current org configuration.

For new EAC implementations, the path is cleaner. For existing orgs, Summer ’25 introduces a migration decision — not an automatic fix.

Closing the activity gap: How Avoma approaches it

Salesforce’s Summer ’25 update improves how email activity can be stored — but only under specific migration paths, and only for certain activity types.

Avoma takes a different approach.

1. Structured CRM storage: All captured activity is written directly into native Salesforce records. Meetings and calls are pushed into Event records. Emails are stored in Task records. The data lives in your CRM — not alongside it.

2. All activity types covered: Email is just one piece of rep effort. Avoma captures and syncs meetings, calls (recorded or unrecorded), and email activity, ensuring full visibility across the customer lifecycle.

3. Record-level ownership: Each activity is attributed to the correct Salesforce user and automatically associated with the relevant Lead, Contact, Account, and Opportunity. That makes reporting, forecasting, and rep-level performance tracking reliable.

4. Admin-level control: Calendar and email sync are centrally managed, giving RevOps and Salesforce admins governance over how activity is captured and written into CRM.

5. Historical continuity: For teams migrating or backfilling gaps, historical email sync is supported on request — helping reduce reporting disruption during transitions.

For more details, check out our help article to learn exactly how Avoma syncs data to Salesforce.

‍

EAC Summer '25 vs. Avoma: What you get

‍

What to do next: Fix your activity data blind spot

If you're already running Einstein Activity Capture, Summer ’25 doesn’t automatically resolve your reporting model.

It introduces a configuration and migration decision.

To avoid disruption before Summer ’26, most orgs will need to:

• Enable Sync Email as Salesforce Activity
• Evaluate whether historical email migration is required — and whether the six-month limit is enough
• Audit dashboards and reports that rely on Activity 360 components
• Prepare for Activity 360 Reporting, Activity Metrics, and Activities Dashboard retirement in Summer ’26
• Decide how non-email activity (calendar events, meetings, calls) will be stored and reported going forward

For a deeper breakdown of how EAC stores activity data — and why that impacts reporting — read our complete guide to Salesforce Activity Capture and reporting limitations.

If you're evaluating how to stabilize activity storage before the Summer ’26 deadline, Avoma can help you write meetings, calls, and emails directly into native Salesforce records — without phased migrations or reporting dependencies.

See how it works in your own Salesforce environment. Schedule a live demo with Avoma