For the most up-to-date information about products and services available on Hyperforce, see the Hyperforce Security, Privacy and Architecture (SPARC) document on the Trust and Compliance Documentation site.
Yes. Watch the Get Ready for Hyperforce YouTube playlist on the Salesforce Support YouTube channel. Additional resources include the Ask a Hyperforce Expert event series, the Hyperforce Webinar, and the Hyperforce Trailblazer Community.
No. Hyperforce runs on Amazon Web Services (AWS). Salesforce Express Connect (SEC) provides direct network connectivity only to Salesforce-operated (first-party) data centers, not to Hyperforce. Customers who need direct network connectivity to Hyperforce should contact their telecom provider for an alternative before upgrading. The recommended solution uses AWS Direct Connect (DX) with a Public Virtual Interface (VIF). See How to Access Salesforce Hyperforce Securely and Reliably with AWS Direct Connect. The AWS DX solution is in addition to SEC, not a replacement.
No. There is no additional cost associated with residing on the Hyperforce infrastructure.
Once your org is prepared for migration, it functions the same as it does today. Services not hosted on Hyperforce continue to operate as before. Note: Upgrading to Hyperforce results in a change to the compliance documentation applicable to your services. Review the Trust and Compliance Documentation for Hyperforce-specific details.
Check your org's instance name by Viewing instance information for your Salesforce Organization, then verify whether that instance is on Hyperforce as described in Where is my Salesforce instance located. For instance details including location and maintenance windows, visit my.trust.salesforce.com.
If your CRM Analytics dashboard has not been run recently, it may take time to refresh after an org migration. The time depends on the size of the data. See CRM Analytics dataflow warnings and errors for more information.
Many customers' maintenance window dates remain the same after migration. However, some customers experience a shift if: (1) the migration moves the org to a region with a different time zone, or (2) the target Hyperforce region is on a different maintenance schedule. The maintenance window for major releases on Hyperforce is 30 minutes with zero downtime. After migration, visit Salesforce Trust Site and search for your new Hyperforce instance name to see the updated maintenance schedule.
Hyperforce generates file previews as JPGs, not SVGs, regardless of account preference settings. SVGs generated before migration remain accessible. New uploads generate JPG previews. Custom implementations using SVG previews are impacted.
Why is my org migrating and when will I receive notice?
During the planned maintenance, the org is placed in read-only mode. The downtime duration is approximately 3 hours. Maintenance notifications are not posted on the Trust site during org migrations.
Yes. All Hyperforce instances accepting customer traffic are listed on Salesforce Trust site. After upgrading, subscribe to Trust notifications for your new instance. See the Trust Notification User Guide for instructions.
Each Hyperforce region is deployed across at least three separate Availability Zones (AZs). A system failure in one AZ (such as power or network failure) does not affect other AZs. Hyperforce uses standardized, automated processes to build and deploy a complete operating image — including infrastructure, operating system, applications, and configuration — defined as code. Disaster Recovery is built on this same well-validated process.
For further details, see the "Reliability, Backup, Business Continuity, and Disaster Recovery" section in the Hyperforce Security, Privacy and Architecture (SPARC) document.
For information on Hyperforce network changes and endpoint updates for SSO, OAuth, and JSON Web Tokens, review Hyperforce Techncial Considerations.
000388902

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.