Loading
 Experience Cloud – Feature Degradation on Lightning Web Runtime SitesRead More
The Trailblazer Community is now read-only Read More

What to Expect During Hyperforce Fleet Management

Publish Date: Oct 7, 2026
Description
You may be in the wrong article.
This article is for Core org migrations between Hyperforce instances. If your Core org is upgrading from Salesforce managed first-party data centers to Hyperforce, see How to Prepare for a Salesforce First-Party to Hyperforce Core Org Migration.
—
To maintain infrastructure health, provide a resilient and available platform, and meet performance standards for evolving workloads, Salesforce occasionally performs scheduled maintenance called Hyperforce fleet management. This maintenance migrates your Core org from one Hyperforce instance to another.
The migration doesn’t change the org ID, but it does change the instance name. Salesforce sometimes migrates orgs to a different public cloud region.
If you consistently follow our recommended practices, this maintenance requires no preparation.
NOTE: This document is for informational purposes only, and is not part of any legal or otherwise binding agreement. The policies and practices described in this document are subject to change at Salesforce's sole discretion.
Resolution

Zero Preparation Required When Following Recommended Practices

You can ensure that Hyperforce fleet management has no additional impact on your org except for the scheduled read-only period, by consistently following Salesforce recommended practices.
  • Don’t hard-code instance references
  • Don't hard-code IP allowlists
  • Don't pin certificates

Consistently following these recommendations keeps your org continuously ready for maintenance without extra preparation, beyond readiness for the read-only period, which generally occurs during standard maintenance windows.

Recommended Practices Detail

Don’t Hard-Code Instance References

Because instance-names change during routine maintenance, Salesforce recommends that you use your My Domain login URL to access your org with code and customizations.
By using My Domain, you ensure that the instance-name change that occurs during Hyperforce fleet management doesn’t impact your org.

Don’t Hard-Code IP Allowlists

Because IPs are frequently added and changed, and can be region-specific, Salesforce recommends implementing modern alternatives such as mTLS. Read more in Preferred Alternatives to IP Allowlisting on Hyperforce.
If you allow Salesforce domains, be sure to allow all the domains in Allow the Required Domains.
For email, implement modern security methods such as TLS, SPF, DKIM, and DMARC. Read more in Email Security Mechanisms.

Don’t Pin Certificates

Pinning Hyperforce certificates isn’t supported.
Because each Hyperforce instance has unique certificates, when your org migrates to a new instance, pinned certificates from the old instance aren’t valid. In addition, because Hyperforce employs SSL/TLS and rotates its certificates regularly, pinning risks outages whether or not the org is migrating.

Custom Configurations Require Additional Preparation

Additional Preparation to Remove Hard-Coded References

Salesforce strongly advises against using hard-coded references.
Maintenance operations such as Hyperforce fleet management change the org’s instance. If your org has hard-coded references to URLs with your old instance name within integrations, email templates, knowledge articles, API calls, configurations, or customizations, then interruptions can occur when your instance name changes. For example, integrations can break, emails may contain broken links and images, and a custom domain that serves your Experience Cloud site content can stop working.
To locate and update hard-coded references, follow the instructions in Updating Hard-Coded References.

Additional Preparation for Users of IP Allowlists

Salesforce strongly advises against using hard-coded IP allowlists, including for email.
When IPs are added or changed, orgs can experience connection interruptions until allowlist databases are updated. Hyperforce fleet management sometimes moves orgs to a new region in the same country. If you constrain your IPs by region, you must add IPs for the new region before the migration, or risk losing connectivity.
By implementing modern alternatives to allowlisting, such as mTLS, you can ensure that Hyperforce fleet management doesn’t impact your org.
If you choose to use IP allowlists, it is your responsibility to establish techniques to frequently and consistently review and update them. Salesforce doesn’t guarantee notification for IP changes.
To learn more, read these articles.

Email and Sender-Policy Framework

Because Salesforce sends email from an ever-growing list of IP addresses, we recommend relying on standard email security protocols - TLS, SPF, DKIM, and DMARC - instead of IP allowlists to ensure that your org’s users receive all Salesforce emails.
If you use allowlisting for email, see Ensure You Can Receive Email from Salesforce.
Sender Policy Framework (SPF) is a simple email validation system designed to detect email spoofing. If you have specific Salesforce IP addresses listed in the SPF, prepare to change them, or include Salesforce SPF records that cover all IP ranges. See Sender Policy Framework and Salesforce SPF Records.

Additional Preparation for Users Who Pin Certificates

