This Knowledge Article covers the Hyperforce migration of four specific Salesforce services: Sales Engagement, Einstein Activity Capture, Salesforce Inbox and Einstein Conversation Insights. These specific services are add-on productivity features for Sales Cloud or Service Cloud. They are hosted on Amazon Web Services (AWS) infrastructure, separate from the org’s Salesforce Core infrastructure. NOTE: The migration of these services is independent from the migration of the org to Hyperforce. Customers will receive separate Email Comms when their Core Org is scheduled to migrate to Hyperforce.
Today, when customers use any of these services, some customer data is stored on these AWS servers and databases behind a Virtual Private Cloud (VPC) in a private instance for Sales Engagement, Einstein Activity Capture, Salesforce Inbox and Einstein Conversation Insights services.
Hyperforce is the next-generation Salesforce infrastructure architecture, built for the public cloud. It provides Salesforce applications with compliance, security, privacy, agility, and scalability, and gives customers more choice and control over data residency. Moving to Hyperforce allows the aforementioned services to be delivered rapidly and reliably to locations worldwide in the future.
During the migration to Hyperforce, the existing productivity services and data are moved from the current AWS infrastructure to new AWS infrastructure built on Hyperforce within the same region.
If you are using any of these Salesforce services: Sales Engagement, Einstein Activity Capture, Salesforce Inbox and Einstein Conversation Insights, then yes.
No, this is a standard Infrastructure upgrade that is rolled out to all Salesforce Customers using any of these services: Sales Engagement, Einstein Activity Capture, Salesforce Inbox and Einstein Conversation Insights.
Starting in September 2023 and then in July 2024, Admins of eligible orgs will begin to receive a Product & Service Notification Email and an in-app notification banner with details about the Hyperforce migration. Note: The Hyperforce upgrade eligibility for these services is independent of whether your Salesforce Sales Cloud or Service Cloud instance is already on Hyperforce.
You’ll receive a Product & Service Notification Email and an in-app notification banner with more information. For most orgs, no action is required. For the orgs needing an action, be on the lookout for any follow-up emails that may have details specific to your org. In particular:
If your company practices allowlisting and uses Microsoft Exchange Web Services (EWS) or Office 365, you must add new, Hyperforce-specific IP addresses and/or domains to your inbound/outbound allowlists. You can find the current address lists in the Einstein Activity Capture Security Guide and the Salesforce Email Integration Security Guide.
The data for Sales Engagement, Einstein Activity Capture, Salesforce Inbox, and Einstein Conversation Insights is hosted on Hyperforce, which runs on AWS, in the United States or Germany.
For customers who onboarded these services or features before May 8, 2017, the data is stored in the United States.
For customers who provisioned these services or features for the first time on or after May 9, 2017, and unless the customer has agreed otherwise, the data is held as follows:
If the instance for Sales Cloud or Service Cloud is located in the EMEA region, Salesforce stores customer data in Germany
For all other customers, Salesforce stores customer data in the United States.
| Country | AWS Region | AWS Region Name |
| United States | us-west-2 | US West (Oregon) |
| Germany | eu-central-1 | Europe (Frankfurt) |
Some related customer data will be stored in the United States, regardless of where the customer’s Sales Cloud or Service Cloud data is located, if any of the following features are enabled:
Additional information about geographies for customer data storage for Sales Cloud and Service Cloud is available in the Infrastructure and Sub-processors documentation.
Existing users can access their Salesforce orgs with no interruption to these services. Users will not be able to connect to new data sources.
For Admins, the setup and administration of these services will be in read-only mode for up to a few hours (depending on the number of transactions in an org). Once the migration is complete, Admins can again add new users and make changes to the services.
Avoid making changes to profiles, permissions, preferences, and packaging for Sales Engagement, Einstein Activity Capture, Salesforce Inbox, and Einstein Conversation Insights during the migration period. Additionally, changes made during the migration window to Salesforce objects (such as Contact and Account) or to email addresses associated with email and calendar events could affect Activity Timeline and A360 Reporting.
Data Deletion requests made during the migration phase aren’t processed. Any deletion requests made before migration begins or after migration has completed are processed as usual.
During the migration process, emails sent via Sales Engagement, Salesforce Emails, Inbox, or Einstein Activity Capture may encounter delivery issues. Therefore, avoid sending emails using these services during the migration window. If you are missing emails after the migration, they can be recaptured. Please contact Support to re-sync your data
If you assigned profiles to the Einstein Activity Capture configurations during migration, you will need to re-assign them once the migration is complete. For example, any old or new users assigned to an Einstein Activity Capture configuration profile during the migration window will need to be re-assigned after the migration is completed.
We recommend that you avoid making changes to profiles, permissions, preferences, and packaging to these services during the migration period.
Your company’s data is stored on the Hyperforce instance located in the same region as your data was stored previously, with improved compliances.
In accordance with the MSA, we will delete redundant data from the source system after 30 days of validating that every service and data has migrated over accurately.
Review the Einstein Activity Capture Security Guide and the Salesforce Email Integration Security Guide. And, review the IP address tables to ensure that your inbound and outbound connection allowlists are up to date.
After a successful migration, the data must be refreshed on the new Hyperforce services. There may be a delay before you see some of your timeline, activity metrics, recurring events, call transcripts, call insights, engagements and email insights data.
If you don’t see your data after 24 hours, create a support case.
The emails sent during the migration window via Exchange that are not logged in the CRM to be counted twice in email metrics. This applies to all sent Exchange messages that are not logged, regardless of if email tracking is enabled. In this case, there could be a slightly elevated metrics count during your org's migration period. Note that this only applies to non-logged emails sent via Exchange; logged Exchange emails and emails sent via Google Workspace accounts are not impacted.
For orgs using Einstein Activity Capture: If your org performs more than one migration, and any events were deleted between the migrations, you may see discrepancies in Activity Metrics. These discrepancies will self-correct after 30 days.
After migration, all entries in the “My Feed” area of Sales Engagement and Inbox (such as email opens and email link clicks) will appear as unread. A blue dot will be shown next to these alerts, even for those that were previously viewed.
Engagements will be tracked as usual immediately after migration. However, Email Engagements sent before February 2024 will no longer trigger Email Open or Link Click engagements (effective Dec 1, 2024). And, Email Engagements sent prior to September 2023 will no longer trigger Reply engagements (effective Dec 1, 2024).
If changes are made to Salesforce objects (for example, Contact or Account) or to email addresses associated with email or calendar events during the migration window, you may notice data discrepancies in Activity Timeline and in A360 Reporting. If you notice a report showing a discrepancy from the source data, open a case with Support.
For more information about Hyperforce in general, see Introducing Hyperforce - General Information & FAQ.
For further details about the integration between these Salesforce services and AWS, see the Einstein Activity Capture Security Guide and the Salesforce Email Integration Security Guide.
And, for more information on security, privacy, and architecture for these services, see the Trust and Compliance Documentation.
000396064

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.