
Tekunda Team

Andrew Hanna

TL;DR: A Hyperforce migration moves your Salesforce org from Salesforce's own data centres onto its public cloud infrastructure. Salesforce runs the move itself, with roughly three hours of read-only time, but your team owns the readiness work: removing hard-coded instance URLs, updating IP allowlists, confirming integrations use HTTP/1.1, and making sure your CI/CD pipeline still authenticates and deploys afterwards.
Hyperforce is Salesforce's unified cloud infrastructure, built with public cloud providers such as AWS instead of first-party data centres. A Hyperforce migration moves your org onto a new instance on that infrastructure. Your configuration, code and data come with it. What changes is where the org runs, and anything that assumed the old location.
The programme is large. Salesforce Engineering reports processing over 95,000 org migrations from more than 15,000 requests in about a year, using an internal automation layer that checks eligibility, scheduling windows and regional capacity.
na14.salesforce.com in Apex, Visualforce, named credentials, remote
site settings or an external system stops working after the move. Replace each one
with your My Domain URL. Run the Assistant's check, then back it up with static
analysis such as PMD or Salesforce Code Analyzer.
The ranking guides cover the org. Few cover the pipeline that deploys to it, and that is where teams lose the day after cutover.
--instance-url https://na14.salesforce.com is a hard-coded reference
too, but it lives in your CI configuration, outside the org the Assistant scans.
Point every job at your My Domain URL.
Often, yes. You are already auditing logins, endpoints and pipelines, so rewiring them once beats rewiring them twice. Teams running Copado, Gearset or change sets can plan the switch in the same window. If that is you, see how migrating to Serpent works, then browse the rest of our SF Guides for the pipeline patterns that follow.
How long is the downtime during a Hyperforce migration?
Salesforce estimates about three hours, during which the org is read-only. The move runs in your preferred maintenance window.
Do I have to do anything if Salesforce migrates my org?
Yes. Salesforce moves the org, but removing hard-coded URLs, updating allowlists and testing integrations is your work.
Can I change my migration date?
If the proposed window is inconvenient, contact your Salesforce account team before the cutover.
Will my integrations break?
Only if they rely on hard-coded instance URLs, HTTP/1.0 or IP allowlists you did not update. Test each one in a sandbox first.
Commitment free!