Definition
A change set created in a Salesforce org (typically a sandbox) to send metadata components to another connected org (typically production), containing customizations like fields, objects, and classes for deployment.
Real-World Example
When an admin at Redwood Financial needs to streamline operations, they turn to Outbound Change Set to ensure the Salesforce org runs smoothly and securely. They configure Outbound Change Set during a scheduled maintenance window, test it in a sandbox first, and then deploy to production. The result is tighter security and a more streamlined experience for all 200 users in the org.
Why Outbound Change Set Matters
An Outbound Change Set is a change set created in a Salesforce org (typically a sandbox) to send metadata components to another connected org (typically production), containing customizations like fields, objects, classes, and other deployable items. The source org is where the changes were made, and the change set is the package being prepared for deployment to the target org. After the outbound change set is uploaded, it appears in the target org as an inbound change set ready for validation and deployment.
Outbound change sets are one mechanism for moving customizations between connected orgs. They're declarative, accessible to admins, and don't require developer tooling. However, change sets have limitations: they only work between connected orgs (no Git workflow), they can't include all metadata types, they don't support modern source-driven development, and they're a manual process rather than automated. Modern Salesforce DX with packages and CI/CD is more powerful but requires more setup. Change sets remain useful for simpler scenarios.
How Organizations Use Outbound Change Set
- •NovaScale — Uses outbound change sets for routine sandbox-to-production deployments where the metadata is straightforward.
- •Skyline Consulting — Helps clients evaluate when change sets are sufficient versus when they need Salesforce DX.
- •BrightEdge Solutions — Uses change sets for admin-led deployments and Salesforce DX for developer-led deployments.