Loading
Prepare for Email to Become the Default Login ExperienceRead More

How to Prepare for a First-Party to Hyperforce Salesforce Core Org Migration

Publish Date: Sep 11, 2026
Description
You may be in the wrong article.
This article is for Core org migrations from Salesforce-managed first-party data centers to Hyperforce.

If your org is migrating between Hyperforce instances, see What to Expect During Hyperforce Fleet Management. If your org is being relocated between Salesforce-managed first-party data centers, see Instance Refreshes and Consolidations.

If your B2C Commerce Cloud realm is migrating to Hyperforce, see B2C Commerce Hyperforce Realm Move — Pre-Move Checklist, Move Timeline, and Post-Move Verification.

--

Hyperforce is the premier Salesforce infrastructure that delivers enhanced levels of security, compliance, availability, and scalability to you. The multi-year conversion from Salesforce-managed, first-party (1P) data centers to Hyperforce is nearly complete.

Salesforce upgrades customer orgs from 1P to Hyperforce through a process called an org migration. During an org migration, your org moves from one instance to another. If you follow our best practices, this maintenance is seamless. This article answers frequently asked questions about Hyperforce-upgrade org migrations. Review the attached pre-migration and post-migration checklists to help you prepare.

For guidance in preparing for your Hyperforce upgrade, run the in-app Hyperforce Assistant. In Setup, enter “Hyperforce Assistant” in the Quick Find Box, and select Hyperforce Assistant.

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.

Helpful Resources: 

For additional questions, open a case with Customer Support via the Help & Training portal.
Resolution

General Migration and Timing


1. I received a Product & Service notification email stating my org is scheduled to migrate to Hyperforce, but I have a conflict with the date. What are my options? 
Starting July 1, 2026, Salesforce no longer defers org migrations from 1P to Hyperforce.

2. How do I prepare for the Hyperforce upgrade org migration?
Follow these guidelines to ensure that your users don’t lose access to your Salesforce org after the migration.
  • Remove hard-coded references: Review the guidance in Updating Hard-Coded References to identify and update any instance-specific URLs.
  • Review changes to IP ranges: Salesforce recommends against using IP allowlists. Instead, use the modern alternatives described in Preferred Alternatives to IP Allowlisting on Hyperforce
  • Prepare to refresh integrations: If you experience connectivity issues after the maintenance, refresh your integrations.
  • Prepare to refresh your DNS cache: If you see a “Maintenance in Progress” alert on your login page after the maintenance window has ended, refresh your DNS cache.
  • Remove certificate pinning in your mobile app and API connections. Pinning certificates on Hyperforce can cause service disruptions. For more details, see Retain uninterrupted access to Salesforce services on Hyperforce.
  • Manage Large Jobs: To ensure sufficient time for processing, avoid starting large jobs within 72 hours of the maintenance window. Bulk API jobs can fail during the migration. If this issue occurs, resubmit the jobs.
  • Run the Hyperforce Assistant. In Setup, enter “Hyperforce Assistant” in the Quick Find Box, and select Hyperforce Assistant.
  • To avoid unintended service disruptions, review the recommendations in Retain uninterrupted access to Salesforce services on Hyperforce.

Data Cloud home orgs are already on Hyperforce. Data Cloud doesn’t require any additional preparatory steps beyond the general best practices described in this article.

For more details and common questions, see Introducing Hyperforce - General Information and FAQ.
 
3.  Can I access Salesforce during an org migration to Hyperforce?
Before a migration, you receive information regarding your org’s availability during the maintenance window. Access depends on the org type:
  • Production orgs: Available in read-only mode for some or all of the maintenance window. Production orgs sometimes become active and available on the target instance before the window ends.
  • Sandbox orgs: Inaccessible for the duration of the maintenance window, as read-only mode isn't supported for sandboxes.

Password resets aren’t supported in read-only mode. For more information, review Read-Only Mode Overview.
 
4. Are sandbox refreshes impacted by org migrations?
​If an org migration occurs while a sandbox copy is in progress, the sandbox refresh fails to complete properly. To avoid this failure, don’t request a Full sandbox refresh within two weeks of the migration, and don’t initiate Developer or Developer Pro copies within one week of the migration. Restart any in-progress refreshes manually after the migration, even if the status indicates a successful completion.
 
