Skip to main content

Handling Salesforce Org Migration (Data Center Move) for Fenergo Integration

Summary:

When a Salesforce organization is migrated by Salesforce (for example, from one data center to another), the managed packages, configurations, and settings are automatically preserved.
However, certain integration components must be refreshed to ensure continued communication between Salesforce and Fenergo (Fen-X).

Applies To

  • Clients using the Fenergo Salesforce Connector

  • Salesforce orgs undergoing infrastructure or data center migration

  • Environments integrated with Fen-X via OAuth/OpenID Connect

Background

Salesforce periodically migrates customer orgs between data centres for performance or capacity reasons.

During this migration:

  • The Salesforce org ID and configuration remain unchanged.

  • The base Salesforce domain (instance URL) may appear the same externally (e.g., my.salesforce.com),
    but the underlying callback and authentication endpoints are refreshed.

This impacts OAuth authentication and external credential mappings between Salesforce and Fenergo.

Impact

Even if the visible Salesforce instance URL does not change, the callback URL and related authentication objects (certificates, named credentials, and webhook registration) must be revalidated.

Failure to do so may cause:

  • OAuth callback mismatches

  • Expired or invalid tokens

  • Webhook communication failures

Required Actions

1. Update Callback URL (Step #8 in Integration Setup)

After migration:

  1. Go to Salesforce → Setup → Auth. Providers

  2. Select your Fenergo (Fen-X) Auth Provider.

  3. Copy the Callback URL displayed under “Salesforce Configuration.”

  4. Update this callback URL in your Fenergo Tenant Configuration (as per Step 8 of the setup guide).

⚠️ This step is mandatory even if your org URL visually looks unchanged.

2. Re-Authenticate External Credentials

Once the callback URL is updated:

  • Navigate to External Credentials → Named Credentials

  • Re-authenticate the Fenergo External Credential

    • This step ensures your Named Credential is re-authorized against the current Salesforce org context.

3. Verify Supporting Components

After re-authentication, review and revalidate:

Did this answer your question?