Get Ready for Your Salesforce Hyperforce Migration

By Andreea Doroftei

Compliance and service resilience are two areas that have been discussed over the past few years regardless of any specific products or industries. As a SaaS market leader, it was only a matter of time before Salesforce brought significant changes and improvements in these areas – all to offer even more possibilities for their customers. Hyperforce represents Salesforce’s unified cloud infrastructure, and a big step forward from the first-party data centers. 

In this article, we will go through the key aspects of Hyperforce and what these mean for your org, including Salesforce recommended best practices, to ensure a smooth migration.

Why Hyperforce?

Focusing on reliability and availability, Hyperforce is the next step in Salesforce’s infrastructure journey. By moving away from private data centers into a partnership with public cloud infrastructure providers like Amazon Web Services (AWS), Salesforce can ensure full compliance. They can also focus on meeting local regulations for data storage and security, while continuously investing in further enhancing the Customer 360 products and functionalities.

Source: Salesforce

Simply put, this means that customers anywhere in the world can store their valuable data according to regulations specific to their industry, geographical location, or company. Here are a few things to expect along with the migration to Hyperforce:

  • Scalability: The Hyperforce architecture is ready to grow alongside your business, processes, and users – now and in the future – to successfully live up to changing demands.
  • Security: Built with the concept of Zero Trust architecture at its core, Hyperforce includes least-privileged control and encryption of customer data at all times.
  • Data Residency: Hyperforce will provide choices and control for residency and compliance purposes, allowing you to continue operating at a global scale even faster.
  • Privacy: Be assured of permanent control mechanisms and transparency over your data, in accordance with Salesforce’s primary value: Trust.
  • Agility: While downtime may still be a necessity for org migrations or major upgrades, Hyperforce increases agility with no downtime for releases and general maintenance, faster development environments, and new interoperability through AWS.
READ MORE: Introducing Hyperforce – General Information & FAQ

Migration Timeline

While there isn’t a general timeline included in the official documentation, Salesforce users with the Modify All Data and Manage Users permissions will receive notifications in the event that their org is selected for Hyperforce migration. Below you can see an example notification, which makes it clear that the dates and the location of data storage will vary.

Additionally, while the migration will happen during preferred maintenance windows, you can reach out to your Salesforce Account Team to discuss this if the proposed timing represents a business inconvenience. Salesforce estimates that downtime for this migration is approximately three hours – during this stage, the impacted Salesforce org will be in read-only mode.

If an org does not meet the eligibility criteria for the Hyperforce migration, the migration will be deferred. Thousands of customers have already been migrated, however, the first-party data centers will be maintained in parallel during this transition.

Note that data residency for Hyperforce is not currently available in all countries, for all products. or all instances. Take a look at the list of available countries within these FAQs provided by Salesforce.

Next Steps

Regardless of where your orgs are in the Hyperforce migration process, Salesforce recommends familiarizing yourself with this infrastructure change sooner rather than later – this will ensure a smooth migration when the time comes.

Check Out the Hyperforce Migration Assistant

Generally available since Winter ‘24, the guided migration experience can be found in the dedicated Setup page in both production and sandbox orgs. There are resources available for you to find out more about the benefits Hyperforce brings to the table, as well as the key steps you should complete (or check) within your org to avoid surprises.

Review Documentation & FAQs

As you would expect when it comes to Salesforce enhancements, there are dedicated resources to help answer the most common questions and explain how the change will impact your org and your business. Don’t forget to go through the General Information & FAQs page to find out more.

Additionally, this Trailmix of Hyperforce related resources (shared at Dreamforce ‘23) will come in handy, especially as it also includes a Hyperforce Assistant demo video!


If you haven’t taken a deep dive into the Hyperforce subject before now, it’s definitely time you do so! It’s likely that, sooner rather than later, all orgs (sandboxes first followed by your production environment) will be migrated to this new infrastructure. The end goal of increasing agility and offering more data residency options, as well as delivering scalable and secure solutions on the platform, is certainly something to aim for.

Have you already migrated your orgs to Hyperforce? Share your experience in the comments below!

The Author

Andreea Doroftei

Andreea is a Salesforce Technical Instructor at Salesforce Ben. She is an 18x certified Salesforce Professional with a passion for User Experience and Automation. 


    Tom Kelleher
    December 11, 2023 6:48 pm
    A customer of mine had their Org migrated already. The impact to the Metadata API has been significant. I was told by support that there are known scaling issues. This has resulted in exponential delays in use of the api.
    Kamal Thakur
    December 12, 2023 12:11 pm
    Salesforce fails to mention in these emails how this migration can break certain things in the org. For us, our Streaming API's broke and we lost our Outbound changesets in Production. It took two Support tickets for to figure it out.
    Jonathan Sholes
    December 20, 2023 3:33 pm
    What adjustments did you need to make to your APIs?

Leave a Reply