Change Set

A Change Set is a Salesforce deployment tool used to send customizations and configurations from one org to another, typically from a sandbox to production. Change Sets can include components like custom objects, fields, Apex classes, Flows, page layouts, and profiles. They require a deployment connection between the source and target orgs.

A Change Set is the declarative way to move work from one Salesforce org to another - usually sandbox to production. You add components (a custom object, a Flow, a profile, a page layout) to an outbound set in the source org, send it across an established deployment connection, and then validate and deploy it in the target. There is no command line, no merge conflict, no manual file shuffling. There is also no version control, no diff, and no rollback once it lands.

Most admin teams know Change Sets as the deployment tool that works without buy-in from engineering - and as the one that breaks down once your release process gets serious. They are slow to assemble for large changes, easy to forget components on (a missing dependency surfaces only when validation fails), and hard to audit after the fact because the set itself disappears once deployed. The platform's modern answer is the Salesforce CLI, DX, and Git-based deployment, and most growing orgs eventually graduate. But Change Sets remain a fine choice for small, occasional, low-risk moves - and they are still the easiest deployment path to teach a new admin.