Loading

Impact on Salesforce Order Management, Omnichannel Inventory, and B2C Commerce SFRA Integration during an Org Migration

Publiseringsdato: Aug 6, 2026
Beskrivelse

Before You Begin

Review How to Prepare for an Org Migration first — it covers the general org-level steps. The sections below cover what is specific to Salesforce Order Management, Omnichannel Inventory, and the SFRA integration.

Løsning

Salesforce Order Management Integration

As long as the OrgId and Org URL stay the same, Salesforce Order Management does not need to be reprovisioned after the org migration — Salesforce Order Management identifies the connected org by these values, so an unchanged OrgId means the connection is preserved automatically.

If orders fail to send to Salesforce Order Management from the associated B2C instance during the migration (because the org is temporarily unavailable), they queue as failed rather than being lost. Once the org is back online, resubmit those orders manually from B2C Commerce Business Manager so they import into Salesforce Order Management.

 

Omnichannel Inventory Integration

There is no need to request a new Omnichannel Inventory service association after the migration, because Omnichannel Inventory's service association is tied to the org's identity rather than its infrastructure location.
Product availability continues to work during the instance migration, so there's no need to put the storefront into maintenance mode.

 

SFRA Self-Service Integration (Using the SFRA Order Management Plugin)

This section applies to sites using the SFRA Order Management plugin.
There is no need to request a new service association after the migration, and orders created before or during the migration remain readable throughout, since the plugin authenticates against the org identity rather than a fixed endpoint.

 

Specific Steps for Hyperforce Org Migrations

Hyperforce migrations move the org to new infrastructure, so extra care is needed to avoid dropped or duplicated orders.
Before the migration, a B2C admin should pause both the Salesforce Order Management Flows and the B2C Commerce Salesforce Order Management Integration in Business Manager.

  • Pause, don't disable, the integration. Pausing lets orders queue up in the B2C platform while paused, so nothing is lost — they send automatically once the integration is re-enabled. Disabling can drop that safety net.

After the migration completes, re-enable the  Salesforce Order Management Flows and the integration with B2C Commerce. If the B2C Commerce Salesforce Order Management Integration was not paused before migration, some orders may show a Failed status in Business Manager — these need to be manually resubmitted so they reach Salesforce Order Management. Orders already in the Sending status will be picked up automatically by the Salesforce Order Management Integration once it's active again.

Also see: Retain uninterrupted access to Salesforce services on Hyperforce

 

Example Scenario

A customer running B2C Commerce with Salesforce Order Management, Omnichannel Inventory, and the SFRA Order Management plugin is scheduled for a Hyperforce org migration over a weekend. Before the migration window, their B2C admin pauses the Salesforce Order Management Flows and B2C Commerce Salesforce Order Management Integration in Business Manager. During the migration, several orders come in and queue up in B2C rather than failing. Once the migration finishes and the org is verified, the admin re-enables the SOM Flows and integration — the queued orders send automatically, and inventory sync and SFRA order visibility resume without any re-association needed.

Knowledge-artikkelnummer

000394832

 
Laster
Salesforce Help | Article