How does Change Set work in Salesforce?
Change Sets are the simplest way to move customizations from a sandbox to production (outbound change set) or from production to a sandbox (inbound change set). An outbound change set is assembled in the source org by selecting individual metadata components, then uploaded to a connected org (linked via deployment connections in Setup). The receiving org's admin then validates and deploys the inbound change set.
Change sets support most metadata types but have notable limitations: they cannot delete components, cannot deploy data, do not support version control or rollback, and require manual dependency management (the Add Dependencies button helps but is not comprehensive). Each change set is a one-time deployment; you cannot update and re-deploy the same change set. For these reasons, mature teams often outgrow change sets in favor of Salesforce DX with source control, the Metadata API, or DevOps tools like Copado or Gearset. However, change sets remain widely used for simple deployments, especially in smaller orgs. Clientell AI can deploy metadata changes directly via the Metadata API, bypassing change set limitations while maintaining a full audit trail.