Andrew Hanna

Andrew Hanna

Hyperforce Migration: A DevOps Checklist for Salesforce Teams

Hyperforce Migration: A DevOps Checklist for Salesforce Teams

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.

What is a Hyperforce migration?

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.

How does the Hyperforce migration process work?

  1. Notification. Users with the Modify All Data and Manage Users permissions are notified when their org is selected. There is no public schedule, and partners report notice periods of 30 to 90 days.
  2. Preparation in Hyperforce Assistant. The guided migration experience has been generally available since Winter '24 on a dedicated Setup page in production and sandbox orgs. It lists the steps to complete and scans your org code for hard-coded instance references.
  3. Eligibility. An org that does not meet the eligibility criteria has its migration deferred.
  4. Cutover. The move runs in your preferred maintenance window with an estimated three hours of downtime, during which the org is read-only. If the proposed timing clashes with a release, contact your Salesforce account team.

What should you fix before the cutover?

  1. Hard-coded instance URLs. A reference such as 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.
  2. Instanced URLs in API traffic. This work pays twice. The release update that blocks API calls to old instance hostnames is now due in Spring '27, Hyperforce or not.
  3. IP allowlists. Hyperforce can change IP addressing, so audit allowlists, endpoints and certificates in firewalls and partner systems, including middleware such as MuleSoft.
  4. HTTP version. Integrations must use HTTP/1.1. Hyperforce does not accept HTTP/1.0 requests.
  5. Authentication flows. Single sign-on, OAuth and JWT setups depend on endpoints, so test each one. Our Salesforce authentication migration guide covers the flows worth checking.
  6. A known-good backup. Capture the org state before cutover. In Serpent, the Backups view captures a known-good state, recovers supported org metadata and records, and keeps a Restore History. See backup and restore for the steps.

How do you keep your CI/CD pipeline working through Hyperforce?

The ranking guides cover the org. Few cover the pipeline that deploys to it, and that is where teams lose the day after cutover.

  • Check every pipeline login. A CI job that authenticates with --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.
  • Freeze deployments around the window. Nothing deploys while the org is read-only. Hold merges for the day before and after so a failed deploy is never confused with a migration issue.
  • Run the full regression suite straight after. Promote your nightly suite to a post-cutover gate. Our guide to what to run on every pull request and what to run nightly shows how to split it.
  • Plan for sandbox drift. Guidance differs on whether sandboxes move with production or on their own schedule, and some partners advise refreshing them after the migration. A refresh resets a sandbox to production and drops in-flight work, so back-promote anything unreleased first.
  • Reseed refreshed sandboxes. Serpent seeds sample or masked data as part of environment setup and release pipelines, so refreshed sandboxes come back populated without a manual script run. PII masking obfuscates common personal fields, which keeps production-shaped data usable while meeting GDPR and similar rules.

What should you verify after the migration?

  • Every inbound and outbound integration completes a real transaction.
  • SSO and connected app logins work for each user group.
  • Scheduled jobs, outbound email and platform event subscribers run on time.
  • A small test deployment from your pipeline succeeds end to end.

Is Hyperforce a good moment to change DevOps tooling?

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.

FAQ

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.

Related Articles

Curious about faster shipping before you dive in? Let's talk

Commitment free!