5. Does the migration preserve the Salesforce IDs and root-relative URIs?
Yes, Salesforce IDs and root-relative URIs for records remain the same.
 
6. Do record IDs change because of an org migration?
No. Existing record IDs don’t change after an org migration.
 
7. Do my org's maintenance windows or release schedule change after the migration?
 Rarely. The release schedule and maintenance windows usually remain the same. In some situations, such as when a migration results in a time zone change, maintenance windows adjust to align with the local time. Very occasionally, a migration changes the major release cycle. In general, to find release and maintenance information, search for your instance in the Preferred Salesforce Maintenance Schedule.
 
8. What happens if the org migration encounters issues?
If an issue prevents the Salesforce Technology team from completing the org migration, the team stops the migration and reactivates your org on the source instance. Salesforce sends notifications for canceled migrations.
 
No data is removed or altered from your org on the source instance during the migration process. Because the source org remains unchanged until the target instance is active, Salesforce can cancel the migration and resume service on the source instance without customer impact. This cancellation is only possible before activation on the target instance. After the org is active on the target instance, it begins accruing new data, making a return to the source instance impossible.
 
9. Where can I go for more information on understanding how my org will be impacted during maintenance?
For more information on the impact during the update that includes weekly exports, physical delete, email threads, SSO, search ability and partner portals, see the Salesforce article on How is my org impacted during Salesforce maintenance.
 

Connectivity and Access

 
10. Are Salesforce for Outlook (SFO) OAuth tokens impacted by an org migration?
After the migration, SFO automatically logs users out and prompts them to log back in via the Setup wizard. If issues occur when logging back into SFO after the maintenance, follow the steps in Salesforce for Outlook OAuth reauthentication. Get help with SFO in the Salesforce for Outlook & Email Connect Trailblazer Community group.
 
11. What are the implications for certificate management when my org upgrades from 1P to Hyperforce?

Hyperforce Certificates
Certificate pinning isn’t supported on Hyperforce.
All Hyperforce certificates have appropriate naming, are valid, and chain to a Certificate Authority (CA) on the Mozilla Server Authentication (SSL/TLS) Root Certificates list.

Because each Hyperforce instance uses different certificates, pinned certificates from the source instance aren’t valid on the target instance after an org migration. In addition, because Hyperforce always employs SSL/TLS and regularly rotates its certificates, pinning risks outages whether or not the org is migrating.

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
Customer certificates stored with the org migrate with the org and remain unchanged.

12. Does an org migration affect OAuth tokens for OAuth clients and third-party ISV apps?
No, refresh tokens remain valid after the migration.
 
13. Does the org migration affect iOS clients?
It can. On Hyperforce, iOS clients that authenticate to Salesforce using mTLS require Salesforce Edge. Make sure to enable Edge before your upgrade.
 

Feature-Specific Impact

 
14. I use Event Monitoring. Is all event log data migrated?
Most log data migrates, however, data not processed before the migration is unavailable on the new instance. Event monitoring relies on a nightly batch process to populate monitoring events. Therefore, the system doesn’t add log data to your org during the days of the migration.

15. Does the migration change email services addresses for Email-to-Case?
No, email services addresses for Email-to-Case don’t change. They continue to include the previous org instance in the address.

16. Does an org migration affect my bots?
After a Salesforce org migration, complete these steps to make sure that your bots run as expected.
  • In Setup, make sure that the Einstein Bots preference is turned on. 
  • After enabling the preference, re-associate bots with their deployed channels, such as Chat or Messaging. 
    • NOTE: Bot session event log data and the bot session object data don’t move during the org migration.  

 17. Does an org migration affect Live Agent?
It’s possible. During an org migration, your org’s instance name changes, which affects the URL you use to access Live Agent/SOS. Salesforce-supplied chat clients and deployment code react to this change and forward HTTP requests to the new endpoint, but some third-party or custom applications, including Live Agent custom REST clients, don’t. These custom applications fail because they can't find your account on your previous instance.

