Einstein Activity Capture: Sync Email Storage Impact

Understanding the impact of 'Sync Email as Activity' on Salesforce storage

If you look after an established org, go and check your data storage consumption. A setting inside Einstein Activity Capture may have switched itself on without anyone clicking anything, and it changes where your email data lives and what it counts against.

The change in Spring '26

Before Spring '26, the Sync Email as Activity setting inside Einstein Activity Capture was largely opt-in for existing orgs. It came on automatically for new orgs setting up EAC for the first time, but existing EAC users who had never enabled email sync were left alone. Spring '26 changed that. The setting is now enabled automatically for:

• All new orgs setting up Einstein Activity Capture.
• Existing EAC orgs that have not previously enabled email sync.

There is no prompt and no opt-in screen for existing users. Enhanced Email is no longer bundled by default, but the automatic activation of Sync Email as Activity is the part to watch.

How this affects your org's storage

With the setting enabled, every synced email is converted into an Email Message or Task record inside your org. Much of that content used to be stored off-platform, typically in AWS, where it did not touch your Salesforce data storage limits. Under the current implementation those Email Message and Task records count against your Salesforce data storage, the same as any other standard or custom object record.

Mature orgs feel this first, particularly ones with high email volume from sales or service teams. A long accumulation of email history can land in Salesforce data storage without anyone planning for it, and the allocation goes quickly from there.

Current limitations: disabling the setting

As of the Spring '26 release, once Sync Email as Activity has been auto-enabled it cannot be disabled through the Salesforce UI. Salesforce's official help documentation confirms that, and support channels have reportedly been advising customers to consider expanding their data storage. Salesforce has indicated it plans to let administrators disable the feature, but there is currently no committed release date for that.

Strategies for managing storage impact

There is no disable toggle yet, so the work is containment.

1. Verify your configuration.

   • Do not assume your org is unaffected. If it uses Einstein Activity Capture, go to Setup > Einstein Activity Capture and review the Sync Email as Activity status. Then watch your storage usage trend for a sudden increase in Email Message records, especially after the Spring '26 release.

2. Assess your email volume exposure.

   • If the setting is active, work out how much mail your teams actually generate. A low-volume org may see a negligible impact. A high-volume one can run into storage limit issues quickly.

3. Consider header-only capture.

   • It stores only the sender, recipient and timestamp, and excludes the subject line and the message body, which cuts storage consumption a long way. The trade-off is real: header-only capture may not be compatible with certain Einstein generative AI features, such as Einstein Email Insights or Agentforce drafting capabilities that rely on email context.

4. Implement deletion and cleanup policies.

   • If you have already hit the storage limit or are close to it, regular data cleanup stops being optional. Define retention policies for the Email Message and Task records you no longer need for operational or compliance purposes.

5. Plan the storage before you need it.

   • If you expect to buy additional storage or discuss archiving with Salesforce, project your usage first. Knowing your current and projected consumption makes for a better conversation than reactive purchasing does.