When Sync Email as Salesforce Activity is enabled in Einstein Activity Capture, email data is stored directly in Salesforce as standard EmailMessage and Task records. This is a fundamental shift from the legacy Einstein Activity Capture behavior, where emails were stored on Activity Platform Hyperforce infrastructure outside the main Salesforce org. Because emails now reside in your Salesforce org, they count toward your org's standard data storage allocation.
Einstein Activity Capture synced email creates two records in Salesforce:
1 Task record — approximately 2 KB in size
1 EmailMessage record — size varies based on the actual email content (excluding attachments)
Note: Email attachments are not captured as part of the email sync, which helps limit file storage consumption.
The total storage consumed depends on the following:
Average size of emails (approximately 25 KB per email, excluding attachments)
Number of emails sent and received per user per day
Number of Einstein Activity Capture users in the org
Length of the retention period for historical email data stored in Salesforce
Use the following formula to estimate how much storage your org will consume:
(Average email size + Task wrapper) × (# emails/day) × (# Einstein Activity Capture users) × (# days retained)
Default size assumptions:
Average email size: ~25 KB (excluding attachments)
Task wrapper: ~2 KB
Combined per email: ~27 KB
Example: 100 users × 50 emails/day × 180 days retained = ~24 GB
Note: This formula is intended for self-service storage estimation purposes only — it is not an official storage guarantee. Actual consumption may vary based on email body length, threading, and org-specific configurations.
Migrated email messages don't count toward your storage quota. This exclusion applies only to migrated emails. Any new emails captured count against your storage. While migrated email message records are excluded, the accompanying task records (one per email, about 2 KB each) count toward your storage quota.
To minimize storage consumption and manage data growth:
Regularly export or delete older activity data using Salesforce public APIs.
Consider archiving email data to long-term storage solutions such as Salesforce Data Cloud.
Use header-only capture if full email body storage is not required. This option captures only the sender, recipient, subject, and date/time — without the email body — significantly reducing storage per record.
Monitor storage usage proactively in Setup > Storage Usage, especially before and after enabling this feature.
If you retain years of email data (for example, a 5-year retention policy), you can quickly accumulate significant storage volumes. We recommend developing an archiving strategy. To store large volumes of data, you must purchase additional storage.
Temporary Processing Storage
Even with Sync Email as Salesforce Activity enabled, email data is temporarily processed on Activity Platform Hyperforce infrastructure for up to 30 days for purposes such as email insights generation and matching retries. This temporary storage:
Is not accessible to admins or end users
Is automatically deleted after 30 days
Does not count toward org data storage that is on Salesforce main instance
Note: Internal emails and excluded emails (per your org's exclusion settings) are not stored in Salesforce.
005385953

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.