To minimize impact to your Live Agent/SOS implementation, make sure that your Live Agent custom REST client properly redirects requests to the new instance of the Live Agent service after any maintenance that moves the org. The best way to avoid issues with your custom client (which doesn’t automatically direct requests to the correct endpoint) is to handle the SwitchServer response. Use the newUrl property for the request that resulted in this response and all subsequent requests. For more information on updating and testing your custom client, read How to update your Live Agent custom client when your org instance changes. This approach ensures that your custom client doesn’t encounter issues after a site switch and gives you time to update the endpoint later.

For more information about Live Agent endpoints and hard-coded Live Agent references, read Live Agent server (endpoint URL) has changed and now Live Agent Chat is no longer working.
 
18. Does Salesforce copy all data from the Dead Letter Queue for Outbound Messaging?
Most of the data will be copied over, but new rows added during and after the org migration maintenance window may not be copied to the target but will remain on the source pod.
 
19. What are the considerations for High Volume Platform Events and Change Data Capture?
Salesforce maintenance activities such as org migrations and instance refreshes move your org to a different data center or hardware stack. 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 delivery of events before or after the maintenance. However, Salesforce doesn’t retain the 72-hour retention window for events. ReplayIDs uniquely identify when an event was published. Because the new location of your org is different, ReplayID values for new events have no relation to events published before the migration or instance refresh. Review the pre- and post-migration checklist attached to this article for actions required for your platform events.
 
Subscribers of platform events and change events include Streaming API (CometD) clients, empApi Lightning components, Pub/Sub API clients, event relays, Apex triggers, and flows
 
See Also: Platform Events Developer Guide: Publishing Events in Read-Only Mode
 
20. Does upgrading to Hyperforce affect search operations?
No. When Salesforce upgrades orgs to Hyperforce, it rebuilds search data on Hyperforce before the maintenance window. This data is available as soon as the Hyperforce org activates. Search-dependent operations are unaffected, even for large orgs.
 
21. Does an org migration or instance refresh affect access to myTrailhead?
You can lose access to your enablement site (myTrailhead) after an org migration or instance refresh. To restore access, review the steps in Resolve Enablement Site (myTrailhead) Access Issues.
 
22. Does an org migration affect Opportunity Trend reports?
After an org moves to a new instance, some Opportunity Trend reports don't show all their Opportunity records. If you encounter missing data, contact Salesforce Support to populate the records.
 
23. Does an org migration affect Matching and Duplicate rules?
Salesforce deactivates Matching Rules and Duplicate Rules during an org migration.  If your matching rules are ineffective, they fail to reactivate after the org migration.  To resolve the problem, see Unable to activate matching rule that identifies duplicate records in the organization.
 

Post-Migration Verification

 
24. Does the Hyperforce upgrade affect my Own Archive managed package?
The Own from Salesforce Archived Managed Package doesn’t support IP allowlisting for orgs that are on Hyperforce.
 
If you use the Own Archive managed package, enable the Archive Use MTLS Settings setting before your Salesforce Core org migrates to Hyperforce. This setting updates the managed-package security configuration so Archive can continue to connect after the migration. For instructions, see Update Archive Security Control for Hyperforce Customers.
 
This requirement applies only to the Own Archive managed package. It doesn’t apply to Archive App or Legacy Salesforce Archive. To identify your Archive product, see Find Documentation for Archive Products.
 
25. How do I confirm that my Salesforce org successfully migrated?
Verify that your instance name reflects the new location by viewing the instance details in Company Information.
From Setup, in the Quick Find box, enter Company Information, and then select Company Information.

For more details, review View instance information for your Salesforce organization.
 
NOTE: The status.salesforce.com search tool often takes several hours to update with the correct instance for your My Domain. Use the preceding steps for immediate confirmation.

 

26. Do integrations require a restart after the maintenance?
Integration restarts aren’t required. However, if issues occur after the maintenance, restart your integrations as the first troubleshooting step. Restarting your integrations clears the DNS lookup cache, which allows the integrations to detect the IP address of the new data center.
Knowledge Article Number

000386897

Attachments

Post-Org Migration Checklist.xlsx

23 KB

Pre-Org Migration Checklist.xlsx

15 KB

 
Loading
Salesforce Help | Article