Store configuration migration with change sets
Key Takeaway
A store migration with a change set starts with "Export" in the source org's Commerce app and ends with "Apply" in the target org's Commerce app. Deploying the change set is not the last step.
After you build and test a B2B store in one org, such as a sandbox, you can move its configuration to another org, such as production, instead of rebuilding it by hand. A change set carries the store's metadata from one org to the other. The process has four steps: export the store configuration, build an outbound change set, deploy it in the target org, and apply the store configuration there.
What a change set is
You create an outbound change set in the sending org. The receiving org sees the same change set as an inbound change set.
For a B2B store, the change set carries the store's metadata, such as descriptions, localization, pricing, and search settings. A typical path is from a sandbox to production.
A change set holds only changes you can make through the Setup menu, not data such as records. For example, you can't use a change set to upload a list of contact records.