Overview
If you're migrating to Salesforce Hyperforce, understand how it affects your Riva integrations and what actions you need to take.
Salesforce Hyperforce is the company's modern cloud infrastructure. It's hosted on public clouds like AWS and Azure.
Some Riva customers have already migrated, and others are preparing to do so. This guide explains how Hyperforce affects Riva Cloud and Riva On-Premises integrations, and outlines the required actions to keep your syncs running smoothly.
What Changes for Integrations Using Static Endpoints
Salesforce Hyperforce may introduce new domains or endpoints, especially if you're using hardcoded Instance URLs for your Riva connections.
Check If You Use Static Endpoints or Hardcoded instance URLs like
After Hyperforce migration:
- These instance-based URLs may change due to a new region/instance.
If Salesforce provides you with new endpoint URLs after migration, you must update your Riva connection configuration. Contact the Riva Support Team to make these changes.
Impact on Riva Cloud
Riva Cloud continues to work normally after Hyperforce migration. No reconfiguration is required.
Expected Downtime
You may experience brief downtime only during Salesforce's migration window. When Salesforce is unavailable, Riva sync pauses automatically. Sync resumes as soon as Salesforce comes back online.
Org ID Changes
In most cases, your Salesforce Org ID remains the same after migration. However, some customers experience Org ID changes.
Is your Org ID the same after migration?
- YES → No action needed. Your Riva connection continues to work.
- NO → Follow the steps below to re-establish your connection.
If Your Org ID Changed
- In Riva, go to Salesforce Connections.
- Disconnect the existing Salesforce connection.
- Create a new Salesforce connection using your updated Org ID.
- Test the connection to confirm it works.
- If you encounter errors, contact the Riva Support Team.
Action Required
- None, unless you discover your Org ID changed or you encounter sync errors.
- If issues occur during or after migration, contact the Riva Support Team.
Impact on Riva On-Premises
After Hyperforce migration, Salesforce uses new IP addresses. If your network uses an IP allowlist (a firewall rule that only allows specific IPs), you must update it with Salesforce's new IP ranges.
Salesforce recommends switching to mTLS instead of IP allowlists. mTLS is a more secure method that doesn't require you to manage and update firewall rules whenever Salesforce changes IP addresses. Ask your network team whether mTLS is an option for your organization.
Do You Use an IP Allowlist?
Before updating firewall rules, determine whether your organization uses IP allowlists to restrict Salesforce traffic.
Check with your network or security team:
- Does your firewall have rules that only allow specific IP addresses or ranges?
- Is there a whitelist or allowlist for outbound Salesforce traffic?
- Does your organization use static IP addresses to connect to Salesforce?
Do you use an IP allowlist?
- NO → You're done. Your connection should work after migration with no additional changes.
- YES → Continue to the next section to update your firewall rules.
- UNSURE → Ask your network team. They can confirm in 5 minutes by checking your firewall configuration.
Update Your IP Allowlist
If your organization uses IP allowlists, your network team must whitelist the new Salesforce Hyperforce IP ranges on the Windows Server firewall that hosts Riva.
Salesforce publishes all IP ranges in this JSON file: All IP ranges
What to do with this file:
- Download the JSON file.
- Send it to your network or security team with this message: "Please whitelist these IP ranges on the Windows Server firewall that hosts Riva."
- Ask your team to confirm when the whitelist has been updated.
Common Errors When Connection Issues Occur
If required Salesforce traffic is blocked at the firewall level, you may see one of these errors:
On Riva Sync Log
"Connection to CRM Server failed: The underlying connection was closed. An unexpected error occurred on a send."On Riva Insights
"Connection error: There was an issue contacting Salesforce."On Salesforce Connection Test
- Timeout error indicating the server rejected the connection.
What These Errors Mean
These errors indicate the connection was blocked at the firewall level. This happens when:
- The request times out before reaching Salesforce.
- A firewall rule is missing or blocking the traffic.
- Network routing to the new Hyperforce IP addresses is not configured correctly.
How to Fix It
- Work with your network or security team to whitelist all new Salesforce Hyperforce IP ranges on the Windows Server firewall hosting Riva.
- After updating the firewall rules, test the Riva connection again in Riva settings.
- If the connection works, you're done. If issues persist, contact the Riva Support Team.
When to Contact Riva Support
Contact the Riva Support Team if you experience:
- Sync failures after migration
- Endpoint URL changes that you're unsure how to handle
- Org ID changes
- Firewall or IP allowlist issues
- Unexpected Salesforce timeout errors
```
Related to