Change sets only move between orgs that have explicit trust. Setting up a connection is a five-minute task across both orgs, but it is a coordinated five minutes: one admin alone cannot do it.
- Identify the two orgs
Confirm both orgs are related (same production parent). Sandbox names are visible in Setup, then Sandboxes. If the orgs are not related, you cannot use Change Sets; use Salesforce CLI or a DevOps platform instead.
- Open Deployment Settings in the source org
In the source org (the one sending changes), navigate to Setup, then Quick Find, then Deployment Settings. The page lists related orgs.
- Edit the target org''s connection
Click Edit next to the target org. Check Allow Outbound Changes. Save. The source org is now willing to send change sets to the target.
- Open Deployment Settings in the target org
Switch to the target org. Same path: Setup, then Deployment Settings. Find the source org in the list.
- Enable inbound on the target
Click Edit next to the source org. Check Allow Inbound Changes. Save. The target org now accepts change sets from the source.
- Test with a small change set
In the source org, create a small outbound change set with one or two components. Upload it. Switch to the target and confirm it appears in Inbound Change Sets. Deploy as a smoke test before relying on the connection for real work.
The receiving org''s switch. When on, the org accepts change sets uploaded by orgs with outbound permission.
The sending org''s switch. When on, the org may upload change sets to the listed connected org.
Both switches on in both orgs, allowing change sets to flow either direction. Common between production and UAT.
Switches on only in one direction. Common between dev sandboxes and an upstream UAT.
- Both switches must be on for traffic to flow. A common mistake is enabling outbound in the source without confirming inbound in the target. The change set uploads but never appears in the receiving org.
- Deployment Settings has no effect on CLI or Metadata API deploys. If your team is on Salesforce DX, this page can be ignored entirely.
- A sandbox refresh can break existing connections. Re-audit Deployment Settings after any refresh, especially in production environments where downtime in the deploy pipeline is expensive.
- Production-to-production deployments require both production orgs to share a parent, which is rare. For unrelated production orgs, Change Sets are not an option; you must use the CLI, Metadata API, or a DevOps platform.