Pinning Hyperforce certificates isn’t supported.
If you pin certificates in the mobile app, disable the pin by following the instructions in Configure Authentication Server Certificate Pin. If you pin another way, discontinue the practice. If you must pin a certificate, create a pinset that contains the entire Mozilla Server Authentication (SSL/TLS) Root Certificates list.
Customer certificates stored with the org migrate with the org and remain unchanged.

What to Expect

Notifications

Salesforce sends a Product & Service Notification email to org admins before Hyperforce fleet management.

Behavior

During its maintenance window, Salesforce places your production or sandbox org in read-only mode. While in read-only mode, you can access your data, but you can’t make any changes. For more information, see the Read-Only Mode Overview.
After the org migration, your org ID, record IDs, Salesforce IDs, and root-relative URIs all remain the same. Only the instance name changes.

Post-Migration Maintenance

  • If you experience connectivity issues after maintenance, refresh your integrations.
  • If you see a “Maintenance in Progress” alert on your login page after the maintenance window ends, refresh your DNS cache.

Confirming Your Migration

To confirm that an org migration is complete, verify that your org has a new instance name by checking Company Information. From Setup, in the Quick Find box, enter Company Information, and then select Company Information.
Note: The status.salesforce.com search tool can take several hours to update with the correct instance for your My Domain. Use the preceding steps for immediate confirmation.

Special Considerations

What are the considerations for Live Agent custom endpoints?

During an org migration, your org's instance name changes, which alters the URL used to access Live Agent and SOS. Salesforce-supplied chat clients and deployment code automatically forward HTTP requests to the new endpoint. However, custom apps—including Live Agent custom REST clients—don't automatically redirect requests, causing these apps to fail because they can't locate your account on the previous instance.
To minimize impact to your Live Agent and SOS implementation, make sure that your custom REST client redirects requests to the new Live Agent instance after any maintenance that moves the org. To avoid issues with custom clients, handle the SwitchServer response. Use the newUrl property for the request that returned this response and for all subsequent requests. After migration, replace the Live Agent deployment code and button snippets on your sites using new code generated in Live Agent Setup, and then test Live Agent. For details on updating and testing your custom client, see How to update your Live Agent custom client when your org instance changes. This approach prevents issues after fleet management and provides time to update the endpoint later.
For more information about Live Agent endpoints and hard-coded references, see Live Agent server (endpoint URL) has changed and now Live Agent Chat is no longer working.

What steps are needed if my org uses High Volume Platform Events and Change Data Capture?

Hyperforce fleet management org migrations move your org to a different Hyperforce instance. Due to the distributed, asynchronous nature of the Event Bus, Salesforce doesn’t migrate events that were published before the org migration.
The org migration doesn’t affect real-time event delivery before or after maintenance. However, Salesforce doesn’t retain the 72-hour retention window for events. ReplayIDs uniquely identify when an event was published. Because your org is in a new location, ReplayID values for new events have no relation to events published before the migration.
Subscribers to platform events and change events include Streaming API (CometD) clients, empApi Lightning components, Pub/Sub API clients, event relays, Apex triggers, and flows.
Before the communicated migration window:
  • Pause Platform Events publishing long enough to process all pending events on the Event Bus.
  • Optionally, to retain events, retrieve them from the Event Bus using the Pub/Sub API and store them in an external system.
After maintenance:
  • Reconnect your subscriber client, and make sure that it tracks and retains new ReplayIDs.
  • After the client resubscribes to real-time events, resume event publishers.
See Also:
Platform Events Developer Guide: Publishing Events in Read-Only Mode
Platform Events Developer Guide: Enterprise Messaging Platform Events
Change Data Capture Developer Guide: Change Data Capture

How does Hyperforce fleet management affect Salesforce for Outlook (SFO)?

After migration, SFO automatically logs users out and prompts them to log back in using the Setup wizard. If issues occur when logging back in, follow the steps in Salesforce for Outlook OAuth reauthentication. To confirm connectivity after logging in, try adding an email to Salesforce from Outlook by selecting Add Email, and test Office and Offline Edition if applicable. For help with SFO, go to the Salesforce for Outlook & Email Connect Trailblazer Community group.

Are there post-migration steps for Einstein bots?

If your org uses Einstein Bots, your bots continue to function, but you may need to verify settings after Hyperforce fleet maintenance. After an org migration, complete these steps so your bots run as expected:
  • In Setup, verify that the Einstein Bots setting is turned on.
  • After turning on the setting, reconnect bots to their deployed channels, such as Chat or Messaging.
Note: Bot session event log data and bot session object data don’t move during an org migration.
Knowledge Article Number

005390954

 
Loading
Salesforce Help | Article